Titanic : 3 lessons for a Business Analyst
Some make it big.
Some make it legendary.
Some make it an epic failure.
Titanic , the tragic ship becomes the inspiration of many books, movies , remake In 3Ds. Titanic (the movie) was the first english movie I saw chupke-chupke on cable TV, its charm has totally mesmerized me. The sinking scenes made me cry. Being a kid (I would be in 6th standard) I learned how to act at the time of crisis, how to keep updating our decisions sensing the need of the hour and how to keep your cool. (Of course , how to stand on the deck of ship *wink *wink )
I managed to watch Titanic 3D three times since it’s release and thought the learning can be extended to any domain.
Here are the 3 learning’s as a Business Analyst (BA) from Titanic.
1. Oh yeah , I know it all 🙂
The mighty and glorious Titanic was believed to be ‘unsinkable’. For that reason, it did not carry the required number of lifeboats. This was one of the biggest causes of loss of life on the ship. The belief that the ship was unsinkable ultimately led to disaster.
Lesson for BA : Your experience and knowledge (read as assumptions) are so powerful that they directly affect how you think, learn and work. When you believe something to be correct, you act in accordance with that knowledge (assumption). Ours is a world where people don’t know what they want and are willing to make us go through hell to get it. Identify, challenge, figure out loop holes and move beyond any assumptions that could ultimately spell disaster for you.
2. Overconfidence is Catastrophic
Overestimating the capability of the Titanic led the captain to make several perilous decisions. One such decision was to abandon the safety drill of lifeboat practice in lieu of a recording a faster sailing time to New York. Another such decision was to increase the speed of the ship, even though a neighboring ship had turned off their engines believing that the waters were treacherous.
Lesson for BA : Invest good amount of brain and time on effort estimation. Follow work break down structure and project plan religiously. Make the team be on same page and try to maintain a journal titled – lessons learned. Keep reviewing the status and the problems faced. No project can succeed without management support. The best sort of management support is the kind in which management doesn’t find out about the project until it’s a success.
3. Address Limitations
The creators of the Titanic feared nothing. They had built a ship that could overcome the major weaknesses in ship design that caused so many ships to sink in the past. But the ‘mathematical certainty’ did happen 😦
Lesson for BA : Being able to design workarounds we can do magic !! We can push our limits and deliver a better, more flexible, robust software product and please the customer, but still there is always a scope of ‘out of scope’ features pouring in. Be specific and clear about these, and address them well in time. Save your well toned neck 🙂 No matter how much you say it to be a demand problem, it’s a technical limitation, accept it. There is always a room for beta version or next phase of release
Source : This article is highly influenced by the original one at http://www.greatmindsinspire.com/5_Life_Long_Lessons_that_we_can_Learn_from_the_Titanic/Default.850.html
Hope you all agree with me. Have some more learning / suggestions, please drop in 🙂