Government IT Project Decision Log
This is a practical guide to building a decision log for a government it project project — a record of the key decisions made, by whom and why, adapted to the realities of delivering an IT project in the public sector.
What a Decision Log is
A decision log is a record of the key decisions made, by whom and why. For the full concept and how it works in general, see Decision Log. On a government it project project it plays the same role, tuned to this kind of work.
Why it matters for a Government IT Project project
Government IT Project projects live or die on delivering an IT project in the public sector. A well-built decision log gives the team a shared, explicit reference for exactly that — reducing ambiguity, aligning stakeholders, and making problems visible early enough to act. Skipping it, or doing it generically, is how government it project projects drift into avoidable delay and cost.
What to include
- Decision
- Date and owner
- Rationale
- Alternatives considered
- Impact
Government IT Project-specific considerations
Tailor the decision log to the risks that most often derail government it project projects:
- Complex procurement rules
- Public scrutiny
- Multi-stakeholder governance
Example
On a real government it project project, the decision log would be shaped by delivering an IT project in the public sector. In particular, it should explicitly account for the project’s biggest risks — complex procurement rules, public scrutiny, multi-stakeholder governance — rather than treating them as afterthoughts.