How to synthesize a client workshop without turning every sticky note into a finding

Louise is a fictional 29-year-old service designer synthesizing a two-day client workshop in Halifax, Nova Scotia. The wall has 180 notes, four stakeholder groups used the same words differently, a decision is due Friday, and the loudest theme has the weakest supporting examples.

Repetition makes one theme look dominant even though four stakeholder groups used the word simple to mean different things.

The loudest theme has the weakest user examples, and Friday's decision cannot honestly collapse that contradiction into a vote count.

In You.one's Superboard view, Louise can give “Produce a synthesis that separates evidence, interpretation, disagreement, and the decision the client actually faces” a Board of its own. That Board connects source evidence, unresolved questions, decisions, and accountable judgment; opening “Follow the largest theme, the strongest user evidence, or one targeted follow-up” creates a Room for its evidence, discussion, state, and decision.

The mission is specific: Produce a synthesis that separates evidence, interpretation, disagreement, and the decision the client actually faces.

The consequential choice is not something a board or an AI should quietly make: Whether the recommendation follows the largest theme, the strongest user evidence, or asks for one targeted follow-up before choosing.

You.one can keep the work, evidence, and “Follow the largest theme, the strongest user evidence, or one targeted follow-up” decision visible through its Superboard view. The Owner boundary stays explicit: Louise owns synthesis judgment and the recommendation she will defend. The client owns permissions and Friday's decision.

The Workshop to decision Board gives this mission one durable operating picture. Louise can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.

Its Cards deliberately distinguish actions, evidence, and decisions while keeping unsent questions in owned work. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Louise's situation: “Follow the largest theme, the strongest user evidence, or one targeted follow-up” is the live choice, “Four meanings of simple” holds evidence, and “Draft the user-example clarification question” is still work Louise controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.

Opening the Card gives the visible item durable depth. Stage can hold Synthesis-decision brief: Place theme counts, source examples, contradictions, stakeholder language, and Friday's decision together. Live choice: Whether the recommendation follows the largest theme, the strongest user evidence, or asks for one targeted follow-up before choosing.. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Louise will decide whether the recommendation follows the largest theme, the strongest user evidence, or asks for one targeted follow-up before choosing.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Synthesis-decision brief and this Card Room's visible notes and left “Follow the largest theme, the strongest user evidence, or one targeted follow-up” with Louise.”

A useful Card Chat request would be: “Using only this Card Room, compare following the largest theme, following the strongest user evidence, and asking for one targeted follow-up. Cite only notes visible in this Room. Do not write the client recommendation, contact stakeholder groups, or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. She does not gain authority over the decision merely because the context is organized.

Louise's call remains explicit: Louise owns synthesis judgment and the recommendation she will defend. The client owns permissions and Friday's decision.

These requests use the visible supported context inside the “Follow the largest theme, the strongest user evidence, or one targeted follow-up” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Louise must provide the relevant facts and check the result.

Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Louise, watch other Lists, or act outside this Card Room.

Louise owns synthesis judgment and the recommendation she will defend. The client owns permissions and Friday's decision. Ava cannot turn workshop notes into client approval or represent the client.

A Friday posture that follows the largest theme, the strongest user evidence, or one targeted follow-up—not a sticky-note count.

• Request idea: using only this Card Room, compare following the largest theme, following the strongest user evidence, and asking for one targeted follow-up. Cite only notes visible in this Room. Do not write the client recommendation, contact stakeholder groups, or choose for me.
• Request idea: use only the Synthesis-decision brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
• Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously

A digitized sticky-note wall is enough when the repeated themes have one shared meaning and the strongest examples support the same Friday recommendation.

It starts to break when four meanings of simple and the loudest theme's weak user examples must inform the same recommendation posture.

The Workshop to decision Board earns its place only when the familiar tool—a digitized sticky-note wall—can no longer keep the reason, Synthesis-decision brief, conversation, current state, decision, and history connected.

Louise should rename every List or Card that feels artificial. This recipe succeeds when “Follow the largest theme, the strongest user evidence, or one targeted follow-up” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

The useful future step is timely orientation: Ava may surface “Follow the largest theme, the strongest user evidence, or one targeted follow-up” when new evidence follows “Draft the user-example clarification question”, explain what changed in the Synthesis-decision brief, and stop at the named Owner's authority boundary.

A future unified You.one experience could carry relevant context from “Follow the largest theme, the strongest user evidence, or one targeted follow-up” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action would still require the applicable capability, connection, grant, and human authority.

• Louise is fictional and is not a customer, testimonial, research participant, or disguised real person.
• This fictional example is not customer-research, privacy, confidentiality, representation, or professional consulting advice; the team must preserve source context and own the recommendation.
• It does not show Ava completing external actions or contacting anyone for Louise.
• It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.