Stop 06 · Interaction Design & Micro-interactionsTopics · 4/9

Feedback & System Status

In short

Nothing makes people more anxious than not knowing what's happening. Is it loading? Did my payment go through? Good feedback answers that question before the user has to ask it.

Always showing the user what's happening — a loading spinner, a success confirmation, a progress bar — so they're never left wondering if their action worked, is still processing, or failed silently.

The jaadu relaxes on a railway platform bench eating a samosa while a train approaches.

Think of it like this

The railway platform announcement

You're waiting for your train. The board says 'Running late by 20 minutes, arriving platform 4'. You relax and grab a samosa. Without that board you'd be pacing and asking every coolie. Status messages turn worry into patience.

Watch it happen

Paying for a movie ticket

User

App

Bank

Tap 'Pay Rs 250'

1/6The user commits money. This is the most anxious moment in the whole flow.

The big ideas

What you need to know

Instant acknowledgement

Within a moment of a tap, show something: a pressed state, a spinner, a disabled button.

Match feedback to wait time

Short waits need a spinner. Longer ones need progress or a message about what's happening.

Confirm the outcome

Say clearly that it worked, with details: 'Saved to Drafts', not just a vanishing spinner.

Show where they are

Step indicators and highlighted tabs tell people where they are in a flow or app.

Save yourself the pain

Common mistakes

Oops

Showing the same spinner for a 1-second save and a 40-second upload.

Do this instead

For long tasks show progress, a percentage or a step label, and let people keep using the app if possible.

Oops

Closing a form silently after it's submitted.

Do this instead

Show a confirmation that says what happened and what comes next.

Your mission

Map the status moments

~25 min

Quick check

An export takes about 30 seconds. What feedback fits best?

Go deeper

1Audit a flow for any point where system status is unclear or missing entirely.
2Design explicit loading, success, and error feedback states for a sample action.
3Learn this maps directly to the first of Nielsen's usability heuristics (Phase 7).