Four decision-making patterns that slow small teams down

Small teams make a lot of decisions quickly, which is one of their real advantages. They also develop decision-making habits that can calcify over time into patterns that slow everything down. Helen Redfern has seen four of these patterns come up repeatedly across very different organizations.

The consensus trap ¶

Some teams develop a norm of reaching consensus before moving on any decision. This feels collaborative and fair, and for certain kinds of decisions it is exactly right. For others, it is a way of ensuring that every decision takes three times as long as it needs to and that the person with the most patience effectively has a veto.

The fix is not to abandon collaboration. It is to be explicit about which decisions require consensus, which require input from several people but a single decision-maker, and which can be made by one person without a meeting. Most teams have never had that conversation explicitly.

The missing decision log ¶

Most organizations have records of what was decided. Very few have records of why. Six months later, when the decision is being questioned or revisited, nobody can reconstruct the reasoning. The debate starts again from scratch.

A simple decision log, even a shared document with three columns (decision, rationale, date), eliminates a significant amount of this repeated work. The barrier is usually not technical. It is the habit of treating the decision as the endpoint rather than the beginning of a record.

The wrong room problem ¶

Decisions get made in the wrong room when the people with the relevant information are not present and the people who are present do not know what they do not know. This is especially common in organizations that have grown quickly and have not updated their decision-making structures to match the new shape of the team.

The symptom is usually a decision that gets made, implemented, and then reversed or significantly modified when the people who were not in the room find out about it. The fix involves mapping which decisions require which information and making sure the right people are consistently in the room for each type.

Revisiting closed decisions ¶

Some teams have a pattern of reopening decisions that were already made, often because the decision was not clearly closed in the first place. The meeting ended without a clear statement of what was decided, who owns it, and what would need to change for the decision to be revisited.

Closing a decision explicitly, including naming the conditions under which it would be worth revisiting, reduces the amount of energy spent relitigating things that are already settled. It also makes it easier to reopen a decision legitimately when circumstances genuinely change.

None of these patterns require a restructure to address. They require a conversation and a small change in habit. The hard part is usually naming the pattern clearly enough that the team can see it.