Example
How to choose a mobile coffee route when the busiest stop is not the best morning
Farah cannot serve all three stops before eleven, and choosing stops by crowd size ignores setup, teardown, menu mix, repeat customers, waste, and travel. Farah owns the choice: anchor at construction, keep the office plaza, or test a school-first two-stop route with a smaller menu using timed operating evidence.
Build a repeatable morning route that keeps one strong promise instead of chasing every crowd
The result Farah is trying to create—not every possible task
Keep one repeatable morning promise inside the eleven-o'clock stop
The current choice, preparation, and other owned next moves
Compare construction, office, and school-first routes
Time setup and teardown once at the current stop
Evidence for the live choice, drawn from the situation's actual sources
Record construction-site volume and service conditions
Record office-plaza food margin and repeat-customer value
Compare margin with the construction site's volume
Record when the school stop earns or loses its place in the route
A separate place for operating constraints without pretending an outside reply is already in motion
Hold the host-access windows and drive constraints that limit setup
Keep setup, driving, and service inside the actual morning
The Morning route Board keeps the promise, stops to test, service evidence, operating constraints, and routes actually proven distinct.
Open Construction, office, or school-first route as the Room with the Route-choice brief and one timed setup and teardown at the current stop.
Ava can compare the visible route evidence. Farah owns food safety, permits, site access, traffic, pricing, money, navigation, hosts, customers, and every operating decision; Ava contacts no one.
Morning route has one live choice: Construction, office, or school-first route
The work has a clear center: Build a repeatable morning route that keeps one strong promise instead of chasing every crowd.
Organizing the evidence does not authorize the software to decide: Whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu.
You.one can keep the work, evidence, and “Construction, office, or school-first route” decision visible through its Superboard view. Authority does not move to the software: Farah chooses the route, drives and operates the cart, handles food and money, and owns every host and customer promise.
Available today
Name the work in plain language
These Card titles come directly from Farah's situation: “Construction, office, or school-first route” is the live choice, “Construction site” holds evidence, and “Host-access windows” is still work Farah controls—not something already awaiting another person. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| Morning route | Route promise | Keep one repeatable morning promise inside the eleven-o'clock stop |
| Construction, office, or school-first route | Stops to test | Compare construction, office, and school-first routes |
| Construction site | Service evidence | Record construction-site volume and service conditions |
| Office plaza | Service evidence | Record office-plaza food margin and repeat-customer value |
| Host-access windows | Operating constraints | Hold the host-access windows and drive constraints that limit setup |
| Time setup and teardown at the current stop | Stops to test | Time setup and teardown once at the current stop |
| Office plaza food margin | Service evidence | Compare margin with the construction site's volume |
| School demand peaks earlier | Service evidence | Record when the school stop earns or loses its place in the route |
| Eleven-o'clock hard stop | Operating constraints | Keep setup, driving, and service inside the actual morning |
Available today
Morning route: separate the kinds of attention
The Morning route Board gives this mission one durable operating picture. Farah 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 Lists use Farah's own language so actions, evidence, open questions, and decisions do not collapse into one queue. A separate place for replies is useful only after Farah has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Route promise | The result Farah is trying to create—not every possible task |
| Stops to test | The current choice, preparation, and other owned next moves |
| Service evidence | Evidence for the live choice, drawn from the situation's actual sources |
| Operating constraints | A separate place for operating constraints without pretending an outside reply is already in motion |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Farah has made visible around “Construction, office, or school-first route.” Farah 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 Farah, watch other work on her own, or contact anyone.
Farah chooses the route, drives and operates the cart, handles food and money, and owns every host and customer promise. Ava does not operate the cart, navigate, sell, or contact anyone.
Farah finishes “Time setup and teardown at the current stop,” keeps “Construction site” beside “Construction, office, or school-first route,” and does not treat “Host-access windows” as completed or sent before doing the work.
- Request idea: help me prepare for Construction, office, or school-first route using only this Card Room and the Route-choice brief. Separate facts, assumptions, and unanswered questions; stop before the final call.
- Request idea: use only the Route-choice brief and notes the Owner has placed in this Card Room to name the missing evidence for each option
- Request idea: in “Construction, office, or school-first route,” group the visible evidence by option and leave the decision open
Available today
One Card Room for the consequential choice
Opening the Card gives the visible item durable depth. Stage can hold Route-choice brief: Place sales mix, setup, travel, host access, waste, and repeat-customer value together. Live choice: Whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Farah will decide whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Construction, office, or school-first route” from the visible evidence. Ava can work from the context Farah deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Farah's call remains explicit: Farah chooses the route, drives and operates the cart, handles food and money, and owns every host and customer promise.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Route-choice brief: Place sales mix, setup, travel, host access, waste, and repeat-customer value together. Live choice: Whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu |
| Chat | Keep Farah's request and Ava's attributed response with the work |
| Pulse | Open decision: Farah will decide whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu |
Build only enough Board to make the next decision
Farah should rename every List or Card that feels artificial. This recipe succeeds when “Construction, office, or school-first route” 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 | Build a repeatable morning route that keeps one strong promise instead of chasing every crowd |
| 2. Open the live choice | Put “Construction, office, or school-first route” in a Room of its own |
| 3. Attach the evidence | Route-choice brief: Place sales mix, setup, travel, host access, waste, and repeat-customer value together. Live choice: Whether to anchor at the construction site, keep the office plaza, or test a school-first two-stop route with a smaller menu. |
| 4. Keep the work owned | Keep “Host-access windows” in owned work and name the next visible move |
| 5. Take the first owned action | Time setup and teardown at the current stop |
Where this example stops
- This is a fictional example, not a customer story.
- This fictional example is not food-safety, traffic, site-access, licensing, pricing, or local-permit advice; the operator verifies every real route and operating requirement.
- It does not show Ava completing external actions or contacting anyone for Farah.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.