coeno GmbH

Why this matters

An overbuilt prototype distracts from the actual questions

An underbuilt prototype delivers no usable feedback

The right fidelity level saves time and effort

Early feedback without expensive development work

An iterable solution before investing in technology

For a test prototype, what counts isn't beauty – it's clarity

Prototypes for testing have one job: make the right questions answerable. Nothing more, nothing less. Depending on the research goal, we create low- or high-fidelity prototypes that specifically map the interactions, content, or concepts to be examined.

01 Research goal as starting point

What does the prototype need to make testable?

02 Determine fidelity level

Low, mid, or high – depending on the test question

03 Define click paths

Which flows need to work in the prototype?

04 Build in hypotheses

Which design decisions do we explicitly want to test?

05 Check testability

Is the prototype clear enough – without giving too much away?

What you get

Clickable prototypes (Figma, Axure, etc.)

Testable concepts in story or use-case form

Documentation of the hypotheses to be examined

Prototyping for Testing: As much effort as needed – and no more

Why this matters

For a test prototype, what counts isn't beauty – it's clarity

01

Research goal as starting point

02

Determine fidelity level

03

Define click paths

04

Build in hypotheses

05

Check testability

`Typical statements`
before the project

What you get

You need a prototype that's genuinely testable?

Prototyping for Testing: As much effort as needed – and no more

Why this matters

For a test prototype, what counts isn't beauty – it's clarity

01

Research goal as starting point

02

Determine fidelity level

03

Define click paths

04

Build in hypotheses

05

Check testability

Typical statementsbefore the project

What you get

You need a prototype that's genuinely testable?

`Typical statements`
before the project