What Happens After the Synthesis

The synthesis completed a few weeks ago. The findings were strong — convergent themes across all the major stakeholder groups, a divergent finding that surprised the sponsor, three follow-up areas flagged in the action plan. The deck went to the leadership team. Everyone agreed the findings were significant. The sponsor sent a note: "Excellent work. Let's discuss next steps in the leadership sync." The sync happened. The follow-up areas were acknowledged.

Three months later, a board member asks what changed as a result of the synthesis. The head of strategy starts reconstructing. Who took what from the findings. Which follow-up areas were explored. Whether the three flagged questions ever had a session run against them. The synthesis deck is in the shared folder. The answers are not in it.

Nobody knows what happened as a result.

---

What Synthesis Produces

A strong synthesis contains real intelligence — convergent themes that reveal where stakeholder groups align without coordination, divergent findings that expose fault lines the organization hadn't named, flagged follow-up areas that point toward what the synthesis doesn't yet know. Each flagged area is a question the organization identified as worth answering. The synthesis named the gap. It didn't close it.

The follow-up areas are the most consequential part of what a synthesis produces. They are the acknowledgment that the intelligence gathered is incomplete — that convergence across groups revealed something requiring a deeper look at a specific stakeholder segment, or that the divergent finding surfaced a question the organization needs to put directly to the people who hold the contrarian view. A synthesis that identifies three follow-up areas has produced a research agenda for the next cycle.

That agenda exists in the synthesis document. It goes nowhere.

---

Why the Document Is the End

Once a synthesis becomes a deck, it is a deliverable. Deliverables get sent. They get filed. The conversation that produced them — the sessions, the briefs, the convergent pattern across stakeholder groups — is over. The deck is the product.

The follow-up sessions the synthesis implies never get opened. Not because the sponsor disagreed with the findings. Because the synthesis ended at the document, and the document has no structural link to whatever happens next. Agreement in the leadership sync is not the same as a session being scheduled. The head of strategy who found the synthesis valuable and intends to act on it still has to reconstruct the research agenda from the document, identify the right participants for the follow-up, and send invitations — all from scratch, all disconnected from the synthesis that produced the agenda.

The synthesis recommended. The follow-up requires a completely separate act of will, organization, and logistics. Most of the time, the act doesn't happen. The synthesis sits in the folder where deliverables go when they've served their immediate purpose. The follow-up areas age into observations nobody checked.

---

What the Head of Strategy Gets

The head of strategy who runs synthesis on a platform where synthesis opens into the next session works differently.

When the synthesis is generated, proposed follow-up sessions appear in the synthesis view. They are scoped to the flagged areas — the questions the synthesis identified as requiring further investigation. Each one has a recommended audience drawn from the stakeholder groups the synthesis analyzed. Opening a proposed session in Session Studio preloads the synthesis context: the specific gap it's investigating, the excerpt from the synthesis that named it, the audience it needs to reach.

The synthesis page tracks what happens next. Each proposed follow-up shows its status: still a draft, collecting responses, brief ready. The head of strategy opens the synthesis three months later and doesn't need to reconstruct what came of it. The status is there. Two of the three follow-up sessions collected responses and produced briefs. One is still a draft — it was proposed, it was never opened. That distinction is visible, not reconstructed.

The second synthesis, when it runs, has something the first one didn't: evidence of whether its recommendations were actually explored. When a new round of sessions produces synthesis, the platform can show what was recommended in the previous cycle and what the follow-up sessions revealed. A synthesis that recommended investigating a specific stakeholder group's divergent view can be compared against what those follow-up sessions found. The second synthesis doesn't start from the beginning. It builds on what the first one surfaced — and on whether the organization acted on what the first one recommended.

---

The System the Research Can Become

The board member's question from the opening — what changed as a result of the synthesis? — now has a structural answer. An org-level Outcome Dashboard tracks the full pipeline: sessions captured, briefs completed, synthesis cycles run, action plans generated, work integrated into external tools. The head of strategy doesn't need to reconstruct what the program produced. It's visible as a live count, by project, with status at each stage.

When it's time to show the board, there's a Pilot Success Report — a downloadable summary of what the organization captured and what it produced, formatted for a sponsor conversation without writing a word of explanation. The question "what changed as a result?" goes from a reconstruction exercise to a download.

A synthesis that ends with a document is a research artifact.

A synthesis that opens the next session — and tracks what each session produced — is an intelligence system.

---

Mayetik helps heads of strategy and consulting principals run synthesis programs where each synthesis proposes, tracks, and connects to the follow-up sessions that close the gaps it identifies. Start your free trial.