UserTesting, Maze, Lookback, or Causal AI: Which Method Fits the Decision?
Choose UserTesting, Maze, or Lookback when the team needs to observe real people using an interface. Choose Subconscious to learn which price, message, product concept, or launch action changes choice.
These methods are complements. Each becomes expensive when asked to answer a question it cannot measure.
What does each method measure?
| Method | What it measures | Best question | Main limitation |
|---|---|---|---|
| UserTesting | Behavior and commentary while real participants use a product or prototype | Where does a person struggle in the experience? | Does not isolate the effect of an unshipped commercial action |
| Maze | Task completion, prototype interaction, survey, and usability outcomes | Can people complete a defined task? | Task success is not the same as market choice |
| Lookback | Live or recorded interface behavior plus participant explanation | Why did the participant act that way in the interface? | Small qualitative sessions do not estimate a causal market effect |
| Subconscious | Choice responses to controlled commercial alternatives in simulated audiences, recruited human participants, or both | Which defined action produces the stronger behavioral response? | Does not replace session-level observation of interface use |
When UserTesting is the right choice
UserTesting records real people interacting with a product, letting researchers watch sessions, hear participants explain their actions, and see where an interface creates confusion.
The method suits behavior inside a working product or prototype. It is less direct for an action that has not shipped, such as choosing among prices, messages, or market-entry plans.
The source material reports enterprise contracts starting above $30,000 per year, with some teams reporting annual spending between $50,000 and $100,000 before added participant or feature fees. Treat those figures as inherited planning examples, not current quotes. Recruiting narrow audiences and collecting sessions can still take days to weeks.
When Maze or Lookback is the right choice
Maze supports moderated and unmoderated studies, including prototype tests, live website tests, interviews, surveys, card sorting, and tree testing. It fits a product team that needs task-level evidence.
Lookback supports live and recorded usability sessions. It fits a researcher who needs follow-up questions, screen interaction, participant commentary, and direct observation.
Both retain an advantage causal simulation should not pretend to replace: a researcher can watch a real participant use the interface.
When Subconscious is the right choice
The study starts with an intervention and an outcome. The team defines the audience, holds the decision context stable, and compares plausible actions.
The team can start on a simulation, then test or validate the same study with real human participants. The intervention, alternatives, audience definition, and outcome stay explicit as the evidence moves from simulation to human confirmation.
This is the right method when a product or marketing leader must choose:
- One price or package over another
- One product concept or claim over another
- One position or message over another
- One launch or market-entry action over another
The output is a decision-specific comparison, not another interview transcript. It estimates which tested action produces the stronger directional response for the defined audience under the study conditions.
The supported causal experiment use cases show where this method fits. The research program explains why human baselines and validation remain part of the workflow.
Use the methods in sequence
- Use exploratory interviews to find the problem and learn the language customers use.
- Use UserTesting, Maze, or Lookback to observe whether people can complete the interface task.
- Use Subconscious to compare defined commercial actions before rollout.
- Observe the rollout to learn whether the measured effect holds in market.
It prevents a stated preference, a usability failure, and a causal effect from being treated as the same result.
Limitations
Remote usability tools depend on recruitment quality, task design, and the realism of the tested interface. A Subconscious experiment, whether simulated or human, depends on the study design, audience definition, alternatives, and outcome chosen for that decision.
No method removes the need for human judgment. Consequential product, health, financial, or policy decisions require real-world validation and qualified review.
If the team has a concrete action to compare rather than an interface task to observe, bring the decision to a Subconscious working session.