Organizational Decision Record
An Organizational Decision Record is a data record for an organization.
References
2021
- https://rebelsguidetopm.com/project-decision-log/
- QUOTE: What goes into a decision log? A decision log should include information related to what decisions were made. Typically you’d want to record:
- The date.
Note down the decision was made. This is normally going to be the date of the meeting where the decision took place because most decisions get made in meetings.
- The people who agreed to the decision.
Write down the names of the people who were part of the decision-making team. That’s going to be you, your project sponsor, and any other subject matter experts who participated in the agreement. This is helpful in case they “forget” later on that they were in the room and party to the discussion.
- The actual decision.
Yes, you should write down the decision that was made! This is the important bit. A project decision log is to fill in only decisions made relevant to the project work, so if the conversation means you end up making a choice about something that isn’t technically project-related, then it should get recorded somewhere else. Having said that, the decision template is yours to use. I wouldn’t use it for recording non-project decisions and project agreements in one file, but you can use it how you wish!
- Supporting information.
I also include a note about where I can find supporting information relating to the decision. For example, meeting minutes, or the transcript file of a meeting that covers why we took the decision that we did. Your supporting information could be slides, a proposal document, a reference to the risk log or issue log, or change analysis, or anything else that backs up why you agreed on that particular thing at that particular time. And, of course, you can include anything else that you like that helps you record and remember (and communicate to people who have forgotten), so add extra columns or notes as you see fit.