Why Your Uptime Number Looks Better Than Customers Feel
A working note on perceived uptime vs measured — what matters, what does not, and where these projects usually go sideways.
Most conversations about perceived uptime vs measured start with a tool comparison. They should start with the workflow. This post walks the order we actually use for perceived uptime vs measured.
The problem underneath
The pattern repeats. Someone raises it in standup, a call is made in ten minutes, and the reasoning is never written down.
A month later three people are working from three different assumptions. The rework costs more than the original choice.
What this looks like in real projects
One common pattern we see: the first customer shaped the design, and the fifth one broke it. Nothing was wrong, the inputs changed.
The fix is usually smaller than the panic suggests, provided somebody maps the current state honestly.
Mistakes companies make
- Choosing tools before the workflow is written down.
- Scoping version one to cover every edge case.
- Leaving the work unowned, then blaming the tool.
- Skipping measurement, so nobody can prove it helped.
- Treating launch day as the end of the cost.
The first and the last are the expensive ones.
The engineering view on perceived uptime vs measured
From inside the codebase, perceived uptime vs measured reduces to three questions. What happens when a step fails halfway. Who finds out. How you reverse it.
Design for partial failure before you need it. Step three failing after one and two succeeded is the case people skip.
Give retries a ceiling and some jitter. A retry storm is an outage you built yourself.
How we approach it step by step
- Reproduce the pain with a real case, not a description of it.
- Write the target outcome as a single number.
- Pick the smallest change that could plausibly move that number.
- Build it with a rollback path.
- Release to one team or a slice of traffic.
- Review in two weeks, then widen, revise, or delete.
Deleting is a legitimate result. It happens less often than it should.
Practical guardrails
- Instrument before optimising.
- Cap spend and volume in code, not on the invoice.
- Write down the decision, not only the outcome.
- Keep one named owner with protected hours.
- Set a review date ninety days out and keep it.
Trade-offs worth saying out loud
Speed against flexibility. Managed service against control. Cheap now against cheap later. None of it is free.
This trade-off usually appears when the second customer wants something the first one didn't. That is the moment to revisit perceived uptime vs measured, not before.
Common misconceptions
“We need the best available option.” You need the one your team can operate at 2am. Rarely the same thing.
“We’ll do it properly later.” Sometimes true. Put a date on later or it never arrives.
“It’s a one-off.” Anything a customer touches becomes a product, support included.
Frequently asked questions
How long does perceived uptime vs measured take to get right?
A narrow first version is usually four to six weeks. Anything quoted at three months with nothing shippable in between is a risk, not a plan.
What is the most common mistake with perceived uptime vs measured?
Choosing tools before the workflow is written down. The tool then dictates the process instead of serving it.
How do we know whether it worked?
Choose the number before you build — hours saved, error rate, response time, or conversion — then compare a two-week window either side.
Do we need to hire someone for this?
Not at the start. One named owner with a few protected hours a week, plus a small build team, is enough to prove value.
Where do teams usually get stuck?
Between the prototype that impressed everyone and the version that survives real inputs. Budget time for the second half.
Conclusion
The useful move on perceived uptime vs measured is almost always the smaller one. Ship a narrow slice a real user can touch this month, measure it, then decide what earns the next four weeks.
Everything gets easier once something is live.
Related reading and next steps
- product design and UX — how we run this kind of work.
- AI product engineering — how we run this kind of work.
- More writing from the team.
Want a second opinion on perceived uptime vs measured for your setup? Book a 30-minute call. If it is not worth building, we will say so.
FAQ
Frequently asked questions
How long does perceived uptime vs measured take to get right?+
A narrow first version is usually four to six weeks. Anything quoted at three months with nothing shippable in between is a risk, not a plan.
What is the most common mistake with perceived uptime vs measured?+
Choosing tools before the workflow is written down. The tool then dictates the process instead of serving it.
How do we know whether it worked?+
Choose the number before you build — hours saved, error rate, response time, or conversion — then compare a two-week window either side.
Do we need to hire someone for this?+
Not at the start. One named owner with a few protected hours a week, plus a small build team, is enough to prove value.
Where do teams usually get stuck?+
Between the prototype that impressed everyone and the version that survives real inputs. Budget time for the second half.
Building something similar?
Let's talk in 30 minutes.