Organization design can expand into months of debate about titles and reporting lines. A focused 90-day effort should instead establish the problem, test a coherent response and create evidence for the next decision.
Ninety days may be enough for a bounded pilot. It is not a universal deadline for completing a major reorganization. Scale the plan to the complexity and consequences of the change.
Days 1 to 15: diagnose the work
Select a significant customer or business outcome that the current organization struggles to deliver. Define the baseline and the limits of the investigation.
Trace recent cases through roles, decisions, information and handoffs. Include successful cases as well as failures so that the team understands which existing strengths to preserve.
In a hypothetical project business, engineering capacity is repeatedly reassigned after customer dates are committed. The diagnostic should examine demand, authority and priority changes rather than assume that another management layer is required.
End the phase with a clear problem statement, evidence and a short list of competing explanations.
Days 16 to 30: develop and compare design options
Translate strategy into design criteria. These might include specialist development, delivery ownership, local responsiveness or platform reuse.
Compare options for grouping work, delegating authority and coordinating dependencies. Include a credible option that improves the current structure without changing reporting lines.
Specify the required roles, decision rights, interfaces, information and measures for each option. Identify capability gaps and transition risks.
Select the option that best addresses the evidence, and record its tradeoffs. Executive preference should be explicit rather than hidden inside an apparently objective score.
Days 31 to 45: prepare a bounded pilot
Choose a scope large enough to test the mechanism but small enough to manage the consequences.
For the project business, the pilot might cover capacity allocation across one set of projects. Functional leaders retain capability ownership while a defined portfolio process controls commitments.
Prepare role mandates, a common capacity view, decision rules and escalation. Train participants and rehearse difficult cases.
Confirm the baseline, success criteria and conditions that would require a pause or redesign. Maintain clear accountability for ongoing customer work.
Days 46 to 75: operate and learn
Use the new arrangement on real work. Observe where people revert to old channels, where rules are unclear and where the design creates additional effort.
Resolve implementation defects quickly, but avoid changing every principle after one uncomfortable case. Distinguish a capability issue from an incorrect authority boundary or a genuinely different business requirement.
Record decisions, exceptions and consequences. Give employees a route to raise problems without having to defend the entire previous organization.
Days 76 to 90: evaluate and decide
Compare outcomes with the baseline and the original design hypothesis. Examine decision time, delivery, quality, workload and the capability needed to sustain the result.
Decide whether to extend, revise or stop the pilot. Document remaining uncertainty and the conditions for the next stage.
If scaling is justified, prepare the transition, ownership of open work, training and review cadence. Confirm that supporting systems and incentives can follow the change.
The executive contribution is to keep strategy, authority, resources and behavior coherent. Organization design becomes useful when the people doing the work can make better decisions and deliver more reliably.