Skip to main content

How Microsoft Vanquished Bureaucracy With Agile by Steve Denning

Microsoft has rapidly rising revenues and today is the most valuable firm on the planet—worth more than a trillion dollars.
In 2004, I would never have predicted this. At the time, I was visiting Microsoft for a short consultancy. I was shocked to find how bureaucratic it was. After working for several decades in another notorious bureaucracy, I knew the problems bureaucracy caused. But Microsoft was worse: it was impossible to get decisions from within a labyrinth of silos and layers that called to mind Kafka’s The Castle.
What can other big old firms learn from Microsoft’s escape from bureaucratic strangulation?
According to The Economist, the reason for Microsoft’s turnaround is that Satya Nadella, the CEO since 2014, took the bold decisions of a heroic leader. He opted not to rely on the existing business (Windows) and chose not to be “rapacious.”
The more important lesson for most big old corporations, though, is not so much the individual decisions of a heroic leader, but rather how Microsoft as an organization overcame the disease of bureaucracy. By the time Nadella became CEO, Microsoft had already embraced Agile and was ready to implement his bold decisions.
Microsoft Agile Journey

The Decisions Of The Heroic Leader
According to The Economist, Microsoft’s triumph lies in decisions taken by Satya Nadella:
Microsoft missed social networks and smartphones because of its obsession with Windows, the operating system that was its main money-spinner. One of Mr Nadella’s most important acts after taking the helm was to de-prioritize Windows. More important, he also bet big on the “cloud”—just as firms started getting comfortable with renting computing power.”
Second, Nadella shifted away from “rapaciousness.”
Mr Nadella has changed Microsoft’s culture as well as its technological focus. The cult of Windows ordained that customers and partners be squeezed and rivals dispatched, often by questionable means, which led to the antitrust showdown… [Instead] work with regulators rather than try to outwit or overwhelm them.”
Breaking From Bureaucracy: Microsoft’s Agile Journey
The bold decisions that Nadella took were good decisions, but they would have had little effect if Microsoft had not been ready to implement them. An Agile transformation process had been underway for some years.


Popular posts from this blog

PDCA & SCRUM (or Agile); Why is it important?

The PDCA (Plan DO Check Act) cycle was made popular by Dr. W. Edwards Deming. This is a scientific cyclic process which can be used to improve the process (or product). This is cyclic in nature and usually time boxed. Plan  This is the first stage of the process. During this step the team discusses the objectives, the process and the clear conditions of exit (conditions of acceptance). This stage sets the measurable and achievable goals for the team. DO Team works together to achieve the objective set in the planning phase. Team works with the set of agreed process. Check Once the implantation is done team regroups and verifies the output and compares it to the agreed conditions of acceptance decided during the planning phase. The deviation, if any, is noted down. ACT If any deviation in planned tasks is observed during the Check stage, a root cause analysis is conducted. Team brainstorms and identifies the changes required to prevent such deviations in future. Team also

Product Backlog: Should you write everything in user story format?

I like user stories a lot. They help everyone talk the same language and results in a better product. User story alone does not constitute product requirement. User story is supposed to be a place holder for discussion which should happen between the team, Product Owner and the customer. This discussion result in a common understanding which along with the user story content is the product requirement. This format captures the essence of requirement without confusing the readers User Story is only one of the many different ways in which requirements can be represented. This is not mandatory in any Agile “process”. But many have made this mandatory. I have seen many spending countless hours trying to write the requirements in user story format when they could have easily written that in simple one-line sentence in few minutes.   I have seen team members refusing to even discuss the requirement until product owner rewrote the requirement in user story format. Once I

Why is potentially shippable product quality important

Agile teams work in iterations. During this period, they are supposed to work on product increments which can be “delivered” at the end of iteration. But how you know that the correct product was delivered? Many teams have different kinds of acceptance criteria and Definition of Done (DoD). But in many cases, this “done” is not the real “done” there might be some testing pending, some integration or review pending or anything else which prevents the actual use of the product increment. Many of these teams will need additional iterations to finish hardening their products. Many teams will implement different types of “gates” or approval steps to move to next stage. The free flow of product will be interrupted. They might end up doing mini waterfall within their agile process. Many don’t even realize this. This results in poor quality and requires additional effort to “harden” the product. Potentially Shippable Product increment The acceptance criteria and DoD should be modified