When decisions take too long, a new organization chart can look like the obvious answer. Sometimes a structural change is needed. But the chart alone does not explain how a decision moves through the business, who contributes to it or why it becomes stuck.
A useful starting point is a small number of decisions that matter. These might concern customer commitments, expenditure, staffing or the introduction of a new process. Follow each decision from the moment it arises to the point at which someone acts on it.
Ask who is expected to decide, whose input is needed and who can delay the outcome. Examine the information available at each stage. A decision may appear to require senior attention because the responsibility has never been made explicit, because a team lacks confidence in its information or because several functions are working to different priorities.
Those are different problems. Moving a role between reporting lines may resolve one and leave another untouched. An effective design therefore connects the structure with decision rights, information, skills and the working routines through which people coordinate.
The next step is to test the proposed change on real work. Clarify one recurring decision, agree the inputs and responsibilities, and observe what happens. Does the decision become faster? Is its quality maintained? Are exceptions visible? Do the people involved understand what has changed?
The findings can inform a wider redesign. They also provide a practical way to involve managers and teams in the work, using a problem they recognize rather than an abstract picture of a future organization.
An organization chart remains useful. Its value increases when it describes an operating arrangement that people can understand and apply. The question to ask first is which decisions the business needs to make well, and what currently prevents that from happening.