Why Opinion Is Not Enough

Research and a solid design system can carry a project far, but neither can tell you whether a real person will instinctively find the button and complete the flow you spent hours perfecting. Until actual users interact with your product, every assumption about navigation, labeling, and layout remains theory.

Usability testing replaces that guesswork with behavioral data. Instead of asking people whether they like a design, it observes what they do: where they click, how long a step takes, and where they get stuck or abandon the task entirely.

Indigo.Design brings this testing into the design workflow, so you can validate an interactive prototype before you commit to building features that miss the mark.

Moderated Versus Unmoderated Testing

Usability tests generally fall into two camps. Moderated tests have a facilitator present in real time, guiding participants and probing their decisions as they happen. Unmoderated tests run remotely on the participant's own schedule, with no facilitator watching the session live. That approach scales to larger participant pools and is often simpler to coordinate.

Indigo.Design supports both scenarios, making it possible to collect quantifiable behavioral data even when a live research session isn't feasible.

Get A Workable Prototype First

The sweet spot for usability testing comes at the medium-fidelity prototype stage. The design needs enough interactivity to support the tasks you plan to test, even if the visual polish is not there yet. A static shell is too thin to reveal navigational problems, while a near-launch design is too late to change cheaply.

Testing an MVP at this stage pays off in two ways: iteration costs stay low, and user feedback prevents you from building features or writing content that your audience does not actually need.

Upload A Prototype

Adding a prototype to Indigo.Design requires either of two routes. You can upload a file directly from your machine in PNG, JPG, GIF, or Sketch formats. Alternatively, install the Indigo.Design plugin for Sketch to sync designs to the cloud, which also streamlines the later handoff to developers.

Once loaded, select "Edit Prototype" to double-check the interactive setup. If hotspots and connections were not defined in Sketch, you can create them right in the Indigo.Design cloud — draw the hotspot on the interface on the left, then drag it to its target card to link the interaction.

Define Tasks And Success Paths

From the prototype dashboard, hover over the design and create a new usability test, or switch to the Usability Tests tab to start one there. That same tab later serves as the hub for managing tests and reviewing results.

A test is built around specific tasks — the meaningful goals you expect users to accomplish, such as "create a new budget" in a finance app. For each task, you walk through the prototype yourself, interacting exactly as you want users to interact on the live product. This defines the expected success path that participant behavior will be measured against.

Set Context And Test Parameters

Bare tasks are not enough. Participants who arrive without context may feel the rough edges of an MVP are defects rather than work in progress. In the "Test Settings" tab, add a welcome message that sets the stage: explain what the product is, why you built it, and what you hope the test will reveal. A thank-you statement closes the session cleanly and can direct participants to follow-up expectations.

The "Success Criteria" toggle changes how results are classified. With it enabled, each task records a binary pass or fail. Leave it off, and the tool will also recognize alternative paths that accomplish the task without following your exact expected route. Identifying those detours is precisely what makes the data useful, so keeping the toggle off is generally the better choice.

Run The Test And Collect Data

Click "Start Testing" to generate a shareable link. Participants using Chrome will be prompted to install a recording extension that captures their screen, microphone, and camera, and they can opt out of any of those feeds. The participant completes the test in their own browser, and you click "Stop Testing" once responses are collected.

Reading The Results

Every completed test appears in the Usability Tests dashboard. Opening a test shows results grouped by task, with three headline metrics per task:

  • Success rate: the percentage of users who followed your expected steps exactly.
  • Accomplished task: the count of users who finished the task, including those on alternative paths when Success Criteria is disabled.
  • Avg. time on task: how long completion took on average.

The numbers tell you whether users reached the goal, but the side panel shows where they diverged. Red marks and numbered indicators on your original path flag the places where participants deviated. Click-level tracing reveals the failure points far more precisely than a heatmap, which only approximates where attention landed.

A detailed legend makes deviations easy to scan:

  • Blue circles mark expected interactions.
  • Red diamonds mark unexpected interactions.
  • Orange squares mark requests for help.

Mine The Alternative And Failed Paths

Comparing the stats for "Alt. Success Path" and "Failed Path" explains the friction. If a significant share of users completes the task via the same route you did not anticipate, their instinctive path is probably the better one — and you should redesigned the flow around it. If a task ends in failure at a noticeable rate, inspect that step for genuinely unintuitive interactions, such as a control that only responds to a right-click.

A handful of stray clicks is normal. The real signal arrives when paths diverge consistently, or when users abandon the task altogether.

Watch The Behavior, Not Just The Numbers

Quantitative steps alone miss the pain participants felt along the way. Reviewing individual sessions adds context. If the browser recording was enabled, the "Play Video" option shows the full session. Alternatively, use the "View path" link for any subject to inspect each click in sequence, laid out over the static prototype pages. That ordering often reveals a misunderstanding faster than a screen recording can, and it makes trends across multiple participants much easier to spot.

Beyond Pixel-Perfect Design

A design system alone doesn’t guarantee a usable product. Consistent, attractive interfaces are a starting point, but they don’t reveal whether users can actually accomplish their goals without friction. That’s where integrated usability testing becomes a differentiator.

What sets the Indigo.Design workflow apart is that it embeds usability testing directly into the design process rather than treating it as a separate, post-launch activity. The tooling is built to surface the real paths users take and the points where they struggle, whether you’re running the sessions in a moderated or unmoderated format.

The value here is in moving beyond the assumption that visual consistency equals intuitive interaction. By mapping user journeys accurately and identifying friction points early, teams can make iterative corrections based on evidence rather than intuition. The result is not just a polished UI, but one that has been validated against actual user behavior.

In short, the focus shifts from shipping designs that look complete to shipping experiences that work as intended. That’s the practical advantage of having usability testing baked into the design environment.