Example
How to synthesize a client workshop without turning every sticky note into a finding
Clustering every note can make frequency look like a finding and facilitator language look like client truth. Louise must choose the strongest supported themes, preserve contradictions, or ask a bounded follow-up before drafting conclusions.
Produce a synthesis that separates evidence, interpretation, disagreement, and the decision the client actually faces
Friday's recommendation and the rule that note count is not a finding
Keep Friday's recommendation separate from note counts and repeated language
Keep the decision date beside the uncertainty in the themes
The largest-theme, strongest-evidence, and targeted-follow-up paths Louise can test
Compare the largest theme, strongest user evidence, and one targeted follow-up
Test each theme against its strongest and weakest user example
Separate observed workshop words from the team's interpretation before naming findings
Four meanings of simple, the strongest and weakest user examples, and their source context
Preserve the four different meanings of simple as source evidence
Make the evidence mismatch visible instead of rewarding note count
The clarification question Louise owns as an unsent draft until she chooses follow-up
Keep the clarification question as an unsent draft until Louise chooses the follow-up path
In You.one’s Superboard view, the Workshop evidence Board separates the client question, synthesis work, exact note groups, clarification drafts, and findings the client has actually reviewed or accepted.
Open Themes, contradictions, or follow-up as the consequential Card Room. Start by linking each candidate finding to exact workshop evidence and marking who inferred the language.
After an explicit request, Ava can group only visible anonymized notes and surface contradictions. Ava cannot disclose client material, invent consensus, contact participants, submit findings, or claim acceptance; Louise and the client retain authority.
The loudest theme is not a finding if four groups used the same word differently
The work has a clear center: Produce a synthesis that separates evidence, interpretation, disagreement, and the decision the client actually faces.
Organizing the evidence does not authorize the software to decide: 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. Authority does not move to the software: Louise owns synthesis judgment and the recommendation she will defend. The client owns permissions and Friday's decision.
Available today
Name the work in plain language
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 something already awaiting another person. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| Friday's recommendation must separate evidence, interpretation, and disagreement; note counts are not findings | Decision promise | Keep Friday's recommendation separate from note counts and repeated language |
| Follow the largest theme, the strongest user evidence, or one targeted follow-up | Themes testing | Compare the largest theme, strongest user evidence, and one targeted follow-up |
| Four meanings of simple | Source evidence | Preserve the four different meanings of simple as source evidence |
| Test each theme against its strongest and weakest user example | Themes testing | Test each theme against its strongest and weakest user example |
| Draft the user-example clarification question | Questions to send | Keep the clarification question as an unsent draft until Louise chooses the follow-up path |
| Separate observed words from the team's interpretation | Themes testing | Separate observed workshop words from the team's interpretation before naming findings |
| Loudest theme, weakest user examples | Source evidence | Make the evidence mismatch visible instead of rewarding note count |
| Client decision due Friday | Decision promise | Keep the decision date beside the uncertainty in the themes |
Available today
Workshop to decision: separate the kinds of attention
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.
The Lists use Louise's own language so actions, evidence, open questions, and decisions do not collapse into one queue. A separate place for replies is useful only after Louise has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Decision promise | Friday's recommendation and the rule that note count is not a finding |
| Themes testing | The largest-theme, strongest-evidence, and targeted-follow-up paths Louise can test |
| Source evidence | Four meanings of simple, the strongest and weakest user examples, and their source context |
| Questions to send | The clarification question Louise owns as an unsent draft until she chooses follow-up |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Louise has made visible around “Follow the largest theme, the strongest user evidence, or one targeted follow-up.” Louise supplies the evidence, checks Ava's work, and decides what belongs in the Room.
Current Ava can prepare help after an explicit request. She cannot make the choice, represent Louise, watch other work on her own, or contact anyone.
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: in “Follow the largest theme, the strongest user evidence, or one targeted follow-up,” group the visible evidence by option and leave the decision open
Available today
One Card Room for the consequential choice
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.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Follow the largest theme, the strongest user evidence, or one targeted follow-up” from the visible evidence. Ava can work from the context Louise deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Louise's call remains explicit: Louise owns synthesis judgment and the recommendation she will defend. The client owns permissions and Friday's decision.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | 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 | Keep Louise's request and Ava's attributed response with the work |
| Pulse | 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 |
Build only enough Board to make the next decision
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.
Swipe or scroll sideways to see every column.
| Step | Action |
|---|---|
| 1. Protect Friday's decision | Put the recommendation and no-note-count rule on Decision promise |
| 2. Preserve source differences | Put Four meanings of simple and the weak-example mismatch on Source evidence |
| 3. Keep clarification unsent | Draft the user-example question on Questions to send |
| 4. Separate words from interpretation | Put observed words and team interpretations on Themes testing |
| 5. Choose the synthesis posture | Open Follow the largest theme, the strongest user evidence, or one targeted follow-up |
Where this example stops
- This is a fictional example, not a customer story.
- 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.