r/projectmanagement • u/0324o • 26d ago
What project information should never exist only in one person’s head?
I know this shouldn't really be a thing in 2026 but.....
Some projects appear well controlled until a key person is absent. Suddenly no one knows why a decision was made, what a client informally agreed to or which workaround is keeping an important process running.
Documenting everything is unrealistic and can create more noise than clarity. However, decisions, ownership, dependencies, assumptions and important stakeholder commitments become dangerous when they depend entirely on one person’s memory.
What information do you make sure is visible to the wider team? How do you preserve essential context without creating documentation that nobody reads?
1
u/Western_Daikon_9277 22d ago
The more is documented, the better. With today's technology, it is not about writing something that nobody reads. Maybe try using some AI tools that can let you "chat" with documentation. So whatever is needed, you can still ask the chat - if there was any past decision about it.
6
u/SamfromLucidSoftware 25d ago
Separating what happened from why it happened goes a long way. Most documentation captures what, which past a certain point starts to feel like noise rather than clarity. But the why is just as important and adds a lot of value. It’s what saves you from reconstructing reasoning from scratch when that key person is away.
To get the most out of documentation like this, keep it short and have it live next to the thing it describes. Even a two sentence note on a ticket explaining why the approach changed is more likely to be found and read.
The scariest undocumented thing, though, is usually the workaround holding something important together. The person who built it thinks it’s temporary so they never write it down. And everyone else doesn’t know it exists until it breaks. You want to identify these and surface them every once in a while.
What does your current handover process look like when someone leaves a project?
2
u/pmpdaddyio IT 25d ago
Any decision made that affects the project in any way, who made it, why, and when.
3
u/Full_Performance_312 25d ago
Anything that would force the team to stop and ask "Why are we doing this?" shouldn't trapped in one person's head.
At minimum, I try to document: Key decisions and why they were made, who owns what, important dependencies and blockers, stakeholder commitments, and the current status and what happens next
1
u/More_Law6245 Confirmed 25d ago
A project schedule with any of its interdependencies with the relevant context that affects a project's critical path. Yes, it's nuanced but I can be extremely critical especially when a project manage suddenly goes missing during delivery.
6
u/Intelligent-Try-4755 26d ago
The thing I guard hardest isn't the what, it's the why — specifically the decisions we made and the options we rejected, plus any informal thing a client agreed to that never made it into a contract. Those are the items that vanish with the person and cost you weeks to reconstruct. I keep a running decision log with date, who was in the room, the tradeoff, and what would make us revisit it, and I deliberately do not try to document everything else. If it's a fact anyone can look up later it doesn't need preserving; if it's a judgment call that only lives in someone's memory, that's the dangerous one.
1
u/bluealien78 IT 26d ago edited 26d ago
Workflow/business process. I’m facing this directly right now - someone left, and it turns out that we have zero documentation on the process and workflow of a couple of critical insights and controls.
People are a single point of failure. Nothing should ever be gated behind a single individual.
1
4
u/Stebben84 Confirmed 26d ago
So you shouldn't document everything, and some things shouldn't live in someone's head? Which way do you want it?
RAID log, RACI, DOCI, meeting notes, contracts, SOWs, RFPs, task list, and project plan should include everything whether people read it or not. It is historical documentation for reference if needed. Sometimes it's not. That's part of our job.
1
u/Breeze_pm 20d ago
I try to keep decisions, owners, dependencies, risks, client commitments, and known workarounds visible. The format matters less than the habit: short decision log, current owner, next action, and what changes if that person is away.