Make a service project understandable from start to finish

A project can feel busy while leaving the customer unsure what has changed. Meetings and messages are activity; useful progress also includes a decision reached, a question resolved or an output ready for the next person. A simple shared record helps both sides see the difference.

Agree what the first stage will establish

Before work starts, describe the uncertainty to resolve and the output you expect. A first stage might produce an agreed specification rather than a finished implementation. Government service guidance separates discovering the problem from committing to a build; that distinction helps keep early work honest.

Write what is outside the stage. If research may show that the initial solution is unsuitable, say so. An informed decision to change direction can be a valid result when it answers the agreed question.

Keep a decision trail

After an important discussion, record the choice, the person who approved it and its effect on the next task. Avoid a transcript of everything said. A colleague joining later should be able to understand the current position without reconstructing several chat threads.

For an illustrative document project, record which version is approved for layout and which comments remain unresolved. A filename containing final is not enough if a different copy is still circulating. Keep one clearly identified current working reference.

Make waiting visible

If the project needs customer information, name what is missing, who will provide it and what work depends on it. Do the same for a provider's outstanding action. This avoids turning a shared dependency into a vague accusation that one side is slow.

Discuss changes when they appear. Explain the effect on scope, timing and responsibilities before treating an extra request as agreed work. Update the shared record after agreement, not merely the next invoice.

Close with something usable

Review the output against the purpose of the stage. Record accepted work, open points and the next owner separately. Where a handover is involved, check that the intended person can locate and use what was delivered.

Keep the record proportionate. A small assignment may need only a short dated note and a few identified files. The aim is not more administration; it is enough shared understanding to make the next decision confidently and prevent a finished conversation from being mistaken for a finished task.

Sources: Government Digital Service: How the discovery phase works.