Dreams and Details: Book Review

  1. The story about SAP reinvention in 2010 where they wanted to double the revenue in 5 years. The company made clear bets on cloud, database tech and mobile. To achieve the revenue target, he talks about how they challenged the 11 month implementation cycle associated with SAP. Through Agile and Design thinking, they reduced this timeframe and with cloud, they were able to achieve their vision. I liked the NASA and NOMA examples which were little extreme but hit the right chords. I also liked the Formula 1 metaphor where the rules of the sport changes every year.
  2. In the long term, the most important question for an individual or a company is not what you are but what you are becoming. This is a very powerful statement and one that I will remember forever.
  3. Dream need to be ambitious but we cannot develop a plan to achieve that dream because the plan cannot be fixed. Instead, the company need to define which capabilities are required to be developed in order for the organization to find the best possible path to the dream.
  1. The sports metaphors don’t go well with the overall narrative. Most of the time it was force fitted to illustrate a point
  2. Ambition cannot be too high they say and they also say it cannot be too low. Landing in moon is high as it can get and so, what is the right level?
  3. The framework what they presented is too exhaustive and I am wondering whether this is replicable.
  • Create a vision & communicate the vision effectively
  • Build capabilities
  • Execute relentlessly to achieve the vision

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store