Example
How to onboard into a remote role without losing access, people, or the first deliverable
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.
Decide a truthful Friday posture—join briefed, join as a note-taker, or delay—so week one is not only account setup
What Friday actually requires besides a laptop
Keep access, a truthful Friday role, and the first useful deliverable inside the same week-one purpose
Accounts, folders, tools still closed, and onboarding modules that do not unblock Friday
Keep the folder Rowan cannot yet see visible as a current access fact
Separate required modules from the work that unblocks Friday
Manager, buddy, and customer names
Capture the overlapping hour with a west-coast buddy
Name who can approve a delay or clarify Rowan's role
Keep the missing customer-side owner explicit; Rowan does not contact anyone until the team names the right person
Kickoff, notes, and the first internal deliverable
Compare delay, silent notes, and same-day briefing options
Keep the missing agenda visible as a gap, not as a scheduled success
Keep the actual first deliverable, its Friday use, and the access it still needs visible
IT tickets and unanswered asks
Hold the submitted IT request as the live dependency instead of re-asking in chat every hour
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 You.one provides the Superboard structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Why Remote week one needs an operating picture
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.
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.
In You.one's Superboard view, Rowan can give “Decide a truthful Friday posture—join briefed, join as a note-taker, or delay—so week one is not only account setup” a Board of its own. That Board connects access requests, Friday outcomes, meeting context, and the new employee's questions and commitments; opening “Choose how to handle Friday’s kickoff” creates a Room for its evidence, discussion, state, and decision.
Access is not orientation, and Friday still happens
The mission is specific: Decide a truthful Friday posture—join briefed, join as a note-taker, or delay—so week one 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.
You.one can keep the work, evidence, live dependency, and “Choose how to handle Friday’s kickoff” decision visible through its Superboard view. The Owner boundary stays explicit: Rowan chooses the Friday plan and owns every conversation with manager, buddy, IT, and the customer.
Available today
Remote week one: one Board shape to adapt
The Remote week one Board gives this mission one durable operating picture. Rowan 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.
Its Cards deliberately distinguish actions, evidence, a live dependency, and decisions. A Waiting List is useful here only because a named request or outside condition is already in motion. That separation makes the current choice, evidence, and next move easier to scan.
| List | What belongs here |
|---|---|
| Mission | What Friday actually requires besides a laptop |
| Access | Accounts, folders, tools still closed, and onboarding modules that do not unblock Friday |
| 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
These Card titles come directly from Rowan's situation: “Choose how to handle Friday’s kickoff” is the live choice, “Customer folder still closed” holds evidence, and “Customer folder access ticket” names something genuinely in motion outside Rowan's control. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Make week one more than account setup | Mission | Keep access, a truthful Friday role, and the first useful deliverable inside the same week-one purpose |
| Choose how to handle Friday’s kickoff | First work | Compare delay, silent notes, and same-day briefing options |
| Customer folder still closed | Access | Keep the folder Rowan cannot yet see visible as a current access fact |
| Kickoff invite without agenda | First work | Keep the missing agenda visible as a gap, not as a scheduled success |
| Buddy briefing window | People | Capture the overlapping hour with a west-coast buddy |
| Manager: Friday kickoff owner | People | Name who can approve a delay or clarify Rowan's role |
| Customer agenda owner not yet named | People | Keep the missing customer-side owner explicit; Rowan does not contact anyone until the team names the right person |
| First deliverable: implementation checklist | First work | Keep the actual first deliverable, its Friday use, and the access it still needs visible |
| Customer folder access ticket | Waiting | Hold the submitted IT request as the live dependency instead of re-asking in chat every hour |
| 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 “Open decision: Rowan will choose how Friday’s kickoff should work.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Kickoff-readiness brief and this Card Room's visible notes and left “Choose how to handle Friday’s kickoff” with Rowan.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, 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 Room context and can make limited reversible changes inside this Card Room after an explicit request. She uses only supported Room context; she cannot summarize the Board, watch other Lists, or act outside this Card Room. 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 | Open decision: Rowan will choose how Friday’s kickoff should work |
| Activity | Ava compared the options in Card Chat using the Kickoff-readiness brief and this Card Room's visible notes and left “Choose how to handle Friday’s kickoff” with Rowan |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose how to handle Friday’s kickoff” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Rowan must provide the relevant facts and check the result.
Current Ava can reply in this Room to an explicit Card mention using supported Room context. She cannot summarize the Board, make the choice, represent Rowan, watch other Lists, or act outside this Card Room.
Rowan owns messages to manager, buddy, IT, and customers. Ava does not request access, join meetings, or speak as Rowan.
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: using only the context visible in this Card Room, compare delaying Friday, joining as a note-taker, and keeping the kickoff with a buddy briefing. Do not contact anyone or choose for me.
- Request idea: use only the Kickoff-readiness brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: name which visible Room note could most change the comparison; do not watch other Lists or follow up autonomously
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.
The Remote week one Board earns its place only when the familiar tool—a company onboarding checklist in email—can no longer keep the reason, Kickoff-readiness brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Rowan should rename every List or Card that feels artificial. This recipe succeeds when “Choose how to handle Friday’s kickoff” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| 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. Choose how to handle Friday’s kickoff | 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.
A future unified You.one experience could carry relevant context from “Choose how to handle Friday’s kickoff” across guidance and the Superboard view. Broad proactive coordination, cross-surface personalized memory, realtime shared editing, and general external execution are not available today. Any future action 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.