The Case for Writing Things Down: Why Documented Decisions Build Better Companies

Every company makes thousands of decisions a year. Most are small. Some are significant: a new price, a new hire, a new supplier, a change in direction. In many businesses, the reasons behind those decisions live only in someone’s memory. Months later, nobody can quite recall why a choice was made, what alternatives were considered or what was supposed to happen next. The habit of writing things down is unglamorous, but it may be one of the most underrated tools in business.

Memory is a poor record

People remember decisions in ways that flatter their judgment and fit later events. Two partners can leave the same meeting with different understandings of what was agreed. A team can repeat a failed experiment because the people who ran it last time have moved on. A written record does not remove disagreement, but it gives everyone the same starting point.

What a simple decision record looks like

Documenting decisions does not require special software or long memos. For significant choices, a few lines are often enough:

• What was decided, and when.
• Who made the decision and who was consulted.
• The main alternatives considered.
• The reasons for the choice and the key assumptions behind it.
• What success would look like and when the decision will be reviewed.

Kept in a shared document or folder, these records become a history of how the business thinks.

Writing improves thinking

The act of writing a decision down forces clarity. Vague ideas that sound convincing in conversation often fall apart when someone has to explain them in a few sentences. Writing reveals missing information, unstated assumptions and disagreements that need to be resolved. Many teams find that the discipline of drafting a short memo before a meeting leads to better discussions and shorter meetings.

Documentation scales the business

As companies grow, knowledge that lived in the founder’s head has to be shared. Written processes allow new employees to learn faster and do work consistently. Decision records help new leaders understand why the business works the way it does before changing it. And when the time comes to raise money, bring in a partner or sell the company, a well-documented business is easier to evaluate and to trust. For companies with boards, formal minutes serve a similar purpose for the most important decisions.

Start small

The goal is not paperwork for its own sake. Too much documentation becomes noise that nobody reads. Start with the decisions that matter most and the processes that are repeated most often. Keep records short, consistent and easy to find. Review them occasionally, especially when a decision did not turn out as expected, and ask what the record reveals about the assumptions behind it. Over time, a company that writes things down builds something valuable: a memory that does not walk out the door when people do, and a habit of learning from its own experience.

Putting It Into Practice: Building the Habit in a Small Team

Most teams agree that writing things down is a good idea. Far fewer actually do it consistently. The difference usually comes down to making the habit easy, visible and expected. Here is a simple way to introduce it.

1. Create one home for decisions. Set up a single shared document or folder called something obvious, like “Decision Log.” If records are scattered across email threads and chat messages, nobody will find them later.
2. Agree on what counts as significant. A useful rule of thumb: anything that commits meaningful money, changes how customers are treated, affects more than one person’s job or would be hard to reverse.
3. Use the same short template every time. The five lines described above are enough. Consistency makes records faster to write and easier to read.
4. Assign the writing. At the end of any meeting where a significant decision is made, name one person to record it within a day.
5. Schedule reviews. Put the review date from each record on a calendar. When it arrives, spend ten minutes comparing what happened with what was expected.
6. Model it from the top. When owners and managers document their own decisions, everyone else follows.

A Sample Decision Record

Here is how a short record might look for a hypothetical small business. The details are invented for illustration.

Decision: Move from weekly to biweekly invoicing for maintenance clients, starting next month.

Decided by: Owner, after discussion with the office manager and two crew leads.

Alternatives considered: Keep weekly invoicing; switch to monthly invoicing with automatic payment.

Reasons: Weekly invoices take significant office time, and many clients pay several at once anyway. Monthly would delay cash too much.

Assumptions: Clients will not pay later overall; office time saved can go to collections follow-up.

Review: In three months, compare average days to payment and office hours spent on billing.

A record like this takes a few minutes to write. Three months later, it turns a vague memory into a clear test of whether the change worked.

Common Mistakes When Documenting Decisions

• Recording only the outcome. “We chose supplier B” is far less useful than knowing why, and what was assumed about price and reliability.
• Writing too much. Long memos discourage both writing and reading. Brevity keeps the habit alive.
• Rewriting history. If a decision turns out badly, add a note about what was learned rather than editing the original record. The value lies in seeing what was actually believed at the time.
• Keeping records private. Decision logs that only one person can see do little to build shared understanding.
• Never looking back. Records without reviews are an archive, not a learning tool.

Questions Teams Ask About Written Decisions

Will this slow us down?

A few minutes per significant decision is a small cost compared with the time spent later re-arguing choices or repeating experiments that already failed.

What about confidential decisions?

Keep those in a restricted location with appropriate access. Sensitive personnel or legal matters should be handled according to your policies and, where relevant, with advice from counsel.

Where should process documentation live?

Ideally near the decision log, in a place every team member can reach. Start with the tasks repeated most often, and ask the people who do them to write the first drafts. They know the real steps, including the shortcuts and workarounds that never appear in an official manual.