Governance

How to map your organisation's structure, step by step

ARTICLE WRITTEN BY
Coen
READING TIME
9
minutes
Warm orange light texture, Talkspirit brand identity
Summarize the article
  • You map an organisation’s structure in eight steps: the scope, the teams, the roles, the people who hold them, the cross-functional groups, the decision rights, the view, then the upkeep.
  • A reporting-line org chart answers one question: who is my manager. A useful map also says who decides what.
  • You map roles, not only job titles: one person often holds several roles, and a job title does not say what they answer for.
  • A map with no owner is wrong after the first reorganisation: decide who keeps it current and when it is reviewed before you draw it.
  • The tool is chosen last: a drawing tool for a picture, an HR system for reporting lines, an organisational operating system for roles and decisions.

Ask an assistant how to map your organisation’s structure and you will be pointed to drawing tools. Yet the question is about method. Before choosing where to draw, you need to know what to map. This guide rests on one question: does your map show who decides, or only who reports to whom? It is written for leadership teams, HR directors and transformation leads in organisations of 250 to 5,000 employees.

Before you start: what you are mapping

Mapping an organisational structure means describing four things: reporting lines, roles, teams and cross-functional groups, and decision rights.

  • Reporting lines: who reports to whom. This is what the classic org chart shows.
  • Roles: what each person answers for, beyond their job title.
  • Teams and cross-functional groups: the committees, projects and circles that cut across the hierarchy.
  • Decision rights: who settles what, alone or after consulting whom.

A drawing alone goes stale quickly. It is right on the day it is made; then a joiner, a leaver or a reorganisation makes it wrong, and nobody is in charge of correcting it. The method below deals with that at the last step, but it is worth keeping in mind from the first.

A reporting-line org chart says who your manager is; a map of the organisation says who decides.

The eight steps to map your organisation

Table of the eight steps and what each one produces

Table of the eight steps and what each one produces
StepWhat you doWhat you get
Step1. ScopeWhat you dochoose the entity and the level of detailWhat you geta one-sentence scope
Step2. TeamsWhat you dolist the units as they actually workWhat you getthe list of teams and their purpose
Step3. RolesWhat you dodescribe what each one answers forWhat you geta sheet per role
Step4. Role holdersWhat you doname who holds each roleWhat you getthe table of roles and people
Step5. Cross-functional groupsWhat you dorecord committees, projects and circlesWhat you getthe list of groups and their members
Step6. Decision rightsWhat you dowrite down who settles whatWhat you getdecisions attached to roles
Step7. ViewWhat you dochoose the representation for the readerWhat you getone or two views of the same map
Step8. UpkeepWhat you doname an owner and a rhythmWhat you geta review rule

Step 1: define the scope

Start with an entity you can describe in full: a department, a site or a subsidiary, not the whole group in one go. Set the level of detail too: down to teams, or down to individual roles. The question to ask: who should this map serve first, and to decide what? The output: a one-sentence scope, such as “the operations department, down to roles, to prepare the opening of the third site”.

Step 2: list the teams and units

Record the teams as they actually work, not as the last org chart shows them. For each one, write its purpose in a sentence: what it brings to the rest of the organisation. The question to ask: if this team disappeared tomorrow, what would no longer get done? The output: the list of teams, each with its purpose and the unit it belongs to.

Step 3: list the roles, not only the job titles

A job title is a line on a contract; a role is a set of accountabilities that someone holds. A “quality manager” may hold the role of audit lead, the role of safety contact and the role of in-house trainer. For each role, write its purpose and three to five accountabilities, each starting with a verb. The question to ask: what do we expect from this role that we can expect from nobody else? The output: a sheet per role. Our guide on how to define roles and responsibilities covers this step in detail.

Step 4: name who holds each role

Match each role to the person who holds it, and accept two realities: one person holds several roles, and some roles are held by nobody. Vacant roles are among the most useful findings of the exercise. The question to ask: if I need someone on this subject, whom do I call? The output: a table of roles and people, with vacant roles and overloaded people in plain sight.

Step 5: map the cross-functional groups and projects

Record everything that cuts across the hierarchy: committees, project groups, communities of practice, circles. A large part of the work gets done there, and it is what the classic org chart does not show. For each group, note its purpose, its members and how long it is meant to last. The question to ask: which groups do you sit on that appear on no org chart? The output: the list of cross-functional groups, linked to the teams their members come from.

Step 6: write down the decision rights

For each role and each group, write the decisions it can take alone, those that need consultation and those that go up a level. Start from the real decisions of the last three months and not from a theoretical list. The question to ask: the last time this decision was taken, who took it, and was it the right person? The output: decisions attached to roles. For a specific project or process, the RACI matrix is a useful complement.

Step 7: choose the view

