The AI Learning Hub Journal

Could Anyone Else Run This?

Could anyone else run this?the prototype was yours, and that was fine — the product belongs to the business, and real customers plan Saturdays around itTODAY, IT ALL LIVES IN ONE HEADevery passwordwhere each bill arrivesthe it-broke habitsthe put-it-back stepswhich service does whatthe awkward customer’s quirka product one person can run is aliability wearing a success costumenothing dramatic needs to go wrong —a holiday will do it; so will flu; so willyou, reasonably, moving to your next ideathis weekTHE HANDOVER FILE — ONE HONEST PAGE, KEPT WHERE THE BUSINESS CAN FIND IT1where the app runs, and how to sign in2where the data lives, where the backups live — and when you last restored one3the services it stands on, and where each bill arrives4how to put back the last good version — the exact steps, written, not remembered5the five recurring support problems, with their fixes, from your support notesnotice what is not on the page: anything about the code — a person taking over does notneed to read it any more than you did; running a product is locations, steps and habitsTHE TEST — HAND IT OVER LIKE A STRANGER, BECAUSE YOUR OWN HEAD CARRIES INVISIBLE HELPa capable friend —sensible, not an engineeronly the page —and you stay quietone houron the clockask them to talk you through taking over:sign infind last month’s billput back the last good versionanswer the commonest support emailevery place they get stuck is a line the page is missing — and every missing line still lives only in your headupdate the page, then repeat once a year, or whenever something big changes — like testing your app as a stranger, but for your headyou are not preparing for disaster, exactly — you are removing the single point of failure that is youA PRODUCT THAT BENEFITS FROM YOU — NOT ONE THAT NEEDS YOU which is what the business always needed it to be — one honest page is the whole distance between the two
The bus factor, asked kindly: if you took three weeks of holiday, what would happen to the bookings?

The Question Nobody Wants to Ask

Engineers have a blunt name for this: the bus factor — how many people would have to be hit by a bus before nobody could run the thing. Let us ask it more kindly. If you went on holiday for three weeks, what would happen to the groomer's bookings? Right now, every password, every bill and every it-broke habit from Module 4 lives in exactly one place: your head. The prototype was yours, and that was fine — it existed to answer your question. The product belongs to the business. Real customers plan their Saturdays around it, and a product that only one person on earth can run is a liability wearing a success costume. Nothing dramatic needs to go wrong for this to matter. A holiday will do it. So will flu. So will you, entirely reasonably, moving on to your next idea.

  • The bus factor: how many people could run this without you
  • Today the passwords, bills and it-broke habits live only in your head
  • The prototype was yours; the product belongs to the business
  • A product one person can run is a liability wearing a success costume

The Handover File: One Honest Page

The fix is not a technical project. It is one honest page, written this week and kept somewhere the business could find it. Where the app runs, and how to sign in. Where the data lives, where the backups live, and when you last restored one. The services it stands on, and where each bill arrives. How to put back the last good version when a change goes wrong — the exact steps from Module 4, written down rather than remembered. And the five support problems that keep recurring, with their fixes, straight from your support notes. Notice what is not on the page: anything about the code. A person taking over does not need to read the code any more than you did. They need to run the product, and running a product is a set of locations, steps and habits — all of which fit on one page.

  • One page: where it runs, where data and backups live, services and bills
  • The put-it-back steps written down, not remembered
  • The five recurring support problems and their fixes
  • Nothing about the code — running a product is locations, steps and habits

Test It Like a Handover

Vibecoding taught you to test your app like a stranger, because your own machine carries invisible help. Test the handover page the same way, because your own head does too. Hand the page to a capable friend — not an engineer, just someone sensible — and ask them to talk you through taking over: signing in, finding last month's bill, putting back the last good version, answering the most common support email. Give them an hour, and stay quiet. Every place they get stuck is a line the page is missing, and every missing line is something that still lives only in your head. Update the page, then repeat once a year, or whenever something big changes. You are not preparing for disaster, exactly. You are turning a product that happens to have you into a product that merely benefits from you — which is what the business always needed it to be.

  • A capable friend, the page, an hour — and you stay quiet
  • Every place they stall is a line the page is missing
  • Whatever is not on the page still lives only in your head
  • The goal: a product that benefits from you, not one that needs you

Prefer slides, quizzes, and saved progress? Read this lesson in the library — free, no sign-up.