The Reality Check
Worldwide spending on digital transformation is forecast to reach almost $4 trillion by 2027, but most organizations struggle to realize business value and sustainable change. The gap between technology’s potential and organizational reality grows wider each day.
Martec’s Law, formulated by Scott Brinker, illustrates this fundamental challenge: Technology changes at an exponential rate, constantly accelerating as innovations build upon each other, while organizations change at a slower, logarithmic rate due to human, cultural, and institutional constraints. Leaders face mounting pressure as operational capabilities fall behind technological possibilities.
The root problem isn’t technology—it’s how organizations operate. Bureaucracy, inertia, and fragmented approaches prevent companies from turning potential into progress. How can leaders build organizations that adapt to new technology?
A Framework for Continuous Change
I’ve identified three practices that separate companies that transform successfully from those that fail:
- Elevate operations to create space for growth.
- Energize people to take ownership and learn.
- Envision goals that connect technology to business results.
Elevate
Operations improve when companies eliminate waste and simplify decisions. By reducing friction—replacing controls with guidelines, creating autonomous teams, and minimizing dependencies—organizations free up resources previously spent on administration and coordination. This not only reduces costs but creates capacity for strategic growth initiatives.
Free resources from IT costs with a systematic reinvestment approach. Give teams visibility into spending, authority to reinvest savings into things they deem important, and tools to optimize their technology portfolio. (https://aws.amazon.com/blogs/enterprise-strategy/it-money-matters-four-methods-to-unlock-investment-capacity)
Use automated guardrails to balance central guidance with team freedom. Provide structure without creating bottlenecks. When uncertain, favor team autonomy. (https://aws.amazon.com/blogs/enterprise-strategy/centralize-or-decentralize/)
Replace vague values with specific principles that guide daily decisions. Create standards on how work happens and help teams move quickly. (https://aws.amazon.com/blogs/enterprise-strategy/from-empty-values-to-working-principles-a-leaders-guide/)
Connect technical work to business results with metrics that matter. Focus on customer value, speed, reliability, and team health instead of activity metrics. (https://aws.amazon.com/blogs/enterprise-strategy/a-ctos-guide-to-measuring-software-development-productivity/)
Energize
Innovation emerges when employees connect their work to desired outcomes. Organizations succeed by hiring curious workers, investing in education, and focusing on customer value. By hiring curious workers they create the conditions for problem-solving. Investing in both technical and business education prepares teams for adapting to new challenges. Focusing on customer value ensures innovation delivers real impact. At AWS, we see that companies that excel in these areas lead innovation in their markets and navigate transformations more effectively.
Start an autonomous team (Two-Pizza Team) by selecting the right challenge and connecting it to business goals. Begin small, secure leadership support, and build its capabilities methodically. (https://aws.amazon.com/blogs/enterprise-strategy/breaking-through-bureaucracy-a-leaders-guide-to-establishing-your-first-autonomous-team/)
Improve feedback. Move beyond annual reviews to create a culture where people want to improve daily. (https://aws.amazon.com/blogs/enterprise-strategy/the-feedback-fix-how-to-fuel-a-learning-culture/)
Use gamification to make digital adoption engaging. Tap into people’s natural motivations to learn new tools and approaches without mandates. (https://aws.amazon.com/blogs/enterprise-strategy/gamifying-digital-transformation-drive-adoption-through-engagement/)
Envision
Many organizations consider technology without applying it to business challenges. Leaders need to set clear goals, view the cloud as a business tool rather than infrastructure, run experiments tied to outcomes, and turn constraints into creative starting points.
Learn what ITIL gets wrong about connecting IT to business value. Avoid process-centered thinking that separates technical teams from customers. (https://aws.amazon.com/blogs/enterprise-strategy/how-itil-changed-it-in-sometimes-painful-ways/)
Complete one thing before starting another to deliver value sooner. Focus teams on finishing current work instead of splitting attention across multiple projects. (https://aws.amazon.com/blogs/enterprise-strategy/deliver-faster-by-limiting-work-in-progress/)
Moving Forward
The organizations that use these practices don’t just respond to change—they create it.