A company wants to close the gap with the market leader, so it does the sensible thing. It studies what the leader does. It benchmarks its operations against the best in the industry, brings in advisors who have seen how the top performers run, and adopts their best practices one at a time. A year later the operation is cleaner, the processes are tighter, but the company is still behind. It did everything right and gained no ground.

The strategy offsite ends on a high note. The leadership team has agreed that the company should become the number one player in the category within three years and reach five hundred million in revenue. They should also be the partner customers choose first and the employer people want to join. The statements are bold, everyone is aligned behind them, and the group leaves feeling it has done the serious work of setting strategy. 

A team is underwater. Requests pile up faster than they clear, employees are working late, quality is starting to slip, and the manager comes to the executive team with a straightforward ask. We need another head. The logic is hard to argue because the work is real, the people are stretched, and adding capacity is the obvious answer. The requisition gets approved, but six months later when the new member is fully ramped, the team is underwater again.

The right organizational design consultant understands operations, processes, accountability, and financial outcomes. Learn what CEOs and PE sponsors should ask.

Most leadership teams treat organizational design as a question of structure. How many layers should there be? How wide should the spans of control run? Which functions report to whom? Should the business be organized by region or by product line? These are legitimate questions, but they are the wrong place to begin because they describe the shape of an organization without touching the detail that determines how it performs. That detail is how decisions get made.

An org chart can show who reports to whom, but it does not always show who gets to make the decisions. Effective organizational design starts by clarifying decision rights before changing reporting lines.

Most organizational design efforts start in the wrong place: the organizational chart. Leaders begin moving boxes, changing reporting relationships, consolidating departments, and debating spans of control. The resulting structure may look cleaner, but that does not necessarily mean the organization will work better - or create more value.

PE operating partners rarely agree on what killed the synergy case on their last deal, but the root causes tend to repeat: predictable, avoidable mistakes made in the first year after close. This post breaks down seven of the most common ones, from treating close as the finish line to declaring victory once the org chart is done, and what disciplined post-merger integration looks like instead.

Every merger gets a hundred-day plan that looks thorough on paper. What most integrations lack isn't a plan, it's an owner. Here's why the gap between a plan built by advisors and a plan the organization actually runs is where deal value quietly slips away.

Rapid growth is a good problem to have - but it is still a problem. As revenue, customers, locations, services, and headcount increase, the organizational structure that supported a company’s early success can quickly become a constraint.

Reorganizations can look like decisive action when something isn't working, but changing reporting lines rarely fixes unclear priorities, broken handoffs, or weak accountability. Before redrawing the org chart, leaders need to understand what is actually causing the problem and address it directly.

Most org charts show who reports to whom, but they rarely show how work actually gets done. The “shadow org chart” reveals the informal relationships, influence, and decision-making paths that often shape how a company really operates.

Ask someone to describe how a process works and they will give you the official version. Watch them do the work and you will usually see something else entirely.

A redesigned process almost always looks better on paper. Whether it survives contact with the people who run it every day is a different question entirely.

Every organization has a graveyard of good ideas. Pilots that never scaled. Systems adopted by three people and ignored by three hundred. Strategic initiatives that looked brilliant in the boardroom and died the moment they touched the org chart.

Org design gets treated as a structural exercise - new boxes, new lines, new titles. But structure is downstream of a simpler question: who owns what, and who is responsible for the outcome. Get that answer right, and the structure to support it becomes obvious. Get it wrong, and no amount of restructuring fixes it.

Most middle-market PMOs aren't under-resourced — they're under-designed. The team stands up a tracker, assigns workstream leads, and runs a kickoff. Then, somewhere around week six, the operating model starts to drift from the plan on the slide.

Most conversations about AI governance start and end with security: model access controls, data encryption, vendor risk assessments, defenses against prompt injection. Those protections matter. But they solve the wrong problem for most organizations right now.

Every organization says it wants to innovate faster. Most respond to that ambition by doing the one thing guaranteed to slow innovation down: adding people.

Everyone wants to talk about the shiny thing. The new AI model. The automation platform. The dashboard that finally makes the data "make sense." Innovation, in most boardrooms, has quietly become a synonym for technology - as if buying the tool is the transformation.