Prototyping and Journey Mapping

Wow. I just built 3 mini-apps for PMs in under 10 minutes: an empathy mapper, a journey analyzer, and a competitive analysis tool with Opal (Google Labs). No PRD. No Figma. No tickets. Just an idea → an experience. Instead of debating documents, I’m now sharing working mini-apps with my team ask them "react to this, let’s refine it” I used Opal to prototype the vibe with an: -Empathy Mapper -User Journey Analyzer -Competitive Landscape Tool Each one took minutes. Each one was immediately shareable. Each one changed the conversation. Use Opal when: -You want to validate an idea before writing a PRD -You need a quick tool for a workshop or meeting -You want to make research or concepts visible -You want to better empathize about your user Think of Opal as your 10-minute lab. If it takes longer than that, move it to a full prototype — that’s where other AI prototyping tools come in. Tips for PMs adopting this workflow -Start tiny. Your first Opal app should take under ten minutes. That constraint keeps you focused on intent, not polish. -Think in verbs, not nouns. Prompts like “summarize feedback” or “visualize trends” produce far better prototypes than static descriptions. -Collaborate live. Invite designers, engineers, and stakeholders into the session. Watching the prototype evolve creates alignment faster than any meeting. -Reflect. After every prototype, note what worked. Each build sharpens your prompting instincts and your product intuition. 🔗 Guides + masterclass in the comments 👇

