Research, evaluation and learning for better experiences.UX audits · Research · Training
Enterprise Planning Research · Discovery research

Understanding the manual work behind an operational planning system.

An internal planning application needed to reflect how specialist users collected, checked and analysed operational information.

6users interviewed
2specialist role groups
4stages in the documented journey
Onlineinterview mode
Discovery in a specialist environment

The interface was only one part of the work.

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

Study design

Qualitative discovery interviews, personas, journey mapping and task analysis

Session mode

Remote interviews through an online meeting platform

Sample

Four participants in one specialist role and two in another

Research question

How do people collect, validate, analyse and report planning information?

01

Understand the roles

Build on workshop knowledge and interview the people doing the work.

Role needs + behavioural observations
02

Map the current journey

Connect the tasks, pain points and workarounds across the planning process.

Current-state journey map
03

Shape opportunities

Translate manual effort and information gaps into proposed capabilities.

Opportunity map + proposed-flow direction
01 / THE CURRENT-STATE JOURNEY

Where manual coordination consumed attention.

01

Request inputs

Work observed
Send requests and follow up for submissions.
Friction
Repeated manual coordination.
Opportunity
Submission tracking and reminders.
02

Validate data

Work observed
Compare new information with previous forecasts.
Friction
Copying and checking across sources.
Opportunity
Highlight changes and discrepancies.
03

Analyse

Work observed
Adjust inputs and assess supply and demand.
Friction
Heavy files and less time for analysis.
Opportunity
Preserve flexible editing with clearer summaries.
04

Report

Work observed
Prepare the view for cross-role review.
Friction
Confirm activities and operational feasibility.
Opportunity
Make the planned picture easier to review.

A generalised reconstruction of the documented journey. It maps qualitative evidence; it does not assign invented effort or time scores.

02 / TWO ROLES, A SHARED WORKFLOW

Design around the handover as well as the screen.

Planning perspective

Collect information, compare forecasts and shape the planned view while retaining the ability to make informed adjustments.

Operational perspective

Bring execution context into the review so planned activities can be considered alongside operational feasibility.

Shared design question: how can the system reduce repeated coordination while preserving expert judgement?
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.

Role profiles
Behavioural observations
Journey map
Pain-point synthesis
Opportunity mapping
Task analysis

Discovery research deck, slides 2–10. Journey and role visuals are redrawn summaries; no additional timing or productivity measures are inferred.

FROM EVIDENCE TO ACTION

What the work made possible.

The study produced role-specific needs, a current-state journey and opportunities to guide proposed workflows.

Recommended next steps

  • Surface changes between current and previous submissions.
  • Make submission status and follow-up needs visible.
  • Preserve controlled editing while reducing repeated data entry.
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