Part 4 of 9 · 2 min read
Turn vague words into numbers
How to make "fast", "many" and "reliable" checkable.
A requirement is useful only if it can be checked. "Fast" cannot be checked. "Under 300 milliseconds for 99 out of 100 requests" can.
Here is a method with three steps. Take a vague word. Ask "measured how?" Then pick a number and a unit.
| Vague word | Measured how? | A checkable version |
|---|---|---|
| Fast | Time until the page appears, for most users | 99 out of 100 page loads finish in under 500 milliseconds |
| Many users | Users who open the app on a given day | 200,000 daily active users |
| Reliable | Share of time the service answers | Up 99.9 percent of the time (about 8.8 hours of downtime a year) |
| Large | Total data stored | 5 terabytes after one year |
| Safe | What must never be lost | No saved order is ever lost, even if one server fails |
Daily active users
Daily active users, often written DAU, is the number of different people who use the system at least once in one day.
Example: if 40,000 different people open a shop app on Monday, the shop has 40,000 DAU that day.
The numbers do not have to be exact. They must be written down and sensible. Level 0, module 3 shows how to turn them into traffic and storage figures.
A worked example. A designer is told: "The school notice board app must be fast and handle all the students."
- Ask: how many students? Answer: 1,500.
- Ask: how many open it each day? Assume two thirds, so about 1,000 daily active users.
- Ask: how fast is fast? Assume the page should appear in under one second for 99 out of 100 views.
- Ask: how reliable? A short outage at night is acceptable. Assume 99.5 percent.
In four lines, a vague wish became four numbers. The design can now be tested against them. With 1,000 users a day, a single small server is enough. That is an important result, and it came from asking.
Check yourself:
- Turn "the app must handle lots of photos" into one checkable sentence.
- Why is "99 out of 100" more useful than "most of the time"?