This is Nielsen's first usability heuristic: people should always be able to tell what state the product is in and what just happened after they acted. On this site it covers loading and progress feedback, confirmation that setup worked, usage meters, and changes over time shown on metrics.
Nielsen's response-time limits give the timing: under 0.1 second feels instant, up to 1 second keeps the user's flow, and beyond about 10 seconds people lose focus unless they see progress. Brad Myers's 1985 CHI study concluded that percent-done progress indicators make programs more attractive and effective to use. Nielsen Norman Group's article on the heuristic ties clear status to user control and trust.
In onboarding, status feedback confirms that a connection, import or deployment actually worked before asking for the next step. In billing and upsells it means showing usage against the limit ("$0 / $120 this month", "14 of 20 left") and turning the pay button into a progress state so nobody double-charges.
How to use it
- Show a progress state on any button that starts a slow or payment action, and disable it while it runs.
- After setup steps, confirm success with a specific message ("API is ready", "3 files imported").
- Display usage as used vs limit with the period, near where users decide whether to upgrade.
Watch out
- Spinners with no end for long jobs; past about 10 seconds show progress or an estimate.
- Status that is technically present but hidden or ambiguous, like a tiny icon change after a payment.
