Why 'Didn't We Already Decide This?' Is the Most Expensive Question in Your Team

You know the scene. Someone suggests switching the project tracker, changing the stand-up time, or resurrecting an old campaign idea. Half the room says, 'Hang on, didn't we look at this already?' The other half shrugs. Twenty minutes later, you're deep in the same debate you had in March, with the same points, the same friction, and no more certainty than before.

It's not that your team is disorganised. Most UK teams are decent at writing down actions: who's doing what, by when, and what 'done' looks like. What we're less good at capturing is the decision itself — the reasoning, the trade-offs, and the quiet agreement that made one option win over another. That gap is what turns a normal working week into a recurring episode of Groundhog Day.

The difference between an action and a decision

An action log tells you what happens next. A decision log tells you why it happened at all. They're related, but they do different jobs.

Take a simple example. The action might be: 'Move the team stand-up to 9:30am.' Useful, but thin. The decision behind it might be: 'We chose 9:30 over 8:45 because two people do the school run, and the later slot still leaves time before client calls.' That's the bit that matters six months later when a new joiner asks whether 8:45 might be more efficient.

Without the reasoning, the debate restarts from zero. With it, someone can paste a link and say, 'Here's what we considered — has anything changed?' That's not shutting down conversation. It's giving the conversation a starting point.

Why the graveyard fills up

Most decisions don't get lost because people are careless. They get lost because they live in places that weren't built to hold them: a fleeting Slack thread, a Teams call nobody minuted, a corridor chat after the meeting, or the head of whoever chaired it. When that person goes on leave, changes role, or simply forgets, the rationale goes with them.

There's a British politeness factor too. Revisiting a past choice can feel awkward, like you're accusing someone of wasting time. So instead of saying, 'We already settled this,' people humour the debate. The result is a strange kind of theatre: everyone half-remembers the original conversation, nobody wants to be the one who says 'we've been here before', and the team spends another hour circling the same square.

Then there's ownership. A decision log with no owner becomes a digital graveyard: a document created with good intentions, visited twice, and never touched again. It's not a tool problem. It's a habit problem.

A decision log that fits your existing stack

You don't need new software, a consultant, or a twelve-column spreadsheet. You need one page, a simple structure, and a rule about when to use it.

Start with a pinned page in your existing workspace — a Kula team space, a Notion page, a Confluence doc, or a channel canvas. Keep it in the place people already look, not in a separate tool that becomes another tab nobody opens.

A workable template is deliberately boring:

• Date — when the decision was made.
• Decision — one sentence, in plain English.
• Context — why we needed to decide, and what constraint we were under.
• Alternatives considered — a short list, ideally with the reason each was rejected.
• Owner — who is accountable for it staying useful.
• Review date — when we'll check whether it's still working.
• Status — active, superseded, or parked.

The rule for adding entries should be equally simple: if a conversation took more than ten minutes and affects more than one person, it goes in. Keep entries to three or five lines. A log nobody writes is worse than no log at all.

To make it stick, attach the habit to a ritual you already have. At the end of a meeting, ask one person to add the entry before everyone disperses. Rotate that role so it doesn't become a permanent admin job for the most organised person in the room. Link the log from meeting notes and pin it in the relevant channel. The easier it is to find, the more likely it is to be used.

Make revisiting normal, not confrontational

The real magic is the review date. Decisions aren't vows. They're working hypotheses made with the information available at the time. Giving each one a built-in expiry — three months, six months, or before the next budget cycle — turns revisiting into routine maintenance rather than a challenge to someone's judgement.

When the review date arrives, the question isn't 'Who was wrong?' It's 'Is this still the best option given what we know now?' If the answer is no, change it and note why. That's the log doing its job, not failing.

Language matters here. Swap 'We already decided this' for 'Let's check the note and see if anything has changed.' Swap 'That was a bad call' for 'What's different now?' A decision log should feel like a shared memory, not a paper trail for blame.

It also helps to log the reopening. If a decision changes, add a line: 'Reopened because client volumes doubled' or 'Reopened after new pricing came in.' That's not failure. That's history.

The fifteen-minute monthly tidy

Once a month, give the log a quarter of an hour. Mark superseded entries, add anything that slipped through, and check upcoming review dates. If people have stopped adding entries, don't make it a disciplinary matter. Just add the missing ones yourself and mention it in the next team catch-up. The goal is a living record, not a perfect one.

UK teams have some natural checkpoints worth using: the end of the financial year, the run-up to the summer holidays, and the pre-Christmas handover. If a decision is made before a period when half the team will be away, write it down. Future-you — and the person covering your leave — will thank you.

What good looks like

You'll know it's working when the phrase 'Didn't we already decide this?' stops being an accusation and starts being a hyperlink. The debate doesn't vanish, but it gets shorter and better informed. New starters can read the reasoning instead of absorbing it by osmosis. People on holiday can catch up without a thirty-minute handover call.

A decision log isn't bureaucracy. It's a small act of respect for everyone's time, including your own. Start with one page and one entry this week. The next time the same argument surfaces, you'll have something more reliable than memory: a link, a date, and a reason.