Example
How a salon can run appointment operations without a double-booked chair
Gloria's problem is not a lack of effort. It is that Run the next two Saturdays with chairs, people, and color stock visible, without taking a wedding party that breaks standing appointments 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.
Gloria is an explicitly fictional portrait, not a customer or testimonial.
The Saturday operations Board gives one mission a visible field; the Choose the wedding-party request 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.
Gloria's pressure is ordinary—and still heavy
Gloria is a fictional 39-year-old owner of a three-chair salon in Chicago, Illinois. Gloria’s salon books from a phone, a website form, and walk-ins. One stylist is out Fridays. Color stock is counted on receipts. A wedding party asked for four simultaneous chairs on a Saturday that already has regulars.
Gloria can fill a Saturday. Filling it from three inboxes without a chair map is how a regular loses her standing time and a wedding party arrives to a wait.
The website form, voicemail, and a stylist’s personal texts all accept yes.
Color that is “probably enough” lives in a cabinet, not beside the wedding-party Card.
The chair is the constraint; the inbox is not the calendar
The mission is specific: Run the next two Saturdays with chairs, people, and color stock visible, without taking a wedding party that breaks standing appointments
The consequential choice is not something a board or an AI should quietly make: Whether to take the wedding party by moving two regulars, decline and offer a Sunday, or take two of the four guests and refer the rest
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Gloria still owns the purpose, tradeoff, and final call.
Available today
Saturday operations: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Gloria 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 | Chair capacity and the standing-appointment rule |
| Chairs | Who is working which seat, including absences |
| Bookings | Standing regulars, inquiries, and walk-in policy |
| Stock | Color and supplies that the week actually needs |
| Waiting | Client replies and vendor restocks |
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 Gloria would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Protect standing times | Mission | Keep chair count and the regulars rule visible beside growth |
| Choose the wedding-party request | Bookings | Compare move-regulars, Sunday offer, and split-party options |
| Friday stylist off | Chairs | Show a missing chair before Friday bookings pile in |
| Standing: Saturday 10am color | Bookings | Hold a regular’s time so an inbox yes cannot overwrite it quietly |
| Color stock versus wedding formula | Stock | Count cabinet inventory against the party request |
| Wedding party reply not sent | Waiting | Keep an unsent answer from counting as a booking |
Available today
Available today: Choose the wedding-party request becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Party-request brief: Place chair count, standing bookings, stock, and the three response options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Gloria to choose how the wedding-party request is answered. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare moving regulars, offering Sunday, and taking two guests. Do not message clients 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.
Gloria's call remains explicit: Gloria chooses the booking, talks to clients and stylists, and owns pricing and stock
| Surface | Job in this example |
|---|---|
| Stage | Party-request brief: Place chair count, standing bookings, stock, and the three response options on one page |
| Chat | Keep Gloria's request and Ava's attributed response with the work |
| Pulse | Waiting for Gloria to choose how the wedding-party request is answered |
| 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.
Gloria owns bookings, staff conversations, and spending. Ava does not message clients, take payments, or order color.
The modest outcome is not that Ava lives Gloria's life. The modest outcome is a Saturday that matches chairs: standing times stay visible, stock is counted, and the wedding party is a chosen yes or no.
- Request idea: summarize chairs, standing bookings, and stock already on the Board
- Request idea: compare wedding-party options using capacity Gloria captured
- Request idea: help keep unsent client replies in Waiting
Phone voicemail plus a paper book may still be enough
Phone voicemail plus a paper book is enough when one chair and no special requests
It starts to break when three intake channels, a missing stylist, and a four-chair party all say yes
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 Gloria'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. Map chairs | Who is working, including days off |
| 2. Protect standing bookings | Regulars as Cards, not assumed memory |
| 3. Count stock against requests | Cabinet facts beside special formulas |
| 4. Park unsent answers | An inquiry is not a yes |
| 5. Decide the special request | Open a Room before an inbox overwrites the book |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a booking Card exceeds visible chair Cards, still leaving every client message with Gloria.
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
- Gloria is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not a booking-system integration or a claim Superboard messaged clients.
- It does not show Ava taking payments, ordering supplies, or managing staff.
- It is not a measured revenue result.