Confluence keeps the documents. Who keeps the decisions?

A discussion paper for organisations that already run on Confluence. Confluence helps people find and share what they know. Pohja keeps the reasoning behind the decisions that matter, so you can recover not only what happened, but why.

The renewal meeting

Picture the room. Your managed-service contract is up for renewal. The supplier’s account director has been on this account for six years. Your contract owner has been in post for eight months.

The supplier opens with: “As we agreed at the last renewal, the service credits cap at 5%.”

Did you agree that? Why? What did you get for it? Your Confluence space has the evaluation, the minutes, the signed contract and forty pages of project updates. Somewhere in there is the answer. Nobody in the room can find it, and the people who would know have left.

The supplier remembers every concession. You remember the documents.

That gap, between what an organisation has written down and what it can actually explain, is where money leaks at every renewal, every handover and every challenge from the board.

This isn’t a Confluence problem

Confluence is doing its job. It is the best place most organisations have for the work itself: the requirements, the designs, the proposals, the minutes. Nobody should move any of that.

But a document and a decision are different things.

A document is written to be worked on. It gets edited, improved, reorganised, archived. That is exactly what you want from a wiki.

A decision is different. Once it’s made, it should never quietly change. You want to know who made it, why, what they turned down, where each part of the business stood, what was promised in return, and, months later, whether it delivered. When it’s overturned, you want the old one kept, with the reason it was replaced.

Confluence can document a decision. The real question is whether you have one connected record of the reasoning behind it, and can find it when it matters. Ask a wiki to hold decisions and it does its best. It just isn’t built for them.

Where your decisions live today

If you run on Confluence, your decisions are probably in at least five places: the DACI decision template, decision lines marked on ordinary pages, decisions logged against projects, AI meeting notes from Loom, and whatever Rovo, Atlassian’s AI assistant, can find when someone asks.

They don’t join up. Atlassian’s own staff have said as much on its Community forum: a decision in meeting notes doesn’t appear in the decisions log, and there is no way to gather them into one list.

Where decisions are logged properly, in a project’s risk, issue and decision log, the log lives with the project. When the programme closes, the space is archived. The decisions don’t close with it. The supplier choice, the contract terms, the service credits conceded: they run on for years after the project team has gone.

And even the best of them is a page. The reason is an optional box. The approver is a name someone typed. The page can be edited next year. Nothing tells you it was overturned in March.

Atlassian knows the size of the prize. At its 2026 conference its chief executive, Mike Cannon-Brookes, put it plainly: “The real moat is your institutional memory: every plan, document, and decision your teams have ever made.” Its own State of Teams 2025 research found teams lose around a quarter of their time just searching for answers.

Searching harder doesn’t help when the reason was never recorded.

What changes with Pohja

Pohja sits beside Confluence and does one job Confluence was never designed for: it keeps the decision itself.

Every decision has a reason. You can’t record one without it.

Nothing is quietly rewritten. A decision is never edited. When it changes, the new one supersedes the old, and both stay, so you can always see what was decided then, and what is in force now.

The full argument is kept. The options turned down, where each part of the business stood and why, what was promised in return.

Decisions come from where people already talk. A Teams or Google Meet meeting becomes a record from its transcript, and your own people are asked before their words are kept. Quick questions across the business, Asks, become decisions without anyone writing a page.

Negotiations keep their history. Every issue, every figure in order, theirs and ours, the target, and what was traded for what.

Supplier reviews stay honest. Each month’s review, with anything outside tolerance raised as a decision someone has to take.

Value is tracked, not claimed. What each decision was said to be worth, who said so, and whether that figure was ever confirmed.

This isn’t more documentation for its own sake. Pohja keeps the context you’ll need when a decision is challenged, revisited or used to make the next one, and little else.

And the reasoning is your people’s, not a machine’s. Where AI helps, reading a meeting transcript to find what was decided, it suggests; your people decide what is kept, and the record always shows which is which.

Your Confluence pages stay exactly where they are. Pohja holds the decisions they led to.

Where it pays

At the renewal. Go back to that room. This time your contract owner opens the record of the last renewal: the 5% cap, who agreed it, the reason, and what the supplier gave in return. The supplier’s memory is no longer the only one at the table.

At the handover. People leave: around a third of UK workers changed employer or left work within a year, on CIPD’s analysis of ONS data (June 2024). Their Confluence pages stay behind, but the reasoning usually walks out with them. With Pohja, every decision they made is still there under their name, with the why attached.

On a major project. Plans change as assumptions shift, risks surface and people disagree. Confluence keeps the latest version of the plan. Pohja keeps why it changed: who argued for what, what was traded away, and which assumption turned out wrong, so the next project starts from the lesson, not from scratch.

In front of the board. “What has this programme actually delivered against what we were promised?” Pohja holds what each decision was said to be worth, who said it, any revision, and the outcome. That is an answer, not a slide someone builds the night before.

When you’re challenged. An auditor, a regulator or a new chief executive asks why a risk was accepted. You can show what was known at the time, what was considered, and who decided, on a record nobody could have tidied up afterwards. It won’t prove the decision was right. It will show, beyond argument, how it was made.

Questions worth asking

Try these on your own organisation. If the answers come easily, you may not need us. If they don’t, it’s worth a conversation.

1. Pick your largest supplier contract. Could someone who wasn’t there explain, in ten minutes, why that supplier won, and what you conceded to sign them?

2. Of the decisions in your Confluence space, how many have since been overturned? Would a newcomer be able to tell?

3. When your last senior manager left, what did they decide that nobody else could now explain?

4. Your last board paper claimed savings from a programme. Could you trace each figure back to the decision that promised it?

5. If your supplier’s account team and your own sat side by side, whose memory of the last negotiation would be better?

Keep the documents. Keep the decisions too.

You’ve already invested in Confluence, and you should keep getting value from it. Pohja doesn’t ask you to change that. It asks a simpler question: when the people who made your most important decisions have moved on, will your organisation still know why?

Confluence keeps what you wrote. Pohja keeps what you decided, and why.

The contract comes up for renewal shows it in four screens. Confluence, DACI, Loom and Rovo are Atlassian’s trademarks; Pohja is not affiliated with Atlassian.