Example
How a new manager can run the first 90 days without losing the listening
Keisha still has two one-on-ones to complete and no director answer on headcount. Before recommending a seventh agent, overtime through March, or a changed night rotation, she needs the listening evidence beside the queue.
Use the first 90 days to learn the team, stabilize coverage, and make one staffing call without turning every week into only the queue
What the 90 days are for besides queue volume
Keep listening and staffing on the same mission as the queue
One-on-ones, observations, and questions still open
Track who has not yet had a first conversation
Keep the private question attached to evidence, not to rumor
Keep the second unfinished listening conversation visible beside the coverage decision
Coverage and queue work that cannot wait
Hold the coverage gap that is already affecting customers this week
Hold the second overlapping coverage gap separately from the weekend problem
Rituals, docs, and changes that take more than a week
Compare hiring, overtime, and night-rotation options
Turn listening into a repeatable practice that survives the first urgent week
Sent budget-information asks and agent replies; no hiring decision is implied
Keep Keisha's sent budget question visible until her director replies
The First 90 days Board keeps listening, this week’s pressure, longer-term building work, and replies already requested in one picture.
The Choose the March coverage path Card becomes a Room for queue gaps, remaining conversations, and the three staffing postures.
Ava can organize the visible evidence. Keisha owns the recommendation and team conversations; the director owns headcount, and Ava hires or changes rotations for nobody.
Listening is work; it needs a list or it disappears
The work has a clear center: Use the first 90 days to learn the team, stabilize coverage, and make one staffing call without turning every week into only the queue.
Organizing the evidence does not authorize the software to decide: Whether to recommend hiring a seventh agent, paying overtime through March, or changing the night rotation after the remaining one-on-ones.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose the March coverage path” decision visible through its Superboard view. Keisha still owns the call: Keisha chooses the coverage recommendation she will take to her director and owns the team conversations; headcount stays with the director.
Available today
Name the work in plain language
These Card titles come directly from Keisha's situation: “Choose the March coverage path” is the live choice, “Weekend queue backup” holds evidence, and “Director reply on headcount requested” names something genuinely in motion outside Keisha's control. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| 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 | Building | Compare hiring, overtime, and night-rotation options |
| Weekend queue backup | This week | Hold the coverage gap that is already affecting customers this week |
| 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 |
| One-on-one remaining: Mateo | Listening | Keep the second unfinished listening conversation visible beside the coverage decision |
| Weeknight queue gap | This week | Hold the second overlapping coverage gap separately from the weekend problem |
| Director reply on headcount requested | Replies already requested | Keep Keisha's sent budget question visible until her director replies |
| Weekly one-on-one ritual | Building | Turn listening into a repeatable practice that survives the first urgent week |
Available today
First 90 days: separate the kinds of attention
The First 90 days Board gives this mission one durable operating picture. Keisha can use familiar language instead of translating the situation into project-management jargon. Its five Lists separate the kinds of attention this situation actually requires.
The Lists use Keisha'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 Keisha has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| 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 |
| Replies already requested | Sent budget-information asks and agent replies; no hiring decision is implied |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Keisha has made visible around “Choose the March coverage path.” Keisha 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 Keisha, watch other work on her own, or contact anyone.
Keisha owns the coverage recommendation, team conversations, and anything she tells her director; headcount stays with the director. Ava does not hire, change rotations, or speak to the team.
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: using only the context visible in this Card Room, compare hiring, overtime, and changing the night rotation. Do not contact anyone or choose for me.
- Request idea: use only the Coverage-path brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Choose the March coverage path,” 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 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 “Open decision: Keisha will choose a coverage path she can take to her director.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose the March coverage path” from the visible evidence. Ava can work from the context Keisha deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Keisha's call remains explicit: Keisha chooses the coverage recommendation she will take to her director and owns the team conversations; headcount stays with the director.
Swipe or scroll sideways to see every column.
| 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 | Open decision: Keisha will choose a coverage path she can take to her director |
Build only enough Board to make the next decision
Keisha should rename every List or Card that feels artificial. This recipe succeeds when “Choose the March coverage path” 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 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 Replies already requested |
| 5. Choose the March coverage path | Open a Room before overtime becomes the default by neglect |
Where this example stops
- This is a fictional example, not a customer story.
- 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.