The Lines Nobody Drew: Mapping the Team That Actually Turns Up

The org chart is a useful fiction. It tells you who reports to whom, who approves leave and where the budget sits. It does not tell you who actually gets the work done, who knows where the files live, or who answers in the channel at 4:50pm on a Friday when everyone else has mentally left the building.

Every UK team has two structures. One lives in the HR system, polished and occasionally out of date. The other is drawn by small acts of collaboration: the people copied into a document, the pairs who book a recurring call, the colleague who always seems to know which version of the deck is current. The second map is the one your team actually uses. It is also the one nobody has drawn.

At Kula, we spend a lot of time thinking about how teams work together — not just where the tools sit, but how people find each other. The informal map matters because it explains why some projects glide and others stall. It shows where knowledge is concentrated, where handovers leak and where a single person is quietly holding three teams together with sticky tape and polite reminders.

The chart is not the work

Formal structure is necessary. It gives people a line manager, a pay grade and a route to escalation. But it is a poor description of daily reality. A team can look tidy on paper and still rely on a shared inbox, a spreadsheet in a drawer and one person who has been there long enough to remember why the Tuesday meeting exists.

This gap is not a failure of management. It is normal. Organisations are messier than their diagrams. The trouble starts when decisions are made as if the diagram were true. Budgets get allocated by department, but work flows across them. Training gets aimed at new starters, but the real onboarding happens in side chats. A restructure moves a box on the chart, while the informal routes carry on unchanged — or snap.

In the UK, there is an extra layer of fog. British workplace culture often rewards understatement. People say 'I'll loop in Priya' rather than 'Priya owns this'. They apologise for bothering colleagues, even when the colleague is the only person who knows how the thing works. Hierarchy is present, but it is often discussed in hints rather than headlines. That makes the informal map harder to see, especially from the top.

Read the trails you already have

You do not need a new platform to sketch the real team. You need permission, a little curiosity and an eye for patterns. Start with three ordinary signals.

First, channel membership. Which channels does each person actually use? Not the ones they were added to, but the ones where they post, reply or react. A person who sits in Finance but lives in three project channels is telling you something about how work moves.

Second, meeting overlap. Look at recurring meetings, not one-offs. Who is in the same rooms week after week? Which names appear across different departments? A calendar is a blunt instrument, but it is a decent map of who is expected to talk to whom.

Third, co-editing. Which documents have multiple editors from different teams? Where do comments turn into conversations? Shared documents are often where the real decisions are made, long before they reach a formal meeting.

Treat these signals as clues, not evidence. Do not turn them into a surveillance exercise. The point is not to score people on activity. It is to notice where the work actually flows. If you use Kula, some of this is already visible in channel membership, shared docs and meeting notes — but the tool is only a lens. The judgement is human.

When you find a hidden hub

Sooner or later, the map will show a surprise. One name will sit at the centre of several clusters. They may not be a manager. They may be an administrator, a project coordinator, a long-serving analyst or the person who set up the team's shared drive and never stopped maintaining it.

This is a hidden hub. They are invaluable and precarious. They answer questions, fix permissions, remember context and translate between teams. They also become a single point of failure. When they take leave, the map wobbles. When they leave, it tears.

If you find a hidden hub, resist the urge to make them a superhero. Instead, ask what can be shared. Which of their routes could become a documented process? Which questions could go in a channel instead of a direct message? Who else could join the recurring call? The aim is not to flatten the map. It is to make the important connections visible and resilient.

A twenty-minute map for your next team session

You can do this with a whiteboard, a shared document or a large sheet of paper. No new software. No performance data. Just a team and twenty minutes.

1. Three minutes, silent. Everyone writes down the names of up to three people they worked with in the past fortnight, and one thing they needed from them. Keep it to work, not personality.

2. Five minutes, drawing. Put initials on the board. Draw a solid line for weekly contact, a dotted line for occasional contact and a star next to anyone they cannot do their job without. Use first names only if the room is comfortable.

3. Four minutes, noticing. Step back. Where are the clusters? Who bridges two groups? Who sits on the edge with only one line? Ask what the map shows that the org chart does not.

4. Five minutes, discussing. Pick one pattern worth changing. It might be a bridge person who needs backup, a cluster that never talks to another cluster, or a new starter with too few lines.

5. Three minutes, agreeing. Choose one small action for the next month. A shared channel, a rotating note-taker, a fortnightly handover. Something modest enough to survive a busy week.

Keep the map alive

The map is not a poster. It is a habit. Revisit it when someone joins, when a project ends, when a restructure is announced. Compare it with the formal chart and ask what has changed. The aim is not to replace the org chart. It is to stop pretending the chart is the whole story.

The team that actually exists is the one that turns up in the channel at 4:50pm, shares the document with three comments attached and quietly keeps the week moving. Draw that team. Then look after it.