How to produce a community conference without losing speakers, rooms, and a lunch count

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. She has sent confirmation requests to the selected speakers, and several replies are still open. A keynote asked for a hybrid setup the hall has never run. Two rooms cannot both have the good projector.

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.

In You.one's Superboard view, Margot can give “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” a Board of its own. That Board connects the shared purpose, logistics, preferences, and decisions people still own; opening “Choose hybrid, cut a breakout, or cap” creates a Room for its evidence, discussion, state, and decision.

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.

You.one can keep the work, evidence, live dependency, and “Choose hybrid, cut a breakout, or cap” decision visible through its Superboard view. The Owner boundary stays explicit: Margot chooses the program, talks to speakers and the hall, and owns spending.

The One-day conference Board gives this mission one durable operating picture. Margot 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.

Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.

These Card titles come directly from Margot's situation: “Choose hybrid, cut a breakout, or cap” is the live choice, “Registration at 52, quote at 80” holds evidence, and “Speaker confirmation replies still open” names something genuinely in motion outside Margot's control. The point is recognition, not a perfect taxonomy.

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 “Open decision: Margot will choose a tech-and-lunch posture.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Scale-and-tech brief and this Card Room's visible notes and left “Choose hybrid, cut a breakout, or cap” with Margot.”

A useful Card Chat request would be: “Using only the context visible in this Card Room, 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 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.

Margot's call remains explicit: Margot chooses the program, talks to speakers and the hall, and owns spending.

These requests use the visible supported context inside the “Choose hybrid, cut a breakout, or cap” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Margot 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 Margot, watch other Lists, or act outside this Card Room.

Margot owns speakers, hall, and money. Ava does not email presenters, run AV, or take registration.

A day that fits: lunch matches a chosen cap, the projector has a room, and hybrid is a yes only with coverage.

• Request idea: using only the context visible in this Card Room, 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.
• Request idea: use only the Scale-and-tech 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

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.

The One-day conference Board earns its place only when the familiar tool—a submissions spreadsheet plus a hall diagram—can no longer keep the reason, Scale-and-tech brief, conversation, current state, decision, and history connected.

Margot should rename every List or Card that feels artificial. This recipe succeeds when “Choose hybrid, cut a breakout, or cap” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Later, Ava may help this Board notice when two session Cards need the same projector, still leaving every program call with Margot.

A future unified You.one experience could carry relevant context from “Choose hybrid, cut a breakout, or cap” 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.

• 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.