Organizational Design Is Not an Org Chart

Organizational design for flow is what separates a company that moves from one that only looks organized. In this solo episode, host Tullio Siragusa takes on one of the most misunderstood levers in business: the difference between an org chart, which tells you who reports to whom, and organizational design, which determines how work actually gets done.

In this episode we explore:

• Why a beautiful org chart can still sit on top of a messy company

• The leadership question that exposes friction faster than any survey

• The four step sequence most organizations run backwards

• Why moving people around relocates dysfunction instead of fixing it

• How internal design shows up in customer experience

• A one page exercise to run this week

Tullio’s opening claim is that the problem is almost never the people. Teams can be talented, committed, and hardworking and still struggle when decisions bounce around, ownership is unclear, efforts duplicate, and meetings multiply. Everyone looks busy while progress stays uneven. That is a design outcome, not a talent outcome.

The diagnostic he offers is a single question, and the phrasing matters. Not what is it like to work here, but what is it like to get work done here. If the answer is slow, political, confusing, or exhausting, the design is manufacturing friction. If it is focused, collaborative, and fast, the design is creating flow.

From there he lays out the sequence: define the outcomes that matter most right now, then decision rights covering who decides, who must be consulted, and who must be informed, then the weekly operating rhythms for progress and escalation, and only then roles. Most organizations invert this, creating roles first and working around them ever after.

His worked example is a growth initiative spanning marketing, sales, product, and customer success, where everyone is involved and nobody owns the outcome. Marketing reports leads generated, sales calls them weak, product says the offering is not final, and customer success calls the handoff messy. The fix is one accountable owner, named contributors, a weekly cross-functional rhythm, a visible scorecard, and clear escalation rules.

The closing argument is the one marketers should sit with: customer experience is the downstream result of internal design. Slow decisions and unclear ownership are felt outside the building. A brand cannot promise responsiveness in market while running a structure that produces delay, which is exactly where campaign promises and operational reality have to be reconciled.

Key Takeaways

• (0:12) The core distinction: an org chart tells you who reports to whom, while organizational design tells you how work actually moves.

• The leadership question that matters is not what is it like to work here, but what is it like to get work done here.

• Friction is named as the enemy of business, and flow as the condition bliss depends on.

• Reshuffling reporting lines without fixing how decisions get made just moves the same dysfunction into a new structure.

• The correct sequence is outcomes, then decision rights, then operating rhythms, then roles. Most organizations do it backwards.

• Customer experience is the downstream result of internal design. If handoffs are broken or decisions slow, customers feel it and trust erodes.

FAQ

What is the difference between an org chart and organizational design?
Tullio Siragusa draws the line clearly: an org chart shows reporting relationships, while organizational design determines how work moves through the company. A company can have a clean chart and still be slow, political, and duplicative.

Why does reorganizing a team rarely fix the problem?
Because reshuffling titles and reporting lines without changing decision rights and accountability moves the same dysfunction into a new structure. Tullio Siragusa argues the design, not the people, is usually the cause.

What is the right order for designing an organization?
Outcomes first, then decision rights, then operating rhythms, then roles. Tullio Siragusa notes most organizations reverse this, creating roles first and then working around them.

Bliss grows when design creates flow and people know what they own. Find more episodes on the BLISS series.