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

What belongs together 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 judgment remains human: 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, anything already waiting on another person or event, and the “Choose hybrid, cut a breakout, or cap” decision visible through its Superboard view. Margot still owns the call: Margot chooses the program, talks to speakers and the hall, and owns spending.

A submissions spreadsheet plus a hall diagram can be enough while the situation stays simple: 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.

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.

The point is a fast scan: what is moving, what is known, what is unresolved, and what Margot must choose. Questions not yet asked stay with Margot; they do not move to a list for outside replies.

Swipe or scroll sideways to see every column.

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

A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose hybrid, cut a breakout, or cap” from the visible evidence. Ava can work from the context Margot deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.

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

Swipe or scroll sideways to see every column.

These requests stay with the facts Margot has made visible around “Choose hybrid, cut a breakout, or cap.” Margot 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 Margot, watch other work on her own, or contact anyone.

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: from “Choose hybrid, cut a breakout, or cap,” draft a short decision note and name Margot as the decider

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.

Swipe or scroll sideways to see every column.

• This is a fictional example, not a customer story.
• 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.