Skip to content
Menu
Cedar Cloud Rise

Organizational design for teams that have grown quickly

Structure problems do not announce themselves. They accumulate.

Top view of diverse creative team collaborating at a workspace with tech and charts.

The structure that works at fifteen people rarely works at fifty. Most organizations figure this out the hard way, after the confusion has been expensive for a year or two. The signs are recognizable if you know what to look for.

How structural problems show up

The first sign is usually decision latency. Things that should be decided quickly take three meetings and two email threads. Nobody is being obstructionist. The structure just does not make it clear who decides.

The second sign is invisible load. A few people are carrying far more than their titles suggest. They are the ones who know how everything connects, who get copied on everything, who are in every meeting that matters. They are also the ones who are most likely to leave, and when they do, the organization discovers how much was held together by one person's knowledge.

What organizational design actually involves

Organizational design is not about drawing a new chart. The chart is a downstream artifact. The real work is about accountability: who is responsible for which outcome, and do they have the authority and information to be responsible for it.

When those three things are not aligned, the structure is broken regardless of what the chart says. The work involves mapping how decisions actually get made, where accountability is unclear, and what changes would make the most difference without creating new problems.

When to do this work

The best time to do organizational design work is slightly before you need it. After a significant hire, after a product line expands, after a merger or acquisition. The worst time is in the middle of a crisis, when the pressure to produce a new chart quickly leads to a chart that looks tidy but does not actually solve the accountability problem.

Cedar Cloud Rise works on organizational design with teams that have grown past their structure. The engagements typically run six to eight weeks and produce a written set of recommendations, not just a new chart.

Related reading

  1. How to read an organization before you start advising it
  2. When strategy consulting actually helps an organization
  3. A simple framework for high-stakes decisions
  4. How to write a strategy memo that people actually use
Keep exploring

Clarity for the work that actually matters