Why is it important to use a Decision Making and Change Control Process, and Decision Log?
Project decisions are difficult. How they are managed can have direct impact on project schedules, scope, risk, cost, quality, etc. Identifying, defining and assigning key decision indicators and change processes facilitates real-time decisions and maintain project momentum. Knowing who (person or role) can make what decision and at what authority level enables teams to work with autonomy when possible, while also providing a clear escalation path for decisions that require higher level authority.
We recommend populating this template in a collaborative session with your planning team.
How to use the Decision Making and Change Control Process, and Decision Log
- Creating the Decision Making and Change Control Process is a collaborative activity conducted by the project team as the project is being planned.
- Decision making indicators will be recognizable as the team defines the project scope, identifies milestones and creates the project schedule.
- During scope definition, identifying milestones and establishing a project schedule, suggested questions for identifying decision indicators:
- How are decisions made on... scope change requests? activities that impact the project schedule?
- How do we address staff resource and skillset needs?
- If funding is required, who can make expenditure decisions and at what level?
- What is the escalation process for decisions that cannot be made at the project team level? Who escalates to who?
- Who determines if a deliverable does not meet quality standards and requires re-work?
- The above steps are started during planning meetings but may also evolve throughout the project. The template should be updated as needed.
- As decisions are made, they should be documented in the Decision Log for reference and historical purposes.