Insights from journey maps
Mark and Zach's journey maps highlight their trust barriers and how editorial copy can define their product experience.
| Dimension | Mark | Zach |
|---|---|---|
| Trust barrier | “Can I interpret this correctly?” | “Can I safely do this?” |
| Peak moment | Simulate | Deploy |
| Risk type | Understanding risk | Action risk |
| Core need | Clarity of reasoning | Safety of execution |
-
The word "simulation": For Mark, the word does real work: dry-run prediction before real-world change. For Zach, the word does nothing. He doesn't know what it means. This is the clearest example of a broader pattern: product language calibrated for professionals actively alienates newcomers.
-
The post-deploy phase Mark's post-deploy is about anxiety decay over 72 hours, monitored through the product. Zach's post-deploy is about a specific emotional event (the first flight) that happens entirely outside the product. The product is currently designed for Mark's version and has almost no surface for Zach's.
-
The peak shifts: Mark's modelled peak is at Simulation (Stage 5), the moment of decision before commitment. Zach's modelled peak is at Deploy (Stage 6), the minutes when the Nimbus is being changed. Mark fears making the wrong decision; Zach fears the process harming the thing he loves.
-
Most opportunities are editorial: Six of seven Zach-stage opportunities are Copy, not Feature. A casual-user mode isn't a separate product; it's a layer of copy, default settings, and disclosure choices on top of the existing one.
Internal ownership
This table summarizes the tasks required per product team to ensure all users' trust concerns are addressed.
| Team | For Mark (Expert User) | For Zach (First-Time User) |
|---|---|---|
| Product | Optimize trust in Simulate → Deploy under uncertainty | Design safe onboarding from setup → first successful execution |
| User Research | Study cognitive load, decision uncertainty, and trust calibration | Study onboarding friction, confusion, and first-time execution anxiety |
| Information Architecture (IA) | Structure complex dependencies, system states, and simulation logic | Simplify system into linear onboarding and predictable progression |
| UX Writing / Content Design | Clarify reasoning, risk logic, and uncertainty in system outputs | Translate system into plain language; reduce fear and ambiguity |
| UX / Interaction Design (IxD) | Enable deep simulation, scenario comparison, and precision workflows | Build guided onboarding, step-by-step flows, and safe first actions |
| Data / Simulation Systems | Provide high-fidelity modeling and uncertainty representation | Simplify outputs into clear, outcome-linked previews |
| Engineering / Platform | Ensure simulation fidelity and reliable production deployments | Ensure onboarding stability, rollback safety, and safe first execution |
| Customer Experience / Support | Handle edge-case troubleshooting and post-decision trust recovery | Provide reassurance, guidance, and confidence during first use |