Mark's journey through the modernization pipeline
info
Method demonstration, not findings
A tabular view of the gap between what Mark is doing and what he's feeling.
The exhibit
| Journey Stage | Register | Assess | Advise | Simulate | Deploy | Stabilize | Monitor |
|---|---|---|---|---|---|---|---|
| Goal | Resume work | Understand risk | Evaluate recommendation | Validate outcome | Make change | Confirm stability | Trust system |
| Action | Reopen pipeline | Review dependency risks | Read advisor explanation | Run simulation | Deploy change | Check health metrics | Passive monitoring |
| Touchpoints | Login screen, session restore banner | Risk dashboard, dependency graph UI | Recommendation card, explanation panel | Simulation interface, what-if tool | Deployment modal, execution console | System health dashboard, post-deploy report | Monitoring dashboard, alert system |
| Thought | “What changed?” | “Is this safe?” | “Can I trust this?” | “What if this breaks?” | “No turning back.” | “Did it work?” | “Looks stable.” |
| Emotion | 😐 Neutral reorientation | 😕 Uncertainty | 😟 Skeptical evaluation | 🔴😰 Peak anxiety (highest uncertainty) | 😰 Stress release | 😌 Relief | 🙂 Trust |
| Pain Point | Context loss after return | Difficulty interpreting system risk | Lack of clarity in reasoning | Uncertainty about consequences of actions | Fear of irreversible execution | Need confirmation of success | Reduced visibility over time |
| Opportunity | Restore context clearly so users understand where they left off | Simplify risk information and clarify dependencies | Make reasoning transparent and understandable | Reduce uncertainty by clearly showing simulated outcomes and consequences | Provide safe execution with rollback and confirmation | Provide clear validation that system changes worked | Reinforce trust through ongoing system health visibility |
What this map reveals
- Emotional topology is inverted from documentation topology: Peak tension is at Simulation, not Deploy
- Strong reporting surfaces are weak companion surfaces: Mark is told what’s happening; rarely accompanied through it
- Sharpest improvements are IA and copy, not features: The product is largely built; what it needs is to be rendered differently at high-stakes moments
View the complete PDF.