How to Build an Org Chart for a 50-Person Company

Your company just crossed 50 employees. Congratulations — and also, condolences. Because somewhere around this number, the "everyone knows everyone" era ends and you need real organizational structure. The org chart that lived in your head (or didn't exist at all) now needs to be visible, shared, and maintained.

This guide walks through how to build an org chart that actually works at the 50-person stage — not a theoretical framework, but practical steps based on how real companies organize at this size.

Why 50 People Is the Inflection Point

At 10–20 people, informal structures work. People self-organize, everyone reports to a founder, and communication happens naturally. At 50, several things change simultaneously:

• Span of control breaks down. No single manager can effectively manage 15+ direct reports. If your CEO still has 12 people reporting to them, important things are slipping through the cracks.
• New hires can't figure out who does what. Onboarding takes longer because tribal knowledge doesn't scale.
• Cross-team coordination gets messy. Engineering doesn't know who to talk to in Sales about a feature request. Support escalations go to the wrong person.
• HR and compliance requirements kick in. Many jurisdictions have reporting requirements at 50 employees. You need to document your structure.

Step 1: Map What You Actually Have

Before designing your ideal structure, document your current one. This is often uncomfortable — you'll discover that your "flat" org is actually a mess of unclear reporting lines and duplicated responsibilities.

Start with a simple spreadsheet. For each person, record:

• Name and title
• Who they actually report to (not who they're supposed to report to)
• Department or function
• Location (if distributed)

Step 2: Establish Your Core Departments

At 50 people, most companies have 4–7 departments. Here's a typical breakdown:

• Engineering / Product (often 15–25 people at a tech company)
• Sales / Business Development (5–12 people)
• Marketing (3–8 people)
• Customer Success / Support (4–10 people)
• Operations / Finance / HR (3–6 people)

Don't force departments that don't exist yet. If you have two marketing people, they don't need their own VP. They can report to a head of growth or even the CEO temporarily.

Step 3: Set Appropriate Span of Control

The "span of control" is how many direct reports a manager has. Research consistently shows that 5–8 direct reports is optimal for most management roles. Here's a practical guide:

• CEO: 4–7 direct reports (department heads + chief of staff)
• VP / Department Head: 5–8 direct reports
• Team Lead / Manager: 4–8 direct reports

If anyone has more than 10 direct reports, you need a management layer. If anyone has fewer than 3, consider whether that layer is necessary.

Step 4: Decide on Management Layers

At 50 people, you should have exactly 3 layers:

1. Executive layer: CEO + co-founders in leadership roles
2. Department heads: VP Engineering, Head of Sales, etc.
3. Individual contributors: Engineers, salespeople, marketers

Some larger departments might need a fourth layer (team leads), but resist adding layers prematurely. Every layer you add slows down communication and decision-making.

A common mistake: promoting your best engineer to "Engineering Manager" because you need another layer, even though they have no interest in management. Consider a dual-track career ladder instead.

Step 5: Handle Cross-Functional Relationships

At 50 people, you'll have people who work across departments. A product manager who works with both engineering and sales. A data analyst who supports marketing and finance. There are two ways to represent this:

• Solid line + dotted line: The person has one primary manager (solid line) and one secondary relationship (dotted line). Use this when there's a clear primary reporting relationship.
• Matrix structure: The person formally reports to two managers. Use this sparingly — it's confusing at the 50-person stage.

For most 50-person companies, stick with a primarily hierarchical structure and use dotted lines for cross-functional relationships. You can always evolve toward a matrix structure later.

Step 6: Document and Share

An org chart that lives in a forgotten Google Doc is useless. Your org chart should be:

• Accessible: Everyone in the company can find it in under 30 seconds
• Current: Updated within a week of any organizational change
• Clear: A new hire can understand the structure without explanation

Assign someone (usually HR or an office manager) as the org chart owner. They're responsible for keeping it updated. If you use a tool like OrgCanvas, you can share a live link that always shows the current structure.

Common Mistakes at the 50-Person Stage

• Too many direct reports to the CEO. If your CEO has 10+ direct reports, they're a bottleneck. Hire or promote department heads.
• Title inflation. You don't need a C-suite at 50 people. "Head of" or "VP" is usually sufficient until you're past 200.
• Copying Big Company structures. Google has a matrix org with 180,000 people. You don't need that. Keep it simple.
• Never updating the chart. An outdated org chart is worse than no org chart — it creates confusion about who's actually responsible for what.
• Ignoring informal influence. The org chart shows formal reporting lines, but real influence flows differently. That's okay — just don't pretend the chart captures everything.

A Sample 50-Person Org Chart

Here's a realistic structure for a 50-person B2B SaaS company:

• CEO (5 direct reports)
  • VP Engineering → 3 team leads → 15 engineers
  • Head of Product → 2 PMs, 1 designer
  • Head of Sales → 2 AEs, 2 SDRs, 1 sales ops
  • Head of Marketing → 3 marketers
  • Head of Operations → HR manager, finance, office manager, 4 support reps

That's 3 layers, reasonable spans of control, and clear ownership. Clean enough that a new hire can understand it in 60 seconds.

Further Reading

• Matrix vs Hierarchical Org Charts: When to Use Each
• The Complete Guide to Org Chart Best Practices
• OrgCanvas for Startups