Physics teaches us that mass has inertia. The greater the mass, the more force needed to change its speed or direction. Organizations follow the same law—and it’s killing them.
Every successful company starts lean and agile. Small teams, quick decisions, direct communication. But success brings growth, and growth brings mass. More employees, more layers, more processes, more committees. What was once a startup becomes a bureaucracy with its own gravitational pull.
Nokia dominated mobile phones in 2007, shipping more than half the industry’s units. They had created the world’s first smartphone back in 1996 and developed Symbian OS as an open platform for mobile devices. Success was intoxicating, but CEO Jorma Ollila sensed danger—rapid growth was killing their legendary agility.
His solution? Reorganize into a matrix structure to prevent any single division from becoming too politically powerful. The cure became worse than the disease.
The matrix immediately paralyzed decision-making. Key executives were measured on strict profit and time-to-market goals, but conflicts over resources got resolved through committee meetings and internal politics. The company began proliferating products—36 different mobile devices in 2004, another 49 in 2006.
Here’s where the technical mass became deadly: Symbian OS was deeply integrated with each device’s processor, requiring complete reengineering for every new product. What should have been modular software became a custom engineering nightmare. When leadership capped R&D spending at 10% of revenue, the technical debt became insurmountable.
Nokia’s engineers spotted Apple’s finger-touch plans in late 2005. The CEO made it a top priority, bringing it up in every executive meeting. But the matrix structure had diffused responsibility so completely that no single person had the authority and budget to abandon Symbian and build something new. By the time Nokia shipped a competitive touch device in 2009, the iPhone had redefined the entire industry.
The leadership style made everything worse. Middle managers reported feeling bullied into making promises they knew were impossible. The top executives, lacking software expertise, would set arbitrary targets without understanding technical feasibility. Anyone who questioned the targets got pushed aside. The organizational mass wasn’t just bureaucratic—it was toxic.
IBM’s story was even more spectacular. Founded in 1911, they had revolutionized computing through brilliant engineering and manufacturing. But by the 1990s, success had created a bureaucratic monster that could barely function.
Consider the absurdity: buying a small piece of equipment for a critical project required 31 signatures and an 8-week approval process. Facility managers complained that any issue would trigger meetings with 30 people showing up. The company had 128 chief information officers running 125 different data centers worldwide—the leading IT company couldn’t even manage its own technology efficiently.
Development projects collapsed under their own weight. When IBM needed an operating system for their PC project, thousands of programmers appeared to write detailed specifications in committee. The project leader, Don Estridge, learned his lesson and went outside to a small company called Microsoft for the OS instead.
Divisions became powerful fiefdoms where a single “nonconcur” could kill any innovation. Profits vanished as the downward spiral accelerated. Wall Street’s advice was brutal: break the company apart and sell the pieces.
This is the mass-inertia trap in its full horror. Nokia clung to Symbian not because it was superior, but because changing required overcoming enormous organizational inertia. IBM couldn’t innovate not because they lacked talent, but because the bureaucratic mass made any movement impossibly slow.
Your startup agility got you here. But every hire, every process, every policy adds mass to your organization. Eventually, that mass creates so much inertia that even survival instincts can’t overcome it.
How much organizational mass are you carrying? And what’s it going to take to get moving again?