Try the workflow yourself to ask better discovery questions

Trying a workflow yourself can reveal friction that a process diagram misses. Use what you observe to ask better questions, then check your interpretation with the people who do the work.

Build & Validate
Customer discovery

By the EWOR Team2 min read

A process diagram may hide repeated logins, missing instructions or a handoff nobody can complete. Trying a small part of the task yourself can reveal these details, provided the exercise is safe, authorised and narrow enough to assess its risks.

What you observe is your own experience of the workflow. Use it to clarify a constraint, not to claim you understand someone else's experience.

Choose one workflow question

Start with a specific question. Can you complete a booking using the information available at that stage? Which handoffs occur when an item is collected? What happens when an instruction refers to a document the user has not yet received?

Use authorised access and an appropriate test environment wherever possible. A sample account can reveal a confusing sequence without exposing real customer data. Keep the exercise narrow enough to understand its potential risks and avoid unnecessary disruption.

The goal is to identify concrete aspects of the activity worth investigating, not to treat yourself as a representative customer after an afternoon of testing.

Do not simulate someone’s life

A short exercise cannot replicate the experience of disability, pregnancy, ageing or poverty, or the accumulated knowledge of someone who has navigated a system for years. Impairment simulations can also overlook the role of learned skills, personal adaptations and environmental barriers.

When accessibility is relevant, involve disabled people through accessible, voluntary research, either as participants or collaborators, and compensate them appropriately for their expertise. Ask about their actual strategies and priorities. Do not substitute a researcher wearing restrictive equipment and claiming to understand for meaningful involvement from the people affected.

Protect everyone affected

Agree on permissions with those responsible for the setting and with participating individuals. Define when to stop, which activities are out of scope and how observations will be recorded. Do not capture bystanders' personal information or attempt tasks that require training you do not have.

Never stage a deceptive public emergency to study people's reactions. When emergency workflows genuinely need to be studied, use an authorised, professionally managed exercise with informed participants and appropriate safeguards. Do not consume real emergency resources or put anyone at risk for research.

Check your interpretation with people who do the work

Afterwards, separate the sequence you experienced, your reaction and your interpretation. An unfamiliar founder may struggle where an experienced user does not. Equally, an experienced user may face burdens that a founder's brief attempt cannot reveal.

Share your observations with people who regularly do the work. Ask what was typical, artificial or missing, then decide which interviews or observations to conduct next. The exercise has been useful if it helps you ask better questions, not if it leads you to claim someone else's expertise.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter