Example
How to develop a conference talk proposal from evidence instead of a clever title
A clever abstract can promise evidence Mei is not yet allowed to share. She must center the public incident lesson, seek clearance for a bounded migration story, or hold that material for another proposal before the CFP closes.
Submit one useful talk whose public evidence, audience promise, and employer boundaries are all explicit
Why this mission matters and what it must not consume
Hold the mission and boundary: submit one useful talk whose public evidence, audience promise, and employer boundaries are all explicit
The small set of work that can change this mission now
Hold the live choice—whether to center the incident, the migration decision, or a general method that uses sanitized examples—so Mei can decide from the evidence in this Room
Outline an opening that makes one audience promise without using uncleared evidence
Draft a clearance request that names the migration result and exact internal details under review
Write one sentence stating what an attendee should be able to do after the talk
What Mei knows, where it came from, and what remains uncertain
Separate the public incident timeline, migration result needing review, and unavailable internal numbers
Hold the incident sequence already cleared for public discussion
Keep the result out of the abstract until the employer decides what may be shared
Keep the submission rules beside the evidence boundary
In You.one’s Superboard view, the Talk worth giving Board separates the audience learning promise, proposal paths, public evidence, material awaiting clearance, and only wording Mei can truthfully submit.
Open Public incident, cleared migration, or hold as the consequential Card Room. Start by marking every claim as already public, requires clearance, or unavailable.
After an explicit request, Ava can structure or compare visible claims but cannot clear confidentiality, invent numbers, submit the CFP, or speak for Mei’s employer. Mei owns authorship and submission; authorized people own clearance.
Talk worth giving has one live choice: Incident, migration, or method
The work has a clear center: Submit one useful talk whose public evidence, audience promise, and employer boundaries are all explicit.
Organizing the evidence does not authorize the software to decide: Whether to center the incident, the migration decision, or a general method that uses sanitized examples.
You.one can keep the work, evidence, and “Incident, migration, or method” decision visible through its Superboard view. Authority does not move to the software: Mei chooses the incident, migration, or method angle, drafts the employer-review request, and owns the proposal. Her employer owns what may be cleared for public use.
Available today
Name the work in plain language
These Card titles come directly from Mei's situation: “Incident, migration, or method” is the live choice, “Evidence boundary: incident timeline public, migration result needs review, internal numbers unavailable” holds evidence, and “Draft the employer-clearance request” is still work Mei 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 |
|---|---|---|
| Talk worth giving | Audience rule | Hold the mission and boundary: submit one useful talk whose public evidence, audience promise, and employer boundaries are all explicit |
| Incident, migration, or method | Talk draft | Hold the live choice—whether to center the incident, the migration decision, or a general method that uses sanitized examples—so Mei can decide from the evidence in this Room |
| Evidence boundary: incident timeline public, migration result needs review, internal numbers unavailable | Shareable evidence | Separate the public incident timeline, migration result needing review, and unavailable internal numbers |
| Outline the first 100 words | Talk draft | Outline an opening that makes one audience promise without using uncleared evidence |
| Draft the employer-clearance request | Talk draft | Draft a clearance request that names the migration result and exact internal details under review |
| Write one sentence naming what the audience can do afterward | Talk draft | Write one sentence stating what an attendee should be able to do after the talk |
| Public incident timeline | Shareable evidence | Hold the incident sequence already cleared for public discussion |
| Migration result needs employer review | Shareable evidence | Keep the result out of the abstract until the employer decides what may be shared |
| CFP deadline and learning-promise criteria | Shareable evidence | Keep the submission rules beside the evidence boundary |
Available today
Talk worth giving: separate the kinds of attention
The Talk worth giving Board gives this mission one durable operating picture. Mei can use familiar language instead of translating the situation into project-management jargon. Its three Lists separate the kinds of attention this situation actually requires.
The Lists use Mei'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 Mei has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Audience rule | Why this mission matters and what it must not consume |
| Talk draft | The small set of work that can change this mission now |
| Shareable evidence | What Mei knows, where it came from, and what remains uncertain |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Mei has made visible around “Incident, migration, or method.” Mei 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 Mei, watch other work on her own, or contact anyone.
Mei chooses the incident, migration, or method angle, drafts the employer-review request, and owns the proposal. Her employer owns what may be cleared for public use. Ava compares only evidence in the choice Card Room and does not contact anyone, clear material, or decide.
Mei finishes “Write one sentence naming what the audience can do afterward,” keeps “Evidence boundary: incident timeline public, migration result needs review, internal numbers unavailable” beside “Incident, migration, or method,” and does not treat “Draft the employer-clearance request” as completed or sent before doing the work.
- Request idea: from this Room only, draft a neutral comparison for Incident, migration, or method. Cite only notes visible in this Room, name missing evidence, and do not decide or contact anyone.
- Request idea: use only the Talk-angle brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Incident, migration, or method,” 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 Talk-angle brief: Place the public incident timeline, migration result awaiting review, unavailable internal numbers, audience promise, and call-for-proposals criteria together. Live choice: Whether to center the incident, the migration decision, or a general method that uses sanitized examples. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Mei will decide whether to center the incident, the migration decision, or a general method that uses sanitized examples.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Incident, migration, or method” from the visible evidence. Ava can work from the context Mei deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Mei's call remains explicit: Mei chooses the incident, migration, or method angle, drafts the employer-review request, and owns the proposal. Her employer owns what may be cleared for public use.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Talk-angle brief: Place the public incident timeline, migration result awaiting review, unavailable internal numbers, audience promise, and call-for-proposals criteria together. Live choice: Whether to center the incident, the migration decision, or a general method that uses sanitized examples |
| Chat | Keep Mei's request and Ava's attributed response with the work |
| Pulse | Open decision: Mei will decide whether to center the incident, the migration decision, or a general method that uses sanitized examples |
Build only enough Board to make the next decision
Mei should rename every List or Card that feels artificial. This recipe succeeds when “Incident, migration, or method” 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. Mark the evidence boundary | Separate public incident facts, migration results needing review, and unavailable numbers |
| 2. Write the audience promise | Say what an attendee can do afterward before choosing a title |
| 3. Compare three angles | Test incident, migration, and general method against the public evidence |
| 4. Draft exact clearance | Ask the employer about named migration details, not the whole talk |
| 5. Incident, migration, or method | Build the first 100 words without treating the draft request as approval |
Where this example stops
- This is a fictional example, not a customer story.
- This fictional example is not confidentiality, employer-clearance, rights, authorship, CFP, or professional speaking advice; the speaker verifies what may be shared and owns the proposal.
- It does not show Ava completing external actions or contacting anyone for Mei.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.