01
Step one: decide the question the page answers
Start by writing the single question the page must answer, such as whether a launch will hit its date. Imagine a team building a customer portal with twelve milestones due in four months. The audience is a sponsor who checks weekly and has two minutes. The headline answer might be on track, at risk or late, followed by one sentence of reasoning. Every later element should support that answer. If a chart or number does not help the sponsor judge the date, it moves to a secondary tab or gets removed from the first release entirely.
02
Step two: choose the line and its markers
Next, define the progress line itself. For the portal example, plot completed milestones against planned ones across the calendar, with today marked clearly. Add three markers only: the planned finish, the current forecast finish and any blocked item. Choose a consistent unit, such as milestones or weighted effort, and state it beside the chart. Avoid mixing units in one view, because readers will compare them without noticing the difference. Give each marker a short label and an owner name, so a gap between plan and forecast leads directly to a person who can explain it.
03
Step three: set the update rhythm and the follow-up
Finally, decide how the page stays truthful. Name who updates each milestone, how often, and what counts as done. In the example, owners might confirm status every Thursday before the sponsor review, and the page shows the last update time so stale data is obvious. Add a short notes area for changes in scope or dates, with the reason recorded. Close the outline with a follow-up rule: any item flagged at risk for two updates triggers a brief discussion. This turns the dashboard from a display into a habit that guides decisions.