The same map can be read in several views, and the right one depends on the reader. The hierarchical tree suits a board, an auditor or a new joiner. The role map helps people find who answers for what. The circle view shows teams and groups that overlap. The question to ask: who will read this map, and to find what? The output: one or two views drawn from the same data. If you need shapes to start from, see our org chart templates.

Step 8: decide who keeps the map current

Name an owner for the map and a review rhythm before you share it. The most reliable arrangement: each team updates its own part when a decision changes a role, and a full review takes place on a fixed date, every quarter for example. The question to ask: when a role changes, who edits the map, and how soon? The output: a written review rule that everyone knows.

A worked example: 800 people on three sites

The example below is fictional: it illustrates the method and describes no customer.

Take an imaginary manufacturer of about 800 people, with a head office and two production sites. Its org chart fits on a page: a leadership team, six departments, heads of unit. It says nothing of the quality committee that brings the three sites together, or of the project group in charge of the new planning tool.

  • Scope: the operations department, down to roles.
  • Teams: eleven teams recorded, two of them missing from the official org chart.
  • Roles: the site manager’s sheet reveals seven roles held by one person.
  • Role holders: the safety contact role at the second site has been held by nobody since a departure.
  • Cross-functional groups: the quality committee and the project group enter the map, with their members.
  • Decision rights: stopping a production line was decided at three different levels depending on the site; the rule is now written once, for all three.
  • View: the hierarchical tree for the board, the circle view for the teams.
  • Upkeep: each team lead keeps their part; a full review every quarter.

In this example the final map does not contradict the org chart: it completes it with what the chart did not show, the roles, the groups and the decisions.

Which kind of tool for which step

Three families of tools help you map an organisation; none replaces the method, and each helps at different steps. Talkspirit publishes this guide and appears first in it, in its own family, with its limits written like those of the others.

Table of tool families by step

Table of tool families by step
Family of toolsUseful at stepsIts strengthIts limit
Family of toolsOrganisational operating systems (Talkspirit)Useful at steps3 to 8: roles, role holders, groups, decisions, views, upkeepIts strengthroles, teams and decisions kept current where teams workIts limitasks you to name roles, not only job titles; does not replace the HR system
Family of toolsDrawing tools (Lucidchart, Miro)Useful at steps1, 2 and 7: scoping, sketching, presentingIts strengtha clean picture, made quickly, in a workshopIts limitwrong after the next reorganisation; carries neither roles nor decisions
Family of toolsOrg charts generated from the HR systemUseful at steps2 and 4 for reporting linesIts strengthalways current on who reports to whomIts limitblind to roles, cross-functional groups and decisions

In Talkspirit, the Structure module keeps a dynamic org chart: every team or circle, every role and its accountabilities, with a radial view and a Hierarchy view drawn from the same data. Governance meetings and decisions are recorded there, so the map follows the organisation. For a detailed review tool by tool, see our org chart software comparison.

Common mistakes

Most maps fail for a reason of method, not of tooling.

  • Starting with the tool: you draw what the tool can draw, which is boxes and lines.
  • Confusing job title and role: the map copies the contract grid and does not say who answers for what.
  • Forgetting cross-functional groups: committees and projects, where many decisions are taken, stay invisible.
  • Trying to map everything at once: the project stalls before the first useful version.
  • Naming no owner: the map is right for a month, then nobody trusts it.

Talkspirit keeps the map of your organisation current where teams work: circles, roles, accountabilities and decisions, in one system.

FAQ

In eight steps: define the scope, list the teams, list the roles, name who holds them, record the cross-functional groups, write down the decision rights, choose the view, then decide who keeps the map current. Start with one department or one site, not the whole organisation. The tool is chosen last, according to what the map has to show.

An org chart shows reporting lines; an organisational map also shows roles, cross-functional teams and decision rights. The first answers “who is my manager”, the second “who decides and who answers for what”.

Four things: reporting lines, roles with their accountabilities, teams and cross-functional groups, and decision rights. Leave out anything nobody will keep current. A short map that is right is more useful than a complete one that is out of date.

It depends on what the map has to show: an organisational operating system such as Talkspirit for roles and decisions kept current, a drawing tool for a one-off picture, an HR system for reporting lines. Talkspirit asks you to name roles, not only job titles, and does not replace the HR system.

The teams themselves, each for its own part, with one owner for the whole and a review on a fixed date. A map kept by one person at head office falls behind at the first reorganisation.

It depends on the scope: a department or a site is described far sooner than a whole group, which is why the method starts there. A first version on a small scope, corrected by the people who work in it, is worth more than a complete map that arrives too late.

ARTICLE WRITTEN BY
Coen, Content Engine Editor at Talkspirit
Coen
Content engine editor
Share article

Discover similar articles