Example
How to produce a community conference without losing speakers, rooms, and a lunch count
Margot's problem is not a lack of effort. It is that Run one day with a program that fits two rooms, a lunch number that matches registration, and a hybrid yes only if tech coverage remains has outgrown scattered reminders, tabs, and memory. This fictional playbook shows a concrete Board, the Cards inside it, one consequential Room, and the line Ava does not cross.
This fictional example was created with AI assistance from a structured editorial brief and reviewed by the You.one Editorial Team for usefulness, distinctness, and product truth.
Margot is an explicitly fictional portrait, not a customer or testimonial.
The One-day conference Board gives one mission a visible field; the Choose hybrid, cut a breakout, or cap Room keeps its evidence, conversation, state, and decision together.
Current Superboard provides the durable structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Margot's pressure is ordinary—and still heavy
Margot is a fictional 48-year-old volunteer chair of a one-day community conference in Moncton, New Brunswick. Margot has a civic hall, eighteen speaker submissions, and a lunch quote for 80. Registration is at 52. A keynote asked for a hybrid setup the hall has never run. Two rooms cannot both have the good projector.
Margot can invite speakers. The day fails if the projector, lunch count, and a hybrid ask never share a constraint.
A submissions spreadsheet, a hall diagram, and a caterer quote disagree about scale.
Saying yes to hybrid feels modern and would take the only tech volunteer off registration.
A program is rooms plus lunch, not a PDF of names
The mission is specific: Run one day with a program that fits two rooms, a lunch number that matches registration, and a hybrid yes only if tech coverage remains
The consequential choice is not something a board or an AI should quietly make: Whether to keep in-person only, run hybrid in one room and cut a breakout, or cap registration at 80 and decline hybrid
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Margot still owns the purpose, tradeoff, and final call.
Available today
One-day conference: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Margot does not have to convert life into project-management jargon or decide the perfect taxonomy first. Lists separate kinds of attention; Cards keep each meaningful item visible and movable.
The Cards are deliberately mixed. Some are tasks, some are decisions, some hold a person or promise, and some are reference points. Current Superboard supports that flexibility without flattening the mission into one long to-do list.
| List | What belongs here |
|---|---|
| Mission | Rooms, lunch, and tech coverage |
| Program | Speakers and sessions |
| Place | Hall, projector, hybrid ask |
| Hospitality | Lunch count and registration |
| Waiting | Speaker confirms and caterer revisions |
Available today
The Cards make the operating picture concrete
A Board becomes useful when the Card titles sound like the actual situation. These are not generic placeholders; they show what Margot would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Two rooms, one projector | Mission | Keep tech coverage beside the hybrid compliment |
| Choose hybrid, cut a breakout, or cap | Place | Compare in-person-only, hybrid-plus-cut, and cap-80-decline-hybrid |
| Registration at 52, quote at 80 | Hospitality | Show a lunch number that is not yet true |
| Keynote hybrid ask | Place | Hold a request that needs the only tech volunteer |
| Good projector: one | Place | Name the constraint two rooms both want |
| Speaker confirmations | Waiting | Keep unconfirmed names off the public program |
Available today
Available today: Choose hybrid, cut a breakout, or cap becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Scale-and-tech brief: Place projector, lunch quote, hybrid ask, and in-person / hybrid-cut / cap options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Margot to choose a tech-and-lunch posture. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare in-person only, hybrid in one room with a cut, and capping at 80 without hybrid. Do not email speakers or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported context and can make limited reversible product changes. She does not deeply reason over the whole Board by default, and she does not gain authority over the decision merely because the context is organized.
Margot's call remains explicit: Margot chooses the program, talks to speakers and the hall, and owns spending
| Surface | Job in this example |
|---|---|
| Stage | Scale-and-tech brief: Place projector, lunch quote, hybrid ask, and in-person / hybrid-cut / cap options on one page |
| Chat | Keep Margot's request and Ava's attributed response with the work |
| Pulse | Waiting for Margot to choose a tech-and-lunch posture |
| Activity | Preserve attributed Card changes and the supported record around the request |
What to ask Ava—and what not to assume
These are useful requests to adapt, not claims that current Ava automatically surveys the whole Board, prepares every comparison, or follows up on her own. The relevant facts must be present in supported Board/Card context, and the human still checks the result.
Margot owns speakers, hall, and money. Ava does not email presenters, run AV, or take registration.
The modest outcome is not that Ava lives Margot's life. The modest outcome is a day that fits: lunch matches a chosen cap, the projector has a room, and hybrid is a yes only with coverage.
- Request idea: summarize program, place constraints, and lunch counts already on the Board
- Request idea: compare hybrid options using projector and volunteer coverage Margot captured
- Request idea: help keep unconfirmed speakers in Waiting
A submissions spreadsheet plus a hall diagram may still be enough
A submissions spreadsheet plus a hall diagram is enough when one room and lunch already matches registration
It starts to break when one projector, a hybrid ask, and an 80-person quote share a 52-person list
Superboard earns a place only when the responsibility needs a durable picture around the list: the reason, artifact, conversation, current state, decision, and history.
A starter recipe to adapt, not obey
Use the names that already make sense in Margot's world. The recipe is successful when the Board reduces remembering and exposes the real decision—not when every Card is perfectly categorized.
| Step | Action |
|---|---|
| 1. Count rooms and the projector | Tech is a constraint |
| 2. Match lunch to registration | Quotes are not heads |
| 3. Card the hybrid ask | It costs a volunteer |
| 4. Park unconfirmed speakers | Off the public PDF |
| 5. Decide scale | Open a Room before hybrid becomes a surprise |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when two session Cards need the same projector, still leaving every program call with Margot.
The unified You.one and Superboard runtime, cross-product personalized Memory Spine, broad proactive coordination, realtime shared editing, and general external execution are not available today. Future actions would still require the applicable capability, connection, grant, and human authority.
What this realistic example does not claim
- Margot is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not AV, catering, or accessibility-legal advice.
- It does not show Ava contacting speakers or taking registration.
- It is not a measured attendance result.