One month back Flutura was in a meeting with a customer in Houston where we were involved in an IOT big data project . It was a very tense meeting ... Budgets were being slashed, heads were rolling because of the steep drop in Oil prices. The CEOs office was forensically examining all projects thru a massive magnifying glass. The tension in the room was palpable. The cross functional team had spent a lot of time building a platform and the CEO wanted to see tangible business outcomes and how it made money for them. Given the intense market pressure, if the team did not articulate an ultra specific path to monetization, the project was definitely going to be axed. After about 3 hours of intense conversation the cross functional team of Engineering and IT folks were able to hammer out a 1 slider to make the case to the CEOs office .The meeting happened a week later.The project survived. Everyone breathed a sigh of relief ....
SO WHAT DID WE LEARN FROM THE NEAR DEATH EXPERIENCE ?
The beauty about this near death experience in executing the IOT big data project ( We must admit ...It was a quite nerve wracking experience for us at Flutura as we went thru the turbulence ) was that it forced us to focus on the core . We have synthesized our learnings and we would be the first ones to admit that many of them are obvious but we felt the strong need to reinforce and internalise them.
Lesson-1 : Think Outcomes ( for example : The project would reduce fuel consumed by 3 % resulting in $ 34,000,000 savings per year in first 2 years )
Lesson-2 : Are we solving a top 5 problem which keeps business awake at night ( for example one should not be solving problem no 18 in the problem list from a business perspective ... forcibly ranking problems helps )
Lesson-3 : Is Status Quo an option ? ( One would be surprised as to how status quo is an option for many industries, businesses and processes. You may be excited about the possibilities but )
Lesson-4 : Don't use the following words while speaking to CXO team
"Analytics", "Data Science", "Algorithms", "Statistics" etc etc
"Hadoop", "Spark" , "Data Lake", "Lamba Architecture" etc etc
These are sure ways to short circuit a project as it activates the wrong neural pathways for attention starved executives
Lesson-5 : Spend 70 % of conversation in first 4-6 weeks of a big data project ontangible Business case and not solution or architecture.
These are tough times ...Markets are undergoing tectonic transition ... Industries which were immune to recession are tightening the belt.Big data and analytics has a huge role to play in driving efficiencies in many industries. The simple but obvious things evade us. We are reminded of a quote by T S Eliot
What we call the beginning is often the end. And to make an end is to make a beginning. The end is where we start from.
We hope the above learnings reinforce your experience and happy to hear your stories :)
SUBSCRIBE TO Flutura
Vivamus suscipit tortor eget felis porttitor volutpat. Praesent sapien massa, egestas non nisi.