Example
How to run a faith-community service project without losing meals, rides, or the signup sheet
Miriam's community has plenty of kitchen capacity and an unresolved delivery scale. The choice is twelve confirmed stops across four cars, an eight-stop cap at two stops per car, or recruiting two more drivers before anyone proposes twelve.
Deliver this year’s meals with a current household list, enough drivers, and a kitchen schedule—without doubling volume by slogan
This year’s count and the cooks-are-not-drivers rule
Keep driver count beside the urge to double meals
Cooks, shifts, and the booked room
Show that cooking capacity is not the constraint
Drivers, routes, and cars
Compare twelve confirmed stops across four cars, an eight-stop cap at two stops per car, and recruiting two drivers before proposing twelve stops
Name the gap a generous slogan wants to ignore
Ground the current route capacity after two dropouts
Put the prior stop and driver counts beside this year's four remaining cars
Current addresses versus last year’s list
Mark a list that has not been confirmed
Household address confirmations already requested
Keep unconfirmed addresses from filling routes
The December meals Board separates cooks, drivers, current household confirmations, routes, and the promises the community has actually made.
The Scale Room compares twelve, eight, and recruit-first paths beside last year's six-driver pattern and this year's four remaining cars.
Ava can compare the supplied counts without using household dossiers. Miriam and the community choose the scale; drivers and households own participation, and Ava cannot contact or enroll anyone.
A last-year list is not this year’s households, and cooks are not drivers
What belongs together is specific: Deliver this year’s meals with a current household list, enough drivers, and a kitchen schedule—without doubling volume by slogan.
The consequential judgment remains human: Whether to stretch four cars to twelve confirmed stops, cap the route at eight confirmed stops with two stops per car, or recruit two more drivers before proposing twelve stops. Unconfirmed household replies never count as stops.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose count versus drivers” decision visible through its Superboard view. Miriam still owns the call: Miriam’s community chooses the scale, talks to drivers and households, and owns the meals.
What changes after a paper signup plus last year’s addresses
A paper signup plus last year’s addresses can be enough while the situation stays simple: drivers and households are unchanged.
It starts to break when two drivers are gone and someone wants to double the food.
The December meals Board earns its place only when the familiar tool—a paper signup plus last year’s addresses—can no longer keep the reason, Scale brief, conversation, current state, decision, and history connected.
Available today
A focused December meals Board
The December meals Board gives this mission one durable operating picture. Miriam 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 Miriam must choose. Questions not yet asked stay with Miriam; they do not move to a list for outside replies.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Mission | This year’s count and the cooks-are-not-drivers rule |
| Kitchen | Cooks, shifts, and the booked room |
| Delivery | Drivers, routes, and cars |
| Households | Current addresses versus last year’s list |
| Replies already requested | Household address confirmations already requested |
Available today
Inside the “Choose count versus drivers” Room
Opening the Card gives the visible item durable depth. Stage can hold Scale brief: Place last year's twelve stops and six drivers, this year's four remaining cars, still-unconfirmed household replies, and the twelve-across-four / eight-at-two-per-car / recruit-two-before-twelve options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Miriam’s community will choose a scale that four cars can actually deliver.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose count versus drivers” from the visible evidence. Ava can work from the context Miriam deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Miriam's call remains explicit: Miriam’s community chooses the scale, talks to drivers and households, and owns the meals.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Scale brief: Place last year's twelve stops and six drivers, this year's four remaining cars, still-unconfirmed household replies, and the twelve-across-four / eight-at-two-per-car / recruit-two-before-twelve options on one page |
| Chat | Keep Miriam's request and Ava's attributed response with the work |
| Pulse | Open decision: Miriam’s community will choose a scale that four cars can actually deliver |
What Ava can prepare from visible context
These requests stay with the facts Miriam has made visible around “Choose count versus drivers.” Miriam 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 Miriam, watch other work on her own, or contact anyone.
The community owns meals, contacts, and routes. Ava does not contact households, drive, or give dietary advice.
A week that can be driven: cooks are not mistaken for cars, last year’s list is a confirmation job, and volume is a decision.
- Request idea: using only the context visible in this Card Room, compare routing twelve confirmed stops across four cars, capping the route at eight confirmed stops with two stops per car, and recruiting two more drivers before proposing twelve stops. Treat unconfirmed household replies as unanswered here; do not move Cards, watch other Lists, contact households, or choose for us.
- Request idea: use only the Scale brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: from “Choose count versus drivers,” draft a short decision note and name Miriam as the decider
A starter shape, not a prescribed workflow
Miriam should rename every List or Card that feels artificial. This recipe succeeds when “Choose count versus drivers” 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. Separate cooks and drivers | Different jobs |
| 2. Confirm this year’s households | Last year’s list is a starting point |
| 3. Count cars | Dropped drivers are a gap |
| 4. Park confirmations | Addresses in Replies already requested |
| 5. Choose count versus drivers | Open a Room before doubling food stranded on a counter |
Where this example stops
- This is a fictional example, not a customer story.
- This is not dietary, medical, or charitable-registration advice.
- It does not show Ava contacting households or driving deliveries.
- It is not a measured service result.