Chapter 29: Transformation Stories

You lead a product organisation at a legacy software as a service company that has reached a significant plateau. Your annual recurring revenue is high but your growth rate has dropped below ten per cent. Your team has become bloated with layers of middle management that slow down every decision. You spend your days in alignment meetings where stakeholders argue over minor features rather than existential threats. You observe small startups shipping artificial intelligence features in days while your roadmap is locked for the next six months. You feel the weight of coordination tax where adding more people to a project only makes it move slower. You are at a crossroads where you must decide whether to protect your existing margins or to disrupt your own business model. The tension lies between the safety of your current success and the necessity of radical innovation. You face a world where the cost of building software is dropping toward zero while the value of intelligence is rising. You must either master the discipline of transformation or watch your company fade into irrelevance. Success requires you to move from a model of administrative control to a model of high context and high agency. If you do not undergo a fundamental shift in your leadership and structure you will become a relic of a slower era.

CORE SKILL OR PRINCIPLE

The core principle of successful transformation is the prioritisation of metabolic speed and radical accountability over operational stability. Transformation is not an incremental update but an act of creative destruction where you must be willing to kill your existing strategy to save the company. This requires a shift from an opinion-based development culture to an evidence-guided approach centered on first principles. You must achieve product market fit again for every new era of technology. Success depends on your ability to move up the ladder of abstraction from execution to judgment and taste. You must adopt a founder mode mindset where you stay in the details of the product while providing extreme clarity on the mission. This skill involves building isolated high velocity teams that operate without the drag of legacy processes. True transformation demands the courage to face the brutal facts of your unit economics and the humility to undergo personal change. Mastering this skill allows you to reinvent your business and your career in the face of massive disruption.

EVIDENCE FROM THE CONVERSATION

Evidence from Intercom illustrates the power of betting everything on a new technology wave. Eoghan McCabe returned to the chief executive role when the company was bloated and growth had plateaued. He observed that the strategy was diluted and the team was trying to do all things for all people. Six weeks after the release of GPT-3.5 the team had a working prototype of their artificial intelligence agent Fin. McCabe decided to go all in on artificial intelligence and ripped up the existing strategy entirely. He took an aggressive founder-first approach to remove the ego bullshit that made the leadership ineffective. This transformation required the image of the perfect brilliant leader to die to make room for truth and learning.

Further evidence from the fastest-growing products in history shows that technical advantages drive explosive growth. StackBlitz was on the verge of bankruptcy before they launched their product Bolt. They reached twenty million dollars in annual recurring revenue in two months and forty million in five months. This success was the result of seven years of foundational work on WebContainer technology. They built the actual product in ninety days by cutting corners on the interface to get online quickly. This illustrates that a deep technical moat is more powerful than surface-level polish during a transformation.

Matt Mullenweg provides a case study in turning around a social network after massive value loss. Automattic acquired Tumblr in 2019 when it was burning cash and had a bloated team of one hundred and eighty five people. Mullenweg had to replace eighty five to ninety per cent of the team to reset the culture. He moved the platform to be powered by WordPress on the back end to unlock themes and plugins for half a billion sites. This turnaround required a humbling shift in how the team managed a social network compared to a traditional software tool.

LinkedIn's transformation demonstrates how an established platform can shift to an artificial intelligence first mindset. Tomer Cohen led the shift of the LinkedIn feed from a promotional activity stream to a knowledge exchange platform. He created an internal AI Academy to train every product manager on how to build with machine learning. He carved out a randomized cohort of two million members to test a radically different experience without affecting global metrics. This secluded testing environment allowed the team to prove that a different DNA for the product could drive higher engagement.

PRACTICAL BREAKDOWN

TRANSFORMING FROM PLATEAUING SAAS TO GROWTH

You must begin your transformation by conducting a brutal audit of your current projects. Label every initiative as a brilliant basic, a bread and butter optimization, or a big bet. If you are in an existential crisis you must invest a lot less in brilliant basics to focus on breaking bad. Breaking bad means redefining your company identity to focus on a new and more urgent problem.

You must move from an imperative model to a declarative model of product development. Stop giving the computer step-by-step instructions and start describing the outcome you want. This shift allows your product to become a reasoning engine that solves whole problems for the user. You must ensure your team understands the difference between imitation learning and reinforcement learning in their product designs.

THE 10-DAY SPRINT MENTALITY

You must implement a thermal project mentality to drive extreme urgency. This involves shipping marketable features every week to maintain a high metabolic rate. You must keep the team small by starting with one person for each critical function. Avoid using complex project management software and run your initiatives with simple shared documents to reduce administrative overhead.

