How to Present Findings to a Client (Structure and Examples)

Present findings by leading with the answer, then the evidence that forces it, then the decision you want made. Tell the sponsor the most uncomfortable finding privately before the meeting. Keep your delivery to about twenty minutes of a sixty minute session and spend the rest on implications, objections and who does what next.

This guide is about the room rather than the document: sequencing a readout, handling a sponsor who does not like what you found, and what to do when someone disputes your evidence with an audience watching. For the written artefact, see how to structure a findings report and what to leave out.

What are findings in simple terms?

A finding is something you observed to be true, written so that a reasonable person looking at the same evidence would reach the same conclusion. It is not an opinion, an instruction or a plan. “Invoice queries are resolved by three teams with no shared queue” is a finding. “You should consolidate invoice queries into one team” is a recommendation.

The distinction matters most in the room, because the two attract different objections. Findings get challenged on accuracy. Recommendations get challenged on feasibility, cost and politics. If you blur them, every conversation about whether the fix is affordable becomes a conversation about whether you got the facts right. Keeping findings and recommendations apart in one report is the written half of the same discipline.

How do I present my findings?

Present findings in the order a decision-maker needs them, which is the reverse of the order you produced them in. You worked from data to pattern to conclusion. They want the conclusion first and the data only if they doubt it.

A workable running order for a sixty minute readout:

1. The answer, in one sentence (2 minutes). What you were asked, and what you found. If someone leaves after this, they should still know the outcome.
2. The decision you are asking for (2 minutes). Name it early so people listen with the right question in mind.
3. Three to five findings, each with its evidence (10 minutes). One claim per slide or paragraph, with the evidence underneath it, not in an appendix.
4. What you looked at and what you did not (3 minutes). Scope, period, sources, and the gap you know about. Volunteering the limitation is cheaper than having it found.
5. Options and recommendations (5 minutes). Each with a rough cost, an owner and a consequence of doing nothing.
6. Discussion (25 minutes). The largest block, deliberately.
7. Agreed actions, owners and dates (10 minutes). Written on the screen while people are still in the room.

A readout is not a viva. Nobody is marking your method, and the twenty minutes you spend proving how thorough you were is twenty minutes not spent on what the client should now do. Method earns its place when it is contested, and only then.

Two practical rules. Do not present a finding for the first time to a group; every person with a stake in it should have heard it from you individually first. And do not read the slides. If the pack can be understood without you, distribute it and use the hour for the argument.

What are examples of research findings?

A strong finding names the thing, quantifies it where possible, and stops before it starts blaming anyone. The examples below are invented, but the shapes are ones you will recognise.

• Weak: “Communication between departments is poor.” Stronger: “Sales commits delivery dates without checking capacity; in the twelve orders we traced, seven dates were set before operations saw the order.”
• Weak: “Staff find the system frustrating.” Stronger: “All nine users we observed keep a personal spreadsheet alongside the system because they cannot see order status in it.”
• Weak: “There is a lack of governance.” Stronger: “No forum has authority to stop a project once it is funded. Of the four projects that ran over, none was reviewed against its original business case.”
• Weak: “Onboarding could be improved.” Stronger: “New joiners wait an average of eleven working days for system access, and their line managers are not told when it is granted.”

Notice that each stronger version carries its own evidence and can be argued with on the facts. That is the test. If a client cannot disagree with your finding except by disagreeing with your character, you have written a judgement, not a finding.

Keep the number small. Five findings get discussed, fifteen get skimmed, and the two that mattered get lost among the thirteen that did not.

What do you do when the sponsor does not like the finding?

Tell them in private first, several days before the readout, and give them a role in the response rather than only a share of the blame. The sponsor should hear the worst of it from you alone, not from you in front of their peers.

That pre-brief has a specific agenda. Say the finding plainly. Ask whether anything in it is factually wrong, and mean it. Ask what they think the room will say. Then agree how the finding will be framed: not whether it appears, but which decision it leads to. Sponsors will accept an uncomfortable fact far more readily when they are already holding the answer to it.

If a sponsor asks you to remove an accurate finding, the position is straightforward and worth rehearsing before you need it. You will not delete it. You will state it in the least dramatic language that remains true, add their response next to it, and let the reader form a view. If they insist, ask for the request in writing. That request rarely arrives, and the asking usually ends the conversation.

Watch for the softer version of the same pressure: a request to move a finding into the appendix, to describe it as an area for further exploration, or to attribute it to “some stakeholders” when it came from eleven of twelve interviews. Each of those is deletion with better manners.

One more thing that reliably lowers the temperature. Separate the finding from the person who owns the process it describes. “The approval route has four hand-offs and no single owner” is a fact about a process. “Finance has not managed this well” is a fact about a colleague sitting three seats away, and it will cost you the rest of the meeting.

What if someone disputes your evidence in the room?

