Example
How to run a bakery preorder week when oven time is the real inventory
Zara has forty-two requests that can each look reasonable alone. The operating decision is whether to cap standard loaves, move the custom cake, or add a Sunday pickup window without inventing an overnight rescue shift.
Fulfill a smaller reliable preorder week with clear pickup promises and no invisible overnight rescue
The governing promise behind every other List
Keep two honest pickup windows and a finishable bake week as Zara's customer promise
Work Zara can actually advance in the current window
Compare capping loaves, moving the custom cake, and adding Sunday
Map oven and cooling hours before Zara accepts another order
Facts worth returning to before Zara decides: whether to cap standard loaves, move the custom cake, or add a Sunday pickup window
Show the custom cake's exact Friday oven block
Show that twelve standard loaves require the same block
What is genuinely blocked, who owns the reply, and when to revisit it
Record the late butter delivery already in motion and its owner
Use a One-oven preorder Board to separate customer promises, next bakes, capacity evidence, and supplies that are genuinely still outside Zara’s control.
The Friday-capacity Room keeps oven and cooling hours, ingredient timing, and the cap-move-Sunday choice beside the work.
Ava can compare the facts in that Room. Zara chooses and sets the cap, changes promises, bakes the food, and communicates with customers and suppliers.
One-oven preorder has one live choice: Cap, move, or add Sunday
This Board has one job: Fulfill a smaller reliable preorder week with clear pickup promises and no invisible overnight rescue.
The decision still belongs to Zara: Whether to cap standard loaves, move the custom cake, or add a Sunday pickup window.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Cap, move, or add Sunday” decision visible through its Superboard view. Zara still owns the call: Zara chooses the preorder cap, changes only promises she owns, bakes the food, and communicates with customers and suppliers.
Available today
One-oven preorder: one place for the mission
The One-oven preorder Board gives this mission one durable operating picture. Zara can use familiar language instead of translating the situation into project-management jargon. Its four Lists separate the kinds of attention this situation actually requires.
The Board is not a master task list. It keeps the live choice, the facts that could change it, and any reply or outside event already in motion visible without pretending every uncertainty is work in progress.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Customer promise | The governing promise behind every other List |
| Bake next | Work Zara can actually advance in the current window |
| Capacity evidence | Facts worth returning to before Zara decides: whether to cap standard loaves, move the custom cake, or add a Sunday pickup window |
| Supply arrivals | What is genuinely blocked, who owns the reply, and when to revisit it |
Available today
Cards that sound like the real work
These Card titles come directly from Zara's situation: “Cap, move, or add Sunday” is the live choice, “Custom cake: Friday oven block” holds evidence, and “Butter delivery” names something genuinely in motion outside Zara's control. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| One-oven preorder | Customer promise | Keep two honest pickup windows and a finishable bake week as Zara's customer promise |
| Cap, move, or add Sunday | Bake next | Compare capping loaves, moving the custom cake, and adding Sunday |
| Custom cake: Friday oven block | Capacity evidence | Show the custom cake's exact Friday oven block |
| Twelve loaves need the same block | Capacity evidence | Show that twelve standard loaves require the same block |
| Butter delivery | Supply arrivals | Record the late butter delivery already in motion and its owner |
| Map oven and cooling hours before accepting one more order | Bake next | Map oven and cooling hours before Zara accepts another order |
Available today
Keep the evidence with “Cap, move, or add Sunday”
Opening the Card gives the visible item durable depth. Stage can hold Friday-capacity brief: Place bake times, cooling space, pickup promises, ingredient arrival, and custom work together. Live choice: Whether to cap standard loaves, move the custom cake, or add a Sunday pickup window. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Zara will decide whether to cap standard loaves, move the custom cake, or add a Sunday pickup window.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Cap, move, or add Sunday” from the visible evidence. Ava can work from the context Zara deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Zara's call remains explicit: Zara chooses the preorder cap, changes only promises she owns, bakes the food, and communicates with customers and suppliers.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Friday-capacity brief: Place bake times, cooling space, pickup promises, ingredient arrival, and custom work together. Live choice: Whether to cap standard loaves, move the custom cake, or add a Sunday pickup window |
| Chat | Keep Zara's request and Ava's attributed response with the work |
| Pulse | Open decision: Zara will decide whether to cap standard loaves, move the custom cake, or add a Sunday pickup window |
Start small and rename what feels artificial
Zara should rename every List or Card that feels artificial. This recipe succeeds when “Cap, move, or add Sunday” 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. Write the mission | Fulfill a smaller reliable preorder week with clear pickup promises and no invisible overnight rescue |
| 2. Open the live choice | Put “Cap, move, or add Sunday” in a Room of its own |
| 3. Attach the evidence | Friday-capacity brief: Place bake times, cooling space, pickup promises, ingredient arrival, and custom work together. Live choice: Whether to cap standard loaves, move the custom cake, or add a Sunday pickup window. |
| 4. Name what is already waiting | Keep “Butter delivery” visibly waiting |
| 5. Take the first owned action | Map oven and cooling hours before accepting one more order |
An order spreadsheet can remain part of the system
An order spreadsheet can be enough while the situation stays simple: “Butter delivery” has a confirmed answer and no longer changes “Cap, move, or add Sunday”.
It starts to break when “Custom cake: Friday oven block” and “Butter delivery” must inform the same choice.
The One-oven preorder Board earns its place only when the familiar tool—an order spreadsheet—can no longer keep the reason, Friday-capacity brief, conversation, current state, decision, and history connected.
Where this example stops
- This is a fictional example, not a customer story.
- This fictional example is not food-safety, allergy, licensing, labor, or local-permit advice; the baker follows the rules and safe practices that govern the real business.
- It does not show Ava completing external actions or contacting anyone for Zara.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.