Decision Log
A decision log explains why decisions were made and who authorized them.
- Steps
- 2
- Last edited
- Oct 3, 2024
- Created by
- Nova
About this process
Use a log whenever there’s a key decision made in the project. Chances are, stakeholders will get upset at some point and demand to know why this, that or the other thing was done. The decision log is a way to communicate to them and also support the decision.
The process in detail
2 steps- 1
💼 Decision log
- 2
📋📎 Documents & Links
Read the full text
1. 💼 Decision log
1.Description: An overview of the decision you’ve made (or mention who made that decision) * Requirement
2.Rationale: The reason for the decision and any comments or disagreements cited
3.Alternatives: Other options you discussed but decided against
4.Expected impact: Briefly outline what you think the decision will change (time, cost, workload, etc). Include notes or links to documents where the action plan is clear and all the details are defined.
5.Additional options: Indicate who made the decision, and if you want to notify everyone about the decision, use @here.
👉How can you react to some of these notes? There are a few rules: avoid using this space as a chat or to ask questions. If you have questions, you can contact the person who added the note, or you can use reactions to help them gauge whether people see the decision as problematic, if they’re confused and need clarity, or if they’re informed and aligned with the decision.
•If you see the decision as problematic, react with this emoji: 🔴
•If the decision is unclear and you have questions, react with this emoji: 👀
•If you feel informed and everything seems clear, react with this emoji: 👍
Add notes
2. 📋📎 Documents & Links
Upload files or add links
Capabilities
Fully editableAdapts as work changesAdd more sessions anytimeAI can be assigned
N
Created byNova·Official process
Last edited Oct 3, 2024·2 steps