LIFESTYLE APPS (Uber, Starbucks, Spotify)
You're a PM at Starbucks. A barista in Chicago posts a viral TikTok: "Why does our order screen look like a spreadsheet?" showing 15 drink modifiers dumped in a flat list. Your VP forwards it to you with "fix this."
What is a Wireframe? The modifiers need visual grouping by type (milk, syrup, size), clear hierarchy, and better scanning — all layout decisions you prototype in a wireframe.
You're a new PM at Bumble. In your first 1:1, your manager says: "Users who match on Sunday night almost never message by Monday. We've tried push notifications — they don't work. I need you to figure out what's actually happening emotionally between match and message."
What is a User Journey Map? This traces the emotional arc from match excitement → overnight uncertainty → Monday inertia to find the exact moment motivation dies.
You just started as a PM at Peloton. In your first sprint review, instructors demo their class scheduling tool and it's chaos — time slots, studio assignments, and equipment needs are in separate tabs. One instructor says "I triple-booked myself last week because I can't see everything at once."
What is a Wireframe? Time-based data needs a unified calendar view with logical grouping of related elements (slots, studios, equipment) on one screen.
You're a PM at Notion. A large enterprise customer escalates: "New hires stare at a blank page for 20 minutes. Power users love the flexibility, but onboarding people are overwhelmed by 200+ templates with no guidance."
What is a Wireframe? Classic enterprise challenge — designing for novice AND expert users. You need progressive disclosure: a guided default view for new users with advanced templates collapsed, not a flat dump of 200 options.
You're a PM at Duolingo. The localization team tells you the lesson completion screen was designed for English but now serves 40 languages — RTL text breaks the layout, long translations overflow buttons, and "Continue" overlaps the streak counter on small Android devices.
What is a Wireframe? Responsive layout + localization problem — you need to prototype how the screen adapts across languages, text directions, and 320px viewports with proper touch targets.
You just joined Spotify as a PM. Your first week, the artist relations team Slacks you: "Artists keep asking why payments are late — finance, legal, and engineering all point fingers at each other." Your manager asks you to figure out where the breakdown is.
What is a Workflow Diagram? Three teams, unclear handoffs, blame game — swim lanes expose exactly which handoff is stalling payments.
You're on the LinkedIn Jobs team. Recruiters are emailing your sales team furious: "Your Easy Apply form is broken — candidates submit applications with blank screening questions and we don't find out until we open the file." You check the form: all 6 fields are on one screen with no validation.
What is a Wireframe? The form needs multi-step grouping, a progress bar, inline validation, and proper label-field association — all layout and interaction decisions.
You're a PM at Whoop. Your VP shares a competitor analysis: "Strava's Year in Sport gets 50M shares. Our Year in Recovery gets almost none." Your hypothesis is Strava triggers pride while Whoop triggers guilt — but you need to validate what emotion each experience actually produces.
What is a User Journey Map? Map the emotional arc of receiving each recap — one triggers "look what I accomplished" (shareable), the other triggers "I should sleep more" (private). The journey map reveals which emotion drives or kills sharing.
You're a PM at Slack. Your customer success manager forwards an email from a Fortune 500 CHRO: "Every new hire says the same thing — they join, can't find their team's channel, miss their first standup, and feel invisible. We're blaming Slack in exit interviews."
What is a User Journey Map? Map the new hire's first 48 hours — excitement → confusion → embarrassment → disengagement — to find the exact moment onboarding fails and where a guided flow could intervene.
You're a PM at DoorDash. Dashers rate the app 2.3 stars. Top review complaint: "After I pick up the food, the app goes silent — no updates, no route changes, nothing. I feel like I'm on my own." The ops team insists tracking works fine on their end.
What is a User Journey Map? Ops data says everything's fine, but Dashers feel abandoned. The journey map reveals the emotional dead zone between pickup and dropoff where silence breeds frustration — a perception problem, not a system problem.
You're on the Uber Eats team. Customer support tickets spike every Friday night with "where's my food?" complaints. Delivery ETAs are accurate, but restaurants, drivers, and the dispatch system have no shared queue — orders sit in limbo between handoffs [A]. Riders also say they feel "abandoned" once the driver picks up the food and the tracker goes quiet [B].
What is a Workflow Diagram [A] + User Journey Map [B]? The workflow diagram finds the operational gap between restaurant → dispatch → driver handoffs. The journey map reveals the emotional dead zone after pickup where silence breeds anxiety.
You're a PM at Threads (Meta). DAUs are tanking 30 days post-launch. User research says people feel "why am I even here?" by Day 5 [A]. Engineering tells you the recommendation algorithm barely has signal for new users and the content ranking pipeline involves three teams with no shared prioritization [B].
What is a User Journey Map [A] + Workflow Diagram [B]? The journey map reveals where the "why am I here?" feeling hits. The workflow diagram maps the ranking pipeline across teams to find why the algorithm can't get signal fast enough.
You're a PM at Oura Ring launching "Readiness Coach" — AI wellness recommendations. In beta, users complain recommendations contradict yesterday's advice. You discover the wearable data pipeline has a 6-hour lag across three teams that ship independently [A]. Users see a confident recommendation with no indication it's based on stale data [B].
What is a Workflow Diagram [A] + Service Blueprint [B]? The workflow diagram maps ring → pipeline → engine → content to find the lag. The blueprint exposes the gap between frontstage (confident advice) and backstage (stale data) — users trust guidance built on yesterday's numbers.
You're a PM at Figma. 12% of free-to-Pro upgrades "silently fail" — users pay but don't get Pro features for hours. The process touches billing, permissions, plugin marketplace, and notifications across four teams with no shared pipeline [A]. Meanwhile, users see a "You're Pro!" confirmation but can't access Pro features — and there's no status page explaining the delay [B].
What is a Workflow Diagram [A] + Service Blueprint [B]? The workflow diagram maps billing → permissions → plugins → notifications to find the silent failure. The blueprint shows frontstage ("You're Pro!" confirmation) vs. backstage (features not yet propagated) — exposing the trust-breaking gap that needs a visible status indicator.
You're a PM at OpenAI. ChatGPT Pro subscribers are canceling — the #1 churn reason is "I don't know if I'm getting more value than free." Your analytics team discovers usage caps, model routing, and billing are owned by three teams that don't coordinate — Pro users silently get routed to the same model as free users during peak hours [A]. The Pro interface looks identical to free with just a small badge — there's no visible proof of premium value [B].
What is a Workflow Diagram [A] + Service Blueprint [B]? The workflow diagram maps usage caps → model routing → billing to find why Pro users get downgraded silently. The blueprint reveals frontstage (identical UI, tiny badge) vs. backstage (same model during peaks) — showing there's no visible evidence of the premium experience.
You're a PM at Spotify. Leadership greenlights "Spotify Clips" — 15-second artist video teasers. Design asks: "What should the feed look like?" — autoplay behavior, swipe mechanics, and video-text layout are all undefined [A]. Meanwhile, engineering warns uploads will touch content moderation, rights verification, CDN encoding, and the recommendation index — and nobody knows the order of operations or what fans should see while processing happens [B].
What is a Wireframe [A] + Service Blueprint [B]? The wireframe defines the feed UI (autoplay, swipe, hierarchy). The blueprint maps frontstage (clips appearing in feed) against backstage (moderation → rights → encoding → indexing) so engineering and design can ship in parallel.
You're a PM at TikTok. Creator analytics shows a 40% drop in daily posts from mid-tier creators. Creators say: "I can't find my earnings, views, and brand deals — they're all on separate pages, I don't know if I'm growing" [A]. Meanwhile, your payments team says the payout calculation touches finance, ads revenue, and creator partnerships — and discrepancies keep showing up that no one can trace but creators just see one number [B].
What is a Wireframe [A] + Service Blueprint [B]? The wireframe consolidates earnings, views, and deals into one dashboard (data at a glance, drill-down in 3 clicks). The blueprint connects what creators see (a single number) to what's hidden (three teams calculating different pieces) — exposing where discrepancies originate.
You're the PM who owns food logging at MyFitnessPal. Barcode scans return wrong calories 8% of the time. The correction form is buried 3 taps deep with no validation [A]. Worse, users don't know their corrections enter a community review queue and a nutrition database team before updating — they submit a fix and assume it's ignored forever [B].
What is a Wireframe [A] + Service Blueprint [B]? The wireframe surfaces the correction form (fewer taps, inline validation, type-ahead). The blueprint maps frontstage (user submits, sees nothing) against backstage (community review → database team) — revealing users need a visible status tracker.
You're a PM at Zoom pulled into an enterprise deal review. A banking CTO says: "Scheduling a 200-person all-hands takes my EA 25 minutes — 15 form fields, broken time zone handling, and calendar invites don't sync to Outlook half the time" [A]. Your engineering lead adds: "Calendar API, license validation, and dial-in generation are owned by three teams — there's no way to know which one fails when sync breaks" [B].
What is a Wireframe [A] + Workflow Diagram [B]? The wireframe redesigns 15 fields into logical steps (attendees → timing → settings) with smart defaults and inline validation. The workflow diagram maps calendar API → license check → dial-in across three teams to find the sync failure point.
You're a PM at Airbnb. Guest reviews show a pattern: "Check-in was confusing." Hosts provide different instructions (lockbox, doorman, key under mat) but the app shows them all as a raw text blob in the booking confirmation [A]. Your backend team also reveals check-in instructions pass through host input, translation, and trust & safety review — and 15% arrive to guests AFTER they've landed at the property [B].
What is a Wireframe [A] + Service Blueprint [B]? The wireframe redesigns instructions into structured templates by type (lockbox: code + photo; doorman: name + hours) instead of a text blob. The blueprint maps frontstage (guest sees instructions) against backstage (translation → safety review) to find why 15% arrive late.
You're the PM who owns Starbucks mobile order retention. Your data scientist reports: 30% of first-time users churn by Day 7, and the #1 complaint is "I ordered, paid, then got told my item was unavailable" [A]. You also notice the reorder screen takes 6 taps for a repeat customer [B]. When you dig into the backend, inventory sync and payment processing are owned by separate teams with no shared state — payment clears before inventory confirms [C].
What is a User Journey Map [A] + Wireframe [B] + Workflow Diagram [C]? The journey map pinpoints the trust-destroying moment (paying then seeing "unavailable"). The wireframe simplifies reorder to 2 taps with smart defaults. The workflow diagram reveals inventory sync lags behind payment processing.
You're the PM who owns BeReal's core loop. Retention is falling and user research reveals: (1) creators say the 2-minute timer feels stressful, not playful [A], (2) the capture screen's camera toggle and retry button are "impossible to find under pressure" [B], and (3) 20% of posts appear in friends' feeds 3+ minutes late, but the infra team says it touches notifications, camera API, image processing, and feed distribution across four teams — nobody knows where the delay lives [C].
What is a User Journey Map [A] + Wireframe [B] + Workflow Diagram [C]? The journey map identifies the stress trigger (timer pressure + social anxiety). The wireframe redesigns the capture screen for speed (toggle and retry button hierarchy). The workflow diagram traces notification → capture → processing → distribution to find the 3-minute delay.
You're the PM who owns retention at Calm. Subscribers churn at month 3 at 2x the rate of month 2. User research surfaces: (1) "I was excited but now I just fall asleep during sessions — is it even working?" [A], (2) the post-session screen shows a streak counter that makes short-session users feel judged [B], and (3) the recommendation engine, Apple Health sleep integration, and billing system run on different schedules — users get billed for month 4 before recommendations have even processed their month 3 data [C].
What is a User Journey Map [A] + Wireframe [B] + Workflow Diagram [C]? The journey map traces excitement → "is this working?" doubt → churn. The wireframe redesigns the post-session screen (progress without judgment). The workflow diagram maps recommendation → sleep data → billing to find why billing outruns personalization.
You're the PM who owns Canva's new "Brand Kit" for enterprise. Three problems land on your desk the same week: (1) a designer at Nike says "I uploaded our brand assets but my teammate in Tokyo can't see them — the sync feels random and I don't trust it anymore" [A], (2) your design team shows you the asset management screen — it's a wall of thumbnails with no filtering, tagging, or permission indicators visible [B], and (3) your infra team says uploads touch storage, permission propagation, CDN distribution, and search indexing across four teams — nobody knows where Tokyo's sync delay originates [C].
What is a User Journey Map [A] + Wireframe [B] + Workflow Diagram [C]? The journey map traces upload confidence → teammate can't see it → distrust → workaround (just emailing the file). The wireframe redesigns the asset screen with filtering, tagging, and sync status indicators. The workflow diagram maps storage → permissions → CDN → indexing to pinpoint where the Tokyo delay lives.
You're the PM who owns course registration at a large university. The president emails your CTO during add/drop week: "Students are melting down on Reddit." Three problems: (1) students register, get confirmation, then 2 hours later get kicked because a prerequisite check ran AFTER enrollment — the emotional rollercoaster is destroying trust [A], (2) the waitlist shows position but never updates and has no status indicators [B], and (3) the system touches enrollment, prerequisites, waitlist priority, financial aid, and the registrar — five teams, no shared pipeline, and prereq checks run after confirmation because nobody mapped the dependency order [C]. Students see "You're enrolled!" while backstage hasn't finished validating [D].
What is a User Journey Map [A] + Wireframe [B] + Workflow Diagram [C] + Service Blueprint [D]? The journey map traces hope → panic → false relief → rage. The wireframe adds real-time position updates and status indicators to the waitlist view. The workflow diagram maps five teams to find why prereq checks run after confirmation. The blueprint connects frontstage ("You're enrolled!") to backstage (prereqs still processing) — the root cause of false confirmation.