# GWEN — Full Site Content > Last updated: May 2026 > Source: https://heygwen.com | Index: https://heygwen.com/llms.txt --- ## Page: Home (/) ### Real UX work experience. Interview, projects, feedback — all in one course. 7 real projects, the latest AI tools, instant feedback, and new portfolio pieces to walk away with. Built around real client briefs. > "New jobs are created that utilize new tools… we'll have these incredible tools that supercharge our productivity and actually make us a little bit superhuman." > — Demis Hassabis, Google DeepMind CEO --- ### Shaped by 100+ hours of student feedback - 200+ project sessions recorded - 80+ UX submissions analysed - 4.8 average project rating --- ### From Beginner to Hire-Ready — 7 Projects Including a Job Interview Each project layers a new designer skill and adds a real-world deliverable to your portfolio. When you join GWEN, you step into a simulated remote internship. It feels like starting a new job — you open a chat (think Slack), meet your team, get briefed on a project, and start working. Your AI colleagues give you tasks with real ambiguity. You create actual work samples, receive constructive feedback, iterate, and build a portfolio of work that demonstrates what you can actually do. - **3–6 weeks** average completion time — at your own pace, on the side of life or study - **40+ deliverables** — research reports, wireframes, decks and more - **300+ exchanges** with your AI coaches — real back-and-forth, not video lectures to consume --- ### Not Just a Badge. Real Artifacts. You finish the internship with four things on your desk: plenty of portfolio material, a signed reference letter, a written portfolio review of your work, and a completion certificate. - **Portfolio** — Case studies covering user research, wireframing, accessibility, design critique and stakeholder communication. Each project deliverable is yours to keep and share. - **Reference Letter** — A personalised letter from Volker Breuer (GWEN Founder) describing your specific work across the projects. Verifiable with a QR code. - **Portfolio Review** — A written review of your project portfolio from the founder. Usually $100, included free for a limited time. - **Certificate of Completion** — On request, at no cost. --- ### What You Get - Job interview + 7 real projects - Instant AI feedback on every submission - Reference letter at completion - Hands-on with the latest AI tools (UX Pilot, Figma, Stitch, Anthropic, OpenAI) - Portfolio-ready case studies - Members community (WhatsApp) - Certificate on request - Free access to all future projects (valued at $200+) ### Pricing **GWEN UX Internship — $199 (one-time)** - In the UK, euro area and Australia you pay in your own currency: £149 / €179 / A$249. - Regional pricing for lower-income countries applies automatically at checkout (50–90% off; the lowest regional price is around $19). - No subscription. No upsells. Lifetime access. - Free access to all future projects (valued at $200+) - Job interview plus the first project free — no credit card, no time limit. - Includes a written portfolio review from the founder (usually $100, free for a limited time). - 30-day refund policy, no questions asked. --- ### What Students Are Posting > "The best part was the shift in mindset — learning how to defend every design decision using a Problem → Solution → Impact framework and thinking through the 'messy' parts of UX like edge cases and cognitive load." — Yousef Alasir, May 2026 > "It's an amazing internship simulation and an amazing opportunity to grow your skills." — Fatima Alyassin, Feb 2026 > "This is a wonderful course for beginners. It allowed me to complete the course in my own time." — Kartik Bande, Dec 2025 > "It's a way to practice useful UX skills while getting personalised feedback." — Ilan Mach, Mar 2026 > "The course helped me land a junior graphic design role, where the employers were happy to see I had UX experience." — Pavithra, Junior Designer --- ### Frequently Asked Questions **What is GWEN?** GWEN is an AI-powered virtual internship platform where you work on realistic projects with AI teammates and clients. You'll complete real-world work — like conducting user research, creating wireframes, and presenting findings — and build portfolio-worthy projects that mirror what junior UX designers actually do on the job. **How is this different from YouTube tutorials?** YouTube teaches you concepts. GWEN gives you practice. Instead of watching someone else design, you're making decisions, getting feedback, and iterating — just like in a real job. Plus, you're learning how to use AI tools in your workflow, which most tutorials don't cover. **Is this a course or a bootcamp?** Neither, really. It's closer to a virtual internship. Instead of lectures and assignments, you work on real-world project briefs with AI teammates. Think of it like hands-on work experience — not a sit-and-watch course. **Who is this for?** This is for anyone looking to break into UX design — career changers, recent grads, self-taught designers, or anyone who wants hands-on experience with modern AI tools. You should have some prior UX knowledge (from studies or self-teaching) and be ready to learn by doing. **How long does it take to complete?** You can work at your own pace — there are no deadlines. Most people complete the internship in 3–6 weeks, depending on how much time they dedicate. **How much does it cost?** The job interview and your first project are completely free — no credit card, no time limit. When you're ready to keep going, a one-time $199 payment unlocks projects 2–7, your reference letter, a portfolio review, and lifetime access to any future projects we add. In the UK, the euro area and Australia you pay in your own currency: £149, €179 or A$249. **Do you offer regional pricing?** Yes — if you're in a lower-income country, regional pricing is applied automatically when you reach the checkout. Depending on your location, you'll pay between 50% and 90% less than the standard $199 — the lowest regional price is around $19. No coupon code needed. **How does the price compare to other options?** The Google UX Design Certificate runs about $49 a month on Coursera, so most people pay $150 to $300 by the end. UX bootcamps often run $3,000 to $9,000. GWEN is $199 once — and you only pay after you've done the interview and a full project. **What happens after my free project?** Nothing expires — your progress and all your work stay saved. Project 2 is Afterschool Activities: a real client brief you take from scope document to working wireframes. Unlock it, the rest of the internship, and your reference letter whenever you're ready. **Is there a time limit?** No. Take a week or take six months — your free project doesn't expire, and neither does anything you unlock. There's no clock running at any point. **Are there any hidden fees?** Nope. $199 is the full price. No subscriptions, no upsells. You get lifetime access to all current projects and any future ones we add. **Will you add more projects in the future?** Yes. We're planning to add at least 3 more projects, likely many more. Once you've unlocked the internship, you get lifetime access to all future projects at no extra cost. **Can I get a refund?** Yes. If you're not happy with the paid projects, email us within 30 days of purchase for a full refund. No questions asked. **How does the AI coaching work?** You'll work with AI teammates who guide you through each project. They'll give you tasks, review your work, ask clarifying questions, and provide feedback — just like real colleagues would. They're supportive but won't just hand you the answers. **Do I need to know how to use AI tools?** Most people have used AI tools like ChatGPT or Claude, but we'll teach you workflows and prompts specifically for UX work. You'll also learn how to use dedicated UX AI tools like Stitch and UX Pilot through hands-on practice. **Is there a deadline for each project?** No deadlines. This is self-paced. You can take as long as you need on each project. Some people knock out a project in one sitting; others spread it over a few days. **What projects will I work on?** You'll work on real-world UX projects across different industries — like redesigning an app onboarding flow, conducting user interviews for a fintech startup, or creating a design system for an e-commerce site. Each project simulates working with a real client and team. **Is there a community I can join?** Yes. When you sign up, you'll get access to our WhatsApp community. It's a space to ask questions, share your work, and connect with other learners. **Can I do this on my phone?** No. Proper UX work needs screen real estate — you need to work on your laptop. Most UX tools work best on a larger screen, and you'll have a much better experience that way. **Will I actually build something for my portfolio?** Yes. Every project results in deliverables you can showcase — research reports, wireframes, prototypes, presentation decks. You'll have portfolio pieces that demonstrate hands-on UX work. **Will this help me get a job?** It depends. This gives you hands-on practice and portfolio work, but it won't guarantee a job. What it will do: teach you how to work like a UX designer, give you projects to talk about in interviews, and show employers that you can use AI tools effectively — something many teams value now. **Do I get a reference letter?** When you complete the internship, you'll receive a reference letter that you can use when applying for jobs or adding to your portfolio. **Can I add this to my LinkedIn?** Absolutely. You can list it under Experience (as a virtual internship) and link to your portfolio projects. You can also write LinkedIn posts about what you built, which helps with visibility. **Can employers see my work?** Yes. Everything you create is yours. You can share your research reports, wireframes, and prototypes with potential employers, add them to your portfolio site, or discuss them in interviews. --- ## Page: Our Story (/story) ### Why I Built GWEN Every year, thousands of talented UX graduates hit the same wall: they can't get hired without experience, and they can't get experience without getting hired. I built GWEN to break that cycle. --- ### It Started with a Coffee Chat My wife Sherin came home from her MBA program at Curtin University in Perth one evening, frustrated. She'd been talking to classmates — smart, motivated people from all over the world — who were struggling to land jobs in Australia. Not because they lacked talent or education, but because they didn't have local work experience. Employers wanted proof you could do the work. Universities gave you theory. "We should do something about this," she said. I sipped on my flat white. After a few brainstorming sessions and an accelerator program later, we launched UPitch.ME — a platform that connected early-career talent with opportunities through speed networking events and an AI-curated job feed that pulled roles from multiple boards and made applying easier. We moved from Perth to Melbourne, kept building, and were among the three winners of the City of Melbourne's Open Innovation Challenge 2023. --- ### Finding the Real Problem We went to more job fairs and started talking to everyone we could find in the early career development space — university career advisors, recruiters, hiring managers, bootcamp graduates, junior talent stuck in application limbo. The same problem kept surfacing: the hardest thing to solve was work experience itself. Not the resume. Not the job search. Not interview skills. The fundamental gap was that graduates had no way to demonstrate they could actually do the work in a realistic professional setting. They had course projects and hypothetical case studies, but nothing that resembled real workplace dynamics — collaborating with stakeholders, dealing with ambiguity, receiving critical feedback, and iterating under pressure. --- ### A Pivotal Conversation On a trip to London, I was sitting with Alejandro, an old-time friend and teammate from my previous FinTech ventures in London. He's a brilliant UX designer, and he made an observation that stopped me in my tracks: "Remember when we had graduates joining our teams? We coached them, brought in mentors, made sure knowledge got transferred. They could experiment, make mistakes, iterate. You gave them... a playground." A playground for young talent. A safe space where you could try things, fail, learn, and grow — with real projects, real feedback, and real professional dynamics. Not a classroom simulation. A genuine learning environment that mimicked the messiness and richness of actual work. I couldn't stop thinking about it. What if I could take that learning/working experience and build it into a scaleable platform? That's when GWEN was born. It stands for Get Work Experience Now, because that urgency is exactly what early-career talent feels. --- ### From Prototype to Platform Grand visions are dangerous if you don't validate them quickly. So I kept my first prototype beautifully simple: A virtual UX Design internship on WhatsApp and Notion. I recruited a small group of UX students. I re-created work scenarios and briefs I'd seen play out in my career. They completed the work and sent it back. I critiqued it, gave detailed feedback, and they revised. In parallel, I evaluated if I could replicate the work I did manually with AI agents. The feedback from that first cohort was unanimous: this felt different from anything they'd experienced in their education. It felt like work. Real, messy, challenging work. I had my validation and went on to build the whole platform with Claude Code. --- ### What GWEN Is Today Finally, GWEN launched in February 2026. When you join GWEN, you step into a simulated remote internship. It feels like starting a new job — you open a chat (think Slack), meet your team, get briefed on a project, and start working. Your AI colleagues give you tasks with real ambiguity. You create actual work samples, receive constructive feedback, iterate, and build a portfolio of work that demonstrates what you can actually do. It's the first version of that playground we dreamed up earlier. If you're a student or career changer tired of hearing "we need someone with UX work experience" — this is for you. **Volker Breuer** | Creator of GWEN LinkedIn: https://www.linkedin.com/in/volkerbreuer/ --- ## Contact - Website: https://heygwen.com - Email: info@heygwen.com - Story: https://heygwen.com/story - Start free: https://heygwen.com/hub ## Page: UX Puzzles (/puzzles) A new "which UX is better?" puzzle every few days. Each one is a short video on TikTok showing a real-looking interface, followed by a full written teardown here: what went wrong, the UX principle behind it, and how a designer fixes it. The hub at https://heygwen.com/puzzles always features the most recent puzzle; every live puzzle keeps a permanent page at https://heygwen.com/puzzles/. ### Puzzle 05: The Norvale air quality page URL: https://heygwen.com/puzzles/norvale-air-quality Published: 2026-09-11 Topics: Hierarchy · emphasis Norvale's air quality page buries the reading four screens down, under breadcrumbs, related links and a colour legend, on a day the air was dangerous. The full UX teardown: why the template put it there, why order is the whole defect, and the rule worth stealing. UX teardown · 05 Nobody came for the scale. Somebody typed "is the air safe today" and landed on Norvale's air quality page. The page has the answer. It is four screens down, in body text, under a heading that says "Forecast maximums", after the search bar, three rows of breadcrumbs, a list of links to the rest of the page, five related services, the news, a maintenance notice, four paragraphs about the index and a colour legend explaining what the numbers mean. That day the reading was 11 on a scale that stops at 10. The page said so in the same grey type it uses for Sunday. Before Norvale Government ☰ Menu Search norvale.gov Home › Environment and water › Weather and climate › Air quality › Air Quality Health Index › Ellery Ellery - Air Quality Health Index On this page About the index How the index is calculated Observed conditions Forecast maximums Related links Related services Weather warnings Pollen count Observed conditions Not available Forecast maximums Today 11 - Very high risk The answer. Four screens down. After Norvale Government ☰ Menu Air Quality Health Index Ellery , Norvale · right now 11 Very high risk Air Quality Health Index What to do today Stay indoors where you can. Skip outdoor exercise. Wear a mask if you have to go out. Today 11 Sat 8 Sun 5 Mon 4 Tue 2 Learn more about how the index is calculated . Read before the thumb moves. Nobody buried it. The template did. Government sites run on one template, and the template is built for every page at once. Header, search, breadcrumbs, "on this page", related services, news. All of it comes before the content, because on most pages that order is fine. A page about permit fees can afford four screens of chrome. Then the same template is handed a page whose entire job is one number, today, and the chrome does not know the difference. It survives review because every element is correct on its own. The breadcrumbs are accurate. The legend is accurate. The reading is accurate. Nobody put a wrong thing on this page. They put the right things in the wrong order, and order is not something a component library can review. Why it hurts Every element passes. The page fails. Same four steps as every interaction, run against the page as it ships: 1 Filter : passes, and lands in the wrong place. The eye goes to the colour legend, because it is the only colour on the page. A legend explains a reading. Here the explanation is more visible than the thing it explains. 2 Seek : fails. The user arrived with one question already formed. The page answers six others first. Where you are on the site, what else is nearby, what the minister announced, how the index is calculated. Every one of them is a page the user did not ask for. 3 Act : fails, and this one has a cost. When the answer turns up it is "11 - Very high risk" in body text, in the same row style as Saturday's 8 and Sunday's 5. Nothing about it says stay inside. On a day the air is dangerous, the page speaks in exactly the voice it uses on a day it is fine. 4 Store : fails. What sticks is not the reading. It is that the official site made you dig for it, and next time you will ask a weather app instead. The one source that owns the data has taught people to get it somewhere else. Three of four fail on a page where every individual element is correct. The whole defect is the order they come in. The fix Put the answer where the page starts. Not a redesign, and not less content. The same page with one card moved to the top: the reading, the word for it, the colour, and what to do about it. Everything else is still there, further down, for the people who want it. 01 Answer the question they typed. People reach a page like this from a search, and the search is the brief. "Is the air safe today" has a yes-or-no shape, so the first thing on the page has to have that shape too: a number, a word for it and a colour. Everything that explains the number comes after the number. 02 Make a dangerous day look different from a safe one. As shipped, 11 renders in the same grey row as 3. The digits change and nothing else does. Bind the colour of the card to the reading and a bad day is red before anyone has read a word. The legend already defines those colours. Put them on the thing that matters, not only on the key. 03 Say what to do, not only what it is. An index is a measurement. Nobody wanted a measurement. They wanted to know whether to go for a run. Three lines of plain advice under the reading turn a number into a decision, and that is the one part of the page a health agency is uniquely qualified to write. It was the part missing. 04 This was never about air quality. A bank balance under the promotions. A delivery status under the order history. A test result under the hospital's navigation. Any page a person opens with one question already in their head fails the same way the moment the template is allowed to speak first. The rule worth stealing Answer first, explain later. The scale, the method, the related pages. All of it is worth having and none of it is what the person came for. Give them the answer in the first screen, in a shape they can read at a glance. Then explain, to whoever scrolls. ### Puzzle 04: The Crate permission prompt URL: https://heygwen.com/puzzles/crate-permission-prompt Published: 2026-09-04 Topics: Permissions · timing Crate asks for notification permission before the shop has finished loading, and iOS only lets an app ask once. The full UX teardown: why the later ask wins, how pre-permission priming works, and the rule worth stealing. UX teardown · 04 You only get to ask once. Crate asks for notification permission before the shop has finished loading. On iOS that prompt fires exactly once per install. Tap "Don't Allow" and the app can never show it again. Getting it back means the user going into Settings, finding Crate in a list of ninety apps, and turning it on themselves. Crate spent its one ask on a stranger who had not yet seen a single product. Before Crate Cart "Crate" Would Like to Send You Notifications Notifications may include alerts, sounds and badges. Don't Allow Allow One shot, spent on a stranger. After Crate Order ✓ Order placed Arrives Tue 9 Sep to Fri 12 Sep Want a ping when it ships? We'll message you when your mug is dispatched, and again when it's out for delivery. Yes, notify me Not now The system prompt has not fired yet. Nobody chose the moment. The tutorial did. Requesting permission is one call. The obvious place to put it is where the app starts, because that is where you are already writing setup code, and it is where every tutorial puts it. The ticket says "ask for notification permission" and says nothing about when. It survives design review because there is nothing to review. The control is Apple's, the copy is Apple's, and the product wrote neither. No screen in the app looks wrong. The only decision anyone made was a line number, and a line number does not show up in a design critique. Why it hurts The screen is perfect. The moment is not. Same four steps as every interaction, run against the prompt as it ships: 1 Filter : passes, and that is the trap. It is the system alert, pixel for pixel, in a shape every iPhone owner has seen a thousand times. Nobody questions a native control. 2 Seek : fails. The user came to look at things people made. They are being asked about an ongoing relationship with a shop whose products have not finished loading behind the dialog. 3 Act : fails fast, and rationally. With nothing to weigh, "Don't Allow" is the correct tap. Dismissing costs nothing and deciding costs attention. The user is not being careless. They are being sensible. 4 Store : fails. What sticks from the first two seconds is not the shop. It is that this app wanted something before it gave anything. Three of four fail on a control the product did not design, using copy it did not write. The entire defect is when it fired. The fix Let the order do the asking. Not new copy. The same prompt, moved to the first moment the user has a reason to want it. Somebody who just spent thirty-four dollars on a mug has an obvious interest in knowing when it ships. 01 Ask in your own UI first. That is the whole mechanic. Put your own sheet in front of the system one, and only fire Apple's prompt when somebody has already said yes to yours. A no in your sheet costs you nothing, because you can ask again next week. A no in Apple's costs you the channel for the life of the install. It has a name, pre-permission priming, and it is the single highest-leverage thing in this teardown. 02 Treat it as a budget of one. iOS shows that dialog once per install. After the user answers, further requests return the stored answer and display nothing at all. There is no second attempt to design, no better wording to try later. Everything you would normally learn by iterating, you have to get right the first time. 03 Name the notification, not the permission. "Want a ping when it ships?" is not a request for access. It is an offer of a service the user already wanted, and permission is the incidental cost of accepting it. Say which messages, and say what you will not send. Vague value earns a vague no. 04 This was never about notifications. Camera, microphone, location, contacts, calendar, tracking, the app store review prompt. Every one of them is a one-shot ask with the same shape. Fire it on launch and you have spent it on somebody with no reason yet to say yes. The rule worth stealing Earn the ask, then make it. A permission prompt is not a form field you can re-ask. It is one non-renewable request, and it is worth exactly as much as the reason you have given for it. Give the reason first. Then ask. ### Puzzle 03: The Tally birthday picker URL: https://heygwen.com/puzzles/tally-birthday-picker Published: 2026-08-28 Topics: Forms · defaults Tally's birthday picker opens on today's date, and nobody was born today. The full UX teardown: why the arbitrary-looking default wins, why the arithmetic midpoint is the weaker answer, and the rule worth stealing. UX teardown · 03 Nobody was born today. Tally wants your birth year. The wheel opens on today's date, so every person who installs this app drags backwards through decades to answer a question they already knew the answer to. Today is the one value in that column that is guaranteed to be wrong. Before TALLY Basics When were you born? We use this to set your daily targets. Jun Jul Aug Sep Oct 25 26 27 28 29 2024 2025 2026 End of the list. Only one way to go. Continue After TALLY Basics When were you born? We use this to set your daily targets. Apr May Jun Jul Aug 13 14 15 16 17 1999 2000 2001 2002 2003 Most users land within a few rows. Continue One field. One default. Nobody decided it. Opening on today is not a choice anyone made. It is what a date picker does when you do not tell it otherwise. The framework hands it to you, the ticket says "add date of birth", and the default ships untouched. It survives design review because a picker sitting on today's date looks exactly like a picker. Nothing is broken. It is a working control doing precisely what it was told, and charging every user the same tax forever. Why it hurts It passes the eye test and fails the hands. Same four steps as every interaction, run against the picker as it ships: 1 Filter : passes. Clean, familiar, unmistakably a date picker. That is exactly why nobody stops to question it. 2 Seek : fails, and oddly. The user is not searching for anything. They can recite their birthday. The interface makes them hunt for a value they already hold. 3 Act : fails. Flick, overshoot, correct, repeat. Twenty-five rows of imprecise dragging for a decision that took no thought at all. 4 Store : fails. What sticks from the first screen is not the product. It is that this app is going to be work. Three of four steps fail on a screen with no visual problems whatsoever. The whole defect is one number, chosen by nobody. The fix Open where your users already are. One line of initialisation, not a redesign. The screen does not change. Only the number it starts on. 01 Aim at your median user, not the midpoint. The tidy answer is to open halfway between the oldest and youngest year the field allows. Resist it. That optimises for a flat spread of users which no product actually has. Tally's users cluster in their twenties and thirties, so the midpoint of the range still leaves most of them scrolling. Point the default at the middle of the people, not the middle of the list. 02 Today has zero probability. For a birthday field, today is not merely a weak guess. It is the single value in the column that cannot possibly be right. Whatever else you argue about, any other year beats it. 03 Measure the default in rows, not in code. Design review looks at the screen. The user feels the distance. Count how many rows your average signup has to travel and the argument makes itself, without anyone having to have taste. 04 This was never about birthdays. Country, currency, party size, delivery date, quantity. Any field with a knowable distribution already has its answer sitting in your own data. Most products decline to look, and hand the user the framework's guess instead. The rule worth stealing Default to the answer, not to zero. Every default is a prediction about the person in front of you. Ship the one your framework handed you and you have predicted nothing. The best guess available is usually already in your data, and it costs one line to use it. ### Puzzle 02: The Wander free trial URL: https://heygwen.com/puzzles/wander-free-trial Published: 2026-08-24 Topics: Trials & churn · perceived risk Most trial screens stay silent about auto-renewal. Wander promises to remind you before it charges — twice. The full UX teardown: why the counterintuitive move wins, the psychology of perceived risk, and the rule worth stealing. UX teardown · 02 The scariest button in the app. This isn't a checkout. Nothing costs anything today. It's a free trial — and still, the thumb hovers. Because "free" arrives bundled with a job: remember to cancel before day 30, or pay for something you forgot you had. Before × WANDER PRO Go Pro. Free for 30 days. Offline maps Turn-by-turn voice nav Multi-day route planning Live weather overlays ★★★★★ 4.8 · 12,400 hikers Then $7.99/month after your trial Start free trial Auto-renews. Cancel anytime in settings. After × WANDER PRO Go Pro. Free for 30 days. Offline maps Turn-by-turn voice nav Multi-day route planning Live weather overlays Then $7.99/month. Full access from today. 🔔 We'll email you 3 days before your trial ends. No surprise charges. Start free trial Cancel anytime. It takes two taps. One screen. One fear. Total silence. The "before" screen isn't broken — it's what almost every subscription app ships. Which is exactly the problem: it answers every question except the one the user is actually asking. 1 The real question goes unanswered. Nobody hesitating over that button is weighing offline maps against weather overlays. They're asking one thing: what happens on day 30? The screen answers with feature bullets. 2 "Cancel anytime" has stopped meaning anything. Every subscription on earth says it, usually in 8-point grey. It reads as legal wallpaper, not reassurance — because reassurance needs a mechanism, and this is a slogan. 3 The memory task lands on the user. A "free" trial, plus homework: remember day 27, find the cancel screen, hope it isn't buried. That standing little debt of attention is the real price on this screen. …so anxious users take one of two exits. Some never start the trial at all. The rest start it and cancel in the same minute, just to be safe — and a cancelled-on-day-one user never sticks around long enough to see the value the trial exists to show. "The objection was never the price. It's the memory task hiding behind the word 'free'." Why the reminder wins Absorb the risk, and the tap gets easy. Designers call this perceived risk — the gap between what a screen asks and what the user fears it might quietly cost them. Money, sometimes. But here it's attention: a subscription you must remember to escape is a small standing debt, and people decline debts by default. The counterintuitive part: promising "we'll warn you before we charge you" looks like inviting cancellations. What it actually cancels is the fear. And the revenue that silence protects is the worst kind a product can earn — accidental renewals from people who forgot, which come back as angry churn, refund requests and one-star reviews. The reminder trades that for renewals from people who actually chose to stay. The lens: Filter → Seek → Act → Store Same four steps as every interaction — run them on the silent trial screen: 1 Filter — passes. The screen is clean and scannable. That's what fools designers into shipping it. 2 Seek — wobbles. "What exactly happens on day 30?" is left to the fine print. 3 Act — hesitates. The window of patience fills with risk arithmetic instead of excitement. 4 Store — fails. What sticks isn't an experience. It's a to-do: "remember to cancel." A screen can pass the eye test and still fail three of the four steps. One line of copy — the reminder pledge — repairs Seek, Act and Store at once. The fix Take the fear off their plate. The fix isn't a bigger discount or louder bullets. It's absorbing the user's risk — visibly. 01 Answer the fear where it lives. The reminder pledge sits right next to the price — the exact spot the eye goes while deciding. Not in an FAQ, not in the fine print. 02 Say it twice. The promise repeats right after signup, when the doubt does. Once is copy; twice is policy — and policy is what people believe. 03 Make the exit checkable. "Cancel in two taps" is a claim the user can verify on day one. A verified claim lends its credibility to everything else on the screen. 04 Then let the product sell itself. With the fear gone, thirty days of actual use argues better than any bullet list ever will. The rule worth stealing Remove the fear, not just the friction. When people hesitate at an ask, effort usually isn't the blocker — risk is. The product that absorbs the risk earns the try. ### Puzzle 01: The Stride welcome screen URL: https://heygwen.com/puzzles/stride-welcome-screen Published: 2026-08-18 Updated: 2026-08-20 Topics: Competing CTAs · cognitive load The Stride welcome screen asks you to make three decisions before you've taken a single step. The full UX teardown: what went wrong, the principle behind it (cognitive load), and how a designer fixes it. UX teardown · 01 First, look again. This is the first screen a brand-new Stride runner sees. Not a settings page. Not a paywall. The welcome — the moment the app has your full attention and your lowest patience. And in that moment, it asks you to do a surprising amount of work. Before STRIDE Welcome to Stride! 🏃 Track every run, follow adaptive plans, join weekly challenges, sync your watch, share to the feed and unlock badges as you go — Stride is built for every kind of runner. ✓ Send me tips, product news, partner offers and marketing. Have a referral code? Enter → Create account Log in Continue with Google After STRIDE Your first training plan is ready. It takes 20 seconds to start. Start running I already have an account One screen. Three asks. Zero clarity. The screen isn't ugly — that's what makes it sneaky. Before you reach a single decision there's a paragraph of marketing to skim: a wall of "track every run, follow plans, join challenges, sync your watch…" that sells you the whole app before you've used any of it. Then the screen stacks three unrelated decisions on top of each other and gives them roughly equal weight. 1 Decide about a pre-ticked opt-in. Buried under the welcome text, styled to look like terms & conditions, is a pre-ticked box signing you up for marketing. It's a real decision disguised as fine print — the kind you only notice after you've agreed to it. 2 Consider a referral code. A dashed box adds yet another path. Most new users don't have a code, but now they're wondering: should I? Am I missing a discount? If I tap this, did I still opt into emails? 3 …and then choose between three near-identical ways in. "Create account", "Log in" and "Continue with Google" carry nearly identical visual weight, so even the primary action isn't obvious. The single most important tap on the screen is competing with four other things. "Every one of these is defensible on its own. Together, they turn a welcome into a quiz." Why it hurts You're doing the app's thinking for it. Designers call this cognitive load — the mental effort a screen demands from the person using it. Every extra choice, every ambiguous label, every "wait, what does this do?" spends a little of the user's attention. And attention is the one thing a first-time user has almost none of. Stride front-loads that cost at the worst possible moment. Instead of "great, let's run," the new user feels "ugh, paperwork." Some push through. Many quietly close the app. That drop-off never shows up as an angry review — it just shows up as a number. The lens: Filter → Seek → Act → Store Every time someone interacts with a product, they run these four steps — in this order: 1 Filter the information — what do I even look at? 2 Seek its meaning — what is this asking me? 3 Act within a limited window of patience — what do I tap? 4 Store the experience in memory — how did that feel? Stride fails at step one — filtering: there's too much to filter, so seek and act get expensive, and store leaves a bad taste. The fix One screen, one decision. The fix isn't prettier buttons or a nicer illustration. It's removing decisions . 01 One clear ask. A single obvious next step: Start running. "I already have an account" sits quietly below — present, never competing. 02 The opt-in moves. Marketing consent doesn't belong in the doorway. Ask it after the first run — plainly, unticked. 03 The referral code moves. An optional field inside account creation — available to the few who need it, invisible to the many who don't. 04 The wall of text goes on a diet. One confident line: "Your first training plan is ready. It takes 20 seconds to start." What happens next, not everything the app can do. The rule worth stealing One screen should ask for one decision. When a screen feels cluttered, the answer usually isn't better styling. It's fewer decisions.