🥪 Service Blueprints From Scratch (https://lnkd.in/dCeutXvu), a neat practical guide on how to turn research insights into a service blueprint, make front stage and back stage visible — and cover roles, processes, systems and data. By Marco Torrente. --- 🔶 1. Painting a Broader Picture To start with, we map the complexity of a system by looking at a broader picture. The real world is complex, contradictory and often riddled with dependencies, undocumented decisions and data flows. So we get together with stakeholders and map across 6 layers: Front stage ⚬ Customer / User ⚬ Experience / Channels Back stage ⚬ Organisation / People ⚬ Performance / Processes ⚬ Assets / Systems ⚬ Data / Information The goal here is to understand and visualize how a service is currently running (at a high level) and what friction points or challenges are involved in delivering that service to a customer. Afterwards, we structure relevant themes according to when they happen in time. --- 🔹 2. Diving Into Details Marco suggests to build the journey by laying out the phases and steps horizontally and the layers vertically. We map customer actions as steps or activities — similar to how we would do it with customer journey maps. However, a journey is never enough because the experience needs to be delivered from the org effectively. So we need to involve the project team to add back stage items (org, performance, systems, data) as they hold deep domain knowledge. It helps understand where and why customers experience friction. --- 🔹 3. Right-to-Left Thinking Personally, I add a different twist to that mapping process. Journey maps often represent ideal user journeys that people should take, but rarely do in practice. There is a lot of complexity and chaos that they hide — from back-and-forth to external factors that influence their decisions. Often many things must happen at the same time, coming all at once, and working together towards the shared goal. As we aim for that goal, we also need to map risks, blockers, opportunities and unknowns. One way to do that is by applying right-to-left (R-L) thinking (also called “backcasting”) to your work: 🚩 Right-to-left → Start from the goal, then move backwards to start. 🎯 Expose complexity → Map a path that maximizes chance of success. 🧱 Map what happens → Known success moments, frequent blockers. 🪜 One step at a time → Always focus on immediate previous step. ❓ Mark unknowns → Flag strong assumptions for research to-do. 🚀 Prioritize work → Choose key blockers/successes to work on next. It takes a lot of grit to change a way of working in organizations. But we can frame your work around the desired outcome and use right-to-left thinking to enforce critical thinking — instead of focusing on 1000s of details that might matter short-term, but won’t make a difference at scale. Details: https://smashed.by/rtl ↓

In today's healthcare the real problem isn’t a lack of tech. It’s a lack of connection. Patients want the same smooth experience they get everywhere else. But most hospitals still run on old, clunky systems. The result is friction at every step — from booking to follow-up. Here’s how we’re changing that in my hospital. We mapped the entire patient journey. Not just one app. Not just one tool. The whole experience. This is what we found: • Pre-arrival: Online booking and digital triage cut confusion and save time. • Check-in: Mobile check-in and digital forms end the paperwork shuffle. • During care: Patients get real-time results and can message their care team securely. • Follow-up: Digital discharge, reminders, and tele-reviews keep care going at home. The impact is clear. Digital appointment systems push satisfaction above 90%. No-shows drop. Clinic flow improves. Patients feel informed, prepared, and in control. But here’s the key: Tech should amplify the human touch, not replace it. A single app is not enough. You need a journey map to spot the “moments that matter.” That’s where you find the friction — and fix it. My advice to leaders: • Start with the journey, not the tool. • Cut friction with care. • Build digital pathways that boost empathy and connection. When you redesign the journey, you restore dignity to every patient. This is the future of healthcare. Simple. Human. Connected.

Prototyping is how ideas turn into evidence. It surface hidden assumptions, generate better stakeholder conversations, test specific hypotheses, reveal unforeseen interactions, and give you a concrete artifact to evaluate before code or tooling locks you in. Use low fidelity sketches and storyboards when you need speed and divergent thinking. They help teams externalize ideas, reason about user goals, and map flows before pixels appear. They are deliberately rough to avoid premature polish. Move to click through wireframes in Figma when the question is structure and navigation. Validate information architecture, menu depth, labeling, and path efficiency while changes are still cheap. When the feel of interaction matters, use interactive digital prototypes to evaluate micro interactions, timing, and visual polish. Treat them as validation instruments, not trophies. Plan change criteria up front so attachment to a pretty artifact does not silence real feedback. Some questions require real performance and materials. Coded prototypes and functional hardware mockups tell you about latency, reliability, durability, ergonomics, and safety. In medical devices and other regulated domains, high fidelity functional and contextual testing is expected for Human Factors validation. Not every question lives on screens. Experience prototyping and bodystorming put bodies in space to surface constraints that lab tasks miss. Acting out a shared autonomous ride with props reveals comfort, cue timing, and social norms. Wearing a telehealth mockup for a week exposes stigma, routine friction, and alert patterns that actually fit domestic life. Before building intelligence, simulate it. Wizard of Oz studies let a hidden human drive system responses while participants believe the system is autonomous. You learn vocabulary, trust dynamics, acceptable latency, and recovery strategies without heavy engineering. AI of Oz replaces the human with a large language model so you can study conversational realism early. Manage risks like model bias, hallucinations, and outages with guardrails and logging so findings remain trustworthy. Strategic prototypes also matter. Provotypes and research through design artifacts challenge assumptions, surface values, and force early conversations about privacy, power, and trade offs that slides tend to dodge.

How to Create a Journey Map for ITSM (Without Losing Your Mind or Your Users) Let’s face it—most ITSM diagrams look like a spaghetti chart married a ticket queue. If you want to stop guessing where your users are frustrated and start fixing what actually matters, a journey map is your new best friend. Here’s how to build one that makes IT look like a hero (not the villain): 1. Pick a Journey That Actually Happens ↳ Password resets, new hire onboarding, broken printer meltdowns. Start with something real, not theoretical. 2. Talk to Users—Not Just IT ↳ Ask them what they expected, what they experienced, and what drove them to curse under their breath. 3. Write Down the Actual Steps (All of Them) ↳ What really happens, not what’s in the SOP. Include email lag, portal confusion, and "calling my cousin in IT." 4. Capture the Pain Points ↳ Highlight friction, frustration, delays, and unnecessary approvals. If a step adds no value, it adds user rage. 5. Add Emotions, Not Just Actions ↳ Mark how users feel at each stage: Confused. Hopeful. Furious. A smiley face where one belongs? Rare. But possible. 6. Visualize the Whole Experience ↳ Build a timeline or flowchart. Make it so clear that even leadership says, “Oh… yeah, that’s not great.” 7. Fix It with Users, Not to Them ↳ Co-create the better experience with feedback loops, pilot changes, and check-ins. 8. Rinse & Repeat ↳ Because once you map one journey, you’ll discover five more that need saving. A few of my favorite resources to help get your journey started: ↳ Customer Experience Professionals Association (CXPA) ↳ Annette Franz, CCXP ↳ Lynn Hunsaker, CCXP Journey Mapping isn’t about perfection. It’s about visibility. You can’t fix what you refuse to see. Have you ever gone through your own IT process as a “test user”? What did you find? (And did you survive?) ♻️ Repost to save someone from another broken ticket loop. 🔔 Follow Bob Roark for more no-fluff ITSM leadership tips.

Safety Innovation Advent: Day 4 - Create a Journey Map for a Safety Process In the lead-up to Christmas, I’m sharing an insight, activity or practical tip each day to help you innovate in health and safety. Today’s activity: Journey map a safety process First: what is journey mapping? At it's core, journey mapping is a great tool to visualise the steps, interactions, and emotions that people experience when engaging with a process. It’s commonly used in customer experience design, but it’s equally valuable in health and safety to highlight pain points, inefficiencies, and areas for improvement in your workflows. By mapping the journey, you gain insights into how well processes support frontline workers and identify opportunities to simplify or enhance them. Here's a high level overview of how to create a journey map: 1️⃣ Choose a process to map Pick a safety-related process that impacts your team, such as: Reporting a hazard | Onboarding a new worker etc. 2️⃣ Define the journey start and endpoint Clearly outline where the process begins and ends. For example, a hazard reporting journey might start when a worker notices an issue and end when the issue is resolved and communicated back to the team. 3️⃣ Break it into steps List every step involved, such as filling out forms, getting approvals, or communicating with others. Be specific; this helps identify bottlenecks or unnecessary complexity. 4️⃣ Identify touchpoints and tools Mark where people interact with forms, technology, or other systems. For example: A worker fills out a paper form (touchpoint: paper form). A supervisor enters the report into a digital system (touchpoint: software). Notifications are sent to a team for resolution (touchpoint: email). 5️⃣ Uncover the pain points: Ask yourself (and your team): Where do delays happen? Are there any confusing steps? What causes frustration or errors? Equally you can do the same for the things that are going well... 6️⃣ Visualise the map Sketch or create a visual representation of the journey, using arrows to show the flow and notes for each step. This can be as simple as a sheet of paper, a whiteboard sketch or a diagram in tools like PowerPoint or Miro - my personal favourite is to use Lucid Charts. Why this matters for safety innovation: A journey map reveals opportunities for improvement and enhances the user experience, making processes more intuitive and effective. Workers who find safety processes easy to follow are more likely to engage with them, leading to better outcomes for everyone. To practice feel free to do this alone, but to employ this approach in your workplace you MUST involve frontline workers when mapping the journey. Their firsthand insights will uncover their unique challenges and ensure the solutions work for the people they’re designed for. Stay tuned for more practical tips in this series by following my profile and the hashtags #SafetyInnovationAdvent #SafetyInnovation #SafetyTech.