Example
How to redesign a personal website without rebuilding it twice in the same month
Ivy’s five-year-old site needs a useful first screen before next month’s talk, but rebuilding the stack would consume the date. She must restyle what exists, migrate one case study, or ship a one-page site and postpone the rebuild.
Ship a site that puts three case studies on the first screen before the talk, without requiring a new stack unless it fits the date
Talk URL and three case studies
Keep the talk date beside the buried work
Work samples that get hired
Name a sample that is not currently findable
Type, layout, and what is only taste
Hold taste work so it cannot outrank content
Current stack versus new stack
Compare restyle-current, migrate-one-study, and one-page-postpone-rebuild
Mark a tempting rebuild as extra until the date allows it
The talk listing date next month
Keep a public date from depending on an unfinished rebuild
In You.one’s Superboard view, the Site before the talk Board separates the public promise, case-study content, design taste, build paths, and the date that is actually fixed.
Open Choose restyle, one-migrate, or one-page as the decision Room, with a Ship-path brief that keeps the three case studies and talk URL ahead of framework work.
After an explicit request, Ava can compare only the visible Room notes. Ivy owns the case-study claims, design, code, accessibility, deployment, domain, and every public release decision.
A new stack is not a case study, and a talk date is a ship date
The mission is specific: Ship a site that puts three case studies on the first screen before the talk, without requiring a new stack unless it fits the date.
The consequential choice is not something a board or an AI should quietly make: Whether to restyle the current site, migrate one case study to the new stack, or ship a one-page site and postpone the rebuild.
You.one can keep the work, evidence, anything already waiting on another person or event, and the “Choose restyle, one-migrate, or one-page” decision visible through its Superboard view. Ivy still owns the call: Ivy chooses the stack, writes the pages, and owns the deploy.
Available today
Site before the talk: the working map
The Site before the talk Board gives this mission one durable operating picture. Ivy 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 separate what Ivy can move now, what is evidence, what is already waiting on a named person or event, and what still needs a decision.
Swipe or scroll sideways to see every column.
| List | What belongs here |
|---|---|
| Mission | Talk URL and three case studies |
| Content | Work samples that get hired |
| Design | Type, layout, and what is only taste |
| Build | Current stack versus new stack |
| Replies and outside conditions | The talk listing date next month |
Available today
Open one decision: Choose restyle, one-migrate, or one-page
Opening the Card gives the visible item durable depth. Stage can hold Ship-path brief: Place talk date, buried case studies, and restyle / one-migrate / one-page options on one page. Chat keeps the request and response beside that artifact instead of in a detached thread. Pulse can show “Open decision: Ivy will choose a ship path that hits the talk.”
A Card Chat request can ask Ava to prepare the specific comparison or extraction in “Choose restyle, one-migrate, or one-page” from the visible evidence. Ava can work from the context Ivy deliberately brings into this Card, List, or Board; she cannot monitor the rest of life, contact anyone, or inherit the decision.
Ivy's call remains explicit: Ivy chooses the stack, writes the pages, and owns the deploy.
Swipe or scroll sideways to see every column.
| Surface | Job in this example |
|---|---|
| Stage | Ship-path brief: Place talk date, buried case studies, and restyle / one-migrate / one-page options on one page |
| Chat | Keep Ivy's request and Ava's attributed response with the work |
| Pulse | Open decision: Ivy will choose a ship path that hits the talk |
Useful Ava requests, with the boundary intact
These requests stay with the facts Ivy has made visible around “Choose restyle, one-migrate, or one-page.” Ivy 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 Ivy, watch other work on her own, or contact anyone.
Ivy owns design, content, and deploys. Ava does not publish the site or write the case studies in her place.
A URL that works: three case studies are findable, a new stack is a chosen extra, and typefaces are not the project.
- Request idea: using only the context visible in this Card Room, compare restyling the current site, migrating one case study, and shipping a one-pager. Do not deploy or choose for me.
- Request idea: use only the Ship-path brief and notes the Owner has placed in this Card Room to separate facts, assumptions, and unanswered questions
- Request idea: in “Choose restyle, one-migrate, or one-page,” show which visible fact could reverse the current choice
The limit of a Figma file plus a half-started new repo
A Figma file plus a half-started new repo can be enough while the situation stays simple: the work is already on the first screen.
It starts to break when a talk URL, buried case studies, and a new stack all claim the month.
The Site before the talk Board earns its place only when the familiar tool—a Figma file plus a half-started new repo—can no longer keep the reason, Ship-path brief, conversation, current state, decision, and history connected.
A practical way to start the Site before the talk Board
Ivy should rename every List or Card that feels artificial. This recipe succeeds when “Choose restyle, one-migrate, or one-page” 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 talk date | A URL that must not 404 |
| 2. List three case studies | The work that gets hired |
| 3. Cap taste work | Typefaces are not content |
| 4. Park the new stack | Until the date allows it |
| 5. Choose restyle, one-migrate, or one-page | Open a Room before rebuilding twice |
Where this example stops
- This is a fictional example, not a customer story.
- This is not a hiring, SEO, or traffic claim.
- It does not show Ava deploying a site or writing case studies.
- It is not a measured career result.