Example
How to run a recruiting search without turning the pipeline into a pile of names
Hugh’s intake says night experience, but the pipeline has been open nine weeks. He must keep that requirement, rewrite the role for days, or pause the on-sites and reopen sourcing without letting tiredness make an employment decision.
Finish this search against the written must-haves, with on-sites that still mean something, or reopen sourcing on purpose
Must-haves and the no-drift rule
Keep the written requirement visible beside fatigue
People with evidence, not vibes
Name the must-have mismatch with candidate evidence
Keep the written must-have beside a candidate who meets it
Screens, on-sites, and offers
Keep the first interview commitment separate from candidate evidence
Keep the second interview commitment separate from candidate evidence
Must-haves versus tired rewrites
Compare keeping nights, rewriting for days, and pausing on-sites
Keep Hugh’s reopen option beside the must-have until he chooses
References already requested from named people
Keep Hugh’s already-sent reference request visible without confusing it with the reopen decision
The Supervisor search Board keeps candidate evidence, process commitments, role truth, and a reference already requested from Maria Chen separate.
Open Choose keep, rewrite, or reopen as a Room with the written requirement, candidate evidence, both on-sites, and the sourcing option.
Ava can compare evidence without ranking or rejecting people. Hugh owns the role decision and every candidate conversation; HR and legal own compliance, and Ava does not contact or hire candidates.
Tiredness is not a new job description
The work has a clear center: Finish this search against the written must-haves, with on-sites that still mean something, or reopen sourcing on purpose.
Organizing the evidence does not authorize the software to decide: Whether to keep the night-experience must-have, rewrite the role for days, or pause on-sites and reopen sourcing.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose keep, rewrite, or reopen” decision visible through its Superboard view. Hugh still owns the call: Hugh chooses the role truth, talks to the recruiter, and owns every candidate conversation.
Available today
Name the work in plain language
These Card titles come directly from Hugh's situation: “Choose keep, rewrite, or reopen” is the live choice, “Days-only candidate: Ana” holds evidence, and “Maria Chen reference reply” names something genuinely in motion outside Hugh's control. The point is recognition, not a perfect taxonomy.
Swipe or scroll sideways to see every column.
| Card | List | Job |
|---|---|---|
| Must-have: night experience | Mission | Keep the written requirement visible beside fatigue |
| Choose keep, rewrite, or reopen | Role truth | Compare keeping nights, rewriting for days, and pausing on-sites |
| Days-only candidate: Ana | Candidates | Name the must-have mismatch with candidate evidence |
| Night-experience candidate: Marcus | Candidates | Keep the written must-have beside a candidate who meets it |
| Recruiter: reopen sourcing? | Role truth | Keep Hugh’s reopen option beside the must-have until he chooses |
| Maria Chen reference reply | Replies and outside conditions | Keep Hugh’s already-sent reference request visible without confusing it with the reopen decision |
| Thursday on-site scheduled | Process | Keep the first interview commitment separate from candidate evidence |
| Friday on-site scheduled | Process | Keep the second interview commitment separate from candidate evidence |
Available today
Supervisor search: separate the kinds of attention
The Supervisor search Board gives this mission one durable operating picture. Hugh 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.
The Lists use Hugh's own language so actions, evidence, open questions, and decisions do not collapse into one queue. A separate place for replies is useful only after Hugh has asked someone or a real outside event must happen first.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Mission | Must-haves and the no-drift rule |
| Candidates | People with evidence, not vibes |
| Process | Screens, on-sites, and offers |
| Role truth | Must-haves versus tired rewrites |
| Replies and outside conditions | References already requested from named people |
Ask Ava to prepare the judgment—not make it
These requests stay with the facts Hugh has made visible around “Choose keep, rewrite, or reopen.” Hugh supplies the evidence, checks Ava's work, and decides what belongs in the Room.
Current Ava can prepare help after an explicit request. She cannot make the choice, represent Hugh, watch other work on her own, or contact anyone.
Hugh owns the role-truth call and candidate conversations. HR and legal own compliance. Ava does not contact candidates or Maria Chen, chase the reference reply, reject people, or write offers.
A search that still has a job description: night experience is kept, rewritten, or sourcing reopens—on purpose.
- Request idea: using only the context visible in this Card Room, compare keeping the night must-have, rewriting for days, and pausing to reopen sourcing. Do not contact candidates or Maria Chen, chase the reference reply, or choose for me.
- Request idea: use only the Role-truth brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Choose keep, rewrite, or reopen,” group the visible evidence by option and leave the decision open
Available today
One Card Room for the consequential choice
Opening the Card gives the visible item durable depth. Stage can hold Role-truth brief: Place must-haves, on-site mismatch, and keep / rewrite / reopen options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Hugh will choose whether to keep the night requirement, rewrite the role for days, or pause on-sites and reopen sourcing.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose keep, rewrite, or reopen” from the visible evidence. Ava can work from the context Hugh deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Hugh's call remains explicit: Hugh chooses the role truth, talks to the recruiter, and owns every candidate conversation.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Role-truth brief: Place must-haves, on-site mismatch, and keep / rewrite / reopen options on one page |
| Chat | Keep Hugh's request and Ava's attributed response with the work |
| Pulse | Open decision: Hugh will choose whether to keep the night requirement, rewrite the role for days, or pause on-sites and reopen sourcing |
Build only enough Board to make the next decision
Hugh should rename every List or Card that feels artificial. This recipe succeeds when “Choose keep, rewrite, or reopen” 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. Put must-haves on the Board | Written, not remembered |
| 2. Card candidates with evidence | Liked-them is not a stage |
| 3. Map process dates | On-sites as commitments |
| 4. Keep sent references on Replies and outside conditions | Maria Chen was already asked; Ava does not chase the reply |
| 5. Choose keep, rewrite, or reopen | Open a Room before fatigue rewrites the job |
Where this example stops
- This is a fictional example, not a customer story.
- This is not employment-law or hiring-outcome advice.
- It does not show Ava contacting candidates or making a hiring decision.
- It is not a measured time-to-hire result.