Sure Product Studio

A CORE OFFERING / SURE PRODUCT STUDIO

Comparative
Prototyping.

Explore different directions
before committing to one.

Bring competing product directions to life through realistic, working prototypes. Help customers compare the consequences—and help your team decide what deserves further investment.

Discuss your product decision

THE CHALLENGE

A shared vision can hide
different expectations.

For complex business software, a positive reaction is a starting point. What did each person imagine? Which tradeoffs will they accept? Who benefits, who takes on more work, and who can authorize a purchase?

One stakeholder imagines flexible workflows; another assumes strict controls. Both approve the demo, but they are approving different products in their heads.

Comparative Prototyping makes those differences tangible. Each version prioritizes something different, with coherent sample data and meaningful interactions. No version is presented as the finished answer. Participants can challenge every alternative—or decide that none is worth adopting.

ILLUSTRATIVE EXAMPLE / FICTIONAL PURCHASING PRODUCT

One business problem.
Different operating choices.

The same urgent purchase, new vendor, and deadline appear in each direction. What changes is how the organization handles the request.

DIRECTION A

Delegated authority

Give departments room to act quickly.

The tradeoff: more responsibility sits with managers.
DIRECTION B

Centralized control

Standardize decisions through procurement.

The tradeoff: requests may wait in a central queue.
DIRECTION C

Shared visibility

Help teams coordinate exceptions and blockers.

The tradeoff: more information needs to be maintained.

Concept illustrations, not screenshots of completed prototypes. Two or three alternatives may be appropriate; the decision determines the scope.

WHERE IT FITS

Built for complex
B2B product questions.

This approach is especially relevant when several roles use the product, multiple stakeholders influence the purchase, and a live experiment may require integrations, security reviews, procurement, training, or changes across departments.

Analytics and A/B testing remain useful where applicable. Comparative Prototyping addresses decisions that often arise before a live product and meaningful usage data exist.

For a small interface question or an inexpensive live experiment, a simpler method may be the better choice.

THE APPROACH

How the work unfolds.

  1. 01

    Frame the decision

    Identify the business problem, the assumptions that matter, and the decision the work should inform. Establish who uses, buys, approves, administers, and is affected by the product.

  2. 02

    Build contrasting alternatives

    Create a small set of working experiences with deliberately different priorities. Use consistent, plausible business scenarios. Build enough to investigate the question; leave unrelated features and infrastructure out.

  3. 03

    Explore individually

    Where possible, let participants try the prototypes before the group meeting. Observe tasks, check understanding, and invite criticism without an audience of colleagues.

  4. 04

    Compare across roles

    Bring the differences into a structured discussion. Explore which compromises the organization can accept, rather than taking a vote on the most attractive interface.

  5. 05

    Turn findings into decisions

    Document observations, unresolved risks, and implications for scope, workflow, architecture, and the next experiment. Investigate buying commitment separately from interface preference.

THE OUTCOME

A clearer decision.
An explicit next step.

An engagement can include a decision brief, working prototypes, an assumptions-and-evidence record, a stakeholder tradeoff map, and recommendations for the next development investment. Scope and deliverables are agreed around your situation.

The goal is to make a consequential product decision clearer. Positive feedback does not establish purchasing commitment, technical feasibility, or production readiness. Those questions need their own evidence.

Led by Sue Raisty, with specialist collaborators engaged as projects require. Our approach builds on established parallel design and product discovery practices, with AI-assisted development supporting the exploration of working alternatives.