Example
How to prepare an interview loop without letting each round wipe the last
Sophie can prepare. What she cannot do is reconstruct Friday’s panel from memory if Thursday’s written exercise eats the notebook. The people, the stories, and the questions already asked need one home.
Walk each remaining round with the same story set, people map, and posting constraints, then decide with evidence rather than adrenaline
The role test and what would make Sophie walk away
Keep the walk-away line visible beside preparation
Keep the employer's role language beside Sophie's walk-away line and preparation choice
Each interviewer and what is known about them
Map who is in the room before Friday
Keep the recruiter's exact comment visible as context, not a promise about the panel
Evidence stories reused across rounds
Keep a reusable story with facts Sophie can stand behind
Hold a second reusable story with Sophie's decision, actions, and consequences separated from confidential detail
Written, panel, and director steps with dates
Compare written-exercise, mock-panel, and split-time options before Thursday
Hold the written prompt and its timebox as the current-round packet
Keep the panel date and preparation needs connected to Thursday's evidence
Keep a possible later round visible without treating it as scheduled
Scheduling, mock-panel times, and recruiter replies
Hold Sophie's sent scheduling request until Alex confirms a time before Thursday
Sophie is an explicitly fictional portrait, not a customer or testimonial.
The Interview loop Board gives one mission a visible field; the Choose Wednesday's prep focus 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 Interview loop needs an operating picture
Sophie is a fictional 28-year-old policy analyst in a four-round interview loop for a central-agency role in Ottawa, Ontario. Sophie has a written exercise Thursday, a panel Friday, and a possible director chat next week. Notes from the recruiter screen are in a notebook; the job posting is a PDF; the written brief is a new prompt that landed tonight.
The written prompt, the original posting, and the recruiter’s “they care about implementation” comment are currently three disconnected facts.
Alex offered to run a mock panel. That offer expires if Sophie does not pick a time before Thursday.
In You.one's Superboard view, Sophie can give “Walk each remaining round with the same story set, people map, and posting constraints, then decide with evidence rather than adrenaline” a Board of its own. That Board connects interview rounds, specific work stories, people involved, open questions, and the candidate's own judgment; opening “Choose Wednesday's prep focus” creates a Room for its evidence, discussion, state, and decision.
Each round needs the last round’s evidence
The mission is specific: Walk each remaining round with the same story set, people map, and posting constraints, then decide with evidence rather than adrenaline.
The consequential choice is not something a board or an AI should quietly make: Whether to use Wednesday night to sharpen the written exercise, run the mock panel, or split the remaining time between both.
You.one can keep the work, evidence, live dependency, and “Choose Wednesday's prep focus” decision visible through its Superboard view. The Owner boundary stays explicit: Sophie chooses Wednesday's preparation focus, writes her own exercise, and owns every conversation with Alex and the recruiter.
Available today
Interview loop: one Board shape to adapt
The Interview loop Board gives this mission one durable operating picture. Sophie 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 | The role test and what would make Sophie walk away |
| People | Each interviewer and what is known about them |
| Stories | Evidence stories reused across rounds |
| Rounds | Written, panel, and director steps with dates |
| Waiting | Scheduling, mock-panel times, and recruiter replies |
Available today
The Cards make the operating picture concrete
These Card titles come directly from Sophie's situation: “Choose Wednesday's prep focus” is the live choice, “Job posting: implementation and analysis language” holds evidence, and “Mock-panel time requested from Alex” names something genuinely in motion outside Sophie's control. The point is recognition, not a perfect taxonomy.
| Card | List | Job |
|---|---|---|
| Stay only if the work is analysis | Mission | Keep the walk-away line visible beside preparation |
| Choose Wednesday's prep focus | Rounds | Compare written-exercise, mock-panel, and split-time options before Thursday |
| Job posting: implementation and analysis language | Mission | Keep the employer's role language beside Sophie's walk-away line and preparation choice |
| Written exercise Thursday | Rounds | Hold the written prompt and its timebox as the current-round packet |
| Panel Friday | Rounds | Keep the panel date and preparation needs connected to Thursday's evidence |
| Director chat next week — possible | Rounds | Keep a possible later round visible without treating it as scheduled |
| Implementation story: grants desk | Stories | Keep a reusable story with facts Sophie can stand behind |
| Panel names from recruiter | People | Map who is in the room before Friday |
| Recruiter note: they care about implementation | People | Keep the recruiter's exact comment visible as context, not a promise about the panel |
| Stakeholder-recovery story: delayed grant launch | Stories | Hold a second reusable story with Sophie's decision, actions, and consequences separated from confidential detail |
| Mock-panel time requested from Alex | Waiting | Hold Sophie's sent scheduling request until Alex confirms a time before Thursday |
Available today
Available today: Choose Wednesday's prep focus becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Prep-focus brief: Place the written prompt, posting language, recruiter note, and Alex's pending time beside written / mock / split options. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Sophie will choose written exercise, mock panel, or split-time preparation.” Activity can preserve this attributed receipt: “Ava compared the options in Card Chat using the Prep-focus brief and this Card Room's visible notes and left “Choose Wednesday's prep focus” with Sophie.”
A useful Card Chat request would be: “Using only the context visible in this Card Room, compare using Wednesday for the written exercise, the mock panel, or a split between both. Do not write the exercise, contact Alex, 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.
Sophie's call remains explicit: Sophie chooses Wednesday's preparation focus, writes her own exercise, and owns every conversation with Alex and the recruiter.
| Surface | Job in this example |
|---|---|
| Stage | Prep-focus brief: Place the written prompt, posting language, recruiter note, and Alex's pending time beside written / mock / split options |
| Chat | Keep Sophie's request and Ava's attributed response with the work |
| Pulse | Open decision: Sophie will choose written exercise, mock panel, or split-time preparation |
| Activity | Ava compared the options in Card Chat using the Prep-focus brief and this Card Room's visible notes and left “Choose Wednesday's prep focus” with Sophie |
What to ask Ava—and what not to assume
These requests use the visible supported context inside the “Choose Wednesday's prep focus” Card Room. They do not imply that current Ava automatically surveys the whole Board or follows up on her own; Sophie 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 Sophie, watch other Lists, or act outside this Card Room.
Sophie owns her answers, her stories, and whether she continues. Ava does not write the exercise, attend interviews, or contact the recruiter.
A loop that remembers itself: Thursday’s prompt sits with the posting, stories are reusable, and Wednesday’s limited preparation time has a deliberate focus.
- Request idea: using only the context visible in this Card Room, compare using Wednesday for the written exercise, the mock panel, or a split between both. Do not write the exercise, contact Alex, or choose for me.
- Request idea: use only the Prep-focus 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 notebook plus the job PDF may still be enough
A notebook plus the job PDF is enough when there is one conversation.
It starts to break when a written round, a panel, and a walk-away line all have to survive the week.
The Interview loop Board earns its place only when the familiar tool—a notebook plus the job PDF—can no longer keep the reason, Prep-focus brief, conversation, current state, decision, and history connected.
A starter recipe to adapt, not obey
Sophie should rename every List or Card that feels artificial. This recipe succeeds when “Choose Wednesday's prep focus” becomes easier to decide and fewer open loops depend on memory—not when the Board looks tidy.
| Step | Action |
|---|---|
| 1. Write the walk-away line | Put it on the Mission Card before adrenaline writes it for you |
| 2. Card each round | Dates, prompts, and logistics in one place |
| 3. Build a story set | Reusable evidence, not a new personality each night |
| 4. Map people | Names and known focus for each interviewer |
| 5. Choose Wednesday's prep focus | Open a Room before the written exercise and mock-panel offer compete for the same night |
Direction
Direction, not a current promise
Later, Ava may help this Board carry notes from one round Card to the next inside the same Board, still leaving every answer with Sophie.
A future unified You.one experience could carry relevant context from “Choose Wednesday's prep focus” 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
- Sophie is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not interview coaching, a hiring prediction, or a claim Superboard contacted an employer.
- It does not show Ava writing answers or attending interviews.
- It is not a measured offer result.