Your Org Chart Isn’t an HR Task. It’s a C-Suite Design Job.

Org Design

Why org design belongs to the C-suite, and how to rebuild structure around outcomes instead of layers.

The short answer

When a company scales on the same structure, decisions drag, projects drift and good people burn out. Org design is strategy, so it belongs to the C-suite with HR as a partner. Trace how work actually moves, name owners for distinct outcomes, match decision rights to accountability, and hire for capability rather than pedigree.

Key takeaways

  • If your org chart needs a legend and a sherpa, it’s a maze.
  • A company that grew to about $60M on the same structure had 7 handoffs for a single order.
  • Rebuild around outcomes: customer fulfillment, inventory health, supplier performance.
  • Every added layer must earn its keep by reducing cycle time or risk.
  • Run the one-week absence drill: if your top 3 leaders vanished for 7 days, what would stop?

The call came after a four-hour leadership meeting that went nowhere.

“We’ve tripled revenue in four years,” the CEO said. “Great people… yet decisions drag, projects slip, and everyone’s frustrated. Is this a people problem or a setup problem?”

“Send the org chart,” we said.

It looked polished: boxes, lines, tidy titles. It just didn’t match how work actually moved. Sales was clinging to project management to “protect the customer,” which buried the sales leader under pipeline and delivery. Estimating lived in finance because… history. Pricing had three versions depending on who you asked. And when we pressed on who owned a customer complaint end-to-end, three different names surfaced.

The people weren’t broken. The design was. They’d scaled from roughly $20M to ~$60M on the same underlying structure, only now with more volume and more friction. If your org chart needs a legend and a sherpa, it’s not a design. It’s a maze.

Stop Swapping Titles. Start Designing Flow.

Too many leadership teams treat org design like seating charts: shift a person here, stretch a span there, rename a few roles. That’s rearrangement, not design.

Design is about how decisions get made, how information travels, and where accountability lives. At $20M, hallway triage and heroics can carry you. At $60M, that playbook collapses. Add headcount to yesterday’s structure and you don’t scale. You stall.

Here’s the predictable pattern when structure lags growth:

  • Decision latency: nobody is sure who decides, so everyone waits.
  • Project drift: two or three “kind-of owners” means no real owner.
  • Signal loss: reporting lines don’t match how value is created.
  • Talent fatigue: your best people burn out trying to push through fog.

And here’s the common mistake: handing the org chart to HR to “fix.” HR is essential, just not as the quarterback of business design. Structure is strategy. It belongs to the C-suite, with HR as a key partner.

What Changed: Outcomes Over Layers

Together, we paused the box-moving and traced the work. Not the theoretical version. The real one.

How does an order travel from sold to fulfilled?

How does a price get set under time pressure?

What actually happens when a quality issue lands?

It was all there: seven handoffs for a single order; pricing with many inputs but no final call; issues ricocheting between functions until someone got loud.

We rebuilt around outcomes instead of hierarchy. Rather than one overloaded VP of Ops, we named owners for distinct results that had been mashed together:

  • Customer fulfillment: on time, as promised.
  • Inventory health: the right product, available when needed.
  • Supplier performance: vendors meeting standards without heroics.

For each outcome, we hard-wired decision rights and escalation paths. No “let me run it past three people.” Clear authority matched to clear accountability.

Week five, the old reflex tried to sneak back in. “We should add a layer to watch this,” the CEO said. Understandable, but it’s how the bloat begins. We held the line: fewer layers, sharper ownership. Uncomfortable at first. Effective immediately.

Six months later, cycle times shortened. Projects shipped. Customer issues closed. And the exec team reclaimed headspace for the future instead of triaging the past.

The Skill Shift Most Teams Miss

Clean structure without the right capabilities in the seats still jams the system. Roles must be designed for the outcomes you need now, not inherited titles or credential wish lists. We assess by doing: working sessions, dry-runs, “week-one” problems. You learn more in 90 minutes of live problem-solving than in nine pages of résumé bullets. Skills travel; titles don’t. Hire for the work.

