Example
How to coordinate a volunteer drive without a signup sheet that lies
Tom wants the park cleaned, but a form response is not a confirmed shift and a radio mention is not capacity. Too many people with too few rakes is not success; it is a reason to choose a smaller Saturday, add Sunday, or wait.
Run the cleanup weekend with shifts that match tools and a safe headcount, and treat extra publicity as a held option rather than a crowd
Safe headcount and tool count
Keep capacity beside the form that said eighty
Saturday morning lead assignment and Sunday overflow option
Keep lead assignment as required follow-through, not a fourth capacity option
Make the extra-day option visible with its own lead and capacity needs
Signups, teams, and waitlist
Compare three exclusive weekend postures with the radio held or deferred
Hold the noon team of ten against the twenty-four-person tool cap
Keep an unrequested publicity option from becoming unplanned arrivals
What is actually in the closet
Attach inventory to the day
The borrowed-tool reply already requested from the neighboring group
Keep Tom’s sent borrowing request from counting as available tools
Separate interested people from confirmed shifts, named skills, available tools, and commitments that still need an answer.
Keep the Saturday-only, two-day, or wait-for-tools decision in one Room with the evidence and final Owner call.
Ava can organize the information Tom supplies. She does not recruit people, verify attendance, assign unsafe work, contact volunteers, or make the go/no-go decision.
Why Cleanup weekend needs an operating picture
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, but tool inventory caps a shift at twenty-four rakes. Sunday is available as an overflow shift under the same cap if Saturday cannot absorb the yeses. Tom already asked a neighboring group to lend six more rakes, and a local radio mention could add more people on Saturday morning.
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.
In You.one's Superboard view, Tom can give “Run the cleanup weekend with shifts that match tools and a safe headcount, and treat extra publicity as a held option rather than a crowd” a Board of its own. That Board connects community promises, volunteer capacity, local evidence, and human authority; opening “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” creates a Room for its evidence, discussion, state, and decision.
A form yes is not a shift, and a radio mention is not capacity
The mission is specific: Run the cleanup weekend with shifts that match tools and a safe headcount, and treat extra publicity as a held option rather than a crowd.
The consequential choice is not something a board or an AI should quietly make: Whether to run Saturday only at twenty-four with radio held, run Saturday and Sunday at twenty-four per shift with radio held, or defer the cap and radio mention until the six borrowed rakes confirm.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” decision visible through its Superboard view. Tom still owns the call: Tom chooses the cap, talks to teams and the radio producer, and owns site safety.
Available today
Cleanup weekend: one Board shape to adapt
The Cleanup weekend Board gives this mission one durable operating picture. Tom 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, something already waiting on another person or event, 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.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Mission | Safe headcount and tool count |
| Shifts | Saturday morning lead assignment and Sunday overflow option |
| People | Signups, teams, and waitlist |
| Tools and site | What is actually in the closet |
| Waiting | The borrowed-tool reply already requested from the neighboring group |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Tom's situation: “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” is the live choice, “Workplace team of ten at noon” holds evidence, and “Borrowed-tool reply from neighboring group” names something genuinely in motion outside Tom's control. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| Thirty people, twenty-four rakes | Mission | Keep capacity beside the form that said eighty |
| Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes | People | Compare three exclusive weekend postures with the radio held or deferred |
| Workplace team of ten at noon | People | Hold the noon team of ten against the twenty-four-person tool cap |
| Tool closet count | Tools and site | Attach inventory to the day |
| Assign Saturday morning lead after the capacity posture | Shifts | Keep lead assignment as required follow-through, not a fourth capacity option |
| Sunday shift option | Shifts | Make the extra-day option visible with its own lead and capacity needs |
| Borrowed-tool reply from neighboring group | Waiting | Keep Tom’s sent borrowing request from counting as available tools |
| Radio mention maybe | People | Keep an unrequested publicity option from becoming unplanned arrivals |
Available today
Available today: Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Capacity brief: Place tool count, the noon workplace team of ten, form yeses, and Saturday-only / Saturday-plus-Sunday / wait-for-six-rakes postures on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Tom will choose the cleanup weekend posture.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” from the visible evidence. Ava can work from the context Tom deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Tom's call remains explicit: Tom chooses the cap, talks to teams and the radio producer, and owns site safety.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Capacity brief: Place tool count, the noon workplace team of ten, form yeses, and Saturday-only / Saturday-plus-Sunday / wait-for-six-rakes postures on one page |
| Chat | Keep Tom's request and Ava's attributed response with the work |
| Pulse | Open decision: Tom will choose the cleanup weekend posture |
What to ask Ava—and what not to assume
These requests stay with the facts Tom has made visible around “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes.” Tom 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 Tom, watch other work on her own, or contact anyone.
Tom owns safety, communications, and who is invited. Ava does not message volunteers or run the site.
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: using only the context visible in this Card Room, compare Saturday-only at twenty-four with radio held, Saturday and Sunday at twenty-four per shift with radio held, and deferring the cap and radio mention until six borrowed rakes confirm. Do not contact the station or choose for me.
- Request idea: use only the Capacity 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
What A signup spreadsheet can still handle
A signup spreadsheet can be enough while the situation stays simple: yeses are fewer than tools.
It starts to break when eighty yeses, twenty-four rakes, and a radio maybe all claim Saturday.
The Cleanup weekend Board earns its place only when the familiar tool—a signup spreadsheet—can no longer keep the reason, Capacity brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Tom should rename every List or Card that feels artificial. This recipe succeeds when “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” 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. Count tools and safe headcount | The form is not capacity |
| 2. Place possible shifts | Saturday and Sunday Cards before assigning leads |
| 3. Cluster team asks | Ten at noon is a fact |
| 4. Hold publicity as an option | Radio stays in People until Tom chooses it |
| 5. Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes | 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.
A future unified You.one experience could carry relevant context from “Choose Saturday-only, Saturday-plus-Sunday, or wait for rakes” 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.
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.