Org Chart

An org chart (organizational chart) is the visual representation of a company's reporting structure, showing who reports to whom and how teams are organized. The chart also documents what each role does at a high level and how groups connect across functions. It is used both as a clarity tool for employees and as a strategic design tool for organizational structure. It's more than a hierarchy diagram. The org chart shapes how decisions get made, where information flows, and ultimately what kind of company gets built.

What an org chart shows:

Reporting relationships: every employee's manager and chain of command up to CEO.

Team structure: how individuals group into teams, departments, and divisions.

Cross-functional connections: dotted-line relationships (matrix reporting, embedded specialists).

Spans of control: how many people report to each manager (see Span of Control).

Levels: tied to career ladder, what level each role represents.

Org chart structures by stage:

Founders' team (1-10): typically flat. Everyone reports to CEO. No formal org chart needed.

Early team (10-30): simple structure. CEO + 2-4 functional leads (engineering, sales, marketing, ops) each managing small teams.

Growth stage (30-100): clear functional groupings. VPs/Heads of each function. Often 4-8 direct reports to CEO.

Scale (100-500): multiple management layers. Directors and managers underneath VPs. Cross-functional teams ("squads," "tribes," etc.) increasingly common.

Enterprise (500+): complex structure with divisions, matrix reporting, geographic groupings, business units.

Common org chart patterns:

Functional: organized by function (engineering, sales, marketing, finance, etc.). Standard at most startups.

Product-led / Squad-based: organized by product or feature area, with embedded engineers, designers, PMs. Common at Spotify-influenced orgs.

Geographic: organized by region. Common at international companies.

Matrix: dual reporting (e.g., to functional lead + product lead). Complex but allows specialization across products.

Holocracy / flat: no formal hierarchy. Rare; usually a transitional state.

Why org charts matter (beyond clarity):

Decision velocity: flat orgs make decisions faster; deep orgs add review layers.

Information flow: hierarchy controls what information reaches the CEO.

Cross-team friction: org boundaries create coordination overhead.

Career paths: the org structure determines what advancement looks like.

Cultural signaling: where people sit and who reports to whom signals what matters.

Common org chart problems:

Premature complexity: 30-person company with 4 management layers. Add layers later, not earlier.

Empire building: managers expanding their team for status rather than need.

Span of control issues: managers with 1-2 reports (under-leveraged) or 15+ reports (overloaded).

Reporting confusion: matrix reporting without clear authority lines.

Strategic mismatch: org structure that doesn't reflect the company's strategy.

How founders should think about org chart design:

Mirror strategy: org should reflect what the company is trying to do.

Communicate clearly: every employee should know where they sit and how they connect to others.

Iterate as you grow: structure that works at 30 doesn't work at 100; redesign every 6-12 months at growth stage.

Watch for managerial sprawl: don't promote ICs to managers just to give them a path; use the IC ladder.

Keep the founder accessible: founders who become unreachable to ICs lose touch with reality fast.

What founders get wrong: Treating the org chart as static infrastructure rather than a strategic tool. The right discipline: review org structure at every 6-12 month milestone; redesign for current strategy; communicate changes clearly; resist premature complexity.

Related: Span of Control · Founder Roles · Hiring Plan · Employee Handbook · Career Ladder

FAQ

What is an org chart?
The visual representation of a company's reporting structure, showing who reports to whom, how teams are organized, and how groups connect across functions. Used both for clarity and as a strategic tool for organizational design.

When should I create an org chart?
Once you have ~15+ employees and any management layer. Earlier than that, everyone reporting to the founder doesn't need a diagram. Past 15-20, formal org chart helps everyone understand structure.

How often should I redesign the org?
At growth stage, every 6-12 months. Org that works at 30 employees doesn't work at 100. Major redesigns at funding milestones (post-Series A, post-Series B) are common.

What are common org chart structures?
Functional (organized by function: eng, sales, marketing, etc.) is standard. Product-led / squad-based (organized by product area) common at Spotify-influenced orgs. Matrix (dual reporting) complex but allows specialization. Geographic at international companies.