The Documentation Habit: Writing Things Down at Work

The Undocumented Workplace

In most organizations, critical knowledge exists in two places: individual people's heads and scattered chat messages. When someone asks "how does this process work?" or "why did we decide that?", the answer requires finding the person who knows and hoping they remember.

This state — where institutional knowledge is oral rather than written — creates several problems:

• Knowledge loss: When people leave, their knowledge leaves with them.
• Repeated questions: The same questions are asked and answered repeatedly because answers are not captured.
• Slow onboarding: New team members spend weeks asking questions that could be answered by documentation.
• Decision amnesia: Teams revisit decisions because the reasoning behind previous decisions was never recorded.
• Communication overhead: Information that could be read is instead communicated verbally, consuming multiple people's time.

The documentation habit — consistently writing things down in accessible locations — addresses all of these problems. It is not about creating bureaucratic paperwork. It is about converting transient knowledge into persistent, accessible knowledge.

What to Document

Decisions and Their Reasoning

When your team makes a significant decision, write down:

• What was decided
• Why it was decided (the alternatives considered and the reasoning for choosing this option)
• When it was decided and who was involved

This prevents the common cycle where teams revisit decisions because no one remembers why the original decision was made. When someone asks "why do we do it this way?", you point to the document rather than reconstructing the conversation from memory.

Processes and Procedures

Any process that is repeated regularly and could be performed by someone else should be documented. This includes:

• How to perform routine tasks (filing reports, running processes, updating systems)
• Step-by-step procedures for complex workflows
• Checklists for recurring activities
• Troubleshooting guides for common problems

The test: if you were absent for a week, could a colleague perform this task using your documentation alone?

Meeting Outcomes

After meetings where decisions are made or actions are assigned, capture:

• Key decisions
• Action items with owners and deadlines
• Open questions and next steps

This does not require formal minutes — three to five bullet points shared in an email or posted in a shared channel takes two minutes and prevents the post-meeting ambiguity that wastes hours.

Project Knowledge

For projects you lead or contribute to, document:

• Project goals and scope
• Key stakeholders and their roles
• Technical architecture or approach
• Status and progress
• Lessons learned upon completion

This documentation serves future teams working on similar projects and preserves institutional learning that would otherwise be lost.

How to Document Efficiently

The 5-Minute Rule

If writing something down takes more than five minutes, you are over-documenting. Documentation should be brief, clear, and immediately useful — not comprehensive, polished, or perfect.

A decision record: three sentences. A process document: numbered steps with brief descriptions. Meeting notes: bullet points of decisions and actions. None of these require elaborate writing.

Write for Your Audience

Your documentation audience is your future self and your colleagues — people who need information quickly and will skim rather than read thoroughly. Write accordingly:

• Use headings to organize content
• Use bullet points for lists and steps
• Bold key information so skimmers can find it
• Keep sentences short and jargon-free
• Include examples when a concept is abstract

Document Where People Will Find It

The location of documentation matters as much as its content. Documentation buried in a personal folder that no one knows about is effectively nonexistent.

Place documentation where your team naturally looks for information:

• Team wiki or knowledge base (Confluence, Notion, Google Sites)
• Shared drive with a clear folder structure
• Project management tool (alongside the relevant project)
• Pinned messages in team channels

Establish team conventions for where different types of documentation live, and follow them consistently.

Update, Don't Abandon

Outdated documentation is worse than no documentation — it provides incorrect information with an appearance of authority. When processes change or decisions are revised, update the relevant documents. A brief note — "Updated Dec 2026: Changed approval threshold from $5K to $10K" — maintains accuracy with minimal effort.

Building the Daily Documentation Habit

After Every Meeting

Within five minutes of each meeting, write three to five bullet points: what was decided, what was assigned, and what remains open. Post or send these immediately. This habit takes one to two minutes per meeting and prevents the information loss that occurs when meeting outcomes go unrecorded.

After Every Problem Solved

When you solve a problem — a technical issue, a process question, a workflow obstacle — take two minutes to document the problem and the solution. The next person who encounters the same problem (often you, six months later) will find the answer immediately instead of repeating the troubleshooting process.

Before Going on Vacation

Before any absence of three or more days, write a brief handoff document:

• What you are currently working on and its status
• What deadlines or deliverables are due during your absence
• Who should be contacted for specific questions
• Where to find important files or information

This practice prevents the chaos that often follows someone's absence and demonstrates professional reliability.

The End-of-Week Summary

Once per week, write a brief summary of your key accomplishments, decisions, and next steps. This serves triple duty: it provides documentation for your team, serves as preparation for performance reviews, and reinforces your own awareness of your contributions.

Overcoming Documentation Resistance

"I Don't Have Time"

Documentation takes less time than not documenting. The five minutes spent writing a process document saves the 15 minutes spent answering questions about that process — every time it comes up. Over a year, a single well-placed document saves hours of repeated explanation.

"No One Reads Documentation"

People read documentation when it is discoverable, current, and concise. If your team does not read documentation, the problem is usually findability (they cannot locate it), accuracy (past documentation has been wrong), or verbosity (documents are too long to scan quickly). Address these three issues and readership follows.

"Things Change Too Fast to Document"

Document the current state with a date. When things change, update the document with a new date. Versioned documentation is more useful than no documentation. The "things change" objection assumes documentation must be permanent — it does not. It needs to be current.

"That's Not My Job"

Documentation is everyone's job. Waiting for someone else to document the knowledge in your head — a technical writer, a manager, an administrator — means the knowledge remains undocumented until it is lost. The person most qualified to document something is the person who knows it.

The Documentation Culture

Individual documentation habits are valuable. Team-wide documentation habits are transformative. If you lead a team or influence team culture:

• Model the behavior: Document your own decisions, processes, and meeting outcomes consistently.
• Reference documentation: When someone asks a question that is documented, point them to the document rather than answering verbally. This trains the team to check documentation first.
• Celebrate good documentation: When someone writes a helpful document, acknowledge it. "That onboarding guide you wrote saved us hours with the new hire."
• Include documentation in workflows: Make "document the outcome" a standard step in project completion, decision-making, and process development.

Two minutes after each meeting. Five minutes for a process document. A brief note after solving a problem. The documentation habit is an investment in your team's future efficiency — and in your own reputation as someone who adds lasting value.