The day you “go live” with a new organization is not the finish line; it is the starting line. The structure you have designed is a hypothesis. Whether it works depends on how you monitor it, learn from it, and refine it over time—without falling into the trap of constant, destabilizing reorgs.
This chapter focuses on sustaining and evolving the design: what to track, how to listen, when to tweak versus overhaul, how to build capabilities in leaders and HR, and how to embed continuous improvement into your operating model.
17.1 Org Health and Performance Metrics: What to Track
To know whether the new organization is working, you need a concise “instrument panel” that blends performance and organizational health.
Think in four layers:
- Business performance – Are we achieving the outcomes the design was meant to support?
- Customer and stakeholder experience – How do customers, partners, and regulators experience us now?
- Organizational health – Are clarity, leadership, and collaboration improving?
- Design-specific indicators – Are the mechanisms we changed (decisions, spans, interfaces) behaving as intended?
You do not need dozens of metrics. Focus on a small set in each category.
1. Business performance
These should mirror the value agenda you articulated early in the effort. Typical metrics include:
- Revenue growth and margin by business unit, segment, or product.
- Cost levels and productivity metrics (e.g., SG&A as a percentage of revenue, cost per transaction).
- Market share in priority segments.
- Risk and control outcomes (e.g., incidents, audit findings) where relevant.
The key is alignment: if you created segment-based BUs, you should now track performance by segment and hold segment leaders accountable.
2. Customer and stakeholder experience
Org design is often felt first by customers and external stakeholders. Track:
- NPS or equivalent satisfaction measures at the segment or account level.
- Complaint volumes and resolution times.
- Time to onboard new customers or launch new offerings.
- Feedback from key accounts, regulators, and partners in periodic dialogues.
Compare trends before and after implementation, with caution about other changes (product, pricing, macro conditions) that may confound the picture.
3. Organizational health
Use a focused set of items from your engagement or org-health surveys that are directly tied to design:
- Clarity of goals and accountabilities.
- Quality and speed of decision-making.
- Collaboration across units and functions.
- Perceived workload and sustainability.
- Trust in leadership and confidence in direction.
Where possible, view these by business unit, function, and location. The new design should not just shift pain from one part of the organization to another.
4. Design-specific indicators
Finally, create a few metrics that track whether the design levers themselves are behaving as intended. Examples:
- Decision latency for a small set of critical decisions (pricing, capital allocation, approvals).
- Number of layers and average spans of control by unit compared to your targets.
- Governance load: number of committees and average meeting hours for senior leaders.
- Use of shared services and CoEs vs local duplication (for example, share of work routed through the new platforms).
You can capture some of these quantitatively (e.g., from HR and calendar data) and others through periodic sampling.
The goal is not to create a new reporting burden but to give the leadership team a compact, repeated view:
- “Is the organization delivering the performance we expected?”
- “Is it healthy enough to sustain that performance?”
- “Are we operating roughly as we designed?”
17.2 Feedback Loops: Listening Mechanisms and Pulse Checks
Metrics tell you what is happening; feedback loops tell you why. Sustaining an organization requires systematic ways to hear from the people who live in it and from the customers who experience it.
Think in terms of three layers of listening:
- Ongoing “pulse” checks.
- Structured feedback from key roles and customers.
- Deep dives when signals suggest problems.
1. Ongoing pulse checks
Instead of relying solely on annual surveys, use short, frequent pulses:
- Quarterly or biannual micro-surveys (5–10 questions) focused on clarity, decision speed, collaboration, and workload.
- Quick pulse polls after major implementation steps (e.g., after new shared services go live or after leadership changes).
- Periodic “barometer” questions embedded in other interactions (e.g., at the end of performance reviews).
Keep pulses light and tight. Repeatedly ask the same core questions so you can see trends over time rather than chasing every new theme.
2. Structured feedback from key roles and customers
Certain groups have privileged visibility into whether the design is working:
- Front-line managers see how roles, spans, and interfaces play out day to day.
- Shared services and CoE leaders see patterns of demand and friction points with business units.
- Key-account managers hear directly from customers about experience and coordination.
- Risk and control functions see where accountability for risk is clear or muddled.
Build simple, recurring feedback mechanisms with these groups:
- Quarterly “org feedback” sections in leadership calls, dedicated to how the organization is helping or hindering delivery.
- Structured interviews or focus groups once or twice a year with front-line managers and key-account leads.
- A standing channel (digital or otherwise) where issues about structure, handoffs, and roles can be raised and triaged—not as complaints, but as input into continuous improvement.
3. Deep dives when signals suggest problems
When metrics or feedback highlight hot spots—e.g., a BU with declining health scores, a function with rising complaint volumes, or a spike in regretted attrition—do targeted deep dives rather than defaulting to another full redesign.
These deep dives can mirror a lightweight version of your original diagnosis:
- Short interviews with leaders and staff in the affected area.
- Process and decision mapping for the problematic interfaces.
- Span and workload analysis for managers in that part of the organization.
The objective is to identify whether the issue is structural, leadership-related, process-related, or some mix—and then choose the smallest effective intervention.
17.3 Periodic Org “Tune-Ups” vs. Major Redesigns
A sustainable organization treats design as a maintenance discipline, not a series of crises. The art is knowing when a “tune-up” will do and when a more fundamental redesign is warranted.
Org tune-ups
Tune-ups are small, frequent, lower-risk adjustments that keep the organization aligned with strategy and reality. Examples:
- Adjusting reporting lines for a few teams to align better with value streams or reduce spans that are too wide.
- Clarifying or revising decision rights for specific processes that remain slow or contentious.
- Consolidating or eliminating a couple of overlapping committees.
- Merging or splitting small teams to reduce role fragmentation.
- Fine-tuning shared-service scopes or SLAs based on experience.
These changes:
- Tend to be local or functional, not enterprise-wide.
- Can often be decided by BU or functional leadership, within agreed guardrails.
- Are easier to implement without major disruption, if communicated clearly.
You can institutionalize tune-ups by:
- Building a design review into your annual planning cycle: one session per unit asking, “Given our strategy and performance, do we need any structural adjustments next year?”
- Allowing BUs and functions to propose small structure changes once or twice a year, with HR and the design authority checking for cross-enterprise impact.
Major redesigns
In contrast, a major redesign is an enterprise or BU-level reset of macro-structure, roles, and governance. It is warranted when:
- Strategy has materially changed (new business model, major acquisitions, significant portfolio shifts).
- The current structure repeatedly fails, despite tune-ups, and the same patterns reappear: chronic accountability gaps, conflicting mandates, entrenched silos.
- External forces (regulation, technology, competitive disruption) have fundamentally altered how value is created and risk is managed.
You want to avoid doing major redesigns too often; they are disruptive and fatigue the organization. As a rule of thumb:
- Reserve enterprise-wide redesigns for significant strategic inflection points, not for fixing isolated performance issues or individual leaders.
- Use metrics and feedback to demonstrate that tune-ups have been tried and are not sufficient.
A simple decision guide
Once a year, ask at the top team level:
- Are the main strategic priorities still the same as when we last designed the organization?
- Are most performance and health issues now localized or systemic?
- Can we see a path to address them with targeted changes, or do we keep “bumping into” structural constraints everywhere?
If the answer is “strategy has shifted materially” or “issues are systemic and recurring,” it may be time to consider a major redesign. If not, focus on disciplined tune-ups and leadership/ process interventions.
17.4 Capability Building for Leaders and HR
A new organization will not sustain itself if leaders and HR treat design as a one-off consulting project. You need to build internal capability so that the system can adapt over time without always calling in large external teams.
Focus capability-building in three areas:
- Leaders as organizational architects.
- HR as method owner and trusted advisor.
- Managers as local designers and stewards.
1. Leaders as organizational architects
Senior leaders should grow comfortable with:
- Reading and interpreting org data: spans, layers, headcount, movement of talent.
- Understanding structural archetypes and when each is fit for purpose.
- Using design principles and decision-rights tools to make trade-offs.
- Distinguishing structural issues from leadership, strategy, or process issues.
You do not need to turn everyone into an org-design expert, but you can:
- Run short, focused sessions on the org-design playbook, using your own recent redesign as a case.
- Use live decisions (e.g., how to structure a new unit) as learning opportunities, making the reasoning explicit.
- Encourage leaders to rotate through roles where they experience different structural models (e.g., BU, function, shared service).
2. HR as method owner and trusted advisor
HR (and sometimes strategy or transformation teams) should be the custodians of the org design method:
- Maintaining and updating the internal org-design toolkit: templates, guidelines, diagnostic approaches.
- Keeping an integrated view of spans, layers, talent pools, and critical roles.
- Coaching leaders through local design decisions and tune-ups.
- Ensuring that job architecture, performance management, and talent processes stay aligned with the design.
Invest in HR capability by:
- Developing a small cadre of HR/OD specialists with deeper org-design skills.
- Giving them opportunities to co-lead design projects, not just provide data.
- Encouraging them to build external networks and stay current on practices—not for fads, but for learning.
3. Managers as local designers and stewards
Front-line and mid-level managers constantly make micro-design decisions: how to set up their teams, how to allocate responsibilities, how to run meetings and processes.
Support them with:
- Simple guides on spans, role clarity, and team design drawn from the playbook.
- Training in practical tools: stakeholder mapping, RACI/RAPID, basic process mapping, effective meeting design.
- “Org health” modules in leadership development programs so they see structure and ways of working as part of their job, not just HR’s.
Over time, this builds a culture where managers feel responsible for improving how work is organized, not only for hitting targets.
17.5 Embedding Continuous Improvement into the Operating Model
Finally, sustaining and evolving the organization means embedding continuous improvement into the way you run the business, rather than treating organization as a separate topic.
Think about embedding design and improvement at three levels:
- In business reviews and performance dialogues.
- In cross-functional forums and value streams.
- In planning and budgeting cycles.
1. Business reviews and performance dialogues
In regular business reviews:
- Include a short section on organizational effectiveness: what is helping, what is hindering, what local changes leaders are making.
- Ask leaders to bring not only numbers, but also reflection on structure and ways of working: “What org or process change did you make this quarter? What did you learn?”
- Track a small set of org health and design-specific indicators alongside P&L numbers.
This keeps organization on the agenda as part of managing the business, not as a separate HR topic.
2. Cross-functional forums and value streams
For critical value streams (customer journeys, product lifecycles, S&OP, etc.):
- Make continuous improvement an explicit objective of the cross-functional forums, not just firefighting.
- Use data from interface maps, SLAs, and customer feedback to identify small improvements in handoffs, roles, or governance.
- Encourage teams to test changes in how they collaborate—simplifying approval flows, redefining meeting cadences—and share learnings.
Over time, you can formalize this into a light kaizen-like cycle: identify issues, design small changes, test, adopt or discard, repeat.
3. Planning and budgeting cycles
Treat each annual or multi-year planning cycle as a moment to ask:
- Given our strategic priorities for next year, is our current organization still fit for purpose?
- Are there specific areas where we should invest in new capabilities, new teams, or structural experiments?
- Are there areas where we can simplify—removing obsolete units, committees, or roles?
Where changes are needed, fold them into the planning process with clear accountabilities and timelines, rather than launching ad-hoc reorgs mid-year whenever someone feels pain.
Sustaining and evolving the new organization is ultimately about discipline over drama. Instead of swinging between long periods of neglect and episodic, high-disruption reorgs, you create a rhythm:
- Clear metrics and listening mechanisms.
- Regular but modest tune-ups.
- Occasional, well-justified major redesigns when strategy truly shifts.
- Growing capabilities in leaders, HR, and managers to own and improve the system.
- Continuous improvement embedded into the operating model.
If you do this, organization design stops being a rare, traumatic event and becomes what it should be: a normal part of how you run, learn, and grow the enterprise.
