A business misses delivery dates, loses decisions between functions and relies on a few people to resolve every exception. Management responds by moving departments on the organization chart. The boxes change; the delays remain.
Organization design determines how work, authority, information and resources come together to produce an outcome. Reporting lines matter, but they are only one part of that system. A useful redesign starts with the work the strategy requires.
Translate strategy into organizational demands
Different strategies place different demands on the organization. A standardized, high-volume offer needs reliable processes and disciplined variation. A complex customer solution needs access to specialist knowledge and effective coordination across boundaries.
Most businesses need both, in different proportions. Avoid assuming that cost leadership always requires centralization or differentiation always requires decentralization. Decide which activities benefit from consistency and which decisions require local knowledge.
Write the strategic requirements in operational terms: faster configuration, repeatable installation, stronger product platforms or more responsive regional service. “Become agile” is too vague to guide a structural choice.
Identify the critical work
Map a small number of activities that create the customer outcome. Show where the work depends on another function, location or partner.
For a hypothetical equipment company, the important chain might connect application assessment, configuration, engineering release, assembly, commissioning and service readiness. A late commercial change affects all of them.
Identify which capabilities need deep functional expertise and which outcomes require end-to-end ownership. These needs can coexist. The design problem is how to connect them without making every decision an executive negotiation.
Design the operating system around the structure
Define how priorities are set, how capacity is allocated and who resolves exceptions. Specify the information required at important handoffs and the conditions for accepting work.
Then align performance measures and incentives. An engineering team rewarded only for utilization may keep starting work while downstream delivery suffers. A sales team rewarded only for bookings may promise variation that the system cannot absorb.
Technology supports these arrangements. It cannot determine the right authority or resolve conflicting objectives on its own. A new workflow tool can automate an unclear handoff just as effectively as a clear one.
Evaluate alternatives against explicit criteria
Compare options using the strategic requirements, customer outcomes, decision speed, coordination cost and risk. Include the effort of transition.
- A functional design may develop expertise efficiently but require stronger horizontal coordination.
- Divisions may bring decisions closer to markets but duplicate resources.
- A matrix may share scarce specialists while increasing negotiation.
There is no structure without tradeoffs. Make those tradeoffs visible and specify the mechanisms intended to manage them.
Test whether structure is the actual constraint
Some problems require a different grouping of work. Others require clearer priorities, better information or more capable management within the current structure.
Before launching a reorganization, trace several recent failures:
- Where did the decision stall?
- Who had the information?
- Who had authority?
- What behavior did the measures encourage?
If the same mechanism explains several failures, address it directly. A limited pilot can establish whether a new arrangement improves the work before the company commits to a broad transition.
The executive task is to maintain coherence between strategy, capabilities, authority and delivery. Start your next design discussion with one customer outcome and the work required to achieve it. Draw the reporting lines after the team understands those requirements.