Skip to main content

Takeaways from Satya Nadella's Hit Refresh

source: https://www.chapters.indigo.ca/en-ca/


Like many of you, I have used Microsoft’s products for a long time. Windows was the first operating system I used. I myself started using Windows even before I knew what operating systems were. Microsoft Word, Excel and Powerpoint were the first few applications I learned to use as part of my computer literacy. Similarly MSN (those of you who still remember it) and hotmail were the first chat and email accounts I used.

However, a few years ago after numerous bad experiences with Windows Operating Systems (OS) including the infamous Windows Vista and my increasing admiration of Apple products, like the iPhone and iPod, I finally bought a Macbook Pro. Consequently I started using Apple’s productivity suite of Pages, Numbers and Keynote for my personal use. However, I still continued to rely on Windows OS and Microsoft Applications at work. This is because most of the companies I worked for continued to rely heavily on Microsoft products. Thus I continued to use Microsoft products.

But recently with the introduction of Onedrive and Office 365 I find myself re-engaging with Microsoft’s products again for my personal use and even considering purchasing a Microsoft Surface as my next personal computer. In the news, I have read a lot about Microsoft’s resurgence as their stocks soared and they reached the coveted one trillion market cap.

This motivated me to read the book, Hit Refresh by Satya Nadella, the current CEO of Microsoft. I wanted to learn more about the story behind Microsoft’s resurgence under Satya Nadella’s leadership. I just finished the book and I wanted to share three takeaways from the book.

1. Impermanence
I first came across this concept of impermanence in meditation while using the popular app called Headspace. There was an entire session dedicated to impermanence. Impermanence refers to the idea that “things change” and “nothing is permanent”. This can be tied with both success and failure. Satya Nadella used impermanence to highlight the fact that as individuals and leaders we should acknowledge the concept of impermanence in our lives. We should use our understanding of impermanence to stay humble when we acquire success and stay strong when we encounter failures. We should also use impermanence to resist our fear of failures and try new things. He reinforces that like everything else in nature failures doesn’t last and we can learn a lot from our failures. I felt he wanted to imply that this extends to an organization like Microsoft as well and I felt his belief in impermanence is ingrained in numerous strategies he discussed in the book. This included his strategies of inviting customers to Microsoft’s Executive Team retreats and showcasing Microsoft products in Apple events ( you can see the video here).

2. The three C’s 
The three C’s stands for Concept, Capability and Culture. The three C’s is typically represented as three concentric circles with Concept at the centre, Capability as the second circle and Culture as the outermost circle. Satya Nadella used the concept of three Cs to describe the importance of Capability and most importantly Culture to implement a new Concept in an organization. He explained that his concept was to implement a cloud first strategy in Microsoft. However in order to successfully implement the concept he needed to ensure that Microsoft has the capability to execute the strategy and most importantly Microsoft had the culture to adopt the strategy. He emphasized that having the right culture is most important for successfully executing a strategy. I found this a timely lesson. Currently I am in a team which is trying to adopt Agile Software Development Process and the three Cs reminds me the importance of the capability of the team to adopt the new process and most importantly the culture of the team and stakeholders to ensure the adoption is successful.

3. Growth mindset 
For me, this is one of the key takeaways from the book. Satya Nadella reiterates the concept of Growth mindset throughout his book. I felt this is tied to the concept of impermanence i.e. things are constantly changing and as individuals and organizations we need to constantly grow to adapt to the ongoing changes. Satya Nadella discusses how he took initiatives like Microsoft Hackathon to instill the importance of Growth mindset within the organization.

In conclusion Microsoft products has been a constant presence in my life since my childhood and learning the story and concepts behind Microsoft’s resurgence over the last few years has been fascinating journey.

Trending posts

Adobe Summit 2022 - Experience Platform

 Our hero image features many air balloons flying, scattered in a blue sky. Each of them has characteristics in their designs that are “part of a whole”, which in this case is an exhibition that is part of a festival. Now, let us leverage this analogy, mapping it to the elements that are relevant for this post’s agenda. Think about the pieces of data scattered through different systems, which combined (behaviour and PII data) becomes part of a whole: an enriched consumer profile that can provide you a “360 view”. This allows corporations to find opportunities, and turn them into value: “enabling ways to engage with that customer(s) to meet a cluster of business goals.” Photo by Lad Fury from Pexels   The objectives for this article are: To provide our takeaways from two (2) Adobe summit 2022 sessions, related to the Adobe Experience Platform and Real-time CDP (Customer Data Platform). Those sessions being S401 (AEP a modern foundation - by Klaasjan Tukler) and  S408 (DMP vs CDP:

Quality Assurance for mobile applications

By: Herak Quality Assurance is an important aspect of Software Development Cycle and it has become even more important with the advent of mobile applications. This is because mobile applications are typically more complex and needs to be supported across a plethora of platforms. Often the same application needs to be coded in different programming languages to support different platforms for example Objective C for iOS and Java for Android. This results in multiple code base and requires multiple streams of testing. QA also need to pay special attention to ensure that the user experience of the app remains somewhat similar across the multiple environments. Thus traditional QA practices need to evolve to adapt to the needs of the mobile app testing. In this article I am going to discuss the first two phases of QA, Preparatory Phase and Testing Phase. I will discuss how QA needs to adapt to the testing need of mobile applications and include links to resources which will help

AWS Amplify as low-code for infrastructure

Low-code development platforms are dominating many conversations lately. Many believe that low-code development platforms will account for millions of USD in revenue in the next five (5) years. An article by Forbes highlights that “ it will account for more than 65% of application development activity by 2024 ”. Some believe it will be the answer to all their development needs. Photo by Tima Miroshnichenko from Pexels  But low-code is not a new concept. The difference now is that its audience has amplified. For developers (or even advanced users) who have been in the Microsoft  ecosystem for a while have already experienced the assembly of software solutions with little effort using tools such as Microsoft Excel, Access, Visual Studio (assembling forms) and others. Putting Microsoft aside, and prior to this “low-code revolution” which has reached high altitude in the last couple of years, there have been many online veterans which allow a user to assemble simple to medium complex

Research around JIRA vs TFS

By: Carlos G.    An opportunity came from a colleague to discuss the case of company “X” for improving the ALM by introducing tools to this company. The challenge was to decide between Microsoft and Attlasian . He came to me because I’m a Microsoft kind of guy and he wanted the opinion from my perspective, not as a consultant, but as a friend of what he was trying to accomplish. He said that even though I was inclined to a technology I was able to explore other things and be “fair”. I agreed to be a part of his research because of 3 things: because of my curiosity I'm always willing to learn new techy stuff. Sometimes is good to be the dumbest one of the group. You learn so much! This was a story that I could blog about. (Of course no names are used in this post). My first impression was thinking “cool”; let’s compare Visual Studio TFS vs JIRA. Immediately I got a comment back with: “ Sure but JIRA by itself is more like an issue tracker in simple terms ”. That sa

This blog uses cookies to improve your browsing experience. Simple analytics might be in place for pageviews purposes. They are harmless and never personally identify you.

Agreed