Why Healthcare Is Different
A bug in a shopping app loses a sale. A bug in a health app can lose something you can't refund. That single difference is why "move fast and break things" runs into a wall here that most other software never hits.
“Move fast and break things” built half the apps on your phone, and most of the time a broken thing is just an inconvenience. A bug in a shopping app loses a sale. A bug in a health app can lose something you cannot refund. That single difference is why the fastest-moving habit in software engineering runs straight into a wall the moment it enters healthcare.
A bug in a shopping app loses a sale
Ship a checkout bug and a customer's cart empties itself. They are annoyed, they maybe tweet about it, and they buy the thing tomorrow instead. The company loses a transaction worth a few dollars to a few hundred. The failure is fully recoverable — refund the order, patch the code, apologise, move on. Most software failures, even bad ones, look like this.
A bug in a health app can lose more than that
Ship a dosage-calculation bug and a patient gets the wrong amount of a drug. Ship a bug that silently drops a penicillin allergy from a record, and the next prescription written against that record can trigger a reaction. Neither failure has an “undo” button. You cannot refund a medication error the way you refund an order.
Shopping app bug
Lost sale, refunded order, an annoyed customer who buys again tomorrow.
Fully recoverable. The cost is measured in dollars.
Health app bug
A dropped allergy, a wrong dosage, a missed alert — the kind of failure a patch cannot undo after the fact.
Not always recoverable. The cost is measured in harm.
Why "move fast and break things" doesn't work here
That slogan works when the cost of a bug is small and reversible enough that shipping fast and fixing later beats shipping slow and safe. Healthcare inverts both halves of that trade: the cost of a bug is not small, and it is frequently not reversible. Moving fast still matters — a clinic drowning in paperwork is its own kind of harm — but the same three months a startup spends on user growth, a health tech team often spends on validating that a feature is safe before anyone with a real diagnosis touches it.
Key takeaways
- A shopping-app bug costs a transaction and is fully recoverable — refund it, patch it, move on.
- A health-app bug can drop an allergy or miscalculate a dose, and neither failure has an undo button.
- "Move fast and break things" assumes bugs are cheap and reversible — healthcare breaks both assumptions at once.
- Moving slower here is not the same as moving worse. It is often the reason a team only has to ship a feature once.