Example
How a cleaning service can grow without breaking the Thursday crew
Imani's problem is not a lack of effort. It is that Add work only on days the crew and van can actually support, while keeping Thursday residential stops honest 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.
Imani is an explicitly fictional portrait, not a customer or testimonial.
The Crew and routes Board gives one mission a visible field; the Choose the commercial Thursday ask 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.
Imani's pressure is ordinary—and still heavy
Imani is a fictional 41-year-old owner of a four-person residential cleaning service in Windsor, Ontario. Imani has a full Thursday route, a commercial inquiry that wants Thursdays, and one cleaner on reduced hours after a family change. Reviews are fine. The constraint is the van and the hours, not marketing.
Imani can sell more work. Selling Thursday work into a full van is how a regular house gets a rushed hour and a cleaner quits.
A booking inbox, a paper route sheet, and a payroll notebook do not agree on Thursday hours.
The commercial inquiry would pay more per hour and still collide with three residential stops that already trust the team.
A new account that lands on the full day is not growth
The mission is specific: Add work only on days the crew and van can actually support, while keeping Thursday residential stops honest
The consequential choice is not something a board or an AI should quietly make: Whether to decline the Thursday commercial job, offer them Tuesday, or split Thursday by dropping the farthest residential stop
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Imani still owns the purpose, tradeoff, and final call.
Available today
Crew and routes: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Imani 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 | Crew hours, van, and the days that are already full |
| Routes | Each day’s houses and travel |
| People | Cleaners’ real hours, including reduced ones |
| Inquiries | New work not yet on a route |
| Waiting | Client replies and supply orders |
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 Imani would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Grow into empty hours, not Thursday | Mission | Keep van and crew hours beside the appetite for new accounts |
| Choose the commercial Thursday ask | Inquiries | Compare decline, Tuesday offer, and drop-farthest-stop options |
| Thursday route: five houses | Routes | Show travel and hours that are already spoken for |
| Cleaner on reduced hours | People | Keep a real constraint from being treated as a full headcount |
| Commercial inquiry: Thursday only | Inquiries | Hold the constraint the client named instead of wishing it were Tuesday |
| Tuesday opening after noon | Routes | Mark actual unused capacity |
Available today
Available today: Choose the commercial Thursday ask becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Growth-path brief: Place Thursday hours, reduced crew, and decline / Tuesday / drop-stop options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Imani to choose whether Thursday can take new work. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare declining the Thursday job, offering Tuesday, and dropping the farthest stop. Do not contact the client 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.
Imani's call remains explicit: Imani chooses the account, talks to clients and crew, and owns scheduling and pay
| Surface | Job in this example |
|---|---|
| Stage | Growth-path brief: Place Thursday hours, reduced crew, and decline / Tuesday / drop-stop options on one page |
| Chat | Keep Imani's request and Ava's attributed response with the work |
| Pulse | Waiting for Imani to choose whether Thursday can take new work |
| 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.
Imani owns pricing, hiring, and client conversations. Ava does not schedule crew, message clients, or handle payroll.
The modest outcome is not that Ava lives Imani's life. The modest outcome is growth that fits hours: Thursday stays honest, Tuesday’s opening is visible, and the commercial ask is a chosen path.
- Request idea: summarize routes, people hours, and inquiries already on the Board
- Request idea: compare growth options using Thursday capacity Imani captured
- Request idea: help keep new work off Routes until it is chosen
A paper route sheet plus an inbox may still be enough
A paper route sheet plus an inbox is enough when the crew is full-time and days are even
It starts to break when a reduced-hour cleaner and a Thursday-only inquiry share a van
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 Imani'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. Mark full days | Thursday as a constraint, not a sales target |
| 2. Card real hours | Reduced hours are not a full person |
| 3. Keep inquiries off the route | Until a day is chosen |
| 4. Show empty capacity | Tuesday after noon as a fact |
| 5. Decide the colliding ask | Open a Room before a better rate overwrites regulars |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when an inquiry Card wants a day already marked full, still leaving every yes with Imani.
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
- Imani is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not employment, tax, or insurance advice.
- It does not show Ava messaging clients or scheduling crew.
- It is not a measured growth result.