A surprising amount of repeated work begins with a simple sentence: I thought we had already decided that.
In small teams, decisions are often made quickly. A few people discuss an issue, settle on an approach, and move on. The problem appears later, when the decision lives only in someone’s memory, a chat thread or a long email chain.
The team then spends time reconstructing the conversation, asking who agreed to what, or reopening a question that was already settled.
A small decision log can prevent much of that.
Record the decision, not the whole discussion
A useful decision record does not need minutes, transcripts or a long explanation. It only needs enough information for someone to understand what was decided and why it matters.
For most everyday decisions, five fields are enough: the date, the decision, the reason, the person or team responsible for carrying it forward, and the point at which the decision should be reviewed again if circumstances change.
That is usually more valuable than preserving twenty messages that led to the same conclusion.
Put decisions somewhere people can actually find them
The best place for a decision log is rarely a new standalone system. It is usually a page, table or shared document inside a tool the team already opens.
The important thing is consistency. If some decisions are in email, others in chat and others in meeting notes, people still have to search several places.
Choose one obvious home and use it for decisions that are likely to affect future work.
Not every choice deserves a record
A decision log becomes unhelpful if it captures every tiny preference. Record choices that could reasonably be questioned later, affect more than one person, change a process, commit resources, or create a rule the team will need to remember.
Those are the decisions that tend to generate rework when they disappear.
Add a review point when the decision is temporary
Some decisions are sensible for the current situation and should be reconsidered when a contract ends, a project closes, a team grows or better information becomes available.
Adding a review date or trigger prevents two opposite problems: reopening the issue too often, or letting an old decision quietly become permanent.
Use the log to reduce meetings, not create them
The point of recording decisions is not to add another administrative task. It is to remove future coordination.
Before reopening an issue, check whether a decision already exists. At the end of a meeting, record only the choices that will matter later. When a new colleague joins a project, point them to the relevant decisions instead of retelling the full history.
Done well, a decision log becomes a small piece of shared memory for the team.
Small businesses do not need heavy governance for everyday work. They do benefit from being able to answer a simple question quickly: what did we decide, and why?