Example
How to onboard into a remote role without losing access, people, or the first deliverable
Rowan's problem is not a lack of effort. It is that Reach Friday’s customer kickoff with enough access, context, and a named backup so the first week is not only account setup 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.
Rowan is an explicitly fictional portrait, not a customer or testimonial.
The Remote week one Board gives one mission a visible field; the Choose how to handle Friday’s kickoff 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.
Rowan's pressure is ordinary—and still heavy
Rowan is a fictional 29-year-old new remote implementation specialist at a software company in St. John's, Newfoundland and Labrador. Rowan’s first week is a maze of accounts, a buddy in another time zone, and a customer kickoff on Friday they have not been briefed for. HR thinks onboarding is complete when the laptop ships.
Rowan can log into email. They cannot yet see the customer folder, the implementation checklist, or who owns the kickoff agenda. The buddy is kind and already underwater.
IT tickets, HR modules, and a team wiki each claim to be onboarding.
A calendar invite for Friday’s kickoff arrived without an agenda or a named backup if access is still blocked.
Access is not orientation, and Friday still happens
The mission is specific: Reach Friday’s customer kickoff with enough access, context, and a named backup so the first week is not only account setup
The consequential choice is not something a board or an AI should quietly make: Whether to ask the manager to delay Friday, join as a silent note-taker, or keep the kickoff and get a same-day briefing from the buddy
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Rowan still owns the purpose, tradeoff, and final call.
Available today
Remote week one: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Rowan 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 Friday actually requires besides a laptop |
| Access | Accounts, folders, and tools still closed |
| People | Manager, buddy, and customer names |
| First work | Kickoff, notes, and the first internal deliverable |
| Waiting | IT tickets and unanswered asks |
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 Rowan would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Be useful by Friday without faking access | Mission | Keep the kickoff real and refuse to treat laptop shipping as onboarding |
| Choose how to handle Friday’s kickoff | First work | Compare delay, silent notes, and same-day briefing options |
| Customer folder access ticket | Waiting | Hold the IT request so Rowan is not re-asking in chat every hour |
| Buddy briefing window | People | Capture the overlapping hour with a west-coast buddy |
| Kickoff invite without agenda | First work | Keep the missing agenda visible as a gap, not as a scheduled success |
| HR modules remaining | Access | Separate required modules from the work that unblocks Friday |
Available today
Available today: Choose how to handle Friday’s kickoff becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Kickoff-readiness brief: Place access status, buddy hours, and the delay / notes / briefing options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Rowan to choose how Friday’s kickoff should work. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare delaying Friday, joining as a note-taker, and keeping the kickoff with a buddy briefing. 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.
Rowan's call remains explicit: Rowan chooses the Friday plan and owns every conversation with manager, buddy, IT, and the customer
| Surface | Job in this example |
|---|---|
| Stage | Kickoff-readiness brief: Place access status, buddy hours, and the delay / notes / briefing options on one page |
| Chat | Keep Rowan's request and Ava's attributed response with the work |
| Pulse | Waiting for Rowan to choose how Friday’s kickoff should 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.
Rowan owns messages to manager, buddy, IT, and customers. Ava does not request access, join meetings, or speak as Rowan.
The modest outcome is not that Ava lives Rowan's life. The modest outcome is a first week with a chosen Friday posture: access tickets are tracked, the missing agenda is visible, and onboarding is not only HR modules.
- Request idea: summarize remaining access, people, and first-work Cards
- Request idea: compare Friday options using access status and buddy hours already captured
- Request idea: help keep IT tickets in Waiting instead of as endless chat pings
A company onboarding checklist in email may still be enough
A company onboarding checklist in email is enough when the first deliverable is internal and access is already open
It starts to break when a customer kickoff is Friday and the folder is still closed
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 Rowan'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. Define Friday | Write what the first customer moment actually requires |
| 2. List closed doors | One Card per account or folder still blocked |
| 3. Name the people | Manager, buddy, and customer contacts as Cards |
| 4. Park tickets | Submitted IT asks go to Waiting |
| 5. Decide the kickoff posture | Open a Room before showing up unbriefed or staying silent by default |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a first-work Card still depends on a Waiting access ticket, still leaving every ask with Rowan.
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
- Rowan is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not an employer’s official onboarding program or a claim Superboard accessed company systems.
- It does not show Ava talking to IT, joining a customer call, or completing HR modules.
- It is not a measured onboarding or performance result.