Example
How to rebuild a job search after a layoff without automating judgment
Andre's problem is not a lack of effort. It is that Run a targeted search for scheduling or operations roles while finishing layoff paperwork and protecting household travel limits has outgrown scattered reminders, tabs, and memory. This fictional playbook shows a concrete Board, the Cards inside it, one consequential Room, and the line Ava does not cross.
This fictional example was created with AI assistance from a structured editorial brief and reviewed by the You.one Editorial Team for usefulness, distinctness, and product truth.
Andre is an explicitly fictional portrait, not a customer or testimonial.
The Search after layoff Board gives one mission a visible field; the Choose travel versus commute Room keeps its evidence, conversation, state, and decision together.
Current Superboard provides the durable structure and explicit, bounded Ava paths described here; broader proactive or external work is not a current promise.
Andre's pressure is ordinary—and still heavy
Andre is a fictional 47-year-old former plant scheduler searching after a layoff in Hamilton, Ontario. Andre’s plant closed a line and his role went with it. He has a severance packet, a benefits deadline, two former colleagues offering introductions, and a spreadsheet of postings that all look equally urgent.
Andre needs work, and he also needs to file the remaining layoff paperwork on time. Treating every job post as the same kind of urgency is how the benefits form gets buried under a Tuesday interview that is not a fit.
The spreadsheet has status columns. It does not hold what a former colleague actually offered to do, or which roles travel more than the household can take.
A benefits form is due Friday. It currently lives in a paper envelope on the kitchen table while the search lives on a laptop.
Benefits dates and role judgment are not the same list
The mission is specific: Run a targeted search for scheduling or operations roles while finishing layoff paperwork and protecting household travel limits
The consequential choice is not something a board or an AI should quietly make: Whether to pursue a well-paid role with weekly travel, keep the search local, or use the colleague introduction at a plant that is a longer commute but no overnight travel
That distinction matters. Superboard can make the work, evidence, waiting, and decision visible. Andre still owns the purpose, tradeoff, and final call.
Available today
Search after layoff: one Board shape to adapt
A useful Board gives this mission one durable operating picture. Andre does not have to convert life into project-management jargon or decide the perfect taxonomy first. Lists separate kinds of attention; Cards keep each meaningful item visible and movable.
The Cards are deliberately mixed. Some are tasks, some are decisions, some hold a person or promise, and some are reference points. Current Superboard supports that flexibility without flattening the mission into one long to-do list.
| List | What belongs here |
|---|---|
| Mission | Role family, travel limit, and remaining paperwork dates |
| Paperwork | Severance, benefits, and records that have hard dates |
| Target roles | Roles worth preparing, not every posting |
| People | Introductions and references as promises with owners |
| Waiting | Applications, referrals, and benefit confirmations |
Available today
The Cards make the operating picture concrete
A Board becomes useful when the Card titles sound like the actual situation. These are not generic placeholders; they show what Andre would need to see to run this mission without carrying every open loop in memory.
| Card | List | Job |
|---|---|---|
| Find work that fits the household | Mission | Keep travel limits and remaining benefits dates on the same mission as the search |
| Choose travel versus commute | Target roles | Compare weekly-travel, local-only, and longer-commute-no-overnight options |
| Benefits continuation form Friday | Paperwork | Keep the kitchen-table envelope visible as work with a date |
| Colleagues intro to Lakeside scheduling | People | Record what the colleague offered, not just a company name |
| Applied: Westend production planner | Waiting | Hold a submitted application so it stops occupying preparation energy |
| Résumé version for scheduler roles | Target roles | Keep the actual file attached to the role family it serves |
Available today
Available today: Choose travel versus commute becomes a Room
Opening the Card gives the visible item durable depth. Stage can hold Search-constraint brief: Place household travel limits, commute times, and the three role-path options beside remaining paperwork dates. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show Waiting for Andre to choose the travel constraint that will govern the search. Activity preserves the attributable Card record supported by the current product.
A useful Card Chat request would be: “Using only this Board, compare the travel role, local-only search, and longer-commute introduction. Do not contact anyone or choose for me.” When live AI is configured, current Ava can respond to an explicit Card mention using supported context and can make limited reversible product changes. She does not deeply reason over the whole Board by default, and she does not gain authority over the decision merely because the context is organized.
Andre's call remains explicit: Andre chooses the travel constraint, files paperwork, and owns every conversation and application
| Surface | Job in this example |
|---|---|
| Stage | Search-constraint brief: Place household travel limits, commute times, and the three role-path options beside remaining paperwork dates |
| Chat | Keep Andre's request and Ava's attributed response with the work |
| Pulse | Waiting for Andre to choose the travel constraint that will govern the search |
| Activity | Preserve attributed Card changes and the supported record around the request |
What to ask Ava—and what not to assume
These are useful requests to adapt, not claims that current Ava automatically surveys the whole Board, prepares every comparison, or follows up on her own. The relevant facts must be present in supported Board/Card context, and the human still checks the result.
Andre owns paperwork, applications, household decisions, and every conversation. Ava does not file benefits, apply, or contact colleagues.
The modest outcome is not that Ava lives Andre's life. The modest outcome is a search with a governing constraint: Friday’s form is on the Board, travel is a decision, and introductions are specific promises.
- Request idea: summarize paperwork dates, target roles, and waiting applications already on the Board
- Request idea: compare travel-versus-commute options using constraints Andre captured
- Request idea: help keep submitted applications and unconfirmed intros in Waiting
A job-search spreadsheet may still be enough
A job-search spreadsheet is enough when paperwork is done and roles are similar
It starts to break when a benefits deadline and a travel tradeoff are hiding behind status words
Superboard earns a place only when the responsibility needs a durable picture around the list: the reason, artifact, conversation, current state, decision, and history.
A starter recipe to adapt, not obey
Use the names that already make sense in Andre's world. The recipe is successful when the Board reduces remembering and exposes the real decision—not when every Card is perfectly categorized.
| Step | Action |
|---|---|
| 1. Put paperwork on the Board | Benefits and severance dates are Cards, not kitchen piles |
| 2. Write the household constraint | Travel and commute limits go on the Mission Card |
| 3. Add only real targets | One Card per role you would actually take |
| 4. Name the people | Record what each colleague offered to do |
| 5. Decide the travel question | Open a Room before applying to a role that breaks the household |
Direction
Direction, not a current promise
Later, Ava may help this Board notice when a people Card has no next visible step, still leaving every message with Andre.
The unified You.one and Superboard runtime, cross-product personalized Memory Spine, broad proactive coordination, realtime shared editing, and general external execution are not available today. Future actions would still require the applicable capability, connection, grant, and human authority.
What this realistic example does not claim
- Andre is fictional and is not a customer, testimonial, research participant, or disguised real person.
- This is not employment-law, benefits, or financial advice.
- It does not show Ava applying, contacting employers, or filing government forms.
- It is not a measured time-to-hire or a testimonial about a layoff.