Example
How to plan a small-team offsite when a change of scenery is not an agenda
Activities can make the agenda look full while work and inclusion stay vague. The team must choose the destination, stay local with better rooms, or split decision work and social time across locations.
Use two days for one relationship outcome, two explicit decisions, and a remote experience that is not a camera on a table
Purpose, boundaries, and the definition of enough
Hold the mission and boundary: use two days for one relationship outcome, two explicit decisions, and a remote experience that is not a camera on a table
The decision and preparation that deserve attention next
Hold the live choice—whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations—so Neha can decide from the evidence in this Room
Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed
Use the result of the first owned action to update the Offsite-shape brief; record the finding, not merely the effort
The visible proof behind the plan—not a vague feeling of readiness
Supply the evidence for the Offsite-shape brief: place outcomes, decisions, travel, room quality, remote inclusion, and energy together. Live choice: Whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations.
Keep this second source of evidence beside the choice and record what could make it stale

In You.one’s Superboard view, the Two days together Board separates the offsite promise, agenda work, decision evidence, team constraints already known, and arrangements accountable people actually confirm.
Open Destination, local, or split as the consequential Card Room. Start by writing what must be different the following week, then test the room and remote connection against both decisions.
After an explicit request, Ava can compare visible constraints or draft an agenda for team review. Ava cannot speak for employees, assess accessibility or privacy, book, purchase, require travel, or approve the plan; the organization and team retain authority.
Two days together has one live choice: Destination, local, or split
This Board has one job: Use two days for one relationship outcome, two explicit decisions, and a remote experience that is not a camera on a table.
The decision still belongs to Neha: Whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations.
You.one can keep the work, several kinds of evidence, and “Destination, local, or split” decision visible through its Superboard view. The organized facts support Neha; they do not replace Neha's judgment: Neha, as the team lead planning a two-day retreat for eight people, owns the preparation and the decision about whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations.
Available today
Two days together: one place for the mission
The Two days together Board gives this mission one durable operating picture. Neha can use familiar language instead of translating the situation into project-management jargon. Its three Lists separate the kinds of attention this situation actually requires.
The Board is not a master task list. It keeps the live choice, the facts that could change it, and any reply or outside event already in motion visible without pretending every uncertainty is work in progress.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Offsite promise | Purpose, boundaries, and the definition of enough |
| Agenda next | The decision and preparation that deserve attention next |
| Decision evidence | The visible proof behind the plan—not a vague feeling of readiness |
Available today
Cards that sound like the real work
These Card titles come directly from Neha's situation: “Destination, local, or split” is the live choice, while “Two decisions needing the room” and “Team constraints already known” hold different facts that can change it. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| Two days together | Offsite promise | Hold the mission and boundary: use two days for one relationship outcome, two explicit decisions, and a remote experience that is not a camera on a table |
| Destination, local, or split | Agenda next | Hold the live choice—whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations—so Neha can decide from the evidence in this Room |
| Two decisions needing the room | Decision evidence | Supply the evidence for the Offsite-shape brief: place outcomes, decisions, travel, room quality, remote inclusion, and energy together. Live choice: Whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations. |
| Design remote participation | Agenda next | Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed |
| Team constraints already known | Decision evidence | Keep this second source of evidence beside the choice and record what could make it stale |
| Write what must be different the week after the offsite | Agenda next | Use the result of the first owned action to update the Offsite-shape brief; record the finding, not merely the effort |
Available today
Keep the evidence with “Destination, local, or split”
Opening the Card gives the visible item durable depth. Stage can hold Offsite-shape brief: Place outcomes, decisions, travel, room quality, remote inclusion, and energy together. Live choice: Whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Neha will decide whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Destination, local, or split” from the visible evidence. Ava can work from the context Neha deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Neha's call remains explicit: Neha, as the team lead planning a two-day retreat for eight people, owns the preparation and the decision about whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Offsite-shape brief: Place outcomes, decisions, travel, room quality, remote inclusion, and energy together. Live choice: Whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations |
| Chat | Keep Neha's request and Ava's attributed response with the work |
| Pulse | Open decision: Neha will decide whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations |
Start small and rename what feels artificial
Neha should rename every List or Card that feels artificial. This recipe succeeds when “Destination, local, or split” 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 mission | Use two days for one relationship outcome, two explicit decisions, and a remote experience that is not a camera on a table |
| 2. Open the live choice | Put “Destination, local, or split” in a Room of its own |
| 3. Attach the evidence | Offsite-shape brief: Place outcomes, decisions, travel, room quality, remote inclusion, and energy together. Live choice: Whether to choose the destination venue, stay local with better rooms, or split decision work and social time across locations. |
| 4. Use the supporting fact | Keep “Team constraints already known” with the evidence that can change the choice |
| 5. Take the first owned action | Write what must be different the week after the offsite |
An agenda document can remain part of the system
An agenda document can be enough while the situation stays simple: “Two decisions needing the room” and “Team constraints already known” are settled enough that “Destination, local, or split” no longer needs comparison.
It starts to break when “Two decisions needing the room” and “Team constraints already known” must inform the same choice.
The Two days together Board earns its place only when the familiar tool—an agenda document—can no longer keep the reason, Offsite-shape brief, conversation, current state, decision, and history connected.
Where this example stops
- This is a fictional example, not a customer story.
- This fictional example is not employment, accessibility, travel, privacy, safety, or management advice; the organization must include the real team and own every decision.
- It does not show Ava completing external actions or contacting anyone for Neha.
- It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.