Decision Log in Confluence: Record Project Decisions
Keep a decision log in Confluence so the team never argues about the same thing twice: the date, the decision, why, and who owns it. Add a new decision to a real project page.
Step by step
Why a decision log
- Decision log. Three weeks after a meeting, nobody remembers what was decided, or why. A decision log fixes that. Let me add a decision to our project's log in Confluence.
- Four columns. This is the log. One row per decision, with four columns. The date, the decision, why we made it, and who owns it.
Add a decision
- Edit. Click edit.
- New row. Click in the last row, and press control, alt and the down arrow. Confluence adds an empty row below.
- The date. Type the date you decided it.
- The decision. Then the decision, in one sentence.
- Why. Then why. This is the column people will thank you for later.
- Owner. And the owner, the person who made the call.
Share it
- Update. Click update to save it for everyone.
- In the log. The new decision is in the log. Link to this page from your meeting notes, so every decision has one home.
Recap
- Date, decision, why, owner. So, one row per decision. The date, the decision in one sentence, why, and who owns it. Add it the same day you decide. Subscribe for more Confluence tips for business analysts.
