16:91 frame · org chart
Case study

Why this artifact is built the way it is

When you’d need it

You need to explain who owns what before a planning meeting, a hiring conversation, or an onboarding session. A bullet list of names will not show reporting lines or cross-functional handoffs clearly enough.

Key decisions

  • The chart uses a hierarchy first, so reporting lines are visible before role details.
  • Dotted-line collaboration is kept in the same diagram because matrix teams need both formal and working relationships.
  • One frame keeps the artifact usable as a standalone diagram or a slide inside a larger deck.

When to copy vs. adapt

Copy this structure for team planning, onboarding, or investor updates. Adapt it when you need contractors, open roles, or a planned future-state org chart.

Inside

What’s in this artifact

  1. 01Leadership
  2. 02Functional teams
  3. 03Reporting lines
  4. 04Collaboration links
FAQ

Org chart questions

What should an org chart example include?

A useful org chart shows the key roles, reporting lines, teams, and any dotted-line relationships that affect how work gets done.

Can I make a planned org chart?

Yes. Ask Toft to mark open roles, future hires, or planned teams so the current and future structure are easy to compare.

Is the org chart editable?

Yes. The chart is generated as real diagram structure, so you can change names, roles, and relationships after generation.

Make your own

Tools that build this.

Make your own org chart.

Describe what you need. Toft returns the finished, editable artifact.

Try it with this prompt