From Hierarchies to High-Performance Networks: In today’s dynamic business environment, organisations can successfully transition from traditional, rigid hierarchies to more agile, flatter, and networked structures without sacrificing accountability. Organisations can achieve this transformation by thoughtfully integrating clear design patterns, robust guardrails, and careful change management practices.
The primary objective of this approach is not to eliminate structure, but to replace the outdated command‑and‑control framework with lightweight, purpose‑driven networks. These networks should facilitate transparent decision‑making, clarify budget ownership, and establish clear escalation paths. This helps organisations ensure every team member understands their roles and responsibilities within the framework.
Implementing these networked structures requires careful planning and execution. Clear design patterns enable teams to navigate their responsibilities and contributions effectively. At the same time, firm guardrails create boundaries that help maintain focus and minimise confusion. Disciplined change management practices are essential to guide teams through the transition, ensuring they adapt to new processes while maintaining alignment with the organisation’s mission and measurable outcomes.
Ultimately, this approach enables greater speed and autonomy within teams, empowering individuals to make decisions that drive results while staying aligned with the organisation’s overarching goals. By fostering collaboration and clarity, organisations can thrive in a complex, rapidly changing landscape and achieve their objectives with confidence and efficiency.
The Importance of Flattening Organisational Structures and the Risks of Poor Implementation
In many traditional organisations, hierarchical structures can significantly delay decision‑making processes. This often happens because decisions must move through multiple functional silos—such as marketing, development, and finance—before projects or products can launch. Each department may create bottlenecks as work moves up and down the chain of command, resulting in missed opportunities and reduced responsiveness to market changes.
To address these challenges, many companies are turning to networked organisational structures. These frameworks prioritise value streams and product lines over rigid functional divisions. This allows the formation of small, cross‑functional teams with end‑to‑end ownership of projects. This empowers teams to make decisions quickly without seeking approval from multiple management layers.
However, while flattening an organisation can enhance agility and innovation, it also poses significant risks if not executed thoughtfully. One major issue with a poorly implemented flat structure is confusion among team members. Without clear guardrails and guidelines, people may duplicate efforts because roles and responsibilities are unclear. Furthermore, when faced with challenging decisions, individuals may shy away from making tough calls, leading to unnecessary escalations and slower progress.
To mitigate these risks, organisations must prioritise designing frameworks that encourage both autonomy and alignment. This can be achieved by establishing explicit decision rights, so team members understand who owns which decisions. Additionally, transparent roadmaps help everyone involved see where the team is headed and what milestones must be achieved along the way. Finally, aligning budget ownership with accountability ensures that resources are allocated effectively, reinforcing the connection between financial decisions and team outcomes.
By taking these steps, organisations can reap the benefits of a flatter structure while minimising the potential pitfalls, fostering a more dynamic and responsive working environment.
Why flatten—and what breaks if you do it poorly
Traditional hierarchies slow decisions because work must climb up and down functional silos before anything ships. Networked structures fix this by organising around value streams and products, giving small cross‑functional teams end‑to‑end ownership. However, flattening without clear guardrails creates confusion: people duplicate work, avoid tough calls, or escalate everything. The solution is to design for autonomy with alignment—explicit decision rights, transparent roadmaps, and budget ownership that matches accountability.
Design Patterns that Enhance Network Scalability
Product and Platform Squads
To scale networks effectively, organisations can adopt a structure of small, long‑lived squads typically comprising 6 to 12 members. Each squad owns a specific product area or segment of the customer journey, overseeing the process from design to operation. This end‑to‑end ownership lets squads operate autonomously, reducing reliance on inter‑team handoffs and accelerating the development cycle.
Each squad is cross‑functional, integrating all necessary skills, including design, engineering, quality assurance, and operations. This holistic approach ensures that teams possess the expertise to tackle challenges within their domain without unnecessary delays. Complementing product squads, platform squads provide essential shared capabilities—such as user authentication systems, data processing pipelines, or continuous integration/continuous deployment (CI/CD) processes. Platform squads stabilise the underlying infrastructure and development processes, reducing the cognitive load on product teams. This division of labour lets product squads innovate and iterate rapidly, while platform squads focus on a robust, reliable foundation.
Guilds and Chapters for Craft and Consistency
To maintain high craftsmanship and consistency across the organisation, the company established chapters and guilds. Chapters consist of individuals sharing the same expertise—be it backend engineers, frontend developers, or UX designers—across multiple squads within a larger organisational unit known as a tribe. Each chapter is led by a Chapter Lead who acts as a line manager, responsible for coaching, recruiting new talent, evaluating performance, and upholding quality standards. This leadership structure not only promotes skill development within chapters but also helps maintain high work quality, even as individual squads begin to specialise around their product focus.
On the other hand, guilds serve as voluntary, interest‑based communities that span the entire organisation, uniting individuals with shared interests or skills who might not otherwise collaborate. Guild members come together to share best practices, organise internal conferences or knowledge‑sharing sessions, and establish lightweight standards that align with the company’s goals without imposing stringent delivery commitments. By fostering collaboration through chapters and guilds, organisations can avoid fragmentation of knowledge and practices, while still allowing squads to operate with the autonomy necessary for innovation.
Clear Decision Rights: RAPID and DACI Frameworks
To improve decision‑making, organisations adopt structured decision‑rights frameworks such as RAPID and DACI. The RAPID model stands for Recommend, Agree, Perform, Input, and Decide. This framework clarifies responsibilities by identifying who recommends actions, who must agree (often involving legal or compliance considerations), who executes the decisions, and who provides necessary input. This separation mitigates the pitfalls of protracted consensus‑seeking and ensures that accountability for decisions is clearly defined.
Alternatively, the DACI framework—comprising Driver, Approver, Contributors, and Informed—offers a more straightforward approach to decision‑making. In this model, the Driver coordinates the decision‑making process, the Approver has the authority to make the final decision, Contributors provide relevant insights or data, and the Informed are kept apprised of the outcomes. Implementing these frameworks clarifies roles and responsibilities, reducing ambiguity in cross‑functional decisions while enabling swift, informed action. By doing so, organisations not only streamline decision‑making but also strengthen accountability across cross‑functional teams.
Guardrails That Ensure Safe Autonomy
Mission Clarity
Establishing a well‑defined mission is crucial for aligning the efforts of every squad and tribe within an organisation. A clear, concise mission statement and a small set of outcome metrics empower teams to understand what success looks like. This clarity doesn’t just highlight the desired results; it also empowers teams to say no to initiatives that diverge from their objectives confidently. Furthermore, mission clarity serves as a guiding beacon for investment decisions across platforms, helping allocate resources efficiently and effectively. This prevents the common pitfall of local optimisation, where individual teams focus solely on their own goals and potentially jeopardise the broader organisational mission.
Budget Ownership
To strengthen accountability and drive results, assign budget ownership to leaders directly responsible for achieving desired outcomes—typically Tribe Leads or product owners. This approach encourages a funding model aligned with value streams rather than tethered to specific projects or initiatives. By letting budget owners allocate resources based on value, we reduce the risk of a flattening failure, where teams gain autonomy but lack the financial means to implement their ideas effectively. These budget owners are tasked with providing reports centred around outcome metrics, rather than merely tracking activities or expenditures. This focus ensures that financial resources are consistently linked to measurable results, fostering a culture of accountability and performance.
Escalation Paths
To maintain efficiency while managing potential challenges, define clear escalation paths in advance. This ensures teams know the right channels for raising issues beyond their decision‑making authority. Instead of escalating concerns to the most senior person available, escalation pathways are directed to the designated Approver or Decide role within the RAPID/DACI framework. This structure helps maintain the pace of routine decisions while ensuring critical, high‑stakes decisions are made swiftly by the right people with the necessary authority. By implementing these escalation paths, organisations can preserve agility and responsiveness in decision‑making.
Communication Rhythms That Replace Status Meetings
Skip‑Level Encounters
Regular skip‑level conversations let leaders engage directly with employees two layers down in the organisational structure. These discussions serve as a vital conduit for unfiltered feedback, giving leaders insight into challenges such as blockers, cultural friction, and innovative ideas that may not typically reach higher levels of management. This practice not only surfaces essential information but also fosters psychological safety, showing employees they can communicate directly with senior leaders without fear of reprisal. These encounters empower staff, encourage openness, and can lead to actionable insights that enhance team dynamics and organisational effectiveness.
Open Idea Channels
To nurture innovation and continuous improvement, establish open channels for idea sharing, such as internal forums, designated office hours, or a lightweight Request for Comments (RFC) process. These platforms should let anyone in the organisation propose enhancements and share suggestions freely. To ensure these ideas lead to tangible outcomes rather than becoming a collection of discussions, implement a routing system like RAPID (Recommend, Agree, Perform, Input, Decide) or DACI (Driver, Approver, Contributor, Informed) to support decision‑making. This structured approach helps the organisation maintain a steady flow of innovative ideas while avoiding a barrage of unvetted requests that may overwhelm teams and disrupt workflows.
Transparent Roadmaps
Publishing comprehensive roadmaps for teams and tribes is essential for clarifying priorities, dependencies, and expected outcomes. By making these roadmaps accessible and transparent, teams can reduce the number of coordination meetings required, as they can self‑serve the context they need to plan their work effectively around one another. Furthermore, transparent roadmaps highlight necessary trade‑offs, build trust, and sharpen team focus. Employees are better equipped to align their efforts when they clearly understand their colleagues’ work and the overall organisational objectives.
A Practical Change Plan: Pilot, Measure, Learn
Instead of overhauling the entire organisation at once, initiate change by piloting one specific value stream. Begin by redefining that stream’s organisational chart to function as a network. This involves designing cross‑functional product squads, appointing a platform enabler as necessary, and establishing chapters (for skill‑based expertise) and at least one guild (for shared learning across disciplines). Clearly delineate decision rights for the top five recurring decisions using frameworks like DACI or RAPID.
To track progress, measure key metrics such as cycle time—the duration from idea inception to production—and engagement levels, potentially through brief pulse surveys administered every two weeks. These metrics will enable continuous refinement by informing adjustments to squad sizes, decision‑making thresholds, and escalation protocols. Once the pilot is successful, the insights gained can be applied to scale the networked organisational model to other value streams.
Call to Action: Test a Networked Org Chart for Two Weeks
Select one team and transform its existing organisational chart into a network model. This involves mapping squads to their respective value streams, designating chapter leads for each discipline to share expertise, and creating a simple guild to promote collaborative learning and growth. Clearly assign decision rights for the team’s critical choices using the DACI framework, publish a two‑week roadmap outlining the team’s objectives, and establish a single outcome metric to measure success. Run the experiment over two weeks, tracking cycle times and employee engagement throughout. At the end of the trial, hold a retrospective meeting to evaluate the findings and discuss what to retain, modify, or eliminate. This focused, time‑bound test will provide concrete evidence that enables the organisation to scale a flattened structure effectively without descending into chaos.
This Post is 6/20. Tomorrow’s post will be: Ethical Leadership as an Innovation Accelerator
