The Working Definition
An org chart, also called an organization chart or organizational chart, is a diagram that shows how a company, team, function, or project group is arranged. The basic elements are boxes and lines: boxes usually represent positions, people, teams, or departments; lines show formal reporting relationships.
A good org chart helps people answer practical questions quickly: who manages this role, where does this team sit, which positions are open, where does work move between functions, and how many layers exist between the CEO and the front line?
Useful test: a chart is doing its job when a new leader, employee, advisor, or client can understand the basic structure without needing a private explanation.
What An Org Chart Shows
Most org charts show the visible structure of the organization. The exact details depend on the audience, but a working chart usually includes:
- Positions and people. Position titles and the people assigned to those positions. This is the minimum viable chart.
- Reporting lines. Who manages whom. The lines on the chart represent formal accountability, not informal influence.
- Teams and departments. How positions are grouped. These groupings are structural choices, see Organization Structure Types.
- Open roles. Positions that are budgeted and part of the plan but not yet filled. Including these shows what the organization is building toward, not just what exists today.
- Leadership layers. The vertical depth of the org: CEO to VP to Director to Manager to IC. Each layer represents a management level with (ideally) distinct decision authority.
What An Org Chart Does Not Show
An org chart is not the same as the organization. It is a model of formal structure, not a full explanation of how work actually happens. Understanding the limits prevents overreading the chart.
Decision rights
The chart may show who reports to whom, but it does not show who decides pricing, roadmap tradeoffs, hiring priorities, or customer exceptions. Two people at the same level on the chart may have very different decision authority. See Decision Rights.
Informal influence
Some people shape decisions through expertise, tenure, relationships, or customer knowledge even when they do not sit high in the formal hierarchy. The chart shows rank, not influence.
Coordination load
A clean chart can still hide difficult handoffs, overloaded managers, unclear ownership, and teams that depend on each other every day but sit in different branches of the tree.
Work allocation
Two people in the same box (same role, same title) may do very different work. The chart shows the position; it does not show what the person actually spends their time on.
Reading An Org Chart As Evidence
The real value of an org chart is not labeling, it's diagnostic. A chart reveals structural patterns that raise questions. Learning to read these patterns is the core skill.
Patterns to look for
| Pattern | What it looks like | Questions to ask |
|---|---|---|
| The fan | One node with 10+ direct children spreading wide. | Is this manager overloaded? Is meaningful coaching possible? Are decisions bottlenecking through this person? See Span of Control. |
| The deep chain | A long vertical line with each node having only 1-2 children. | Are all these layers adding value? Could reports skip a level without losing management quality? Is information getting filtered through too many intermediaries? |
| The lopsided tree | One branch of the org is much larger or deeper than its peers. | Does this reflect real scale differences, or has one function grown without structural review? Is the leader of the large branch overwhelmed compared to peers? |
| The orphan | A role or small team that sits oddly in the structure, far from related work. | Was this role placed here for historical reasons? Would it function better in a different part of the org? Does the manager have context to support this work? |
| The mirror | Two branches that look structurally similar but serve different functions. | Is the duplication intentional (two product lines, two geographies) or accidental? Are there opportunities to share capabilities? |
| The missing middle | A VP with 3-4 ICs reporting directly, no manager layer. | Is this a lean-on-purpose team, or has the team outgrown its structure? Is the VP doing manager-level work (1:1s, code reviews) when they should be doing VP-level work? |
Worked Example: Reading A 60-Person Chart
The chart shows a CEO with five direct reports: Head of Sales (3 reps), Head of Delivery (4 team leads, each managing 5-8 consultants), Head of Operations (12 direct reports), VP Finance (2 reports), and Head of People (1 report).
3 reps
4 leads
12 reports
2 reports
1 report
Signal 1: The fan. Head of Operations has 12 direct reports spanning office management, procurement, IT, legal coordination, and project management. This is a mixed-bag span: the reports do fundamentally different work, so the manager can't provide expert coaching to any of them. The role has likely accumulated responsibilities over time as the company grew and nobody else wanted to own these functions.
Signal 2: The lopsided tree. Delivery has 4 team leads and ~25 consultants (nearly half the company), while Sales has 3 people. This might be fine for a services business where delivery is the core, but it raises the question: is the Head of Delivery's span (4 direct reports + strategic oversight of 25+ people) sustainable, or should there be a layer between the team leads and the department head?
Signal 3: The chain. Head of People has 1 direct report: an HR coordinator. This is a layer that may not be earning its keep. Unless the Head of People also owns culture initiatives, talent strategy, and executive coaching, the organization is paying for a VP-level role to manage one coordinator.
Signal 4: Missing functions. There is no Marketing function. Customer acquisition relies entirely on the Head of Sales and referrals. As the company grows, this gap will become a constraint, but it's not visible on the chart unless you know to look for what's absent.
None of these signals prove the structure is wrong. They identify where to ask deeper questions. The chart is evidence, not the verdict.
Model the real structure, then use it to inspect spans, layers, open positions, and reporting patterns.
Create org chartCommon Org Chart Anti-Patterns
These habits make charts less useful as working evidence. For embedded examples of overloaded spans, deep chains, and orphan roles, see the full Common Org Chart Anti-Patterns guide.
The stale chart
The chart was accurate 6 months ago. Since then, three people left, two were hired, one role was split, and a team was reorganized informally. Nobody updated the chart, so it's now misleading. A chart that isn't maintained is worse than no chart because people make decisions based on wrong information.
The executive-only chart
The chart shows the CEO's direct reports and maybe one layer below. Everything else is hidden. This is fine for a board presentation but useless for operational planning, span analysis, or reorg modeling. A working chart needs to go all the way down.
The aspirational chart
The chart shows the org the company wants to be, not the one it is. Roles that are "planned but not yet hired" appear as filled. Functions that have one person are shown as full departments. This confuses current-state analysis and makes it impossible to identify real structural issues.
The contractor-blind chart
Contractors, fractional executives, and outsourced teams are excluded from the chart even when they do critical work. If a contractor manages three people or owns a key deliverable, leaving them off the chart hides a real structural dependency.
Common Org Chart Types
| Type | What it emphasizes | Where it helps |
|---|---|---|
| Hierarchical | Clear reporting lines from leadership through each layer. | Most companies, departments, and teams with formal managers. |
| Functional | Teams grouped by discipline such as Sales, Product, Finance, or People. | Understanding expertise, leadership coverage, and functional ownership. |
| Matrix | More than one reporting relationship, often a functional manager plus project or product leadership. | Showing shared accountability, cross-functional work, or dotted-line reporting. |
| Team-based | Groups arranged around products, regions, customer segments, or workstreams. | Planning operating models where outcomes matter more than functional boundaries. |
For a deeper treatment of how these structures work, their tradeoffs, and when to transition between them, see Organization Structure Types.
Org Chart FAQ
What is an org chart?
An org chart, or organization chart, is a visual map of an organization's positions, people, teams, and reporting relationships.
What should an org chart include?
A useful org chart usually includes position titles, assigned people, teams or departments, managers, direct reports, and open roles when they are part of the operating plan.
Is an org chart the same as organization design?
No. An org chart shows visible structure. Organization design is the broader set of choices about work, authority, decision rights, processes, incentives, and people. The chart is one tool for reasoning about design. See What Is Organization Design?
Sources And Further Reading
- Henry Mintzberg, Structure in Fives: Designing Effective Organizations.
- Jay R. Galbraith, Designing Organizations: An Executive Guide to Strategy, Structure, and Process.
- David A. Nadler and Michael L. Tushman, Competing by Design.
- Matthew Skelton and Manuel Pais, Team Topologies.
Continue Reading
Once the chart is clear as an artifact, the next step is understanding the broader design choices behind it.
Next guideWhat Is Organization Design?
Learn how structure, roles, decision rights, processes, and people fit together as one operating system.