How much detail belongs on a programme plan on a page?
Include work whose date, owner, status or dependency matters across workstreams. Keep team-level tasks in the team's delivery system unless they affect the shared programme picture.
Programme planning
A programme plan everyone can actually read
Bring multiple workstreams, milestones and cross-programme dependencies into one view—then keep that view connected as delivery changes.
Programme plans fail when the steering picture and the delivery detail become separate artefacts. Plan on a Page keeps the shared layer deliberately concise while retaining the dates and relationships needed to update it honestly.
01
What the plan needs to show
- Separate outcomes and workstreams into readable swimlanes
- Show the hand-offs that cross organisational boundaries
- Make milestones, late work, leave and blockers visible
- Move connected unfinished work when a delivery date changes
- Use the same source for the board, Kanban, calendar and status report
Plan at the level where coordination happens
A programme one-pager should not contain every team task. It should contain the deliverables, activities and milestones whose timing or status matters beyond one team.
That makes dependencies explicit without turning the page into a full scheduling system.
Keep the steering view true
When a date moves, connected successors can move with it. When work is marked blocked, the blocker register can open with its plan context already attached. Planned leave remains visible against the work it affects.
The plan therefore supports the meeting instead of needing a separate evening of preparation before it.
Give each audience the right view
Executives need the whole horizon and the exceptions. Delivery teams need the work grouped by status. A PMO needs risks, blockers, overdue work and upcoming decisions. Each view is derived from the same programme plan.
Questions people ask
Can several people edit it?
Team workspaces support editors and free viewers, with Team-wide and Restricted spaces controlling who can see each plan.
What happens when the programme changes?
Dates, bars and dependency paths are data-bound. Update the underlying plan and its Board, Kanban, Calendar, Reports and exports follow.