Examples
What a reporting page is made of.
The formats a project hands over, in their working layout. What you receive is adapted to your workflow and carries your projects.
A project summary page
The status at the top, the detail under it, the next move at the bottom. A client reads the page instead of asking.
Project summary page
Four readings of the same project, one page.
An issue note
Where a problem is written down so a client can read it without alarm: what came up, what it touches, what is being done, and when it is reviewed.
Issue note
- What came up
- one plain sentence, no blame
- What it affects
- the stage, the date or the scope it touches
- What is being done
- the action, and who owns it
- When it is reviewed
- the point the client hears about it again
A problem on the page is a problem being handled. A problem in a thread is a surprise.
The update rhythm
The handover guidance in one view: the four moments the page changes, so keeping it current is a habit rather than a task.
Update rhythm
- A stage closes: the page moves it to Done with a line on what it produced
- Something waits: the page names what and whose move it is
- A stage slips: the page says so, and says what changes
- The project ends: the page closes with what was delivered and where it lives
Each moment has its line in the guidance. Nothing else needs to change.