Skip to content

Example

How to leave a long-running volunteer role without taking the institution home

Being helpful after leaving can prevent the next person from ever becoming the owner.

AI assistance helped shape this fictional example from a structured editorial brief. It was reviewed for usefulness, distinctness, accessibility, and product truth.

Superboard exampleVolunteer succession

Transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility

Successor promise1

Purpose, boundaries, and the definition of enough

Volunteer succession

Hold the mission and boundary: transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility

Transfer next4

The decision and preparation that deserve attention next

Live handover, written handbook, or records-only exit

Hold the live choice—whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing—so George can decide from the evidence in this Room

Draft the fallback boundary

Prepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed

Draft the successor-question prompt

Complete this as owned preparation; if another person must answer, keep it as an unsent draft until it is actually sent

List what only George currently knows before choosing a handover mode

Use the result of the first owned action to update the Succession-boundary brief; record the finding, not merely the effort

Institution evidence1

The visible proof behind the plan—not a vague feeling of readiness

Annual rhythm map and final access date

Supply the evidence for the Succession-boundary brief: place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.

An illustrative Board built from this fictional scenario. Adapt the Lists and Cards to your own mission.
01

George is an explicitly fictional portrait, not a customer or testimonial.

02

The Volunteer succession Board gives one mission a visible field; the Live handover, written handbook, or records-only exit Room keeps its evidence, conversation, state, and decision together.

03

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 Volunteer succession needs an operating picture

George is a fictional 72-year-old treasurer ending twenty years with a community club in Halifax, Nova Scotia. George knows every annual rhythm, files are partly digital, a successor is willing but cautious, and members keep asking him to remain available indefinitely.

Partly digital files do not explain the annual judgment George has carried for twenty years.

Every handover mode ends access on the same date; the choice is how much live explanation happens before responsibility actually transfers.

In You.one's Superboard view, George can give “Transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility” a Board of its own. That Board connects what matters, practical constraints, open questions, and personal agency; opening “Live handover, written handbook, or records-only exit” creates a Room for its evidence, discussion, state, and decision.

Volunteer succession has one live choice: Live handover, written handbook, or records-only exit

The mission is specific: Transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility.

The consequential choice is not something a board or an AI should quietly make: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.

You.one can keep the work, evidence, and “Live handover, written handbook, or records-only exit” decision visible through its Superboard view. The Owner boundary stays explicit: George, as the treasurer ending twenty years with a community club, owns the preparation and the decision about whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.

Available today

Volunteer succession: one Board shape to adapt

The Volunteer succession Board gives this mission one durable operating picture. George 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.

Its Cards deliberately distinguish actions, evidence, and decisions while keeping unsent questions in owned work. A Waiting List would be premature until a named request or outside condition is actually in motion. That separation makes the current choice, evidence, and next move easier to scan.

Volunteer succession Board shape
ListWhat belongs here
Successor promisePurpose, boundaries, and the definition of enough
Transfer nextThe decision and preparation that deserve attention next
Institution evidenceThe visible proof behind the plan—not a vague feeling of readiness

Available today

The Cards make the operating picture concrete

These Card titles come directly from George's situation: “Live handover, written handbook, or records-only exit” is the live choice, “Annual rhythm map and final access date” holds evidence, and “Draft the successor-question prompt” is still work George controls—not a fake Waiting item. The point is recognition, not a perfect taxonomy.

Example Cards for George
CardListJob
Volunteer successionSuccessor promiseHold the mission and boundary: transfer records, recurring decisions, and relationships with a clear end to George's operating responsibility
Live handover, written handbook, or records-only exitTransfer nextHold the live choice—whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing—so George can decide from the evidence in this Room
Annual rhythm map and final access dateInstitution evidenceSupply the evidence for the Succession-boundary brief: place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.
Draft the fallback boundaryTransfer nextPrepare the next owned move without treating a draft, check, or test as evidence that anyone has agreed
Draft the successor-question promptTransfer nextComplete this as owned preparation; if another person must answer, keep it as an unsent draft until it is actually sent
List what only George currently knows before choosing a handover modeTransfer nextUse the result of the first owned action to update the Succession-boundary brief; record the finding, not merely the effort

