Zach's journey through the modernization pipeline
info
Method demonstration, not findings
A journey map for a non-technical user isn't the professional map in simpler words. It's a different artifact, because the user's relationship to the tool is different. Mark evaluates NimbusWiz as a professional instrument. Zach evaluates it as a stranger he wasn't sure he should trust with something he loves.
The exhibit
| Journey Stage | Register | Assess | Advise | Simulate | Deploy | First Flight | Diary |
|---|---|---|---|---|---|---|---|
| Goal | Set up account | Understand system | Evaluate options | Preview outcome safely | Make first real change | Experience system working | Build ongoing trust |
| Action | Creates account, completes onboarding | Reads system overview | Compares upgrade options | Runs preview / simulation | Executes guided deploy | Uses system in real environment | Returns to check system status |
| Touchpoints | Signup flow, onboarding screens | System overview dashboard | Recommendation page, explanation cards | Simulation / preview UI, risk visualization | Deployment checklist, confirmation modal, rollback prompt | Live system interface, first task flow | Monitoring dashboard, activity log |
| Thought | “What is this?” | “How does this work?” | “Which option should I trust?” | “What will happen if I proceed?” | “I hope this works…” | “Okay… it actually worked.” | “This seems reliable.” |
| Emotion | 😐 Neutral curiosity | 😕 Uncertainty | 😟 Cautious evaluation | 😌 Controlled understanding | 🔴😰 Peak anxiety (first real execution) | 😌 Relief | 🙂 Growing trust |
| Pain Point | Lack of context | System unfamiliarity | Confusing choices | Difficulty fully trusting simulation | Fear of irreversible change | First-time execution pressure | Fragile trust formation |
| Opportunity | Make onboarding explain purpose clearly in plain language | Reduce cognitive load and clarify system value early | Simplify decision-making with transparent comparisons | Ensure simulation clearly reflects real outcomes without ambiguity | Provide strong safety guarantees (rollback, confirmation, reassurance) | Reinforce success with immediate feedback and visible system stability | Strengthen trust with consistent signals of reliability over time |
What this map reveals
- Documentation overpowers experience: Zach is continuously told what is happening rather than being guided through it
- The biggest friction is editorial, not architectural: naming, framing, and tone shift determine whether Zach trusts the system
- First-time users don’t fail at complexity, they fail at unclear consequences during Deploy
- Simulation reduces anxiety, but does not resolve it; real trust is only formed after First Flight succeeds
- The system lacks a true onboarding trust layer between Advise → Deploy → First Flight
View the complete PDF.