Example
How to develop a conference talk proposal from evidence instead of a clever title
A clever abstract can outrun the evidence and the permission to share it.
AI assistance helped shape this fictional example from a structured editorial brief. It was reviewed for usefulness, distinctness, accessibility, and product truth.
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
Mei is an explicitly fictional portrait, not a customer or testimonial.
The Talk worth giving Board gives one mission a visible field; the Incident, migration, or method Room keeps its evidence, conversation, state, and decision together.
Current You.one provides the Superboard structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Why Talk worth giving needs an operating picture
Mei is a fictional 38-year-old staff engineer proposing her first industry conference talk in San Jose, California. Mei has one incident review, a migration with surprising results, five possible talk titles, and a submission form that asks for a learning promise before the internal numbers are cleared for public use.
The CFP asks for a learning promise before the strongest migration evidence is cleared.
A public incident timeline can support a useful talk now; the draft must not smuggle unavailable numbers into a better-sounding abstract.
In You.one's Superboard view, Mei can give “Submit one useful talk whose public evidence, audience promise, and employer boundaries are all explicit” a Board of its own. That Board connects a public incident timeline, uncleared migration results, unavailable internal numbers, the CFP promise, and an unsent clearance request; opening “Incident, migration, or method” creates a Room for its evidence, discussion, state, and decision.
Talk worth giving has one live choice: Incident, migration, or method
The mission is specific: Submit one useful talk whose public evidence, audience promise, and employer boundaries are all explicit.
The consequential choice is not something a board or an AI should quietly make: 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. The Owner boundary stays 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.
Available today
Talk worth giving: one Board shape to adapt
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.
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.
| 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 |
Available today
The Cards make the operating picture concrete
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 a fake Waiting item. The point is recognition, not a perfect taxonomy.
| 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
Available today: Incident, migration, or method becomes a Room
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.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Talk-angle brief and this Card Room's visible notes and left “Incident, migration, or method” with Mei.”
A useful Card Chat request would be: “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.” 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.
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.
| 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 |
| Activity | Ava compared the options in Card Chat using the Talk-angle brief and this Card Room's visible notes and left “Incident, migration, or method” with Mei |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Incident, migration, or method” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Mei 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 Mei, watch other Lists, or act outside this Card Room.
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: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously
An abstract draft may still be enough
An abstract draft is enough when “Outline the first 100 words” and “Draft the employer-clearance request” no longer change the “Incident, migration, or method” choice.
It starts to break when “Evidence boundary: incident timeline public, migration result needs review, internal numbers unavailable” and “Draft the employer-clearance request” must inform the same choice.
The Talk worth giving Board earns its place only when the familiar tool—an abstract draft—can no longer keep the reason, Talk-angle brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
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.
| 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 |
Direction
Direction, not a current promise
A future Ava may notice that “Evidence boundary: incident timeline public, migration result needs review, internal numbers unavailable” no longer supports the Talk-angle brief and help Mei reopen “Incident, migration, or method.” Every real action remains with the people or institutions named in the Owner boundary.
A future unified You.one experience could carry relevant context from “Incident, migration, or method” 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.
What this realistic example does not claim
- Mei is fictional and is not a customer, testimonial, research participant, or disguised real person.
- 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.