Example
How to coordinate a volunteer drive without a signup sheet that lies
Tom's problem is not a lack of effort. It is that Run Saturday with shifts that match tools and a safe headcount, and treat extra publicity as a waitlist rather than a crowd 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.
Tom is an explicitly fictional portrait, not a customer or testimonial.
The Saturday cleanup Board gives one mission a visible field; the Choose cap, Sunday, or skip radio 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.
Tom's pressure is ordinary—and still heavy
Tom is a fictional 51-year-old volunteer coordinator for a weekend park cleanup in Thunder Bay, Ontario. Tom posted a signup form. Eighty people said yes. The site can safely use thirty at a time. Tool inventory is twenty-four rakes. A local radio mention could add more people on Saturday morning.
Tom wants the park cleaned. Too many people with too few tools is how someone gets hurt and nobody comes back.
A form spreadsheet, a tool closet count, and a radio producer’s text do not share a cap.
A group of ten from a workplace asked to come as a team at noon, which is already the peak hour.
A form yes is not a shift, and a radio mention is not capacity
The mission is specific: Run Saturday with shifts that match tools and a safe headcount, and treat extra publicity as a waitlist rather than a crowd
The consequential choice is not something a board or an AI should quietly make: Whether to cap at thirty and waitlist the rest, add a Sunday shift, or decline the radio mention until tools are borrowed
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Tom still owns the purpose, tradeoff, and final call.
Available today
Saturday cleanup: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Tom 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 | Safe headcount and tool count |
| Shifts | Morning and afternoon with named leads |
| People | Signups, teams, and waitlist |
| Tools and site | What is actually in the closet |
| Waiting | Borrowed tools and radio hold |
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 Tom would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Thirty people, twenty-four rakes | Mission | Keep capacity beside the form that said eighty |
| Choose cap, Sunday, or skip radio | People | Compare waitlist, extra Sunday shift, and decline-radio options |
| Workplace team of ten at noon | People | Hold a peak-hour cluster that would break the cap |
| Tool closet count | Tools and site | Attach inventory to the day |
| Saturday morning lead still unnamed | Shifts | A shift without a lead is not a shift |
| Radio mention maybe | Waiting | Keep extra publicity from becoming unplanned arrivals |
Available today
Available today: Choose cap, Sunday, or skip radio becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Capacity brief: Place tool count, form yeses, and cap / Sunday / skip-radio options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Tom to choose Saturday’s capacity posture. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare capping at thirty, adding Sunday, and declining the radio mention. Do not contact the station 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.
Tom's call remains explicit: Tom chooses the cap, talks to teams and the radio producer, and owns site safety
| Surface | Job in this example |
|---|---|
| Stage | Capacity brief: Place tool count, form yeses, and cap / Sunday / skip-radio options on one page |
| Chat | Keep Tom's request and Ava's attributed response with the work |
| Pulse | Waiting for Tom to choose Saturday’s capacity 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.
Tom owns safety, communications, and who is invited. Ava does not message volunteers or run the site.
The modest outcome is not that Ava lives Tom's life. The modest outcome is a Saturday that matches tools: the cap is chosen, the noon team is placed or waitlisted, and a radio mention is not an unplanned crowd.
- Request idea: summarize shifts, people clusters, and tool counts already on the Board
- Request idea: compare capacity options using inventory Tom captured
- Request idea: help keep radio and borrowed-tool maybes in Waiting
A signup spreadsheet may still be enough
A signup spreadsheet is enough when yeses are fewer than tools
It starts to break when eighty yeses, twenty-four rakes, and a radio maybe all claim Saturday
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 Tom'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 tools and safe headcount | The form is not capacity |
| 2. Split shifts | Named leads |
| 3. Cluster team asks | Ten at noon is a fact |
| 4. Park publicity | Radio is Waiting until chosen |
| 5. Decide the cap | Open a Room before Saturday morning |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a shift Card has no named lead, still leaving every invite with Tom.
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
- Tom is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not safety, insurance, or labor advice.
- It does not show Ava contacting volunteers or a radio station.
- It is not a measured turnout result.