A Five-Point Gut-Check (Use It Next Week)

  1. Trace one customer outcome end-to-end. Name the owner of each decision. If you can’t, you’ve designed ambiguity.
  2. List your five recurring decisions. For each: who proposes, who decides, who’s consulted, who’s informed? (If more than three weigh in on most calls, you’ve built consensus where clarity belongs.)
  3. Open three job descriptions. Do they specify outcomes and decisions, or just activities and credentials? Rewrite for outcomes, then test for the skills that produce them.
  4. Run the new-hire test. Hand your org chart to a recent hire and ask, “How does a pricing decision move?” If the chart can’t answer, the chart isn’t helping.
  5. Do the one-week absence drill. If your top three leaders disappeared for seven days, what would stop? If the answer is “most things,” you’re running on heroics, not design.

How to Start (and Keep It Out of the Weeds)

Block two focused hours next week with your COO, CFO, and HR lead. No slides. Map order-to-cash as it truly runs today. Mark every handoff, stall point, and decision. You’ll see the gaps immediately:

  • Outcomes with no single owner.
  • Decisions with many inputs but no decider.
  • Information traveling the long way because the structure demands it.

Then change the questions:

  • From “Who reports to whom?” to “Who owns this outcome, and what decisions come with it?”
  • From “What title?” to “What capabilities must this seat bring on day one?”
  • From “How do we add oversight?” to “How do we shorten the path to a clear yes/no?”

Lock in three guardrails as you implement:

  • Clarity beats layers. Every added layer must earn its keep by reducing cycle time or risk. If it doesn’t, it’s noise.
  • Cadence over heroics. Use light operating rhythms (reviews, stand-ups, retros) that keep outcomes visible without turning managers into traffic cops.
  • Escalate by rule, not by volume. When boundaries are clear, escalation is a designed path, not a shouting contest.

The Bottom Line

Your org structure is either a force multiplier or a tax on execution. There’s no neutral. Treat it like strategy, not stationery. Map the real work. Name the outcomes. Match authority to accountability. Fill seats for capability, not pedigree. And when someone says, “Let’s add another layer to keep an eye on this,” remember: the shortest line between “idea” and “done” is ownership.

Do that in the C-suite, with HR as a partner, and the business you actually run will finally match the one on your wall. Next time your leadership team spends four hours together, you’ll walk out with decisions made, not just notes taken.

Questions CEOs ask

Who should own organizational design?

The C-suite, with HR as a key partner. Structure is strategy, so it shouldn’t be handed to HR alone to fix.

What are the signs your org structure is lagging growth?

Decision latency, project drift from having several partial owners, reporting lines that don’t match how value is created, and talent fatigue.

How do you redesign an org chart around outcomes?

Trace how work really moves, name a single owner for each distinct outcome, and hard-wire decision rights and escalation paths for each one.

Should we add a management layer to keep an eye on problems?

Usually not. Each layer should earn its place by reducing cycle time or risk. Otherwise it’s noise. Fewer layers with sharper ownership work better.

About Jane Gentry

Jane Gentry is a strategic operating model advisor and former CEO who ran two private-equity-backed companies. An operator by background, she works with mid-market CEOs at companies between $20M and $800M in revenue. She redesigns org structure, decision rights, and workflows when revenue grows faster than the business was built to run. For more, visit www.janegentry.com. Connect on LinkedIn.

Does your structure match how work actually moves?

Jane works directly with mid-market CEOs on who owns what, how decisions get made and where work stalls. Start with a 30-minute conversation.

Book a 30-minute consultation

Originally published in Exhibit City News. Updated for janegentry.com.

Jane Gentry is a strategic operating model advisor and former CEO of two PE-backed companies who helps mid-market CEOs redesign their companies when revenue grows faster than the business was built to run.