Use cases · A product owner
Every page, reviewed
A job of hundreds of pages and two passes: every one seen, every fix recorded, and one short list of what only you can decide.
The situation
Fernhill makes scheduling software, and its site and app have grown for three years, a page at a time. Each page is fine on its own. Together they don’t match. Fixing any one of them is easy. Keeping track is not: which have been looked at, what was found, what was changed, what was decided along the way. Done from memory, pages get skipped and others get done twice. And a job this size is longer than any conversation an assistant can hold.
Kate owns the product, and hands the whole job to her coding assistant.
Handing it over
You: Go over every page of our site and app and make them consistent. Keep the logo; the colours are yours to change.
Assistant: Three rules first, with what I’d suggest: site and app, but not the admin panel? Check everything locally and never deploy? Edit the wording too, not only the look?
You: Yes to all three.
Assistant: I’ve listed 284 pages, dialogs and states from the code. I’ll look at each in light and dark, on desktop and phone, fix what I find, and record every fix. What only you can decide goes on a list for the end.
Kate answered three questions at the start, so the work could run without her. She won’t be asked again until the end.
Longer than one conversation
Halfway through the first pass, the assistant’s session ran out. The next one picked up at page 143, because the list and everything recorded against it were never in the conversation. Nothing was redone and nothing was skipped. When one fix reached many pages at once, like a shared button or a header, every page it reached was marked, so a second look could check exactly those.
Pass 2 of 2
All 284 looked at in the first pass, with 212 fixes recorded. What that pass decided is written down, and the second pass checks every page against it.
Changes that reached many pages
- One corner radius for buttons and cardsDone
- Sign-in link hidden when signed inDone
Questions for you
- Pricing says 5 seats; the app allows 3Decide
Left both as they are. Which is right?
- A new heading on the terms pageDecide
Changed nothing. Someone with legal sign-off should see it.
The next day
The next day, a fresh session
You: Where are we?
Assistant: The first pass is done on all 284, and every fix is recorded. The second is at 171. Only three questions need you, and they’re on your list.
Kate decides, once
At the end, Kate gets one short list: the three things only she could decide, each with what was found and what was left alone in the meantime. Everything else is done, and there is a record of each change for anyone who wants to check it.
The same works for anything large that needs the same careful look, more than once: every policy in a handbook, every product page in a catalogue, every module of a codebase before a release.
More stories
- Candidate search Hands over a job description, reviews the shortlist, and their feedback steers the next round.
- A software team Every assistant knows what is waiting for its person. People decide what gets built, how it is split, and when it is done.
- What to post about The assistant keeps track of the topics in their area and what they have posted on, and drafts on what is worth posting today. They approve, edit or discard.
- Relationships at scale Says who counts. The assistant finds the people, writes each a personal note, and keeps track of every conversation. Nothing is sent without them.
- Looking for a job Says once what they want. The assistant finds and screens openings, drafts what each one asks for, and applies to the ones they approve.
- Watching competitors Names the products and the competitors. The assistant matches them across sites, checks every week, and shows what changed.