Take the challenge literally and answer it with the specific number, then move to the consequence. Most objections in a readout are not really about the evidence. They are about what the evidence implies for the person raising it, and arguing method with them for ten minutes gets you nowhere useful.

What they say	What it usually means	What to do
”Your sample is too small”	The result is inconvenient	Give the actual n, say what it does and does not support, and ask what sample would convince them
”That data is out of date”	They have a newer version, or hope they do	Name the period and the source, and ask them to send the newer figures by a stated date
”That is not how it works in our region”	Genuine local variation, often true	Accept it as a scope limit on the spot, and record it as a caveat rather than defending the general point
”We already knew that”	The finding is uncomfortable but correct	Agree, then ask why it is still true, which is the more interesting question
”Who told you that?”	An attempt to identify a source	Never say. Restate the confidentiality terms you agreed at the start

Three habits make this manageable. Bring the underlying numbers with you, even if they never leave your bag, because “I can show you the twelve orders” ends most disputes without needing to show anything. Timebox anything unresolvable: “let me check that and come back to you by Thursday” is a complete answer, and unfinished arguments in front of a steering group cost more than a two day delay. And when you are genuinely wrong, say so immediately and without decoration. A consultant who concedes one point cleanly is believed on the other four.

If a challenge survives all that and you still hold your position, put the question back to the room. “If that figure were right, would it change what we do next?” Often the answer is no, and everyone can see it.

What is the best way to show client results?

Show results against the baseline you agreed before the work started, using the client’s own measure rather than one you introduced afterwards. If no baseline was captured at kickoff, say so and describe the change qualitatively rather than inventing a percentage.

Be careful with attribution. You almost never own the outcome alone, and a claim the client cannot repeat internally without embarrassment is worse than a modest one they can. Three levels of claim, in descending order of how well they survive scrutiny:

• Output: what was produced and handed over. Always defensible, rarely interesting on its own.
• Adoption: whether the thing is in use, by whom, and how often. Usually measurable within the engagement.
• Impact: the business change. Strongest claim, hardest to attribute, and the one to make jointly with the client rather than about them.

For the readout itself, the useful move is to show the measure and the mechanism together. “Exception handling dropped from four teams to one, and the queue is now visible to the team that owns it” is checkable. “Efficiency improved significantly” invites the one question you cannot answer.

What is a summary of findings document and what goes in one?

A summary of findings is a one to two page document stating what you found and what should happen, written for people who will not read the full report. It is the artefact most likely to be forwarded, so it should survive being read alone, on a phone, by someone who was not in the room.

A workable outline:

1. Headline (one sentence): the answer to the question you were asked.
2. Findings (three to five bullets): each a single claim with one line of supporting evidence.
3. Implications (short paragraph): what follows if nothing changes.
4. Recommended next steps (three at most): each with an owner and a timeframe.
5. Decision requested: the specific thing you need from the reader.

Leave out the method, the acknowledgements, the caveats about further research and the charts that need explaining. Those belong in the report. Writing a summary of findings a client will actually read goes into the drafting in detail.

The half hour after a readout is where agreed actions quietly evaporate, because the discussion produced them and nobody wrote them down with a name attached. Some teams hand that step to software: Projan, for instance, takes the summary document in as context, asks in Slack or Microsoft Teams who owns each agreed action and by when, and writes the answers out to Confluence or Asana. Whatever the method, the rule holds. Nobody should leave the room without knowing which action has their name on it.

Frequently asked questions

How do you present research findings? Same running order as any readout, with one addition: say what your method can and cannot support before anyone asks. State the sample, the period covered and the obvious gap. For qualitative work, quote participants rather than paraphrasing them, and give the count behind every pattern you claim, even when the count is four.

What is a summary of findings example? One page for an operations review might read: headline sentence, then four findings, each a single bold claim with two lines of evidence beneath it, then three options with rough cost and owner, then the decision requested. No method section, no appendices, no charts wider than the page. If it takes longer than four minutes to read, cut a finding.

How long should a findings presentation be? Book sixty minutes and plan to talk for twenty. The value of a readout sits in the discussion, not the delivery, and a consultant still presenting at minute forty has lost the room’s attention and the chance to test the recommendation. If you cannot cover it in twenty minutes, you have too many findings.

Should you send the deck before the meeting? Send the headline and the findings, not the full pack. A sponsor who has read the answer arrives ready to discuss it, and the awkward reactions happen in private beforehand. Holding everything back to preserve a reveal only guarantees the first ten minutes are spent reading in silence.

What if the client asks you to change the report after the readout? Distinguish between accuracy and comfort. Correct anything factually wrong immediately and say so openly. If the request is to soften a finding that is accurate, offer to add the client’s response alongside it rather than delete it, and put the ask in writing so the decision to omit it belongs to the person making it.

A readout succeeds when the client argues about what to do rather than about what you found. Get the uncomfortable finding to the sponsor early, keep your delivery short enough that the discussion has room to happen, and leave with actions that have names on them.