Example
How a new manager can run the first 90 days without losing the listening
Keisha's problem is not a lack of effort. It is that Use the first 90 days to learn the team, stabilize coverage, and make one staffing call without turning every week into only the queue 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.
Keisha is an explicitly fictional portrait, not a customer or testimonial.
The First 90 days Board gives one mission a visible field; the Choose the March coverage path 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.
Keisha's pressure is ordinary—and still heavy
Keisha is a fictional 31-year-old newly promoted customer-support manager in Denver, Colorado. Keisha now leads six agents she used to sit beside. She has a 90-day outline from her director, a queue that is still on fire, and two overlapping coverage gaps. She does not want the first month to become only ticket volume.
Keisha’s director asked for a 90-day plan. The team needs coverage this week. If those live in different notebooks, the plan will be a slide and the week will be the real job.
One-on-ones are on a calendar. Notes are in a doc. The coverage gap is in the scheduling tool. None of them is the same picture.
A senior agent asked privately whether the night rotation will change. That question is now occupying Keisha’s commute.
Listening is work; it needs a list or it disappears
The mission is specific: Use the first 90 days to learn the team, stabilize coverage, and make one staffing call without turning every week into only the queue
The consequential choice is not something a board or an AI should quietly make: Whether to hire a seventh agent, pay overtime through March, or change the night rotation after the remaining one-on-ones
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Keisha still owns the purpose, tradeoff, and final call.
Available today
First 90 days: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Keisha 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 | What the 90 days are for besides queue volume |
| Listening | One-on-ones, observations, and questions still open |
| This week | Coverage and queue work that cannot wait |
| Building | Rituals, docs, and changes that take more than a week |
| Waiting | Director input, hiring, and agent replies |
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 Keisha would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Learn the team without losing coverage | Mission | Keep listening and staffing on the same mission as the queue |
| Choose the March coverage path | This week | Compare hiring, overtime, and night-rotation options |
| One-on-one remaining: Priya | Listening | Track who has not yet had a first conversation |
| Night-rotation question | Listening | Keep the private question attached to evidence, not to rumor |
| Weekend queue backup | This week | Hold the coverage gap that is already affecting customers this week |
| Director note on headcount | Waiting | Separate an unanswered budget question from Keisha’s next action |
Available today
Available today: Choose the March coverage path becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Coverage-path brief: Place queue load, remaining one-on-ones, and the hire / overtime / rotation options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Keisha to choose a coverage path she can take to her director. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare hiring, overtime, and changing the night rotation. Do not contact anyone 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.
Keisha's call remains explicit: Keisha chooses the coverage recommendation, talks to her director and team, and owns every staffing and schedule change
| Surface | Job in this example |
|---|---|
| Stage | Coverage-path brief: Place queue load, remaining one-on-ones, and the hire / overtime / rotation options on one page |
| Chat | Keep Keisha's request and Ava's attributed response with the work |
| Pulse | Waiting for Keisha to choose a coverage path she can take to her director |
| 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.
Keisha owns staffing, schedules, performance conversations, and anything she tells her director. Ava does not hire, change rotations, or speak to the team.
The modest outcome is not that Ava lives Keisha's life. The modest outcome is a 90-day Board that still includes listening: the weekend gap is visible, the private question has a home, and March coverage is a chosen path.
- Request idea: summarize listening, this-week coverage, and waiting items already on the Board
- Request idea: compare the three March coverage options using captured constraints
- Request idea: help keep unanswered director questions in Waiting
A private notes doc plus the scheduling tool may still be enough
A private notes doc plus the scheduling tool is enough when coverage is stable and listening is optional
It starts to break when a 90-day plan, a private question, and a weekend gap all claim this week
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 Keisha'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. Write the 90-day purpose | Listening and coverage both belong on the Mission Card |
| 2. Card the remaining conversations | One Card per one-on-one still ahead |
| 3. Put this week’s gaps on the Board | Queue and coverage issues get dates |
| 4. Park budget questions | Director input lives in Waiting |
| 5. Decide one staffing path | Open a Room before overtime becomes the default by neglect |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a listening Card has had no note for too long, still leaving every people decision with Keisha.
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
- Keisha is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not management training, HR advice, or a claim Superboard changed a schedule.
- It does not show Ava hiring, speaking to agents, or evaluating performance.
- It is not a measured team or customer-service result.