Available today

Available today: Live handover, written handbook, or records-only exit becomes a Room

Opening the Card gives the visible item durable depth. Stage can hold Succession-boundary brief: Place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: George will decide whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Succession-boundary brief and this Card Room's visible notes and left “Live handover, written handbook, or records-only exit” with George.”

A useful Card Chat request would be: “Compare the options on the Live handover, written handbook, or records-only exit Card using only the context visible in this Card Room. Tell me what is missing; do not choose, submit, book, buy, or message anyone.” 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.

George's call remains explicit: George, as the treasurer ending twenty years with a community club, owns the preparation and the decision about whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.

Inside the Live handover, written handbook, or records-only exit Room
SurfaceJob in this example
StageSuccession-boundary brief: Place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.
ChatKeep George's request and Ava's attributed response with the work
PulseOpen decision: George will decide whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing
ActivityAva compared the options in Card Chat using the Succession-boundary brief and this Card Room's visible notes and left “Live handover, written handbook, or records-only exit” with George

What to ask Ava—and what not to assume

These requests use the visible supported context inside the “Live handover, written handbook, or records-only exit” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; George 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 George, watch other Lists, or act outside this Card Room.

George, as the treasurer ending twenty years with a community club, owns the preparation and the decision about whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing. Ava may help only inside this Card Room; she cannot decide, represent anyone, contact people, or act elsewhere.

George finishes “List what only George currently knows before choosing a handover mode,” keeps “Annual rhythm map and final access date” beside “Live handover, written handbook, or records-only exit,” and does not treat “Draft the successor-question prompt” as completed or sent before doing the work.

  • Request idea: compare the options on the Live handover, written handbook, or records-only exit Card using only the context visible in this Card Room. Tell me what is missing; do not choose, submit, book, buy, or message anyone.
  • Request idea: use only the Succession-boundary 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 shared drive handover may still be enough

A shared drive handover is enough when the annual rhythm, final access date, successor questions, member expectations, and one agreed handover mode are already explicit.

It starts to break when partly digital files, annual judgment, indefinite fallback requests, and the final access date must inform the same exit choice.

The Volunteer succession Board earns its place only when the familiar tool—a shared drive handover—can no longer keep the reason, Succession-boundary brief, conversation, current state, decision, and history connected.

A starter recipe to adapt, not obey

George should rename every List or Card that feels artificial. This recipe succeeds when “Live handover, written handbook, or records-only exit” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.

Start with the Volunteer succession Board
StepAction
1. Write the missionTransfer records, recurring decisions, and relationships with a clear end to George's operating responsibility
2. Open the live choicePut “Live handover, written handbook, or records-only exit” in a Room of its own
3. Attach the evidenceSuccession-boundary brief: Place recurring work, access, judgment, relationships, and George's final date together. Live choice: Whether to run a live handover and end access on the final date, deliver a written handbook and end access on that date, or end access on the date with records transferred but no briefing.
4. Keep the work ownedKeep “Draft the successor-question prompt” in owned work and name the next visible move
5. Take the first owned actionList what only George currently knows before choosing a handover mode

Direction

Direction, not a current promise

The useful future step is timely orientation: Ava may surface “Live handover, written handbook, or records-only exit” when new evidence follows “Draft the successor-question prompt”, explain what changed in the Succession-boundary brief, and stop at the named Owner's authority boundary.

A future unified You.one experience could carry relevant context from “Live handover, written handbook, or records-only exit” 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

  • George is fictional and is not a customer, testimonial, research participant, or disguised real person.
  • This fictional example is not governance, fiduciary, financial, access-control, relationship, or succession advice; the club and successor own the real transfer and George owns his final boundary.
  • It does not show Ava completing external actions or contacting anyone for George.
  • It does not report a measured result, and this Board is a starting shape to adapt—not a universal prescription.

Use this example as a starting shape—not a claim about your life.

Get early access