Chapter 19: Organizational Structures

You lead a product organisation at a scaling technology company. Your current structure follows the standard industry playbook. You have functional silos for engineering, design, and product. Your org chart is a complex tree of directors and vice presidents. You operate with a ratio of one product manager for every five engineers. You spend most of your day in alignment meetings. You watch as your teams wait for approvals from stakeholders who are three layers removed from the customer. Your velocity has slowed as your headcount has grown. You feel the weight of coordination tax. You observe that your teams have become feature factories that produce output but lack accountability for outcomes. You face a new reality where competitors are shipping faster with significantly smaller teams. They use artificial intelligence to collapse the traditional boundaries between roles. You realize that your rigid hierarchy creates friction that your business can no longer afford. You must decide whether to protect the safety of your existing structure or to dismantle it to survive. The tension lies between the comfort of proven management layers and the metabolic speed of a flat network. You need to transition from a project-based bureaucracy to a dynamic system of autonomous builders. If you do not evolve your organisational structure now, your product will become a relic of a slower age.

CORE SKILL OR PRINCIPLE

The core principle of modern organisational design is the prioritisation of metabolic speed and extreme ownership over administrative control. You must stop building your teams around functional specialisations and start building them around mission-driven pods. This requires a shift from managing people to orchestrating task-based networks. You must adopt the local CEO model where product owners have end to end responsibility for their part of the business. You must significantly reduce your product manager headcount to force other builders to think like product owners. Success in the current era requires you to flatten your hierarchy and remove middle management layers that act as filters rather than force multipliers. You must replace rigid career ladders and traditional titles with fluid role stages that focus on scope and impact. You must move from a culture of solid lanes to a culture of dotted lines where anyone is permitted to build regardless of their functional title. You must run ultra-fast teams that prioritise shipping and learning over complex planning rituals like OKRs or granular ticket management. This approach reduces coordination costs and ensures that your best talent remains on the tools rather than in meetings.

EVIDENCE FROM THE CONVERSATION

The pod model with local CEOs is a defining characteristic of high velocity organisations like Revolut. In this model, product owners act as line managers for everyone on their team, including engineers and designers. The product owner defines what the team builds while functional managers provide guidance on how to build it with quality. This structure grants teams end to end responsibility for their products from inception to growth. Revolut maintains this flat hierarchy even at scale, with founders remaining hands-on in the details of weekly product reviews. Product owners are expected to be fully autonomous and able to demonstrate the logic behind every decision they make. This model allows the company to execute dozens of complex projects simultaneously across fifty countries without the bottleneck of central planning.

Operating with significantly fewer product managers is a proven lever for increasing speed and reducing bureaucracy. Ramp reached a run rate of one hundred million dollars in annual recurring revenue with only fifty people by forcing everyone to think like a PM. They achieved this by making product engineering, design, and data science report into the same leadership and distributing the PM workload across the entire team. OpenAI takes a similar belief that a company should be PM light to avoid filling the world with decks and ideas instead of execution. They operate with approximately twenty-five PMs for the entire organization. This forces PMs to guide teams with a light touch and leaves more decision-making responsibility with high-agency engineers. 37signals uses an even more extreme version where projects consist of only two people, one designer and one engineer, who manage their own work within a six-week cycle.

Ultra-flat structures are essential for maintaining founder-level quality at scale. Brian Chesky at Airbnb removed layers of management to return the company to a functional startup model. He believes that leaders must be in the details to know if their teams are doing a good job. Airbnb operates with a single roadmap across the entire company to ensure everyone rows in the same direction. This removal of divisions prevents the rise of politics and bureaucracy that occurs when teams become siloed. Flat structures allow the CEO to have an implicit dotted line to every employee, ensuring that the vision is executed with high fidelity.

Traditional titles and complex career ladders are frequently avoided by top-tier firms to prevent unproductive conflicts. HubSpot operated without titles for its first eighteen years to maintain a flat culture. They found that titles often act as a memetic totem that people compete for rather than focusing on impact. Coda uses five role stages from apprentice to principal instead of standard titles to keep people oriented toward their team. These role stages are not visible across the company and are used primarily for internal guidance on growth. Palantir similarly used a single title for most employees, forward deployed engineer, while only the CEO and a handful of directors held formal management titles.

The loop, not the lane, serves as the organizing principle for full stack builder teams. Claire Vo at LaunchDarkly operates with a leadership principle that there are no lanes. This gives product managers permission to pencil out designs and engineers permission to write specs. This fluid approach avoids the situation where individuals feel blocked by the absence of a specific functional partner. It breeds leaders who are technical enough to understand architectural decisions and operational enough to manage organization design. Ramp lean on their engineers to do a significant amount of product work, calling them product engineers. These engineers are responsible for announcing the features they ship rather than funneling them through a separate marketing department.

Transitioning from hierarchies to task networks allows organisations to behave like slime molds. Alex Komoroske describes a model where an organisation splits into a swarm of independent sports cars rather than a single big rig. This bottom-up autonomy allows the overall suite of products to be anti-fragile even if they appear less coherent externally. Slime mold organisations focus on autonomy and agency, allowing them to find solutions to problems that leaders did not know they were searching for. This requires the company to embrace chaos and allow fires to burn in less critical areas to focus energy on the most important bets.

Running ultra-fast teams often involves abandoning standard rituals like OKRs and Jira. Shopify avoids standard industry metrics because the moment a metric becomes a goal it loses its usefulness. They focus on taste, intuition, and the technical how rather than local conversion rates. Ramp avoids writing tickets in Linear, instead using a high-level spec and vision as the contract with engineering. Engineers are then empowered to create their own tickets and break down the work as they see fit. Twitter and other elite teams use simple Google Docs for project management instead of complex tracking software to ensure that priorities remain visible without the overhead of backlog grooming.

