Operations template
Project delivery OKR template
Deliver the project on time, within budget and to the agreed scope.
Cross-team projects fail quietly: a workstream slips, a risk nobody owns becomes an issue, and the deadline moves. This template measures the three things a project board needs to see: milestones delivered on time, workstreams within budget and high risks with a named mitigation owner.
It suits projects such as a system rollout, an office move, a new country office or a merger of two programmes, where several teams must deliver to one deadline.
When to use this template
- The project crosses teams or departments and nobody has a single view of progress.
- You report to a steering committee or funder on milestones and budget.
- Risks are listed in a register that is reviewed once and then forgotten.
The goal tree
Everything below is created for you when you use the template, ready to edit. Each part is tagged with its logframe level, so the goal sits alongside a donor results framework without being rewritten.
Objective
OutcomeDeliver the project on time, within budget and to the agreed scope
A clear plan, owners for every workstream, and weekly risk reviews.
Key result 1
OutputMilestones delivered on time: 90%
Key result 2
OutputWorkstreams within budget: 100%
Key result 3
ActivityHigh risks with a named mitigation owner: 100%
Milestones
Activity- Day 7 · Project charter signed off
- Day 14 · Plan and owners confirmed
- Day 45 · Mid-point review
- Day 90 · Handover complete
First actions
Activity- Write the project charter
- Assign workstream owners
- Hold a weekly risk review
Logframe levels: Impact is the long-term change, Outcome is what changes for the people or organisation you serve, Output is what you deliver, and Activity is the work that produces it.
Example KPIs to track alongside it
These indicators are not part of the template. Add the ones that fit as extra key results or as KPIs you watch.
| Indicator | Definition | Level |
|---|---|---|
| Schedule variance | Days ahead of or behind plan for the next major milestone. | Output |
| Budget variance | Actual minus planned spend to date, by workstream. | Output |
| Open issues past due date | Issues that are not resolved by their target date. | Activity |
| Change requests approved | Scope changes approved by the project board, with their effect on time and cost. | Activity |
| Benefits realised | Benefits from the business case that are measurable three months after handover. | Impact |
How to adapt it
- Replace the generic milestones with your project's real stage gates, and assign each one to a workstream owner.
- Set 'on time' tolerance in the key result description, for example within five working days of the baseline date.
- For a fixed-scope contract, add a key result for deliverables accepted by the client.
- Link each workstream as a child goal so the project lead sees one roll-up rather than several status reports.
Frequently asked questions
Is a project an OKR or a plan?
Both. The plan holds the tasks. The OKR states what success looks like and measures it. Milestones and actions in the template bridge the two.
Why measure risk ownership rather than number of risks?
Counting risks rewards long registers. Measuring ownership checks that someone is acting on each high risk, which is what reduces it.
How is this different from the operational efficiency template?
This template is for a project with a start and end date. Operational efficiency is for improving a process that keeps running after the work is done.
Use this template
Start with this goal already set up
The objective, 3 key results, 4 milestones and 3 first actions are created in your workspace. Change the numbers, assign owners and run weekly check-ins.