Org chart examples for small teams

A small team rarely needs an org chart to know who the boss is. It needs one for the questions that come up as the team grows: who approves a purchase, who a new hire should ask about payroll, who owns the customer relationship when two people both think they do.

The examples below are written for teams of roughly five to forty people. Each one is a pattern rather than a template. Pick the one that matches how your team actually works, not how a larger company would draw it.

Example 1: The founder-centred chart

The simplest structure has one person at the top and everyone else reporting directly to them.

• Top: Founder or managing director
• Second row: Operations lead, sales lead, two engineers, a designer, an accountant

This is honest for a team of six or seven. It tells a new joiner that decisions go to one place. Past ten direct reports, though, it starts to describe a bottleneck rather than a structure. If the chart has a single box with more than eight lines coming out of it, that’s worth a conversation before it’s worth a redraw.

Drawing tip: keep the second row in one line. If it won’t fit, you’ve found the problem the chart is meant to reveal.

Example 2: Two or three functional groups

As a team passes ten people, it usually forms groups by function. For example, a 15-person services firm in Pune might look like this:

• Director
  • Delivery lead → three consultants, one analyst
  • Business development lead → two account managers
  • Operations manager → finance executive, office administrator

Three boxes under the top, each with its own small team. Readers can see at a glance where to take a question. Draw each group as a column and align the leads on one row, so the levels are visually obvious.

Example 3: The chart with a dotted line

Small teams often have people who report to one person but spend most of their time working with another. A designer might report to the product lead while sitting in on every marketing review.

Show this with a dotted line from the person to the secondary manager. Use it sparingly. One or two dotted lines clarify reality. Five or six suggest the structure itself needs rethinking, and the chart will be hard to read.

Add a one-line legend: solid line = reports to; dotted line = works closely with. Without it, people will interpret the dotted line in different ways.

Example 4: Roles, not names

Some teams change people faster than they change structure, for instance an agency that staffs projects with freelancers. Here it helps to draw the chart with role titles in the boxes and names added beneath in smaller text, or left off entirely.

Box label	Name line
Studio lead	Priya
Project manager	(rotating)
Senior designer	Arjun
Freelance developers (2–4)	varies by project

A role-based chart stays useful when individuals move, and it makes vacancies visible. An empty box labelled “Finance lead (hiring)” tells everyone where the gap is. If new joiners also need to put faces to the roles, pair the chart with a few team slides that give each person a photo and a line about what they do.

Example 5: The chart with an external ring

Small companies depend on people who aren’t employees: an outsourced accountant, a legal adviser, a fractional HR consultant. Leaving them off the chart hides who handles what.

Draw the internal structure as normal, then add a separate row or a lightly shaded area labelled External support. Connect each external box to the internal person who manages that relationship. A new hire then knows that GST questions go to the operations manager, who works with the outside accountant.

How to choose between them

Ask what question the chart needs to answer for the person reading it:

• “Who do I report to?” Examples 1 or 2.
• “Who should I involve in this decision?” Example 3, with dotted lines.
• “What roles exist, and which are empty?” Example 4.
• “Who handles things we don’t do in-house?” Example 5.

You can combine them. A functional chart with one dotted line and an external support row is common and still readable. If the chart is headed for an all-hands deck, start from an org chart slide laid out for the screen rather than shrinking a full-page chart to fit.

Layout rules that hold for every size

A few conventions make any org chart easier to scan:

1. One level per row. Everyone at the same reporting level sits on the same horizontal line.
2. Consistent box size. Larger boxes for senior people imply importance the chart doesn’t need to state.
3. Title first, name second. Titles change less often and tell the reader what the person does.
4. Group colours, not rank colours. Colour by team (delivery, sales, operations) so the eye finds a group quickly.
5. Date the chart. A small “as of October 2026” in the corner tells readers how far to trust it.

If you also document how work moves between these groups, a swimlane diagram is the natural companion. See swimlane diagrams explained for how to draw one.

Keeping it current

An org chart is out of date the day someone joins or leaves. Small teams can keep it accurate with a simple habit: update it as part of onboarding and offboarding, not as a separate task. Whoever sends the welcome email or collects the laptop also updates the chart.

Keep the source somewhere editable rather than as a pasted image, so the update takes a minute. If you describe the structure in plain words (who reports to whom, which roles are open), DiagramsPro can lay it out for you, and the next change is a sentence rather than a redraw.