Research, evaluation and learning for better experiences.UX audits · Research · Training
Operational Workflow Evaluation · Moderated prototype testing

Finding the controls specialist users could not discover.

An operational planning prototype was tested on forecast review, limits and status changes before further design refinement.

5specialist participants
9reported task results
40–100%completion across tasks
Prototypeevaluation stage
Usability beneath the overall impression

High ease ratings did not mean every task worked.

Method, sample and scope make the evidence meaningful. Here is how the work was structured.

Study design

Moderated, task-based usability testing

Session mode

Moderated sessions using a user-testing tool; physical setting not specified

Tasks

Forecast review, planning navigation, limit setting and status changes

Measures

Task completion, reported ease-of-use ratings and observed failures

01

Set realistic tasks

Translate specialist activities into a prototype test.

Task scenarios
02

Observe performance

Record completion and ease ratings while watching the interaction.

Task-level evidence
03

Explain the failures

Connect missed controls and misplaced expectations to design changes.

Findings + proposed fixes
01 / PERFORMANCE & PERCEPTION

Observe the task, then interpret the rating.

TASK COMPLETIONReported study data

Nine tasks. Very different outcomes.

Five participants. Each participant represents 20 percentage points. Task wording is generalised; the results are not production performance measures.
View exact values
MeasureCompletion
Start planning100%
Find forecast100%
Review outlook80%
Find remarks80%
Open planning100%
Set field limit60%
Set facility limit100%
Change line status40%
Change facility status80%
REPORTED EASE OF USEReported study data

Even the difficult tasks received positive ratings.

Reported task ease ratings on a five-point scale. Interpret alongside observed performance; ratings and completion use different scales.
View exact values
MeasureEase rating
Start planning4.8 / 5
Find forecast4.6 / 5
Review outlook4.8 / 5
Find remarks4.2 / 5
Open planning5 / 5
Set field limit4.2 / 5
Set facility limit4.6 / 5
Change line status4.2 / 5
Change facility status4.2 / 5
A concrete mismatch worth investigating.

The line-status task recorded 40% completion alongside an ease rating of 4.2 out of 5. The observation notes explain that participants looked in a different planning area. This is why ratings alone would have concealed an important navigation problem.

02 / FROM FAILURE TO DESIGN ACTION

Trace a missed task to a specific interface decision.

01

A control was overlooked

Participants tried to change a default value rather than using the add-limit action.

DESIGN IMPLICATIONMake the add-limit action visible within the task context.
02

The wrong planning area felt plausible

Users looked for an operational status change in another planning tab.

DESIGN IMPLICATIONClarify tab labels and the boundary between planning areas.
03

Remarks were hard to locate

Review tasks depended on finding comments alongside forecast data.

DESIGN IMPLICATIONMake the presence and location of remarks easier to detect.
OBSERVE THE WORKThe UX Faculty
Our perspective
The most useful finding is the one that changes what you build next.

Real people. Real tasks. Evidence that gives the next design decision a reason.

THE WORK PRODUCED

Evidence that carries into the next decision.

Nine task results
Ease-of-use ratings
Observed failure patterns
Control-discovery findings
Navigation recommendations
Retesting priorities

Moderated usability report, pp. 2–5. Charts transcribe the key-results table. Labels are generalised. Five participants is a small sample, not a population estimate.

FROM EVIDENCE TO ACTION

What the work made possible.

Task-level results identified specific discoverability problems that broad satisfaction ratings would have missed.

Recommended next steps

  • Make the distinction between planning areas easier to recognise.
  • Increase the visibility of the control for adding a limit.
  • Retest the difficult tasks after revising labels and navigation.
YOUR NEXT STEP

What would you like to do better?

Tell us about your product, your questions or the skills you want to build.

Discuss your goals