PRACTICAL BREAKDOWN

You must restructure your organization to eliminate the friction of functional handoffs. Start by identifying your high-agency builders who can operate across disciplines. These individuals are your full stack builders. You must provide them with the autonomy to take an idea from insight to launch without waiting for functional approvals.

Implement the local CEO model for your core product pods. Select one person to own the business outcome of each pod. This person must be the line manager for the engineers and designers in that group. They must have the authority to make all trade-off decisions between speed, quality, and scope. You must hold them accountable to results rather than their adherence to a specific process.

Drastically reduce your product manager headcount. Aim for a ratio closer to one PM for every fifteen or twenty engineers. This forces you to hire only the most senior and strategic product talent. It prevents PMs from falling into the trap of being team secretaries who spend their days writing Jira tickets and getting approvals. You must distribute the traditional PM duties such as user research and project management to your engineers and designers.

Flatten your hierarchy by removing middle management layers. No more than three layers should exist between the CEO and the individual builders. This ensures that the strategic intent of the leadership remains clear as it reaches the front lines. You must expect your senior leaders to stay in the details of the product. They must participate in code-level reviews for the most impactful projects to rebuild their technical intuition.

Abolish traditional titles and visible career levels. Replace them with internal role stages that focus on the complexity of the problems an individual can solve. For example, use a four-stage scale such as practitioner, career, principal, and master. Do not make these stages public in your corporate directory. This prevents your team from focusing on their position in the hierarchy and forces them to focus on the value they deliver to the company.

Adopt the no lanes leadership principle. Give your team permission to work outside their functional silos. Encourage engineers to write marketing copy and designers to push code. Evaluate your team members on their ability to move the product forward regardless of their job description. This fluidity is essential for maintaining velocity in a rapidly changing market.

Stop using complex project management software for your highest priority teams. Move your roadmap and task tracking into a single shared document or a simple spreadsheet. This ensures that the team spends its time building rather than managing a backlog. Abandon quarterly OKR cycles for your zero-to-one teams. Task them with shipping a marketable feature every week and use their output to determine the next set of priorities.

SKILL APPLICATION

Apply the local CEO model to your next critical product launch. Give one person the power to hire, fire, and direct the work of a cross-functional pod. Remove the requirement for them to seek consensus from functional heads. This person should be able to stand in front of the board and explain the business logic behind their roadmap.

Execute a PM light pilot project. Form a team of eight engineers and one designer with no dedicated product manager. Assign the engineering lead the responsibility for the product strategy. Ask them to write the founding hypothesis and the one-page strategic plan. Monitor the velocity of this team compared to your traditional pods. You will likely find that the lack of a PM reduces communication overhead and increases the metabolic speed of the builders.

Implement the walk the store ritual with your leadership triad. Select fifteen of your most critical user journeys. Once a week, your head of product, head of engineering, and head of design must experience these journeys exactly as a new user would. They must friction log every paper cut and janky interaction. Use these logs to set the quality bar for the entire organisation.

Manage your leadership state by becoming an IC CEO. Block out four hours every week to build something yourself using the latest AI tools. Write a functional prototype of a new feature. This hands-on work prevents you from becoming an armchair quarterback who makes decisions based on slide decks rather than reality.

Foster a culture of two-way write-ups. Replace presentations with prose documents that include sentiment tables and done reading buttons. Require every participant to read the document in silence and provide feedback within the document itself. This ensures that the best ideas surface and prevents the loudest voices from dominating the decision-making process.

Transition your management style to coaching. Spend your one-on-ones helping your team improve their craft rather than checking on their status. Use the inquiry versus advocacy framework to approach disagreements with curiosity. Ask powerful questions that unlock insight and build the capacity of your team to operate without you.

ACTION CHECKLIST

• Evaluate your current management layers and identify any group with more than three steps between the builder and the CEO.
• Select one pod to pilot the local CEO model where the product owner is the line manager for all functions.
• Conduct a headcount audit and identify how to increase your engineer-to-PM ratio by twenty percent this year.
• Block four hours on your leadership calendar for a walk the store session this week.
• Delete any recurring status meeting that can be replaced by an asynchronous document update.
• Create a draft of five internal role stages to replace your current public career ladder.
• Remove the requirement for Jira ticket writing for your most senior engineering pod for one cycle.
• Identify three high-agency builders to form a no lanes team for a zero-to-one project.
• Schedule a demo Friday where teams must show working software instead of slides.
• Set a personal SLA to unblock any organisational decision within four hours.
• Write a one-page strategy for your department that includes who you are NOT solving for.
• Conduct a pre-mortem with your team to identify the most likely reason your current structure will fail.
• Move the desks of your product trio so they sit together without physical barriers.
• Identify one task that can be fully automated by an AI agent and assign a builder to implement it.
• Recruit ten lighthouse users for your next experimental feature and create a direct communication channel with them.
• Audit your meeting schedule and cancel any recurring sync that does not focus on outcomes or problem solving.
• Define what quality means for your product using a specific rubric and share it with your team today.
• Commit to a six-week execution cycle for your next major initiative and use the circuit breaker principle.
• Ask your lead engineer to identify the most technically elegant part of the product that customers do not care about.
• Write your personal README or operating manual and share it with your direct reports.
• Commit to the nail it then scale it philosophy by refusing to add headcount to any team that has not reached level four product market fit.