A decision log should remain short enough to use in a live meeting. If it becomes a second project plan, it has lost its purpose. Keep supporting analysis elsewhere and link it to the choice it informs.
Decisions Before Deliverables
A polished plan can conceal a weak agreement. The team may have a timeline, a workstream map, and a weekly meeting, yet still lack a shared answer to three basic questions: what must change, who can decide, and which constraint takes priority when the plan meets reality.
Good advisory work settles those questions early. Deliverables then become evidence of decisions, not substitutes for them.
Map the decisions first
Before scheduling workshops, list the decisions the engagement is expected to resolve. Name the owner of each decision, the evidence they need, and the latest useful decision date.
This simple record exposes false dependencies. It also distinguishes a genuine executive choice from work the delivery team can resolve within its mandate.
A useful decision record
Field
Question it answers
Example
Decision
What must be settled?
Choose one service owner across all regions
Owner
Who has authority?
Chief Operating Officer
Evidence
What makes the choice defensible?
Service cost, risk, and customer impact
Deadline
When does delay become expensive?
Before the next planning cycle
Consequence
What changes once agreed?
Regional teams move to one operating cadence
Discuss the work
Put the next decision in view
Meridian Works helps leadership teams turn broad change mandates into clear choices, ownership, and an executable sequence.