The AI Learning Hub Journal

Finding Out It Broke Before They Tell You

A broken booking page is quiet: no bookings, and no complaintscustomers do not report problems — they leave, and what you notice is a quiet week, days laterTWO SILENCES — IDENTICAL FROM THE INSIDEa quiet inbox — everything is finebookings arriving, nothing to saya quiet inbox — the door is lockedcustomers have stopped knocking=a dog owner who meets a blank page at nine in the evening does not email you — they ring in the morning, or try the place across town“nobody has complained” is the most dangerous sentence in running a productTHREE MODEST WATCHERS — NOT A WALL OF SCREENS, ONE DAY ON THE LEDGERA HEARTBEATsomething checks the page everyfew minutes, and messages youthe moment it isn’t therea standard, cheap service — silentuntil the day it earns its keepcatches deadAN ERROR LOGa running list of things the appfound wrong, glanced at overcoffee once a daysmall problems surface beforethey have time to growcatches sickA WEEKLY NUMBERfor the groomer: bookings madethis week — a number you wouldnotice going to zerofailures that look healthy fromevery other angle show up herecatches looks-healthy-but-isn’tWHEN THE ALARM GOES — THE ORDER MATTERS MORE THAN THE SKILL1LOOKopen the page yourself andsee what a customer sees2PUT IT BACKroll back to the last versionthat worked — steps practised3DIAGNOSEonly now, with customers backon a page that worksrunning the broken thing while you investigate is optional, and it is the option to decline — customers do not benefit from your curiositythe heartbeat message arrives while you are making dinner — this order is what turns that moment into a routineWATCHING BUYS TIMING, NOT PERFECTIONknowing within minutes instead of next morning is the difference between a hiccup nobody noticed and a story your customers tell
Silence cannot tell a healthy week from a locked door — you need something other than silence.

Silence Is Not a Signal

Here is the uncomfortable fact about a broken booking page: it is quiet. It produces no bookings, and it also produces no complaints, because customers do not report problems — they leave. A dog owner who meets a blank page at nine in the evening does not email you about it. They ring the groomer in the morning, or they try the place across town. What the groomer notices is not an error message but a quiet week, and by then the page may have been down for days. This is why "nobody has complained" is the most dangerous sentence in running a product. Silence can mean everything is fine, and it can mean the door is locked and customers have stopped knocking. From the inside, those two silences are identical. You need something other than silence to tell them apart.

  • A broken booking page produces no bookings and no complaints
  • Customers don't report problems — they leave, quietly
  • The groomer notices a quiet week, not an error message
  • "Nobody has complained" cannot tell a healthy week from a locked door

Three Modest Watchers

Watching a product does not require a wall of screens. Three modest things cover most of it. First, a heartbeat: something that checks the page every few minutes and messages you the moment it isn't there. This is a standard, cheap service — you give it your address and your phone, and it does nothing at all until the day it earns its keep. Second, an error log you actually glance at: a running list of things the app found wrong, read over coffee once a day, so small problems surface before they grow. Third, a weekly number you would notice going to zero — for the groomer, bookings made this week. Each watcher catches what the others miss: the heartbeat catches dead, the log catches sick, and the number catches failures that look healthy from every other angle. Setting them up is the ledger's watching line: one day.

  • A heartbeat: something checks the page every few minutes and messages you
  • An error log you glance at daily, so small problems surface early
  • One weekly number you would notice going to zero — bookings made
  • Dead, sick, and looks-healthy-but-isn't: each watcher catches one

When the Alarm Goes

The heartbeat message arrives while you are making dinner. What now? The order matters more than the skill. First, look: open the page yourself and see what a customer sees. Second, put it back: roll back to the last version that worked, using the steps you practised in the first lesson. Only then, third, diagnose. Running the broken thing while you investigate is optional, and it is the option you should decline — customers do not benefit from your curiosity. Vibecoding taught you to watch the first five minutes after sharing; this is that habit made permanent. It is worth being clear about what the watchers actually buy you: not the absence of failure, but the timing of it. Knowing within minutes instead of next morning is the entire difference between a hiccup nobody noticed and a story your customers tell.

  • Look first: open the page and see exactly what a customer sees
  • Roll back before you diagnose — put back the version that worked
  • Running the broken thing while you think is optional; decline it
  • Watching buys timing, not perfection: minutes instead of next morning

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