Common failures
Where this usually goes wrong
The three we are called in to fix most often. If any of these describe your current setup, that is the first thing we would change.
Measurement
How you will know it is working
Agreed before we start, so progress is visible in the months before it shows up in revenue.
- Time to first usable release
- How quickly real users are on something real. Shorter is better almost regardless of scope.
- Weeks 6–10
- p95 response time under load
- Measured against projected volume, not current volume. It is the number that decides whether growth breaks the product.
- Pre-launch
- Error rate per session
- From the error reporter. A rising rate after a release is the fastest signal that something shipped broken.
- Ongoing