You must use the one-pager structure to communicate what you are building and why. This document must include a customer quote that describes how their life is different after your launch. You should ask your teams to write three divergent versions of a press release to help leadership choose the most impactful path. This forces the team to consider the trade-offs of different strategic bets before they commit code.

HOW THERAPY AND EGO DEATH SHAPE LEADERSHIP

You must recognize that your internal state is the primary constraint on your leadership. Transformation often begins with suffering and the recognition that your old patterns are no longer working. You must seek the truth behind why you are suffering by digging through your history and your relationships. This process leads to self-compassion and the removal of shame.

You must ask yourself how you are complicit in creating the conditions you say you do not want. This question shifts you from a victim mentality to a position of personal agency. You must be willing to let your image as a perfect leader die to become an effective student of your business. Use a personal board of directors to get raw feedback on your behaviors and blind spots.

ACCIDENTAL DECISIONS THAT CHANGE HISTORY

You must stay alert to the adjacent possible where one small success unlocks a massive new opportunity. Sam Schillace observed that the browser could be a platform for real apps after building Writely. This accidental realization led to the creation of Google Docs and shifted the entire category of productivity software. You must be willing to follow your curiosity into goofy or weird goals to rebuild your technical intuition.

You must manage your focus by understanding when to use your gut versus data. If you are in a completely new solution space use vibes and intuition to explore possibilities. Transition to rigorous evaluations and data-driven metrics once you have identified a core use case that works.

BUILDING IN PUBLIC ON LINKEDIN FOR GROWTH

You must view writing as a core leadership craft that creates momentum and impact. Brandon Chu used his writing to onboard new product managers and teach the culture of Shopify. When you share your insights publicly you attract people who are aligned with your values. This builds a lovable brand that resonates with people and increases word-of-mouth growth.

You must use LinkedIn as a platform for knowledge exchange rather than just self-promotion. Share your journey and what you are learning to build authentic relationships with your audience. If you are a founder you must lead the sales process to set the mindset with buyers around your new process.

SKILL APPLICATION

Apply the three eras of growth framework to your current organization. In era one you focus on survival. In era two you fight stagnation. In era three you must fight complexity above all else. Implement a rule that for every new feature added you must remove one existing dial or feature. This net zero complexity policy forces you to prioritize only the most valuable work.

Use the seasons planning framework to ground your team on secular changes in technology. Set loose quarterly goals that allow you to pivot when model capabilities change. This prevents you from being trapped in a roadmap that is no longer relevant to the market.

Operationalize your vision by using the once upon a time template to tell your story. Describe the world as it is and then paint a picture of the world as it could be. Use speeches and ceremonies at each phase of your transformation to give your team the emotional fuel they need.

Implement the associate product builder model by teaching your team to code and design using artificial intelligence. This increases their technical agency and reduces the silos between functions. You must move to a culture of working prototypes where the language of the company is code.

Manage your transformation velocity by using the 10 percent planning rule. Spend no more than one week planning for a ten-week execution cycle. This forces the team to learn through shipping rather than endless circular discussions. Use silent reading and sentiment tables in your meetings to surface the best ideas quickly.

Practice selective micromanagement on the pixels and the flows that determine the user experience. Do not delegate the hierarchy or the details of your product to people who do not share your taste. You must be the chief tastemaker who ensures that your product reflects meticulous craft at scale.

ACTION CHECKLIST

• List your current projects and label them as brilliant basics or big bets this week.
• Identify one project with a bloated team and reduce it to one person per function.
• Write a draft press release for your most ambitious big bet and include a customer quote.
• Ask yourself how you are complicit in your team's current lack of speed today.
• Block out four hours for deep thinking and hands-on building with new AI tools this Friday.
• Identify one "side quest" in your roadmap that adds more complexity than value and remove it.
• Create a shared document to replace your next recurring status meeting.
• Run a randomized cohort test for a new feature idea to get evidence without global risk.
• Write down your founding hypothesis for your transformation in one sentence.
• Record a customer interview and share a five-minute highlight reel with your builders.
• Audit your calendar and delete any meeting where you are not a driver or a braintrust.
• Set a personal service level agreement to respond to all team blockers within four hours.
• Schedule a walk the store review to experience your product as a new user would.
• Ask three customers to explain your new value proposition back to you this week.
• Define what quality means for your product using a specific rubric and share it with the team.
• Recruit ten lighthouse users for your next experimental feature and create a direct channel with them.
• Identify one high conviction low consensus bet and document the logic behind it.
• Use the note and vote technique for the next major decision in your team meeting.
• Draft your own Personal Operating Manual or README and share it with your team.
• Commit to a six-week execution cycle for your next major initiative and use a circuit breaker.
• Ask your lead engineer to identify one piece of strategic technical debt you can leverage for speed.