Example
How to attend a professional conference without losing sessions, contacts, and the trip home
Victor’s badge and approved budget do not decide Tuesday. He needs to choose whether to skip an overlapping workshop, decline the customer dinner, or change the flight under the written fare rules already in his itinerary.
Leave with one recap the team can use, contacts that have next steps, and a return flight that does not quietly cancel the session he promised
Team recap, budget number, and the promised session
Keep the promised session beside the budget number
Workshops and the overlap
Compare skip-overlap, skip-dinner, and change-flight options
Name a conflict the agenda PDF does not solve
Customer dinner and contacts to actually follow
Hold a relationship ask against the recap he promised
Flights, hotel, and fare rules as written
Show the session that would be missed
Keep the written change terms beside the flight option
The workshop-seat confirmation Victor already requested
Keep Victor’s sent request from counting as a confirmed workshop seat

The Three conference days Board keeps sessions, people, travel, the recap promise, and real replies in one scan.
Open the skip-workshop, skip-dinner, or change-flight decision as a Room with the agenda and fare evidence attached.
Ava can compare only what Victor adds. Victor owns customer and team conversations, spending, and travel changes; Ava does not send messages or change plans.
A badge is not a plan; a dinner is not a session recap
The work has a clear center: Leave with one recap the team can use, contacts that have next steps, and a return flight that does not quietly cancel the session he promised.
Organizing the evidence does not authorize the software to decide: Whether to skip the overlapping workshop, skip the customer dinner, or change the flight using the fare rules already in the itinerary.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose skip workshop, skip dinner, or change flight” decision visible through its Superboard view. Victor still owns the call: Victor chooses the schedule, talks to the customer and his team, and owns spending.
Available today
Name the work in plain language
These Card titles come directly from Victor's situation: “Choose skip workshop, skip dinner, or change flight” is the live choice, “Overlapping workshops Tuesday” holds evidence, and “Workshop-seat confirmation requested” names something genuinely in motion outside Victor's control. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| One recap, not two ghosts | Mission | Keep the promised session beside the budget number |
| Choose skip workshop, skip dinner, or change flight | Sessions | Compare skip-overlap, skip-dinner, and change-flight options |
| Overlapping workshops Tuesday | Sessions | Name a conflict the agenda PDF does not solve |
| Customer dinner versus keynote | People and replies | Hold a relationship ask against the recap he promised |
| Return flight same afternoon | Travel | Show the session that would be missed |
| Fare rules on the itinerary | Travel | Keep the written change terms beside the flight option |
| Workshop-seat confirmation requested | Replies already requested | Keep Victor’s sent request from counting as a confirmed workshop seat |
Available today
Three conference days: separate the kinds of attention
The Three conference days Board gives this mission one durable operating picture. Victor can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.
The Lists use Victor'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 Victor has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Mission | Team recap, budget number, and the promised session |
| Sessions | Workshops and the overlap |
| People and replies | Customer dinner and contacts to actually follow |
| Travel | Flights, hotel, and fare rules as written |
| Replies already requested | The workshop-seat confirmation Victor already requested |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Victor has made visible around “Choose skip workshop, skip dinner, or change flight.” Victor 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 Victor, watch other work on her own, or contact anyone.
Victor owns work conversations, spending, and travel changes. Ava does not email customers, change flights, or recap the conference.
A Tuesday with one job: the recap is protected or consciously traded, the dinner is a yes or no, and overlapping workshops are not both attended in theory.
- Request idea: using only the context visible in this Card Room, compare skipping the extra workshop, skipping dinner, and changing the flight. Do not email the customer or choose for me.
- Request idea: use only the Conflict brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Choose skip workshop, skip dinner, or change flight,” 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 Conflict brief: Place overlap, dinner, promised recap, written fare rules, and skip-workshop / skip-dinner / change-flight options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Victor will choose what Tuesday actually is.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose skip workshop, skip dinner, or change flight” from the visible evidence. Ava can work from the context Victor deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Victor's call remains explicit: Victor chooses the schedule, talks to the customer and his team, and owns spending.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Conflict brief: Place overlap, dinner, promised recap, written fare rules, and skip-workshop / skip-dinner / change-flight options on one page |
| Chat | Keep Victor's request and Ava's attributed response with the work |
| Pulse | Open decision: Victor will choose what Tuesday actually is |
Build only enough Board to make the next decision
Victor should rename every List or Card that feels artificial. This recipe succeeds when “Choose skip workshop, skip dinner, or change flight” 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. Write the recap promise | What the team actually needs |
| 2. Mark overlaps | Two workshops are a choice |
| 3. Card people asks | Dinners versus sessions |
| 4. Put fare rules on the Board | As written |
| 5. Choose skip workshop, skip dinner, or change flight | Open a Room before the badge fills itself |
Where this example stops
- This is a fictional example, not a customer story.
- This is not a professional-development or sales claim.
- It does not show Ava emailing customers or changing travel.
- It is not a measured conference result.