Why planning often ends up with one colleague
Planning ending up with one person is rarely a conscious decision. In many teams, this happens naturally, and in the beginning, it often works just fine.
Phase 1: it works as long as the team is small
In small teams, communication is direct:
- Everyone is close to one another
- Agreements are made verbally
- One colleague naturally keeps the overview
That person knows who is working on what, which deadlines are shifting, and what the priorities are. As long as the team remains manageable, this feels efficient and logical.
Phase 2: the planning grows, but the structure doesn’t
As the workload increases, the planning grows with it, often without fixed agreements:
- An Excel file gets more and more tabs
- Colour codes and comments replace proper documentation
- Details are remembered instead of written down
What’s missing is a moment where someone says: this no longer works like this.
Phase 3: knowledge sits in heads, not in systems
Much information is passed on verbally during meetings, through brief chat messages, or simply remembered. It feels fast, but it makes the planning implicit. Important context sits in the head of one or two people, not in a place where everyone can access it.
Phase 4: growth exposes the vulnerability
As the organisation grows, new colleagues join, not everyone is included in everything, and even more dependencies arise. What was once manageable becomes complex. The overview becomes person-dependent and therefore vulnerable.
As long as everything is going well, you don’t notice it.
Only when someone is absent or the team grows further does it become clear that the planning hasn’t grown along.
The risks of planning that isn’t shared
As soon as planning isn’t shared, structural risks emerge:
- Dependence
The team is vulnerable if one person holds the overview. - Lack of insight
Workload and capacity are difficult to assess. - Delays during changes
In case of absence or shifts, everything has to be figured out again. - More coordination, less focus
Colleagues constantly have to check in to see what's going on.
These risks often stay beneath the surface, until things go wrong.
Why this is also unsustainable for that one colleague
The problem doesn’t just affect the team or the organisation, but especially the colleague who “knows everything”. What’s often seen as commitment or experience is, in practice, not a pleasant role.
For this person, it usually means:
- Constantly having to remember everything
Deadlines, exceptions, agreements, and changes live in their head, not in a system. - Responsibility for every change
If something shifts or goes wrong, it feels like it's up to them to fix it. - Difficulty letting go
Holidays or time off feel uncomfortable, because no one else has the full overview. - Mental pressure and stress
Always being 'on', because forgetting doesn't feel like an option.
The more information someone has to store in their head, the greater the risk of mistakes and overload, especially during busy periods or unexpected changes. No one can function indefinitely as a living planning system.
That’s why this situation isn’t a compliment, but a risk. Not only for the company, which becomes dependent on one person, but also for the colleague themselves, who carries a structurally heavy burden of responsibility.
Good planning protects not only processes, but people too.
Why you shouldn’t settle for this
As long as the work continues, it may seem like nothing’s wrong. But that mostly means the system hasn’t been put under pressure yet, not that it’s well set up.
The moment circumstances change, the vulnerability of person-dependent planning becomes clear. Not because people fail, but because there’s no transferable overview.
That’s why this isn’t a matter of trust, but of organisation.
Planning must continue to function, even if someone is temporarily absent or leaves.
By addressing this in advance, you prevent problems instead of solving them afterwards.
How to prevent planning from staying in one head
You don’t have to change everything at once. With these practical steps, you can make planning transferable, step by step.
1. Make planning visible to the whole team
Ensure that everyone can see the same planning, even if it’s not perfect yet. Visibility is the first step towards shared ownership.
2. Record decisions and context
Not just what is planned, but also:
- Why something has priority
- Who is responsible
- What assumptions have been made
This prevents knowledge from existing only verbally.
3. Plan based on capacity rather than assumptions
Planning tasks without considering available time leads to structural overload. By taking capacity into account, workload becomes something you can discuss and manage.
4. Regularly check for transferability
Ask yourself and your team:
“Could someone else take over this planning today?”
If not, the knowledge is still too hidden.
5. Work from a single source of truth
Separate Excel files, lists, and chats lead to fragmentation. One central planning avoids differences in interpretation and reduces dependency.
What shared planning delivers and how vPlan helps
When planning no longer lives in people’s heads but is organised explicitly and centrally, the way teams work together changes noticeably.
Organisations experience:
- More peace of mind in teams, because the overview is available to everyone
- Less ad-hoc coordination, as information doesn’t need to be retrieved repeatedly
- A fairer distribution of workload, thanks to visibility into capacity
- Greater continuity, even during absences or changes
But perhaps even more importantly: team members gain more space to let go. Knowledge no longer rests on one person, but is shared within the team.
vPlan supports this by taking planning out of people’s heads and turning it into a shared, structured process. With vPlan:
- Planning is centrally available to everyone
- Workload is visible at both team and individual level
- Context is recorded alongside tasks and projects
- And planning is transferable
This way, planning is no longer an individual responsibility, but a team process that continues to function, regardless of who is or isn’t present.
Planning is team information, not personal knowledge
A planning that lives only in the head of one colleague may seem efficient, until the system comes under pressure. That’s when the vulnerability of this way of working becomes clear.
By making planning explicit, transparent, and transferable:
- You avoid unnecessary risks
- You support your team in their work
- And you build an organisation that relies not on individuals, but on structure
That’s not a luxury, but a requirement for sustainable collaboration.
Want to discover how your planning can become less person-dependent? See how vPlan helps teams create clarity, calm, and continuity, without everything resting on one person.
Work at vPlan
We are looking for new colleagues.
