Interview & workshop synthesis
Interview and workshop synthesis handles the evening job on every engagement: turning a week of stakeholder conversations into something the team can work from. It reads the notes and workshop output, groups what was said into themes, attributes each point to the conversation it came from, and keeps the disagreements visible. The engagement manager approves the synthesis before it enters the workspace.
Step by step
Collect notes and outputs
Interview notes, workshop captures and any recorded transcripts are read from the engagement folder as the team drops them in.
Group the points into themes
Points that recur across conversations are grouped, with the theme named in the stakeholders' own language.
Attribute every point to source
Each point keeps the role and the session it came from, so weight can be judged rather than assumed.
Keep the contradictions visible
Where two stakeholders disagree, both positions are shown against each other instead of being resolved into a bland middle.
Mark the thin areas
Themes resting on a single conversation are flagged as thin, which tells the team who still needs to be interviewed.
Manager approves the synthesis
The engagement manager reviews and approves before the synthesis is written to the engagement workspace and shared with the team.
Exactly what this agent can see, touch and change
The same five controls sit behind every ollo agent. These are this one's settings — visible before you build it, not buried in an admin screen afterwards.
Context
What reaches the modelTeams running a heavy interview programme in a short diagnostic window, where notes pile up faster than anyone can read them back.
Escalation
When it asks a personThe engagement manager approves the synthesis before it is written to the engagement workspace
Applications & Rights
Which tools it uses, and what it may do in each
Google DriveRead only
DropboxRead only
NotionReadWrites newCreates new records or documents. Never edits, moves or deletes anything that was already there.Verification
How you know it’s rightEvery claim links to the document it came from. A statement the agent cannot cite does not make it into the output — which is what makes the result reviewable in minutes rather than re-read end to end.
Who it’s for
Teams running a heavy interview programme in a short diagnostic window, where notes pile up faster than anyone can read them back.
What you’ll need
- Notes folder connected
- Stakeholder roles recorded
- Attribution rules agreed with the client
- Engagement manager to approve
What you get
- A themed synthesis with attribution
- A list of contradictions to resolve
- A note of who still needs interviewing
What it doesn’t do
It groups and attributes what people said. It does not decide which stakeholder is right, and it will not promote a single strong opinion into a finding.
We build the first one with you
Not a template you configure alone. We sit with your team, build it on real data, and hand over the controls.
Scope
One session with the people who actually do the work. We agree what the agent reads, what it may write, and who approves.
Co-build
Built on your own data, not a sandbox. You watch it being made, so you know why it behaves the way it does.
Handover
You own the controls. Change the context, tighten the rights, move the approval gate — without coming back to us.
Parts of the work currently spread across the categories below. It does not replace any of those products outright.
Frequently asked
Can we keep interviews anonymous?
Yes. If the client was promised anonymity, the agent attributes to a role or a group rather than a name, and that rule is set once during the co-build. Attribution rules are worth agreeing before the first interview, not after.
What if the notes are rough?
It reads them as they are and marks where a point rests on a fragment. Rough notes produce a synthesis with more flags in it, which is a fair signal that a follow-up conversation is needed.
Does it decide what the findings are?
No. It produces themes with evidence attached; the findings are the consultants' judgment. The distinction matters, because a finding is something the firm stands behind and an agent cannot stand behind anything.
Can the client see the synthesis directly?
Only if you share it. The output stays inside your engagement workspace under your permissions, and nothing is sent to the client by the agent. Most teams share a rewritten version rather than the raw synthesis.