What clients really need from progress reports

A progress report is often treated as a record of activity: meetings held, tasks completed, research conducted and milestones reached. Yet clients rarely struggle to find evidence that work is happening. Their real difficulty is understanding what the work means, what has changed and what decision deserves their attention next.

This information gap becomes costly when a report is accurate but not useful. A senior stakeholder in Sydney may need a clear choice before a steering meeting, while a delivery team in Melbourne needs to know which assumptions have been tested. Both need a view of progress that reduces uncertainty without hiding the complexity of the work.

Activity does not equal progress

Consultants often report inputs because inputs are easy to count. Interviews completed, workshops delivered and prototypes produced can create an impression of momentum. These measures matter, but they do not explain whether the service, product or customer experience is becoming more valuable.

Clients need a connection between action and outcome. A stronger report might state that six interviews revealed a recurring barrier for regional customers, that a prototype reduced confusion in testing, or that an employee journey contains a preventable delay. The shift is from “what we did” to “what we learned and why it matters”.

This distinction is especially important in Australian organisations, where projects can involve dispersed teams across Brisbane, Perth and regional locations. A concise explanation of the evidence helps people make decisions without requiring every stakeholder to attend every research session.

The hidden questions behind a status update

Most clients are silently asking four questions: Are we still solving the right problem? What evidence supports the current direction? What risks could affect time, cost or adoption? What do you need from us now? A report that answers these questions is more useful than one that simply follows a project template.

The format itself can support better decisions. Thoughtful choice architecture can guide readers towards the critical implication, rather than presenting ten equally weighted updates. This might mean placing the decision required at the top, grouping findings by consequence and using plain language instead of internal project terminology.

Australian business customs make this clarity valuable. A report circulated before a Friday meeting or an end-of-financial-year budget discussion may be skimmed between competing priorities. Readers need to see the commercial or customer implication quickly, whether the project concerns a bank in Sydney, a government service in Canberra or a retailer operating across the states.

A reporting model built around decisions

A practical report can separate information into four layers. The first records delivery: what has been completed and what is underway. The second explains evidence: what research, data or observation supports the current view. The third identifies implications: how the evidence affects customer behaviour, employee experience or business performance. The fourth makes the next decision explicit.

This structure also makes uncertainty easier to communicate. Instead of presenting a recommendation as settled fact, the report can show what is known, what remains provisional and what experiment would reduce uncertainty. That is particularly useful in service design, where behaviour may vary between metropolitan customers, remote communities and different frontline contexts.

A good progress report should make the next conversation sharper. It might ask for approval to test a revised Medicare booking journey, release a prototype to contact-centre staff or investigate why customers abandon an online application. The report becomes a decision tool rather than an archive.

Recommendations for more useful client updates

The strongest reporting rhythm is usually predictable, brief and connected to action. A weekly update may be appropriate during discovery or implementation, while a fortnightly report can work for a strategic research programme. The frequency matters less than giving clients a reliable way to see movement, meaning and responsibility.

Leaders who want to improve how teams communicate progress can also draw on practical leadership learning, particularly when reporting requires constructive challenge between consultants, executives and operational teams. Psychological safety helps people surface weak evidence early rather than polishing uncertainty into a reassuring status colour.

Useful recommendations include:

• Start with the decision, risk or opportunity that deserves attention.
• Distinguish completed activity from validated progress.
• Link every major finding to a customer, employee or business consequence.
• Show confidence levels and explain important evidence gaps.
• Name the person responsible for each next action and its due date.
• Use one clear visual summary before adding supporting detail.

From reporting performance to creating trust

Clients do not expect every project to move in a straight line. They expect to know when the direction changes, why it changed and what the change requires from them. A report that makes trade-offs visible can increase trust, even when it contains bad news about a delay, failed test or weak assumption.

The information gap in progress reports is therefore a service-design problem. The reader is a user with limited time, competing goals and predictable attention constraints. Designing the report around that context improves comprehension and increases the chance that insight becomes action.

The same behavioural principles can strengthen conversations around recommendations. For example, understanding the chameleon effect in sales can help consultants build rapport without imitating clients mechanically. Trust grows when the tone, level of detail and recommendation style fit the client’s real decision environment.

When progress reporting becomes a deliberate experience, every update can reduce uncertainty, focus attention and support better choices. Nick Naumof helps organisations apply behavioural science to services, customer experiences and employee experiences through research, consulting, workshops and training. Engage him to redesign the way your team communicates evidence and moves important decisions forward.