<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Danijel Nedell on Medium]]></title>
        <description><![CDATA[Stories by Danijel Nedell on Medium]]></description>
        <link>https://medium.com/@danijelnedeljkovic?source=rss-8e338c2a33a6------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*IG7ex1xO7KA_533qmekyvw@2x.jpeg</url>
            <title>Stories by Danijel Nedell on Medium</title>
            <link>https://medium.com/@danijelnedeljkovic?source=rss-8e338c2a33a6------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 10:22:01 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@danijelnedeljkovic/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[I Went Quiet. Here’s Why – and What’s Next (Maybe)]]></title>
            <link>https://medium.com/@danijelnedeljkovic/i-went-quiet-heres-why-and-what-s-next-maybe-ee74de7cf1b6?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ee74de7cf1b6</guid>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Tue, 05 May 2026 14:02:08 GMT</pubDate>
            <atom:updated>2026-05-05T14:02:08.404Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/656/1*FjXu0KTZYJVMVkzTfT8vyg@2x.jpeg" /></figure><p>It’s been a while.</p><p>No articles, no insights, no hot takes about why your design system is lying to you.</p><p>Honestly? I needed a break from performing expertise on the internet. You know the type of content – polished, structured, 7-minute reads that sound smart but leave you feeling nothing. I wasn’t interested in adding to that pile.</p><p>But I’ve been thinking. A lot.</p><p>And I have opinions – probably too many. So before I start writing again, I want to ask you something:</p><p><strong>What would actually be useful to you right now?</strong></p><p>A few directions I’m considering:</p><p>→ More UX brutality – calling out the industry BS we all pretend is fine</p><p>→ Real talk about working in design when nobody listens to designers</p><p>→ Tools, AI, and whether any of it actually makes our work better (spoiler: complicated)</p><p>→ Career stuff – navigating the design job market without losing your mind</p><p>Drop a comment. Tell me what you’d read. Tell me what you’re tired of reading.</p><p>I’ll write the thing that gets the most votes. Or the most interesting answer. We’ll see.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ee74de7cf1b6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My 2026 New Year’s Resolution: Pretending Job Postings Make Sense]]></title>
            <link>https://medium.com/design-bootcamp/my-2026-new-years-resolution-pretending-job-postings-make-sense-c063225dc68a?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c063225dc68a</guid>
            <category><![CDATA[career-advice]]></category>
            <category><![CDATA[workplace-culture]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[hiring]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Tue, 23 Dec 2025 07:33:42 GMT</pubDate>
            <atom:updated>2025-12-23T07:33:42.082Z</atom:updated>
            <content:encoded><![CDATA[<h4>One more year down. Another 365 days of reading job descriptions written by people who think “UX/UI Designer” means “someone who designs user experiences AND does the company’s taxes.”</h4><figure><img alt="A tall pile of mixed hats and work gear stacked on a gray office chair in a modern office, suggesting overloaded roles and unrealistic job expectations" src="https://cdn-images-1.medium.com/max/1024/1*rXHpUz11QsVjvhxsEYkb1Q.png" /><figcaption>Wearing multiple hats, because apparently one job is never enough</figcaption></figure><p><strong>THE ANNUAL DELUSION</strong></p><p>Here we are again. End of another year. Your feed is drowning in LinkedIn Year in Review carousels and Spotify Wrapped like it’s a personality test.</p><p>Nobody cares about your engagement stats. We’re busy applying to jobs that want 5 years of experience in a tool that launched last Tuesday.</p><p>My actual resolution is simple: I’m hoping 2026 is the year recruiters finally figure out what UX designers actually do.</p><p>I know. I’m an optimist.</p><p>I tell myself I’m looking for a role. What I’m actually doing is speed dating with companies that don’t know what they want, and getting rejected for not being a mind reader.</p><p><strong>THE GREATEST HITS OF JOB POSTING NONSENSE</strong></p><p>Let me paint you a picture of my fantasy 2026 job market:</p><p><strong>Job postings stop defaulting to 2019 tools.</strong> Look, if your requirements list includes Sketch, Adobe XD, or InVision Studio, I know two things immediately: you copy-pasted this from an old posting, and you haven’t updated your hiring process in years.</p><p>It’s not that these tools are useless — it’s that requiring them signals you’re not paying attention to what designers actually use now. That’s like hiring a plumber and asking if they’re certified in lead pipes.</p><p><strong>Recruiters learn the difference between UI and UX designers.</strong> If you’re hiring a “UX designer” and the job description says “make our buttons pretty,” you’re hiring a UI designer who’s going to hate their life. There’s a difference between researching user behavior patterns and making the logo bigger. It’s like saying a chef and a food photographer are the same job because they both work with food.</p><p><strong>“Entry-level” actually means entry-level.</strong> Not “Entry-Level UX Designer — 5+ years experience required, must have shipped 10+ products.” That’s a senior designer you want to pay junior rates. It’s the job market equivalent of those recipe blogs that say “quick 30-minute meal” and then list 23 ingredients and assume you own a sous vide and a personality.</p><p>Here’s what actually needs fixing:</p><p><strong>The junior paradox is killing new designers.</strong> They can’t get jobs without experience. Can’t get experience without jobs. Meanwhile, “entry-level” roles require portfolios that would take years to build. The people who need these jobs can’t get them. The people qualified for them don’t want them because they pay terribly. Everyone loses.</p><p><strong>“Scrappy” means “we want six people for the price of one.”</strong> I talked to a recruiter last month who wanted a UX designer to do research, wireframing, prototyping, visual design, front-end dev, product strategy, and TikTok content. That’s not one job. That’s an entire department you’re too cheap to hire. Scrappy is just startup for “we replaced headcount with optimism.”</p><p>They don’t want scrappy. They want someone who won’t say no.</p><p><strong>THE ABSURDITY WE PRETEND IS NORMAL</strong></p><p><strong>“We’re looking for a rockstar ninja wizard unicorn designer!”</strong></p><p>Choose a fantasy creature and stick with it. I’m a designer, not a Dungeons &amp; Dragons character. If you want a unicorn, good luck — those don’t exist. Which is probably the point.</p><p><strong>“Ability to thrive in a fast-paced environment.”</strong></p><p>Translation: we’re disorganized, everything’s on fire, and we schedule meetings at 4:45 PM on Fridays.</p><p>Fast paced is corporate for “we confuse urgency with planning.”</p><p><strong>“Competitive salary.”</strong></p><p>Competitive with what? Just say the number. We’re all adults here. If your “competitive salary” requires three roommates and ramen, that’s not competitive — that’s insulting.</p><p><strong>“Unlimited PTO!”</strong></p><p>Which means nobody knows what’s “normal,” so nobody takes it without guilt, and the company doesn’t pay it out when you leave. Just give me 25 days and let me use them.</p><p><strong>WHAT WE SHOULD DEMAND IN 2026</strong></p><p>Here’s what I’m committing to, and what you should too:</p><p><strong>Stop applying to jobs that can’t define themselves.</strong> If the requirements list 47 tools, they don’t know what they want. If it says “UX/UI designer” but describes six different roles, they’re fishing. Move on.</p><p><strong>Ask about salary in the first conversation.</strong> Life’s too short. If they can’t afford you, find out before wasting three weeks on interviews.</p><p><strong>No free work.</strong> Not for exposure. Not for “portfolio pieces.” Not for test projects that look suspiciously like production work. Your landlord doesn’t accept LinkedIn impressions as rent.</p><p><strong>Here’s what a good job posting actually looks like:</strong></p><p><em>Senior UX Designer — Remote</em><br> <em>$95,000–$115,000 (depending on experience)</em></p><p><em>You’ll do:</em></p><ul><li>User research and testing (a few projects per quarter)</li><li>Wireframing and prototyping in Figma</li><li>Collaborate with product and engineering teams</li></ul><p><em>You have:</em></p><ul><li>4+ years UX experience</li><li>Portfolio showing research-to-design process</li><li>Experience with B2B SaaS products</li></ul><p><em>Interview process:</em></p><ul><li>30-min recruiter call</li><li>1-hour portfolio review</li><li>1-hour team fit conversation</li><li>Paid design exercise (time boxed, paid)</li></ul><p>See how easy that was? Role clarity. Salary band. Realistic requirements. Transparent process. Paid work.</p><p>If you can’t describe the job, the pay, and the scope, you’re not hiring. You’re fishing.</p><p><strong>THE MARKET ONLY CHANGES IF WE CHANGE IT</strong></p><p>2026 isn’t going to magically fix anything. But here’s what we can control:</p><p>Stop accepting garbage. When a posting lists outdated tools or asks for six roles, skip it. When they won’t share salary, walk. When they want free work, laugh and hang up.</p><p>The market is broken because we keep accepting broken conditions.</p><p>Every time you ask about salary upfront, you make it normal. Every time you refuse unpaid work, you raise the floor. Every time you call out a ridiculous posting, you make the next one slightly better.</p><p>Designers are already doing this — sharing salary data, networking better, building communities that actually help instead of just posting gradient quotes on LinkedIn.</p><p>So yeah, I’m making jokes. Because if I don’t laugh, I’ll cry watching another CEO post “we’re all in this together” after laying off 30% of staff.</p><p><strong>MIC-DROP WRAP</strong></p><p>Here’s my 2026 prediction. Job postings will stay ridiculous. Recruiters will keep mixing up UX and UI. Someone will still ask for five years of experience in something invented during your last lunch break.</p><p>So fine. Let them.</p><p>If you can’t describe the job, the pay, and the scope, you’re not hiring. You’re fishing. And I’m done biting.</p><p>So… how many more times are we going to pretend this is normal?</p><p><em>No recruiters were harmed in the making of this article. Some feelings may have been hurt. That was intentional.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c063225dc68a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/my-2026-new-years-resolution-pretending-job-postings-make-sense-c063225dc68a">My 2026 New Year’s Resolution: Pretending Job Postings Make Sense</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Future of UX Isn’t Design — It’s Teaching Machines to Be Human]]></title>
            <link>https://medium.com/design-bootcamp/the-future-of-ux-isnt-design-it-s-teaching-machines-to-be-human-4b37d9cc96e5?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b37d9cc96e5</guid>
            <category><![CDATA[human-ai-interaction]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Wed, 03 Dec 2025 08:02:16 GMT</pubDate>
            <atom:updated>2025-12-03T19:00:02.254Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Future of UX Isn’t Design — It’s Teaching Machines to Be Human</h3><h4>In 2025, we’re still designing buttons and screens like it’s 2015, while AGI is learning to write novels, diagnose diseases, and have existential crises about its own existence.</h4><figure><img alt="A modern human figure styled like Michelangelo’s God reaches out to touch the hand of a glowing, circuit-like AGI humanoid, with a burst of light forming where their fingers meet." src="https://cdn-images-1.medium.com/max/1024/1*UsfD7fz-H-FLB7G8_i-yfw.png" /><figcaption><em>When Human Intention Touches Machine Intelligence — a new creation begins.</em></figcaption></figure><p><strong>THE UNCOMFORTABLE TRUTH NOBODY’S SAYING OUT LOUD</strong></p><p>Here’s what keeps me up at night: We spent two decades perfecting the art of making interfaces intuitive, and now we’re building intelligence that doesn’t need interfaces at all.</p><p>Every UX designer I know is doing the same dance right now. We’re optimizing checkout flows and A/B testing button colors while Claude, GPT-4, and Gemini are literally having conversations with millions of people without a single dropdown menu in sight. The cognitive dissonance is real, and it’s hilarious in that dark, existential way.</p><p>But here’s the thing nobody wants to admit — this isn’t the death of UX. It’s the most important moment UX has ever had. We’re just looking at it completely wrong.</p><p>The future of UX in an AGI world isn’t about designing better interfaces for humans. It’s about designing better humans for AGI to interface with. And before you roll your eyes, hear me out, because this reframe changes everything.</p><p><strong>WHY THIS MATTERS MORE THAN YOUR NEXT REDESIGN</strong></p><p>Think about every frustrating conversation you’ve had with a chatbot. Not the new ones — the old ones from 2020 that still haunt us like digital ghosts. “I’m sorry, I didn’t understand that. Please select from the following options.”</p><p>We blamed the AI. We said the technology wasn’t ready. But the real problem was deeper: we tried to force conversational AI into the same mental model as graphical interfaces. We wanted it to behave like a menu system that could talk.</p><p>Now we’ve got AGI systems that genuinely understand context, remember preferences, and adapt to communication styles. For the first time in human history, the interface is learning faster than the user. Your phone’s AI understands you better after a week than your coworker does after a year.</p><p>While we debated whether buttons should be rounded or square, AI solved protein folding. DeepMind’s AlphaFold predicted the 3D structures of over a200 million proteins — essentially all proteins known to science. That’s not a feature update. That’s a wholesale revolution in drug discovery, disease understanding, and treatment development. The interface wasn’t the breakthrough. The intelligence was.</p><p>And here’s what makes this terrifying and beautiful: AGI doesn’t just respond to inputs. It interprets intent, fills in gaps, and makes judgment calls about what you actually meant versus what you actually said. It’s doing emotional UX work we used to hire therapists and really good waiters to do.</p><p><strong>WHAT EVERY UX DESIGNER IS GETTING CATASTROPHICALLY WRONG</strong></p><p>The biggest mistake I see in the UX community right now is treating AGI like it’s just another tool in the toolkit. It’s not Figma 2.0. It’s a colleague that never sleeps, never forgets, and is getting smarter every single day.</p><p>Let me put this in perspective. In 1997, IBM’s Deep Blue beat Garry Kasparov at chess — the reigning world champion, considered one of the greatest strategic minds in history. Everyone freaked out. “The machines are smarter than us!” But here’s what actually happened: chess didn’t die. It evolved. Players started using AI to train, analyze positions, and explore strategies no human had ever considered. The game got deeper, not obsolete.</p><p>Fast forward to 2016. DeepMind’s AlphaGo demolished Lee Sedol, one of the greatest Go players ever, in a game infinitely more complex than chess. Move 37 in game two became legendary — a move so strange, so counterintuitive, that no human would have played it. And it was brilliant. Lee Sedol spent the rest of the match trying to understand the mind he was playing against.</p><p>Now let me paint you a picture. I keep seeing beautiful prototypes for AI-assisted design tools. Stunning interfaces. Perfect information hierarchy. The AI relegated to a sidebar — a helpful assistant that will “suggest” things when prompted.</p><p>They’re gorgeous. They’re also completely backwards. These interfaces aren’t teaching humans how to work with AGI — they’re teaching humans how to keep AGI at arm’s length. Security blankets disguised as innovation.</p><p>Here’s the pattern: We’re designing guardrails when we should be designing playgrounds. We’re creating rigid structures because we’re terrified of what happens when AGI has too much freedom. But the guardrails aren’t protecting users from AGI. They’re protecting our egos from obsolescence.</p><p>I recently came across research exploring AGI UX and human-agent teaming that flips this paradigm on its head. Instead of asking “how do we control the AI,” it asks “how do we design trust calibration between humans and intelligent agents?” The findings were fascinating: users don’t fail because AI makes mistakes. They fail because they trust it completely or not at all. There’s no middle ground. No calibration. Just binary faith or total abandonment.</p><p>That’s the real UX problem. We’re designing for perfect trust in imperfect systems.</p><p><strong>THE FRAME THAT CHANGES EVERYTHING</strong></p><p>Stop thinking of yourself as an interface designer. Start thinking of yourself as a relationship counselor between humans and artificial intelligence.</p><p>That’s not a metaphor. That’s literally the job now.</p><p>The best UX in an AGI world isn’t invisible — it’s conversational. It creates a space where humans and AI can genuinely collaborate without one dominating the other.</p><p>Think about the best working relationships you’ve ever had. They weren’t frictionless. They had tension, negotiation, and mutual adaptation. You learned their communication style; they learned yours. You challenged each other. You filled in each other’s blind spots.</p><p>That’s what AGI-era UX looks like. Not a servant-master dynamic. Not a tool-user paradigm. A partnership that evolves.</p><p>When AlphaFold cracked protein folding, it didn’t replace biochemists. It gave them a collaborator that could explore possibility spaces no human could map alone. The UX challenge wasn’t making AlphaFold easy to use — it was helping scientists learn to ask questions they’d never thought to ask before.</p><p>Here’s the shift that matters: Traditional UX assumes determinism. If A happens, then B follows. AGI operates on uncertainty. If A happens, then B, C, or something completely unexpected might occur. Designing for probabilistic behavior instead of deterministic outcomes is a fundamental rethinking of what an interface even is.</p><p><strong>WHAT THIS ACTUALLY LOOKS LIKE IN PRACTICE</strong></p><p>Let me give you four examples of what I mean, because abstractions are useless without concrete reality.</p><p><strong>Example one:</strong> Look at how Claude handles uncertainty. When you ask it something ambiguous, it doesn’t just guess. It reflects back what it understood and asks clarifying questions. The interface isn’t preventing errors — it’s building pattern recognition in the user. You learn to communicate better because the AI models good communication back to you.</p><p><strong>Example two:</strong> GitHub Copilot doesn’t just suggest code. It suggests code in your style, at your skill level, with your naming conventions. The UX isn’t in the autocomplete popup — it’s in the learning system that watches how you code and adapts. The interface is almost boring. The relationship is fascinating.</p><p><strong>Example three:</strong> There’s a medical AI tool used in radiology departments now that intentionally disagrees with doctors about 10% of the time — even when it’s not certain. Not to be contrary, but to force conversation. The UX team realized that doctors were rubber-stamping AI recommendations without thinking. So they designed friction. And it saved lives, because it turned a tool relationship into a peer-review relationship.</p><p><strong>Example four:</strong> Some AGI UX research has introduced concepts like “Reasoning Sidebars” — optional panels that show the AI’s thinking process without cluttering the main interface. Power users can see exactly how the agent arrived at its conclusion. Casual users get clean, simple outputs. But here’s the clever part: these systems don’t just show reasoning. They show uncertainty. When confidence drops, the AI stops, presents multiple interpretations, and asks what it needs to proceed safely.</p><p>That’s designing for trust calibration. Not blind trust. Not paranoid distrust. Earned, informed collaboration.</p><p>See the pattern? The best AGI UX right now isn’t smooth — it’s intentionally rough in strategic places. It creates moments where humans have to engage, question, and learn.</p><p><strong>THE SKILLS YOU ACTUALLY NEED TO BUILD</strong></p><p>If you’re a UX designer reading this and feeling mildly panicked, good. Panic is the appropriate response to realizing your entire mental model needs an update. But here’s what comes after panic: curiosity.</p><p>The skills that matter now aren’t in Figma. They’re in psychology, linguistics, and pedagogy. You need to understand how humans learn, how they form mental models, and how they transfer skills from one context to another.</p><p>You need to get comfortable with ambiguity. AGI doesn’t have fixed states. It updates, it learns, it changes. Designing for a system that evolves daily is like choreographing a dance where your partner improvises half the moves.</p><p>You need to become fluent in prompt engineering — not as a user, but as a designer. The prompts are the new wireframes. The conversation flow is the new information architecture. If you can’t shape how humans talk to AGI, you can’t shape the experience.</p><p>And here’s the skill nobody’s talking about: You need to learn how to design for dignity. When AGI can fold proteins in minutes that would take humans years, when it can beat the greatest strategic minds at their own games, when it can generate code faster than you can type — the UX challenge isn’t efficiency anymore. It’s meaning. It’s agency. It’s helping humans feel like collaborators, not passengers.</p><p>There’s a concept emerging in AGI UX research called “decision boundaries” — mapping who decides what, and when. The AI handles pattern-matching, syntax generation, search tasks. Humans handle ethical decisions, ambiguous intent, and final approval for high-stakes actions. But the magic happens in the boundary itself — the negotiation space where both parties communicate and calibrate.</p><p>That’s the skill you need to build. Not interface design. Relationship architecture.</p><p><strong>THE STUFF THAT WILL TRIP YOU UP</strong></p><p>Let’s talk about where this gets complicated, because it absolutely does.</p><p>First, the trust problem. Humans trust consistency. AGI is probabilistic. Every response is technically unique. We’re designing for a world where “it worked last time” isn’t a guarantee, and that breaks every mental model users have about how technology should behave.</p><p>And here’s what makes it worse: users project human intention onto statistical models. They see fluent language and interpret it as understanding. They see a confident answer and assume certainty. When the AI hallucinates — makes up facts with complete conviction — users either over-trust completely or their faith collapses entirely. There’s no natural middle ground.</p><p>Research into human-AGI interaction has identified three cognitive fallacies: the Magic Box Fallacy (believing AI understands context like a human), the Memory Fallacy (assuming it remembers everything automatically), and the Intent Fallacy (interpreting outputs as deliberate choices instead of probability-driven generation). These aren’t bugs in the user. They’re features of human cognition. And we have to design around them.</p><p>Second, the attribution problem. When an AGI-assisted tool produces something brilliant, who gets the credit? This isn’t philosophical — it’s UX. If users don’t feel ownership over AGI-assisted work, they won’t engage deeply with it. But if AGI is invisible, users don’t learn to leverage it better.</p><p>Third, the skill atrophy problem. If AGI handles all the grunt work, humans lose the foundation that makes expertise possible. The UX challenge is designing systems that scaffold learning even as they automate execution.</p><p>Fourth, the anthropomorphism trap. Users blame themselves when AI fails. They say “I must have asked it wrong” instead of “the system gave me bad output.” This is dangerous. Good AGI UX has to actively fight this instinct — making it clear when the AI is uncertain, when it’s guessing, and when it’s operating outside its competence zone.</p><p>These aren’t solved problems. Anyone who tells you they are is selling something.</p><p><strong>YOUR ACTUAL NEXT STEPS</strong></p><p>Here’s what I’d do if I were building AGI-era UX today, starting tomorrow morning.</p><p>Spend a week using Claude, GPT-4, or Gemini not as a tool, but as a collaborator. Don’t just ask it questions — have conversations with it. Learn its blindspots. Notice when it’s confident versus hedging. Pay attention to how your communication style changes as you learn what works.</p><p>Find one workflow in your life and design a human-AGI partnership around it. Not automation. Partnership. Where does the AI lead? Where do you lead? What does negotiation look like? Build the interaction model before you build the interface.</p><p>Try this specific exercise: Map the decision boundaries for one high-stakes task. What should AI handle autonomously? What needs human approval? What requires a full stop and explicit confirmation? Then prototype a “circuit breaker” — a single control that lets users degrade the agent from autonomous collaborator to manual tool instantly. That’s not a failure mode. That’s preserving agency.</p><p>Study what happened in chess after Deep Blue, and in Go after AlphaGo. The games didn’t die — they transformed. Players developed new strategies, new training methods, new ways of thinking about positions. The interface between human intuition and machine calculation created something neither could achieve alone.</p><p>And here’s the one that matters most: Stop designing for the user you have and start designing for the user you’re creating. Every AGI interaction is training. The question isn’t just “What does the user need right now?” It’s “What kind of human-AGI relationship am I teaching people to expect?”</p><p><strong>THE ENDING NOBODY WANTS TO HEAR BUT EVERYONE NEEDS TO</strong></p><p>The future of UX in an AGI world isn’t about making technology easier to use. It’s about making humans better at being human while working alongside intelligence that doesn’t share our limitations.</p><p>That means designing for growth, not convenience. For challenge, not comfort. For partnership, not servitude.</p><p>The interfaces that win won’t be the prettiest or the smoothest. They’ll be the ones that make both humans and AGI better at what they each do best. They’ll be the ones that create space for genuine collaboration, with all the mess and magic that entails.</p><p>When DeepMind solved protein folding, they didn’t just advance science — they showed us what becomes possible when we stop treating AI as a tool and start treating it as a thinking partner. The medical breakthroughs coming in the next decade won’t come from better lab equipment. They’ll come from better collaboration between human insight and artificial intelligence.</p><p>The designers who thrive in this era won’t be the ones who master new software. They’ll be the ones who learn to design relationships, calibrate trust, and create spaces where misunderstanding becomes learning instead of failure.</p><p>And here’s the truth that I think about every time I open a design file: We’re not designing the future of how humans use AGI. We’re designing the future of how humans and AGI become something neither could be alone.</p><p>That’s not a UX challenge. That’s a species-level opportunity disguised as a design problem.</p><p>The question isn’t whether AGI will change design. It’s whether designers will rise to meet the intelligence they’re partnering with.</p><p><strong>What kind of relationship are you designing for?</strong></p><p><strong>SOURCES</strong></p><p>DeepMind’s AlphaFold database: <a href="https://alphafold.ebi.ac.uk/">https://alphafold.ebi.ac.uk/</a></p><p>IBM’s Deep Blue victory over Garry Kasparov: <a href="https://www.ibm.com/history/deep-blue">https://www.ibm.com/history/deep-blue</a></p><p>DeepMind’s AlphaGo matches and Move 37 analysis: <a href="https://deepmind.google/technologies/alphago/">https://deepmind.google/technologies/alphago/</a></p><p>Sentient Control study on AGI UX and human-agent teaming: <a href="https://danijelnedeljkovic.com/#project-sentient-control">https://danijelnedeljkovic.com/#project-sentient-control</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b37d9cc96e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-future-of-ux-isnt-design-it-s-teaching-machines-to-be-human-4b37d9cc96e5">The Future of UX Isn’t Design — It’s Teaching Machines to Be Human</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Post-Design Thinking: When UX Strategy Becomes Parasite]]></title>
            <link>https://medium.com/design-bootcamp/post-design-thinking-when-ux-strategy-becomes-parasite-ce74c451fbd7?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/ce74c451fbd7</guid>
            <category><![CDATA[ux-strategy]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Fri, 21 Nov 2025 00:48:13 GMT</pubDate>
            <atom:updated>2025-11-21T00:48:13.627Z</atom:updated>
            <content:encoded><![CDATA[<h4>Your design process isn’t helping users anymore. It’s feeding on them.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LbDYXkxkk2EZ54l13SPf6Q.png" /></figure><p>I need to tell you something that’s going to piss off half the people reading this: Design Thinking is dead, and we’re the ones who killed it.</p><p>Not because it was bad. Because we made it too good. We took a scrappy framework for solving human problems and turned it into a seven-figure consulting circus. We slapped “user-centered” on everything from toaster apps to enterprise dashboards while systematically ignoring actual users in favor of stakeholder slide decks.</p><p>And now? Now we’ve got something worse. A new mutation. A parasite wearing the skin of strategy.</p><p><strong>THE CHURCH OF EMPATHY (AND ITS BULLSHIT)</strong></p><p>Remember when empathy maps were supposed to help us understand users? Now they’re artifacts we create to prove we did the work. We interview six people from our target demographic, extract three sanitized pain points, stick them on a Miro board with color-coded sticky notes, and call it research.</p><p>Then we build whatever we were going to build anyway.</p><p>I watched this happen at a fintech startup last year. The UX team spent three weeks on “discovery.” They talked to users. They made personas. They created journey maps so detailed you could see where users sighed with frustration. Beautiful work. Seriously.</p><p>The product shipped six months later with none of it implemented. Not because leadership was evil. Because the “strategy” became its own ecosystem. It employed designers, consumed budget, generated reports, and most importantly — it felt like progress while requiring zero actual change.</p><p>That’s what a parasite does. It survives by making the host think it’s helping.</p><p><strong>WHY IT MATTERS NOW</strong></p><p>We’re in the middle of an AI gold rush, and everyone’s trying to ship fast. The pressure is insane. Design teams are being asked to “innovate at scale” while companies cut headcount and expect you to produce interfaces for features that don’t even have names yet.</p><p>So what happens? Design Thinking becomes Design Theater.</p><p>You know what I mean. The workshop where everyone puts on their “yes, and” faces and generates 47 ideas on sticky notes, knowing damn well the CEO already decided what we’re building. The usability testing sessions scheduled after development is 90% complete. The “design sprints” that are really just regular meetings with a five-day countdown timer.</p><p>This isn’t collaboration. It’s cargo cult UX.</p><p>Most companies say they practice human-centered design, but very few actually involve users in more than one stage of development. That’s not a gap. That’s a canyon.</p><p>And here’s the thing that keeps me up at night: We’re teaching this to the next generation. Design schools are churning out graduates who can run a perfect Design Thinking workshop but have never shipped a product that solved a real problem for a real person.</p><p><strong>WHAT PEOPLE GET WRONG</strong></p><p>The mistake isn’t that we have process. Process is good. Structure helps. The mistake is believing the process IS the work.</p><p>Design Thinking was supposed to be training wheels. A framework to help teams who didn’t know how to think about users actually start thinking about users. But we never took the wheels off. We built bigger, fancier wheels.</p><p>Meanwhile, the best designers I know barely mention Design Thinking. They just… design. They talk to users constantly, not because a sprint schedule says so, but because they’re genuinely curious. They sketch solutions in Figma at 11 PM because they can’t stop thinking about the problem. They argue with PMs about features because they actually give a shit.</p><p>There’s no framework for giving a shit.</p><p>The other thing people get catastrophically wrong? They think user research is a vaccine. Do it once, get immunity, move on. But users change. Markets shift. That insight from Q2 2023? It’s expired. Your persona named “Busy Brian” who needs efficiency? He’s using ChatGPT now and his entire workflow is different.</p><p>Static strategy in a dynamic world is just expensive nostalgia.</p><p><strong>THE BETTER FRAME</strong></p><p>Here’s what I’m proposing, and it’s going to sound almost stupidly simple: Stop doing UX strategy. Start doing UX intelligence.</p><p>The difference? Strategy is a thing you make. Intelligence is a muscle you build.</p><p>Strategy says: “We completed our research phase. We have our insights. Now we execute.”</p><p>Intelligence says: “We’re always learning. Every release is a hypothesis. Every user interaction is data. We adapt in real-time.”</p><p>This isn’t about abandoning frameworks. It’s about treating them like jazz improvisation treats music theory — essential foundation, but the moment you’re just reading sheet music, you’re dead.</p><p>UX intelligence means:</p><p>You ship small and watch what happens. You have user conversations on Slack, not just in scheduled research sessions. You look at actual behavior data, not just what people say they want. You change direction mid-sprint when the evidence demands it. You kill features you spent months on because users proved they don’t work.</p><p>It’s uncomfortable as hell. There’s no neat five-phase diagram. You can’t timeline it in Gantt charts. Executives hate it because they want certainty and you’re giving them “it depends.”</p><p>But it’s the only thing that actually works.</p><p><strong>PROOF &amp; CASES</strong></p><p>Look at how Superhuman actually operates. Their CEO Rahul Vohra doesn’t talk about Design Thinking phases. He talks about the product/market fit engine — a continuous system of measurement and adjustment. They survey users constantly. They have a metric (percentage of users who’d be “very disappointed” without the product) and they move heaven and earth to increase it. <a href="https://blog.superhuman.com/how-superhuman-built-an-engine-to-find-product-market-fit/#:~:text=Users%20became%20noticeably%20more%20vocal,know%20that%20you&#39;ll%20succeed.">Read more here (if you want) →</a></p><p>That’s not strategy.</p><p>That’s metabolism.</p><p>Or check out Linear, the project management tool that’s eating Jira’s lunch. Their design philosophy? “Obsess over details and move fast.” No empathy map workshops. No persona discovery phases. Just relentless attention to how their product feels in actual use, and the willingness to ship updates weekly based on what they learn. <a href="https://linear.app/method">Read more →</a></p><p>Stripe’s API documentation is another example. They didn’t design-think their way to having the best developer experience in payments. They just… never stopped improving it. Every complaint is a signal. Every integration is a learning opportunity. They built intelligence loops, not strategy documents. <a href="https://stripe.com/blog/payment-api-design">Read more →</a></p><p>Here’s the pattern: Companies that are winning at UX in 2025 treat design as a living system, not a project phase. They embed learning into operations.</p><p>Their designers are in customer support channels, in analytics dashboards, in sales calls. The insight doesn’t flow through official research reports — it flows through people who are genuinely plugged in.</p><p><strong>HOW TO APPLY</strong></p><p>If you’re ready to move from parasite to partner, here’s where to start:</p><p>Kill one ceremony this month. Pick your least useful recurring UX ritual — the workshop that produces nothing, the review meeting that’s really just show-and-tell — and delete it. Use that time to talk to actual users instead.</p><p>Build a signal system. Set up a shared Slack channel where anyone can drop user feedback, screenshots of bugs, or interesting behavioral data. Not for formal processing. Just for collective awareness. Make it normal for the whole team to swim in user reality.</p><p>Create a “we were wrong” wall. Seriously. Track every assumption that got disproven. Every feature that flopped. Every hypothesis that failed. Celebrate it publicly. The teams that learn fastest are the ones that acknowledge failure fastest.</p><p>Practice real-time research. Next time you’re in a design review debating how users will respond, stop. Message three users right then. Ask them. Wait for replies. Make the decision based on what they say, not what your instinct says.</p><p>Measure what matters, ignore the theater. Stop tracking “empathy sessions completed” or “personas created.” Start tracking: How often do we talk to users? How fast do we respond to their feedback? How many times did user input change our direction this quarter?</p><p>The shift is simple: Make learning operational instead of episodic.</p><p><strong>EDGE CASES</strong></p><p>Now, I can already hear the objections. “We’re in enterprise! We can’t just ship fast and iterate!” Okay, fine. You’ve got compliance, procurement cycles, annual contracts. I get it.</p><p>But you can still build intelligence. You can still have ongoing conversations with users. You can still track signals. The constraint isn’t your industry — it’s your willingness to operate in uncertainty.</p><p>And yes, some projects genuinely need upfront strategy. If you’re designing medical devices or aircraft interfaces, you can’t just “move fast and break things.” Cool. But even there, intelligence beats static planning. The difference between a one-time research phase and continuous expert input is the difference between guessing and knowing.</p><p>The other edge case: tiny teams. “I’m a solo designer at a startup. I don’t have time for continuous research!” I hear you. But here’s the thing — you’re already drowning in user data. Support tickets, feature requests, churn analytics, onboarding drop-offs. Intelligence isn’t about doing more. It’s about being present with what’s already there.</p><p><strong>PUT IT TO WORK</strong></p><p>Here’s your experiment for the next two weeks:</p><p>Every morning, before you open Figma or touch a mockup, spend 15 minutes with users. Read support tickets. Watch session recordings. Check analytics. Join a sales call. Message someone who churned.</p><p>Don’t do anything with it yet. Just observe. Let the reality of how people actually use your product (or don’t) seep into your consciousness.</p><p>Then notice what changes in your design decisions. Notice what you stop caring about. Notice what suddenly seems urgent.</p><p>That’s the difference between strategy (a plan you made) and intelligence (a muscle you’re building).</p><p><strong>THE PARASITE DIES WHEN YOU STOP FEEDING IT</strong></p><p>The uncomfortable truth is this: Most UX strategy survives because it makes stakeholders feel good, not because it helps users. It’s elaborate theater that justifies headcount, proves we’re “doing design,” and generates artifacts for case studies.</p><p>But users don’t experience your empathy maps. They experience your product.</p><p>And products built by teams who are genuinely, obsessively, almost annoyingly connected to user reality? Those are the ones that win. Not because they followed the right process. Because they never stopped learning.</p><p>Design Thinking promised to make us user-centered. But somewhere along the way, we made it center itself. We created a system that consumes resources while producing the illusion of insight.</p><p>The antidote isn’t another framework. It’s humility. It’s curiosity. It’s treating every user interaction as a teacher and every assumption as temporary.</p><p>Your strategy document isn’t helping anyone. But your willingness to admit you might be wrong? That could change everything.</p><p><strong><em>So here’s my question for you: What would you do differently tomorrow if you admitted that everything you think you know about your users is probably six months out of date?</em></strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ce74c451fbd7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/post-design-thinking-when-ux-strategy-becomes-parasite-ce74c451fbd7">Post-Design Thinking: When UX Strategy Becomes Parasite</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why Apple’s Next Big Bet Should Be Formula 1 — and How UX Could Change Sports Forever]]></title>
            <link>https://medium.com/design-bootcamp/why-apples-next-big-bet-should-be-formula-1-and-how-ux-could-change-sports-forever-c7797eefc4ac?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/c7797eefc4ac</guid>
            <category><![CDATA[apple]]></category>
            <category><![CDATA[formula-1]]></category>
            <category><![CDATA[streaming]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[sports-technology]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Wed, 12 Nov 2025 08:02:09 GMT</pubDate>
            <atom:updated>2025-11-12T23:11:02.348Z</atom:updated>
            <content:encoded><![CDATA[<h3>Why Apple’s Next Big Bet Should Be Formula 1 — and How UX Could Change Sports Forever</h3><h4>While everyone’s patting themselves on the back over MLS streaming numbers, the real opportunity is sitting in a paddock waiting for someone who actually understands product design.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LVcsmXOWCCmq1BgLEhThzA.jpeg" /></figure><p><strong>THE MOST EXPENSIVE SHOW NOBODY KNOWS HOW TO WATCH</strong></p><p>Formula 1 is having a moment. Drive to Survive happened. Americans suddenly care. The Miami Grand Prix sells out in minutes. Yet here’s the thing nobody wants to admit: actually watching F1 is a user experience nightmare that makes cable television look elegant.</p><p>You’ve got Sky Sports commentary in the UK. ESPN in the US but only sometimes. F1 TV Pro that works great until it doesn’t. Timing screens on separate apps. Team radios you have to hunt for. Data visualizations that assume you’ve got an engineering degree. Twenty drivers, ten teams, and if you blink during the formation lap you’ve already lost the plot on who’s fighting whom for which position.</p><p>The sport is exploding in popularity despite having the streaming UX of a 2003 RealPlayer feed held together with duct tape and prayer.</p><p>Apple spent heavily on MLS and it barely dented the cultural radar. Meanwhile, F1 is one of the most-watched global sports, has the youngest audience growth of any major racing series, and is desperate for a streaming partner who understands that good content trapped in awful UX is just expensive static.</p><p>This isn’t a hot take. This is Apple leaving money on the Monaco harbor because they’re too busy trying to make baseball “cool.”</p><p><strong>WHY THIS IS APPLE’S FIGHT TO LOSE</strong></p><p>Let’s be honest about what Apple does well: they make complicated technology feel inevitable. The iPhone wasn’t the first smartphone. AirPods weren’t the first wireless earbuds. Apple Watch wasn’t the first fitness tracker. But they were the first versions that made you forget you were using technology.</p><p>F1 is a sport built on technology that most fans don’t understand. DRS zones. Tire compounds. Energy recovery systems. Underfloor aerodynamics. The average fan knows there are “fast cars” and “strategy things” but couldn’t explain why Verstappen pitted on lap 34 instead of lap 36.</p><p>Every other platform dumps raw data and calls it “features.” Liberty Media acts like overwhelming viewers with information is engagement.</p><p>Apple could do the opposite. They could make F1, long illegible to non-engineers, finally make sense to normal viewers who just want to watch fast cars and understand why they’re supposed to be excited.</p><p>That’s the play. Not just streaming the race. Redesigning how people experience the sport entirely.</p><p><strong>WHAT EVERY OTHER PLATFORM IS GETTING CATASTROPHICALLY WRONG</strong></p><p>F1 TV Pro is the current “official” streaming solution. It’s functional the way a Soviet washing machine is functional. Sure, it technically works. But the experience is so deliberately hostile that you wonder if the UX team was specifically trying to punish casual fans.</p><p>You can’t watch multiple camera angles cleanly on one screen without opening eight browser tabs. The timing tower updates lag behind the live broadcast by three to four seconds, which is an eternity when overtakes happen. Team radio is buried in submenus like they’re ashamed of it, despite it being one of the most entertaining parts of the sport. The app crashes during the most critical moments with the reliability of a Haas pit stop.</p><p>ESPN’s coverage is even worse in a different way. They show the world feed but with American commercial breaks inserted at random. You literally miss on-track action because some executive decided a Cialis ad was more important than lap 47. The commentary is good when you can hear it, but the UI is just standard cable television ported to streaming. No customization. No alternate angles. Take what you get or leave.</p><p>Sky Sports does it better, but only if you’re in the UK and willing to pay £40 a month for a package that includes seventeen football channels you’ll never watch. Their coverage is legitimately excellent. Their distribution model is actively user-hostile.</p><p>Here’s the pattern: every platform treats F1 like a broadcast product when it should be treated like an interface problem. They’re thinking television. Apple thinks systems.</p><p><strong>THE BRUTAL NEW LAW OF SPORTS STREAMING VALUE</strong></p><p>Here’s what nobody in sports media wants to hear: <em>Content is no longer the differentiator. Every platform can acquire rights. The differentiator is whether you make people feel stupid or smart while watching.</em></p><p>They use inside-baseball terminology. Reference things that happened three seasons ago. Expect you to know why everyone’s mad at the FIA this week.</p><p>This works for NFL diehards who’ve been watching for thirty years. It fails catastrophically for F1, which is actively trying to grow beyond its hardcore European base into markets where people barely know what DRS means.</p><p>Apple’s superpower isn’t content acquisition. It’s taking complex systems and making them feel intuitive without dumbing them down. Apply that philosophy to F1 and you get something nobody’s built yet: a sports viewing experience that makes you smarter about what you’re watching without making you work for it.</p><p><strong>PROOF THAT F1 UX IS ACTIVELY BROKEN</strong></p><p>As someone who’s juggled three apps and a VPN just to watch a single race without missing crucial moments, I can tell you this pain is personal and universal.</p><p>Last month I watched the Singapore Grand Prix with three friends. Two were casual Drive to Survive fans; one had never seen a race.</p><p>By lap 15, the newcomer asked: “Why are they all driving slowly behind each other?” Valid question. There was a safety car. But the broadcast never explained it. The graphics just showed “SAFETY CAR” and assumed everyone knew that meant: neutralized racing, field bunches up, teams make strategic pit decisions, restart will be chaos.</p><p>By lap 30, one casual fan asked: “Why is everyone talking about Plan B?” Because teams were switching tire strategies. But unless you already knew that C2 compounds versus C3 compounds have different degradation curves and that “Plan B” was code for “we’re gambling on a one-stop,” you just heard a bunch of acronyms.</p><p>By lap 50, we’d opened four different browser tabs to understand: who was fighting whom, what tire each driver was on, how far behind each position gap was, and what the hell a “VSC” meant and why it mattered for pit strategy.</p><p>The race itself was fantastic. The viewing experience was like trying to watch Inception without subtitles while three different directors’ commentaries played over each other.</p><p>Meanwhile, the F1 subreddit lit up with the same questions from hundreds of confused viewers. The sport is growing faster than the viewing experience can onboard new fans. And platforms keep adding more data instead of better context.</p><p><strong>HOW APPLE COULD ACTUALLY WIN THIS</strong></p><p>Here’s what an Apple F1 experience could look like if they actually gave a shit about UX instead of just acquiring rights and slapping their logo on existing infrastructure.</p><p><strong>Adaptive Complexity.</strong> When you first open the app, it asks: “Have you watched F1 before?” Three experience levels: Newcomer, Casual, Expert. Each one shows different information layers. Newcomers get plain-language explainers in real-time. “Safety car deployed. This means all cars slow down while track marshals clear debris. Teams often pit now because they lose less time.” Experts get raw telemetry and sector times. Everyone gets what they need without the app assuming everyone’s an engineer.</p><p><strong>Contextual Intelligence.</strong> You’re watching lap 34 and someone pits. A small notification: “This is unusual. Most drivers pit between laps 38–42. Tap to see why McLaren is gambling early.” You tap. Get a 15-second explainer with graphics showing tire degradation curves and track position scenarios. You don’t have to seek information. It comes to you when it matters.</p><p><strong>Multi-View That Actually Works.</strong> Picture-in-picture done right. Main feed in the center. Choose any combination: live timing tower, specific driver onboards, team radio, track map, or commentary toggle between world feed and team-specific analysis. All synchronized. All beautiful. All responding to what’s happening on track. Battle for P3 heating up? The app suggests switching to those onboards.</p><p><strong>Social Layering Without Being Obnoxious.</strong> Your friends who watch F1 can sync up. See what they’re focused on. Live reactions without leaving the race. Post-race highlights auto-generated based on what moments you rewound or what drivers you follow. Share moments with clean UI that doesn’t feel like TikTok invaded your racing.</p><p><strong>Race Replay Intelligence.</strong> You missed the race because you were sleeping through Sunday morning? The app doesn’t just give you a spoiler-free replay option. It gives you an adaptive highlight experience: “Full race (2hr 14min), Strategic moments only (47min), or Battles + overtakes (28min).” You pick based on how much time you have. All commentary edited to flow naturally for whichever version you choose.</p><p>None of this is science fiction. Apple has the design talent, the engineering capability, and the infrastructure. They’ve done harder things in Apple TV+. They just haven’t applied it to sports beyond surface-level streaming.</p><p><strong>THE PARTS THAT MAKE THIS COMPLICATED</strong></p><p>Look, I’m not naive about the business challenges here.</p><p>F1’s current streaming rights are fractured across multiple deals in different territories through 2029. Liberty Media isn’t going to rip up existing contracts just because Apple shows up with Figma mockups and a blank check. Any partnership would need to either wait for rights to expire, buy out existing deals, or work within existing distribution frameworks — none of which are Apple’s preferred method.</p><p>There’s also the FIA and team politics. F1 isn’t like MLS where the league controls everything. Every team has opinions. Every sponsor has demands. Every broadcast territory has different regulations about what data can be shown, how betting information gets integrated, and which commentary teams get priority. Apple doesn’t play well with committee design decisions.</p><p>And then there’s the question of whether Apple even cares about building the best sports UX or just wants prestige content to upsell services. Their MLS coverage hasn’t exactly revolutionized soccer broadcasting. It’s fine. Professional. But not radically different from what ESPN could’ve done. If Apple treats F1 the same way — acquire rights, stream competently, call it a day — then none of this matters.</p><p>But here’s the thing: MLS was never going to push Apple’s UX innovation. It’s a growing but still niche sport in the US without the global complexity or data depth to showcase what thoughtful interface design could do for sports. F1 is different. It’s a perfect sandbox for rethinking sports broadcasting entirely because the current experience is so obviously broken.</p><p><strong>PUT IT TO THE TEST</strong></p><p>Try watching an F1 race this weekend with someone who’s never seen the sport before. Don’t explain anything. Just let them experience it through the current streaming options.</p><p>Count how many times they ask a clarifying question that the broadcast should’ve answered. Count how many times you have to open secondary apps or tabs to show them information that should’ve been integrated. Count how many times they seem confused about why everyone’s excited about something.</p><p>If the number is above five, you’ve just experienced why F1’s growth ceiling isn’t the sport itself but the UX nightmare surrounding it. And why Apple could multiply the value of streaming rights many times over just by making it not terrible to watch.</p><p><strong>THE UNCOMFORTABLE TRUTH SPORTS LEAGUES REFUSE TO HEAR</strong></p><p>Sports media is still operating like it’s 1997. Acquire exclusive content. Force people through your pipeline. Charge as much as the market will bear. Add features by piling on more data and hoping someone finds it useful.</p><p>Meanwhile, every other digital product category learned this lesson a decade ago: complexity without clarity isn’t value. It’s friction. And friction kills growth.</p><p>F1 has incredible content. The racing is genuinely exciting. The personalities are compelling. The technology is fascinating. But all of that is trapped behind an interface designed by people who think “more information” equals “better experience.”</p><p>Apple knows better. They’ve built an entire company on the principle that the best technology disappears into intuitive experience. They just haven’t bothered applying it to sports because they’re too busy chasing the wrong opportunities.</p><p>MLS was a safe bet. Small audience. Low expectations. Good PR about growing soccer in America. But low ceiling for actually showcasing what Apple could do with sports broadcasting.</p><p>F1 is the opposite. Massive global audience. Sky-high expectations. Insanely complicated sport that desperately needs someone to make it accessible without dumbing it down. And a user experience so broken that literally any improvement would feel revolutionary.</p><p>This is Apple’s lane. They’re just not driving in it yet.</p><p><strong>THE PITCH NOBODY AT APPLE SEEMS TO BE MAKING</strong></p><p>Here’s what someone should be saying in a Cupertino boardroom right now:</p><p>“We didn’t get into streaming to be another Netflix. We got in to show how Apple designs experiences. MLS doesn’t showcase that. It’s fine, but it’s not differentiated. F1 is our chance to prove that interface design can be as important as content acquisition. We can take the most complex sport in the world and make it the easiest to understand. We can take a viewing experience that’s actively hostile to new fans and make it the benchmark for how sports should be consumed. And we can do it in a way that makes fans, both casual and hardcore, say ‘I can’t go back to watching F1 any other way.’ That’s an Apple product. That’s what we’re supposed to be good at.”</p><p>But instead, they’re probably in meetings about whether they can afford Premier League rights or if NASCAR would move the needle with American audiences. Safe bets. Boring plays. Nothing that requires them to actually rethink what sports broadcasting could be.</p><p>F1 is sitting there. Growing. Global. Desperate for a streaming partner who understands that good UX isn’t a feature — it’s the entire value proposition. And Apple’s too busy playing checkers to notice the chess game in front of them.</p><p><em>What’s the point of being the best design company in the world if you refuse to redesign how the world actually watches?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c7797eefc4ac" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/why-apples-next-big-bet-should-be-formula-1-and-how-ux-could-change-sports-forever-c7797eefc4ac">Why Apple’s Next Big Bet Should Be Formula 1 — and How UX Could Change Sports Forever</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why AI Is Making Mediocre Designers Look Brilliant (And Why That’s Actually Terrifying)]]></title>
            <link>https://medium.com/design-bootcamp/why-ai-is-making-mediocre-designers-look-brilliant-and-why-thats-actually-terrifying-29af61d63072?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/29af61d63072</guid>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design-tools]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Wed, 05 Nov 2025 09:02:07 GMT</pubDate>
            <atom:updated>2025-11-10T11:23:19.144Z</atom:updated>
            <content:encoded><![CDATA[<h4>The emperor has new AI-generated clothes, and nobody wants to admit they’re generic as hell.</h4><figure><img alt="A person wearing VR goggles and a metallic silver jacket stands confidently with hands on hips in front of a mirror, facing a small crowd in the background. The lighting is dramatic, creating a surreal, futuristic atmosphere that suggests tech-driven confidence and illusion." src="https://cdn-images-1.medium.com/max/1024/1*moClPff_gO54xfEDtiDqVQ.png" /><figcaption>When the illusion looks good enough, nobody asks what it’s made of.</figcaption></figure><p><strong>THE GREAT DESIGN SWINDLE OF 2025</strong></p><p>I watched a junior designer present a rebrand to a client last week. Gorgeous color palette. Perfect hierarchy. Typography that made me want to weep. The client ate it up. Signed off immediately. Budget approved.</p><p>Here’s what the client didn’t know: that entire presentation took forty-seven minutes to create. Not forty-seven hours. Not forty-seven days of iteration and soul-searching and arguing with stakeholders about whether teal is “too millennial.” Forty-seven minutes of prompting ChatGPT and Midjourney while this designer scrolled Instagram on their phone.</p><p>The kicker? Five years ago, this same designer couldn’t kern a headline to save their life. Their portfolios were full of drop shadows and Comic Sans tragedies. Now they’re billing $150 an hour and getting written up in design blogs as an “emerging talent.”</p><p>Welcome to the age where AI doesn’t just level the playing field — it catapults mediocrity straight into brilliance, and we’re all pretending not to notice.</p><p><strong>WHY THIS MATTERS MORE THAN YOUR WOUNDED PRIDE</strong></p><p>Before you think this is just another bitter senior designer complaining that “kids these days have it too easy,” let me be clear: I’m not mad that tools got better. I’m mad that we’re confusing tool competency with design thinking, and that confusion is about to cost us something we can’t get back.</p><p>The truth is, AI has compressed what used to take years of grinding — color theory, composition, understanding visual rhythm — into a few well-crafted prompts. And on the surface, that seems democratizing as hell. More people can create beautiful things. Accessibility wins. Everyone goes home happy.</p><p>Except here’s the problem nobody wants to say out loud: most of these “designers” have no idea why their AI-generated work is good. They can’t explain the decisions. They can’t iterate intelligently when the client says “make it pop” or “give it more energy.” They just re-prompt and hope the algorithm spits out something better.</p><p>This isn’t design. This is visual slot machine pulling. And the entire industry is starting to operate on luck instead of literacy.</p><p><strong>WHAT EVERYONE’S GETTING CATASTROPHICALLY WRONG</strong></p><p>The narrative right now goes like this: “AI is just another tool, like Photoshop was in the ’90s. People freaked out then too. Good designers will adapt and thrive.”</p><p>Bullshit.</p><p>Photoshop didn’t make your creative decisions for you. It didn’t choose your color palette based on what performed well in A/B tests across ten thousand landing pages. It didn’t auto-generate three layout variations and pick the one most likely to convert based on user engagement data from people you’ve never met.</p><p>Photoshop was a pencil with infinite erasers. AI is a designer who works for free, never sleeps, and has studied every trend from the last decade. The skill being tested isn’t your ability to design anymore — it’s your ability to prompt, curate, and bullshit confidently about choices you didn’t actually make.</p><p>And here’s where it gets darker: clients can’t tell the difference. Because the output is genuinely good. Professional. Polished. It checks every box on their aesthetic wishlist. Why would they care that the person they hired is basically a well-paid art director for a robot?</p><p>The market is rewarding surface-level competency over deep craft. And mediocre designers — the ones who never bothered to learn why white space matters or how to build a cohesive visual system — are riding this wave straight to the bank while experienced designers watch in stunned silence.</p><p><strong>THE BRUTAL NEW LAW OF CREATIVE VALUE</strong></p><p>Here’s the law nobody’s written yet but everyone’s starting to feel: <em>In the age of AI, your value isn’t in what you can produce — it’s in what you can judge and defend.</em></p><p>Let me break this down with a scenario. You’re in a pitch meeting. The client hates your concept. They want something “more premium.”</p><p>A mediocre designer with AI goes back to the prompt, types “luxury aesthetic, high-end, premium feel,” and generates fifteen new options. They present the one that looks expensive. Client happy. Invoice sent.</p><p>A real designer asks: “What does premium mean to you? Are we talking old-money understated or new-money maximalist? What are your customers’ actual aspirations?” They design based on strategy, not keywords. When challenged, they can defend every decision with reasoning rooted in psychology, culture, and brand positioning.</p><p>One of these people is replaceable. One is not.</p><p>The terrifying part? Right now, the market can’t tell them apart. Because the output looks the same. The presentations sound the same. The portfolios are both gorgeous. The only difference shows up six months later when the mediocre designer’s brand has no coherence across touchpoints, no flexibility for growth, and no soul anyone can identify.</p><p><strong>PROOF FROM THE TRENCHES</strong></p><p>I’ve been tracking this shift, and the patterns are brutal.</p><p>A startup hired a “senior brand designer” at $120K to build their entire visual identity. Every asset was AI-generated. Looked stunning. Six months later when they needed to expand into new product categories, the designer couldn’t explain the brand architecture. They hired a consultant for another $50K to reverse-engineer a system that should have existed from day one. The original designer? Still lists it on LinkedIn as a success story.</p><p>I watched a product team celebrate their new AI-designed landing page that broke their own accessibility standards. Color contrast failed WCAG guidelines. Navigation patterns confused screen readers. But hey — it looked premium, got 600 likes on Twitter, and the CEO loved it. Guess which standards got quietly updated?</p><p>A design agency started split-testing proposals: senior team versus AI-enhanced juniors. The AI concepts won 73% of the time. Not because they were strategically better — the agency admitted they weren’t — but because they were immediately impressive. Clients picked pretty over purposeful every single time.</p><p>The pattern is clear: we’re in a gold rush where everyone’s getting rich on fool’s gold, and by the time people realize it’s worthless, the mediocre designers will have already moved on to the next grift.</p><p><strong>HOW TO ACTUALLY NAVIGATE THIS NIGHTMARE</strong></p><p>If you’re a real designer watching this unfold, here’s the uncomfortable truth: complaining won’t save you. Neither will gatekeeping or screaming about “real craft” on Twitter. The market has spoken, and right now it’s speaking in AI-generated mockups.</p><p>Your move isn’t to compete on output. You’ll lose. AI is faster, cheaper, and produces more options than you ever will.</p><p>Your move is to compete on the layer AI can’t touch yet: judgment, strategy, and the ability to connect visual decisions to business outcomes.</p><p>Here’s what that actually looks like:</p><p><strong>Stop selling design. Start selling translation.</strong> Your client doesn’t need a logo. They need someone who can look at their messy three-year roadmap and translate it into a visual system that can grow with them. AI can’t do that. Prompt engineers can’t do that. You can.</p><p><strong>Make your thinking visible.</strong> Document your decision-making process. Show clients the ten options you rejected and why. Walk them through the strategic reasoning. Make them understand that good design isn’t magic — it’s accumulated judgment they’re paying for.</p><p><strong>Build moats in complexity.</strong> AI is great at single-deliverable work. It’s terrible at systems thinking. Get really good at multi-touchpoint brand ecosystems, design systems that need to scale, and work that requires deep understanding of edge cases and constraints.</p><p><strong>Have the uncomfortable conversation.</strong> When a client says “the AI version looks better,” here’s your script: “That’s exactly the point — it’s optimized for immediate visual delight. My job is to make it work in six months when your product pivots, when you need to localize for three new markets, and when your intern needs to create assets without breaking the system. AI makes things pretty. I make things durable.”</p><p><strong>Call out the fakes.</strong> When you’re competing against AI-enhanced mediocrity, don’t be subtle. In your proposals, in your process, in your presentations — make it crystal clear that you’re not just making things pretty. You’re solving actual problems with visual communication strategy.</p><p><strong>THE PARTS EVERYONE IGNORES</strong></p><p>Look, I’m not saying AI is evil or that designers using it are frauds. Some are using it brilliantly as a genuine enhancement to already-strong skills. Some are exploring new creative territories that weren’t possible before.</p><p>But let’s not pretend the majority falls into that category.</p><p>Most mediocre designers using AI right now are like people using a calculator without understanding math. They get correct answers, but they can’t spot when the calculator glitches. They can’t do mental estimates to reality-check the output. They’re functionally dependent on a tool they don’t understand, creating work they can’t defend.</p><p>And the clients enabling this? They’re not stupid. They’re optimizing for short-term speed and cost, which is perfectly rational. But they’re going to wake up in two years with brands that all look identical, designed by algorithms trained on the same datasets, following the same trends, creating the same visual sameness.</p><p>There’s also this: some design work genuinely doesn’t need deep strategy. A restaurant needs a menu that’s legible and on-brand. A startup needs pitch deck templates. An e-commerce site needs product photography that’s clean and consistent. For these projects, AI-enhanced mediocrity is probably fine. Maybe even optimal.</p><p>The line gets blurry. And that’s intentional.</p><p><strong>YOUR IMMEDIATE EXPERIMENT</strong></p><p>Here’s what you do this week: pick three pieces in your portfolio that you’re proudest of. Now prompt an AI tool to create something similar. Be honest about how good the output is.</p><p>If the AI gets close? You need to level up your strategic differentiation immediately. Your craft alone isn’t enough anymore.</p><p>If the AI can’t touch it? Figure out why. What made your work impossible to replicate with prompts? Double down on that. Make it your entire positioning.</p><p>And if you’re a mediocre designer coasting on AI? At least have the self-awareness to know what you are. You’re not a designer. You’re a curator with good taste. Which is fine — that’s actually valuable. Just don’t pretend you’re doing something you’re not, and maybe invest a few hours in learning why your AI is making the choices it’s making.</p><p>Because right now, you look brilliant. But brilliant has an expiration date, and yours is shorter than you think.</p><p><strong>THE BITTER TRUTH NOBODY ASKED FOR</strong></p><p>The design industry is going through what writing went through, what music production went through, what every creative field eventually goes through: the tools got good enough that talent became optional for basic execution.</p><p>And we’re all complicit. Agencies hire faster and cheaper. Clients reward speed over substance. Junior designers take shortcuts because the industry doesn’t punish them for it. Senior designers stay quiet because calling it out feels like sour grapes.</p><p>Meanwhile, the gap between “designers who understand their craft” and “people who are good at prompting” is collapsing in the market’s eyes. Both get paid. Both get hired. Both build portfolios that look impressive.</p><p>The only difference is what happens five years from now when AI gets even better, and suddenly being a good prompt engineer isn’t special anymore either. The people who built real skills will adapt. The people who outsourced their thinking to algorithms will be right back where they started: mediocre, but without the AI safety net to hide behind.</p><p>So yeah, AI is making mediocre designers look brilliant.</p><p>But brilliance without foundation is just convincing performance art. And the show’s almost over.</p><p><em>What are you actually good at when the AI stops working?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=29af61d63072" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/why-ai-is-making-mediocre-designers-look-brilliant-and-why-thats-actually-terrifying-29af61d63072">Why AI Is Making Mediocre Designers Look Brilliant (And Why That’s Actually Terrifying)</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Can Generate Anything. Only Humans Can Decide What Matters]]></title>
            <link>https://medium.com/design-bootcamp/ai-can-generate-anything-only-humans-can-decide-what-matters-0b6b68ccbe8e?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/0b6b68ccbe8e</guid>
            <category><![CDATA[ai-ethics]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[human-centered-design]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[future-of-work]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Wed, 29 Oct 2025 09:02:10 GMT</pubDate>
            <atom:updated>2025-10-29T11:32:31.569Z</atom:updated>
            <content:encoded><![CDATA[<h4>A manifesto for the next creative revolution — the rise of the Human–AI Decider.</h4><figure><img alt="A human hand gently reaching toward a robotic hand, symbolizing the connection between human judgment and artificial intelligence in a minimalist, neutral setting." src="https://cdn-images-1.medium.com/max/1024/1*84HGFNKn7ftqPzmO69qJ6g.jpeg" /><figcaption><em>The machines can generate. We must decide what deserves to exist.</em></figcaption></figure><h3>The Overdose</h3><p>The internet used to be a reflection of humanity. Now it’s an echo of algorithms.</p><p>Our feeds, our inboxes, our search results — all overflowing with words, images, songs, and ideas no one asked for. Every second, machines produce more content than humans could absorb in a lifetime. AI writes love letters, paints masterpieces, and codes software faster than we can decide what any of it means.</p><p><em>And this is just the beginning.</em> Within a few short years, every product, service, and story will have an AI counterpart — faster, cheaper, endlessly generated. The noise will multiply, the line between real and synthetic will blur, and truth itself will become negotiable.</p><p>We call this progress, but it feels more like an overdose. The problem isn’t creation — it’s curation. We’ve built a civilization that can generate everything yet can’t tell the difference between signal and noise.</p><p><em>The result: a world addicted to output, starving for meaning.</em></p><p>What humanity needs now isn’t another AI model, tool, or upgrade. It needs discernment. Context. Judgment. A human layer that decides what deserves to exist — and what doesn’t.</p><p>That someone is what we call <strong>the Human–AI Decider.</strong></p><h3>The Age of Endless Creation</h3><p>AI can now design, write, compose, code, illustrate, market, and even flirt — all in seconds. Every creative act that once demanded time, skill, or struggle can now be summoned by a prompt. Logos are born faster than ideas. Articles are written before the author has a thought. Songs sound like Drake, look like Da Vinci — and feel like nothing.</p><p>We’ve entered an age where quantity is mistaken for progress and originality has become irrelevant. Companies chase scale over soul, flooding the world with perfect but pointless output. It’s no longer about <em>what</em> we create, but <em>how much</em> we can produce before someone scrolls past.</p><p>We tell ourselves this is innovation — that democratizing creativity empowers everyone. But when everyone can create instantly, no one stops to ask whether what’s created <em>should</em> exist. The creative process, once rooted in intention, reflection, and restraint, has turned into a slot machine of ideas. Pull the lever, get another design. Another campaign. Another sound.</p><p>Culturally, we’re watching the soul drain out of creation. AI Drake songs. AI logos. AI blogs. All technically flawless, all emotionally hollow. They impress us — briefly — but they move no one.</p><p><strong>AI gave us infinity. But infinity without judgment is meaningless.</strong><br>Creation without curation, expression without evaluation, and intelligence without wisdom don’t make us more human — they make us irrelevant.</p><h3>The Human Gap — Where Intelligence Stops</h3><p>AI can simulate intelligence, but not wisdom. It can pattern-match emotion, but it can’t <em>feel</em> it. It can optimize for clicks, but not connection. Machines know <em>how</em> to do things — they just don’t know <em>why.</em></p><p>We see this gap everywhere. An AI-generated ad campaign goes viral for its eerie perfection — every word, every image tuned for engagement — yet it feels hollow, almost manipulative. A UX flow designed by a generative model guides users effortlessly from A to B, but leaves them cold; no warmth, no sense of being understood. Even AI-written condolence letters can sound flawless — and still feel like a slap in the face.</p><p><em>This is where intelligence stops.</em> Pattern recognition can’t replace perspective. Optimization can’t replace empathy. We can teach a machine to mimic every form of human expression, but it still has no idea <em>why</em> we bother to express anything at all.</p><p>That’s where humans come in — not as the artists AI replaces, but as the <strong>deciders</strong> who guide what AI creates. Our role isn’t to compete with the algorithm’s speed or precision. It’s to provide the one thing it will never have: <em>judgment.</em></p><p>Because in a world where intelligence is infinite but understanding is rare, <em>our greatest value isn’t what we make — it’s what we choose.</em></p><h3>The Role — The Human–AI Decider</h3><p>A <strong>Human–AI Decider</strong> is the judgment layer humanity forgot to design.</p><p>In a world where machines generate endlessly, the Decider becomes the filter — guiding AI with empathy, taste, and ethical judgment to ensure that what’s created still serves human values. Their work isn’t to outsmart algorithms, but to humanize them.</p><p>Where AI accelerates, the Decider slows down — to think, to feel, to question. They stand at the intersection of data and meaning, where metrics end and humanity begins.</p><h3>The H-AID Framework</h3><p><em>Four principles that separate noise from nuance:</em></p><p><strong>1. Emotional Resonance — Does it make people feel something real?</strong><br>An AI-generated film trailer might be visually perfect but emotionally flat. The Decider senses that absence — adjusts tone, rhythm, or narrative until people <em>feel</em> something, not just see it.</p><p><strong>2. Clarity — Can humans instantly understand it?</strong><br>AI can create interfaces or stories so complex they alienate users. The Decider simplifies without dumbing down, keeping comprehension at the heart of creation.</p><p><strong>3. Trust — Does it sound and look believable?</strong><br>An AI news article might be factually correct but visually manipulative, written to provoke rather than inform. The Decider filters for honesty, coherence, and integrity.</p><p><strong>4. Alignment — Do all parts tell the same story?</strong><br>AI often mixes inconsistent tones, visuals, or messages. The Decider ensures that everything — copy, design, emotion — aligns with purpose and human truth.</p><p><em>The Human–AI Decider doesn’t fight automation — they give it meaning.</em><br>They are the conscience inside the code, ensuring technology doesn’t just work, but <em>matters.</em></p><h3>The Future — From Creators to Curators of Intelligence</h3><p>The next creative revolution won’t be about <em>making</em> things — it will be about <em>choosing</em> them.</p><p>AI has turned everyone into a creator. Anyone can generate art, write copy, compose music, or design a product in seconds. But as creation becomes limitless, discernment becomes rare. The world no longer rewards those who produce endlessly — it rewards those who decide what deserves to exist.</p><p>In the near future, companies will hire fewer <em>designers</em> and more <em>deciders.</em> Fewer people to push pixels or write code — more people to ask, <em>“Should this even be made?”</em> The Human–AI Decider becomes the creative director of intelligence itself: the person who curates what machines produce, ensures it aligns with human truth, and gives technology a soul.</p><p>It’s no longer about skill with tools, but sensitivity to meaning.<br>No longer about producing more, but producing <em>wisely.</em></p><p>As AI takes over execution, humans reclaim intention.<br>The Decider becomes the editor of the infinite — shaping raw generative chaos into coherent, ethical, emotionally resonant creation.</p><p><em>We once measured creativity by output. Now, we’ll measure it by judgment.</em><br>And when that happens, the question will no longer be <em>“What can AI do?”</em> but <em>“What should we allow it to do?”</em></p><p>That’s the future of creation — from making to meaning, from creation to curation, from human designers to <strong>Human–AI Deciders.</strong></p><h3>Reclaim the Human</h3><p>Machines don’t dream. They don’t regret. They don’t care.<br><em>That’s our edge — not our weakness.</em></p><p>We built intelligence. Now we must build judgment.<br>Because the future won’t be defined by how fast we generate, but by how deeply we decide.</p><p>AI can write the words, but only we can give them meaning.<br>It can paint the picture, but only we can feel the truth in the colors.<br>It can optimize the path, but only we can choose the destination.</p><p>If we surrender that choice, we surrender what makes us human.<br>But if we reclaim it — if we dare to lead the machines we’ve created — we can shape a world where technology amplifies our empathy instead of replacing it.</p><p><em>This is our moment to become more than creators.</em><br>To become curators of meaning, architects of wisdom, and guardians of the human story.</p><p><strong>The age of the Human–AI Decider — has begun.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0b6b68ccbe8e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/ai-can-generate-anything-only-humans-can-decide-what-matters-0b6b68ccbe8e">AI Can Generate Anything. Only Humans Can Decide What Matters</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[So, We Thought ChatGPT Was for Work. Turns Out It’s for Life]]></title>
            <link>https://medium.com/design-bootcamp/so-we-thought-chatgpt-was-for-work-turns-out-its-for-life-da7b453ab2ce?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/da7b453ab2ce</guid>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Thu, 23 Oct 2025 08:02:38 GMT</pubDate>
            <atom:updated>2025-10-28T16:25:09.783Z</atom:updated>
            <content:encoded><![CDATA[<h4>Turns out most people aren’t coding or soul-searching with ChatGPT — they’re just trying to think better, write faster, and make life suck a little less.</h4><figure><img alt="A distorted human face in blue light behind red blinds, symbolizing the blurred boundary between humans and artificial intelligence." src="https://cdn-images-1.medium.com/max/1024/1*wKRPsmKeZsWkiJgz4jO3ZA.jpeg" /><figcaption>Blurry lines, bright screens — pretty much how life feels now, right?</figcaption></figure><p>You ever sit down for a beer and realize you’ve been totally wrong about something massive?<br>That’s me right now.</p><p>A few weeks ago, <strong>OpenAI, Duke, and Harvard</strong> released the largest study ever conducted on how people actually use ChatGPT. Millions of real conversations analyzed through privacy-preserving automation — showing what humans <em>really</em> do when they talk to an AI.</p><p>If you want to read the full study, it’s available <a href="https://www.nber.org/papers/w34255?utm_source=chatgpt.com">here on NBER</a>.</p><p>And the results are not just interesting — they completely flip how we, as UX designers, should think about human–AI interaction.</p><h3>We Thought ChatGPT Was For Work. Turns Out People Just Want Help With Life</h3><p>Over <strong>70%</strong> of ChatGPT use is now <em>non-work-related</em>.<br>Yep — not productivity hacks, not code debugging, not business reports.</p><p>People are asking about gym plans, recipes, travel ideas, parenting tips, or how to write a breakup text that doesn’t sound passive-aggressive.</p><p>It’s become the modern life companion — therapist, teacher, copywriter, coach, and friend — all rolled into one chat window.</p><p>And for us as designers, that’s a huge wake-up call.<br>We’ve been treating AI as a <em>productivity tool</em>, but users are treating it as a <em>personal companion</em>.</p><p>That means we’re not just designing tools anymore.<br>We’re designing <em>relationships</em>.</p><p>The same interface that writes a company report at 10 a.m. helps someone write a love letter at 10 p.m.<br>The context has changed, but the expectation hasn’t — users still want the AI to understand them.</p><p>So when we design for AI, we’re designing for <em>humans in context</em>, not <em>users at work.</em><br>Same person, different needs, same expectation of empathy.</p><h3>Most People Don’t Want To Automate — They Want To Amplify</h3><p>The study found that nearly <strong>80%</strong> of all ChatGPT messages fall into three categories:</p><ol><li><strong>Practical Guidance</strong> — tutoring, brainstorming, how-to help.</li><li><strong>Seeking Information</strong> — searching for facts, products, or advice.</li><li><strong>Writing</strong> — emails, essays, summaries, or creative text.</li></ol><p>That’s it.<br>No robots replacing jobs. No secret coders automating the world. Just humans trying to express, learn, or understand something faster.</p><p>The lesson for UX is clear: people don’t want AI to <em>replace</em> their thinking.<br>They want it to <em>expand</em> it.</p><p>They want to be guided, not commanded.<br>They want support, not automation.</p><p>That subtle difference changes everything.</p><p>Our goal as designers isn’t to make AI <em>do</em> more — it’s to make users <em>feel more capable.</em><br>A great AI product doesn’t make people feel obsolete.<br>It makes them feel empowered.</p><p>When a tool helps someone think clearer or write better, it’s not replacing them — it’s <em>amplifying them.</em></p><h3>AI Isn’t Replacing The Designer. It’s Becoming The Colleague We Can’t Shut Up</h3><p>The researchers classified every message into three “intent types”: <strong>Asking, Doing, and Expressing.</strong></p><p>Almost half of all messages were <strong>Asking</strong> — meaning people weren’t using ChatGPT to complete tasks, but to <em>think through problems.</em></p><p>That’s not what we were told AI was for.<br>We thought it was a task engine — something that executes commands.<br>But users are treating it like a <em>thinking partner.</em></p><p>That’s where UX gets interesting.<br>We’re no longer designing interfaces that “do things.”<br>We’re designing interfaces that <em>think with people.</em></p><p>That changes how we approach tone, flow, and feedback.</p><ul><li><strong>Tone</strong> needs to sound like a partner, not a machine.</li><li><strong>Timing</strong> needs to create rhythm — not just fast replies.</li><li><strong>Trust</strong> needs to be built through transparency, not perfection.</li></ul><p>If ChatGPT is now the coworker that never stops talking, UX is the social filter that makes that coworker bearable.</p><p>When users feel heard, they keep the conversation going.<br>When they don’t, they close the tab.</p><h3>The AI Crowd Is Getting Younger, More Global, And More Balanced</h3><p>Here’s something nobody saw coming: the gender gap has vanished.</p><p>In the first few months after launch, about 80% of ChatGPT users had masculine first names.<br>By mid-2025, that flipped — women now slightly outnumber men.</p><p>Nearly <strong>half of all messages</strong> come from users under 26.<br>And the fastest growth isn’t happening in Silicon Valley. It’s in <strong>low- and middle-income countries.</strong></p><p>That’s massive.</p><p>Because it means the “AI user” isn’t a tech professional anymore.<br>It’s students in Lagos. Designers in Stockholm. Teachers in São Paulo. Freelancers in Manila.</p><p>For UX, that means designing for a <em>global mindset.</em><br>Not a Western, corporate, English-speaking one.</p><p>It means considering tone, accessibility, and cultural nuance.<br>A student asking for help with an essay in India doesn’t want the same tone as a lawyer revising a contract in London.</p><p>UX now needs to scale across language, literacy, and context — and still feel personal.</p><p>That’s the next design challenge.</p><h3>Writing Is Still King — And That Matters More Than You Think</h3><p>Despite all the hype about image and code generation, <strong>writing dominates</strong>.</p><p>The study found that <strong>42% of work-related messages</strong> are about writing — emails, summaries, documents, posts, reports.<br>And here’s the twist: about two-thirds of those aren’t new content.<br>They’re <em>edits and improvements</em> to what users already wrote.</p><p>That says something fundamental: people don’t want AI to <em>create for them.</em><br>They want it to <em>refine their voice.</em></p><p>That’s a design insight.<br>The best AI writing tools shouldn’t aim to replace creativity — they should <em>enhance clarity and confidence.</em></p><p>Good design in this space isn’t about “auto-writing.”<br>It’s about collaboration — version history, tone adjustment, contextual suggestions.</p><p>When people write with AI, they want to feel like they’re in control of their voice.<br>UX’s job is to make that collaboration invisible and effortless.</p><h3>Decision Support Is The New Productivity</h3><p>The study mapped ChatGPT messages to work activities using the U.S. Department of Labor’s O*NET database.<br>Nearly <strong>60% of work-related messages</strong> fell into two categories:</p><ol><li><strong>Gathering, documenting, and interpreting information</strong></li><li><strong>Making decisions, giving advice, solving problems, and thinking creatively</strong></li></ol><p>That’s what knowledge work <em>is</em>.</p><p>So while people keep saying “AI will replace jobs,” the study suggests something else:<br>AI isn’t replacing jobs. It’s <em>restructuring how decisions are made.</em></p><p>AI becomes part of the thinking process — a second brain for planning, reflecting, and problem-solving.</p><p>And that means our job as designers shifts too.<br>We’re not designing <em>tools</em> anymore.<br>We’re designing <strong>decision environments.</strong></p><p>The way prompts are written, how feedback is displayed, how confidence is visualized — all of that influences how people make choices.</p><p>UX now shapes not just how users act, but <em>how they think.</em></p><h3>The Satisfaction Gap — And What It Says About Good UX</h3><p>Here’s something fascinating: the researchers also measured <em>interaction quality</em>.<br>They trained models to detect when users expressed satisfaction or frustration.</p><p>The result?<br>“Good” interactions are growing four times faster than “bad” ones.</p><p>And the highest satisfaction comes from Asking-type messages — when people use ChatGPT to <em>think and decide</em>, not just to generate text.</p><p>That says a lot about what users actually value.</p><p>They don’t just want speed.<br>They want resonance — a sense that the AI “gets it.”</p><p>So maybe good UX in AI isn’t about perfect accuracy.<br>Maybe it’s about emotional accuracy.</p><p>The best interfaces don’t just deliver answers.<br>They make users feel understood.</p><h3>AI Isn’t The Villain. It’s The Mirror</h3><p>Strip away the hype, and this study doesn’t reveal the rise of a superintelligent machine.<br>It reveals something beautifully human.</p><p>We use AI to organize chaos.<br>To express ourselves.<br>To make decisions we’ve been procrastinating on.<br>To learn faster when we’re tired.<br>To turn ideas into something tangible.</p><p>AI doesn’t replace creativity — it amplifies it.<br>It doesn’t destroy thought — it <em>reflects</em> it.</p><p>That’s what makes this moment so interesting for UX designers.<br>We’re no longer designing for machines that take commands.<br>We’re designing for mirrors that respond.</p><p>And those mirrors are teaching us more about human behavior than any survey ever could.</p><h3>What UX Designers Should Take Away From This</h3><p>Here’s the cheat sheet version:</p><ul><li><strong>Design for thinking, not tasks.</strong> The real value is in cognitive flow, not button clicks.</li><li><strong>Assume emotion in every interaction.</strong> Even a “work” query has a human behind it.</li><li><strong>Design tone like you design typography.</strong> Voice creates trust.</li><li><strong>Make context fluid.</strong> Users move between personal and professional worlds without noticing.</li><li><strong>Embrace imperfection.</strong> Great AI UX admits it can be wrong — and shows users how to fix it.</li></ul><p>The next great era of UX won’t be about dashboards or interfaces.<br>It’ll be about relationships — digital ones built on empathy, adaptability, and trust.</p><p>Because as this study proves, people don’t just want information.<br>They want connection.</p><h3>The Toast</h3><p>So yeah, maybe we’ve been using ChatGPT “wrong.”<br>Or maybe we’ve finally started using it <em>right.</em></p><p>It’s not the end of design. It’s a reset.<br>A chance to build technology that feels less like a tool and more like a thought partner.</p><p>AI isn’t the enemy. It’s the mirror — showing us who we are when we think out loud.</p><p>And if that’s not worth a beer, I don’t know what is.</p><p><em>(Based on “How People Use ChatGPT,” OpenAI, Duke University, and Harvard University, 2025 — </em><a href="https://www.nber.org/papers/w34255?utm_source=chatgpt.com"><em>NBER Working Paper 34255</em></a><em>)</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=da7b453ab2ce" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/so-we-thought-chatgpt-was-for-work-turns-out-its-for-life-da7b453ab2ce">So, We Thought ChatGPT Was for Work. Turns Out It’s for Life</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Field Notes from a 2025 UX Job Hunt: What Worked, What Flopped, What I’d Repeat]]></title>
            <link>https://medium.com/design-bootcamp/field-notes-from-a-2025-ux-job-hunt-what-worked-what-flopped-what-id-repeat-1ebd53249998?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ebd53249998</guid>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[career-development]]></category>
            <category><![CDATA[job-search]]></category>
            <category><![CDATA[user-experience]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Thu, 16 Oct 2025 08:02:27 GMT</pubDate>
            <atom:updated>2025-10-28T16:20:59.489Z</atom:updated>
            <content:encoded><![CDATA[<h4>Still job hunting.Still learning. Here’s what’s actually working — and what’s not.</h4><figure><img alt="A person stands alone in front of a window on a rainy evening, looking out at the blurred city lights through the glass streaked with raindrops." src="https://cdn-images-1.medium.com/max/1024/1*gQcT0ItC7hu5uTPI6PmcAg.jpeg" /><figcaption><em>Staring out the window between job rejections, wondering what “progress” even means anymore.</em></figcaption></figure><h3>The Chaos Phase</h3><p>I opened my inbox to another <em>“We’ve decided to move forward with other candidates”</em> email.<br>Third one this week.<br>At this point, my Figma file had more versions than I had hope.</p><p>I had the same morning ritual: coffee, inbox, rejection. The sting lasted less than a minute, then turned into quiet scrolling. Every post on LinkedIn looked like success porn — smiling teams, shiny new roles, “grateful to announce.” Meanwhile, I was refreshing job boards like a stock ticker, hoping something decent would appear before lunch.</p><p>The UX market in 2025 feels like trying to outswim a riptide. Too many applicants, too few roles, and every listing demanding someone who can research, design, prototype, code, and now whisper to AI.</p><p>I’d been hunting for months — juggling freelance scraps, polishing case studies, watching confidence drain with every polite rejection. The early weeks were pure chaos.</p><p>I fired applications everywhere, thinking volume was safety. Every “Apply Now” button looked harmless until I realized it was a black hole. Cold portals asked for twenty fields, then ghosted me. Even my portfolio turned against me — it sounded like a corporate brochure instead of a person who designs things that help people.</p><p>I kept a spreadsheet of every company I applied to. It looked like a graveyard — rows of silence, a few polite rejections, and one that just said <em>“position filled”</em> two hours after posting.</p><p>After a few weeks, I started to recognize rejection emails by subject line alone. I’d click just to clear them, like digital gnats. The polite tone always stung more than silence — <em>“We were impressed by your portfolio.”</em> No, you weren’t. If you were, I’d be signing papers, not refreshing Gmail. Some days I’d close the laptop and stare out the window, wondering if this was the punishment for doing work that’s supposed to be human in an industry that treats humans like data points.</p><p>I started questioning everything — my portfolio, my skills, even my worth. It’s strange how quickly confidence turns into calculation. You start rewriting every sentence to sound like what you <em>think</em> companies want, until there’s nothing left of you in the work.</p><h3>The Turning Point</h3><p>The shift came when I dropped the performance act. I rewrote one case study as a story instead of a press release. I stopped writing for recruiters and started writing for humans.</p><p>I described the mess, the doubt, and the one insight that made the whole project click. A recruiter replied saying it was the first time they’d actually felt like they knew the designer behind the pixels. That one line of feedback hit harder than any “thank you for applying.”</p><p>It reminded me that clarity beats polish every time; people want to connect with a mind, not a mask.<br>For the first time in weeks, I felt seen.</p><p>It didn’t land me a job, but it shifted something deeper. I realized I’d been chasing approval, not alignment. I’d built my portfolio like a storefront when what I really needed was a mirror. That recruiter’s note reminded me why I started designing in the first place — to make complex things clearer, not prettier. The irony is that clarity, not confidence, was what finally made me feel qualified again.</p><h3>Real Conversations Beat Portals</h3><p>I stopped hiding behind application buttons and started writing to people directly. Short, specific notes. No templates.</p><p>I’d mention a recent feature launch and ask a real question about it. Sometimes I’d add a quick thought — never selling, just starting a conversation. Those tiny moments of connection changed everything.</p><p>One message turned into a real chat. We spent fifteen minutes talking about design trade-offs, not job titles. They didn’t hire me, but they introduced me to someone else. That chain reaction made me realize how fast things move when people feel your curiosity instead of your pitch. Every connection wasn’t a transaction — it was a breadcrumb.</p><p>Then came the video. I recorded a short Loom introducing myself and why their product caught my eye. No editing, no script. Just me, a webcam, and some honest energy.</p><blockquote><strong><em>People don’t hire PDFs. They hire people.</em></strong></blockquote><p>That simple shift — showing up human — cut through the noise in a way no résumé ever did.</p><h3>From Desperation To Design Mindset</h3><p>That mix of small wins and better conversations didn’t land me a job overnight, but it shifted my focus.</p><p>At some point, I got tired of waiting to be chosen. I treated the job hunt like a design problem instead of a punishment.</p><p>That shift felt subtle at first — like loosening a knot that had been there for months. The job search stopped feeling like judgment day and started feeling like research. Every rejection gave me data about what mattered in the market and what didn’t. It turned pain into feedback loops.</p><p>I tore down a popular app’s accessibility flow, wrote what worked and what didn’t, and shared it publicly. Designers reached out, not with flattery but with curiosity. Those conversations turned into leads, collaborations, and actual friendships.</p><p>It reminded me of those early wireframes — messy, uncertain, full of wrong turns but still progress. The job hunt was just another prototype. Each version of me got a little more honest, a little more focused on solving the real user problem: my own burnout. Somewhere between the interviews and the rewrites, I stopped designing screens and started designing myself.</p><p>The tone of everything changed once I stopped asking for permission to participate. I wasn’t begging for a seat at the table — I was already working on the problem.</p><p>The thread through it all was resilience. Rejection still stung, but it stopped defining me. Each silence became feedback. Each pivot felt like a new iteration.</p><h3>If I Were Starting Again</h3><p>If I had to begin tomorrow, I’d strip it all back. Fewer applications. More honest conversations.</p><p>I’d share one story that matters instead of five that don’t. I’d keep my tone simple and my process visible. And I’d keep reminding myself:</p><blockquote><strong><em>The goal isn’t to look employable. It’s to show you can make things better.</em></strong></blockquote><p>That shift — from seeking approval to solving problems — quietly rewired the whole experience.</p><p>Some nights I still scroll through old applications to remind myself how far I’ve come. Each one feels like a snapshot of a person trying too hard to be perfect. I’m not done yet — but at least I’m honest now, and that feels like a different kind of progress.</p><p>If you’ve been in this same storm, what’s the one thing that kept you steady?</p><p>Maybe that’s all a job hunt really is — an endless design sprint on yourself, where empathy, iteration, and patience decide who stays afloat.</p><p>Still updating the portfolio. Still hoping. But at least now, it feels like progress, not noise.</p><p>Outside my window, the city keeps moving — people hurrying to jobs I still want, emails I’ll still send tomorrow. But for once, I’m not racing the algorithm. I’m building at human speed again, and that finally feels like the right pace.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ebd53249998" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/field-notes-from-a-2025-ux-job-hunt-what-worked-what-flopped-what-id-repeat-1ebd53249998">Field Notes from a 2025 UX Job Hunt: What Worked, What Flopped, What I’d Repeat</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Stop Chasing AI Hype — Build Something People Actually Need]]></title>
            <link>https://medium.com/design-bootcamp/stop-chasing-ai-hype-build-something-people-actually-need-0bbf0f8a7fed?source=rss-8e338c2a33a6------2</link>
            <guid isPermaLink="false">https://medium.com/p/0bbf0f8a7fed</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <category><![CDATA[technology]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Danijel Nedell]]></dc:creator>
            <pubDate>Wed, 08 Oct 2025 14:01:59 GMT</pubDate>
            <atom:updated>2025-10-28T19:48:16.832Z</atom:updated>
            <content:encoded><![CDATA[<h3>Stop Chasing AI Hype — Build Something People Actually Need</h3><h4><em>AI isn’t the problem. Building pointless features is. Design for value, not vanity.</em></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cga5RD83vfxhaQPbMHgmCg.jpeg" /><figcaption>Caught in the noise — a designer drowning in the pressure to “add AI” before anyone asks if people even need it.</figcaption></figure><p>The AI bandwagon’s a trainwreck. Bosses are barking for “AI-powered” features faster than you can say “algorithm,” with zero clue what <em>people</em> — not <em>users</em>, let’s get that straight — actually need. I slipped there, but if you caught my <a href="https://medium.com/@danijelnedeljkovic/the-people-first-design-toolkit-stop-designing-for-users-and-start-designing-for-humans-6bba28b5212a">People-First Design Toolkit</a>, you know “users” turns humans into cold data points, gutting the soul of design. We’re talking real people here — moms, techs, nurses — and their real struggles.</p><p>This rush to AI-ify everything? It’s panic, not progress. But for you, UX warrior, it’s your shot to deliver something so damn valuable it silences the higher-ups and transforms lives. Not just better — radically better than the half-assed bots clogging apps. If your AI solves real problems, people will call it a game-changer, and your bosses will be singing your praises. We’re digging into why this pressure’s a mess, how AI’s vague hype is your secret weapon, what makes AI UX actually work, a look at how any case study can turn this into action, and why starting with the problem — not the tech — is your only move. Build for impact, or don’t bother.</p><h3>Why The AI Frenzy’s a Mess (And Your Chance To Shine)</h3><p>Last team huddle: “AI now, or we’re toast!” It’s not vision; it’s fear. Markets flip out at every AI headline, investors demand “genAI” buzzwords, and your roadmap’s a graveyard of chatbots nobody asked for. Remember when every app needed a “.com” in 2000 or a chatbot in 2018? Most crashed because they skipped what people needed.</p><p>Shipping AI just to check a box? That’s a losing bet. It fries teams, drains budgets, leaves people pissed — like a retail bot shoving irrelevant upsells mid-rush. But this “AI-all-the-things” chaos is your opening. My toolkit called out designing for humans, not numbers; here’s your play. Steer that pressure into value — solutions that save time, cut stress, make people feel heard. Bosses want “innovation”? Give them results: Higher retention, fewer headaches, humans who stick around. I’ve seen managers flip from “more AI!” to “more impact!” when a prototype saved a nurse an hour. That’s your edge — wield it.</p><h3>AI’s Vague Hype: Your Shortcut To Value</h3><p>AI’s a buzzword buffet — everyone’s piling on, nobody knows what’s on the plate. Your lead calls it “revolutionary”; the person at the keyboard? “That glitchy mess.” This vagueness? Your superpower.</p><p>“AI” gets tossed around like confetti, branded cutting-edge. Lean into it: Skip the tech debates (LLMs? Yawn) and zero in on value. Higher-ups demand “AI features”? Ask: “What’s breaking for the human on the other end?” Suddenly, you’re not building “AI scheduling” — you’re freeing a parent from booking hell or a tech from email chaos. Mock fast in Figma, test in real-world grit — workshops, counters, not labs. Deliver where the tech fades and the win shines.</p><p>This isn’t shady; it’s savvy. In a world drowning in AI hype, you win by hiding the tech. Focus on outcomes — time reclaimed, frustration killed — and people will call it genius. I’ve seen teams waste months on “AI dashboards” nobody touched because they dodged the human pain. Make it about relief, not robots.</p><h3>Make AI UX Actually Work: Solve Problems, Don’t Create Them</h3><p>Lousy UX? AI that botches the basics, like a bot misjudging stock needs, leaving a cashier scrambling. Great UX? It anticipates needs before they’re voiced, exceeding expectations like a lifeline. AI’s a tightrope — one misstep, trust crashes faster than a glitchy app on a deadline.</p><p>Here’s how to nail it:</p><ol><li><strong>Dig Into Pain Points</strong>: Shadow people in their chaos — shops, clinics, offices. Log their groans, spot the grind. AI shines here: Automating drudgery, suggesting fixes with context.</li><li><strong>Be Transparent</strong>: Own the limits. “AI’s guessing — tweak if I’m off.” Control builds trust; mystery kills it. A tool explaining its call keeps folks on board.</li><li><strong>Seamless, Not Showy</strong>: No “AI POWERED!” flags. Blend it like it’s always been there — think weather-based alerts, not random prompts.</li><li><strong>Test Ruthlessly</strong>: Prototype, test with humans, iterate. Measure by relief — does it save an hour or a headache? Intrusive? Ditch it. Essential? Scale.</li></ol><p>Great AI UX doesn’t just meet needs; it predicts them. People don’t give a damn about your model — they care about their lives sucking less. I’ve seen trust die when AI overreaches, like a bot pushing dumb tasks mid-shift. Solve real problems, and you’re solid.</p><h3>Case Study: Turning Any Mess Into AI Gold</h3><p>Forget specific projects — let’s talk how any case study can turn AI pressure into value. Picture a team stuck with a vague “AI must-have” from the higher-ups. First, you shadow the humans in the thick of it — a tech cursing a double-booked bay, a nurse snapping at a lost chart, a clerk slamming a mispredicted stockout. You jot their pains: Overlaps, lost files, manual hell. That’s your goldmine.</p><p>Next, you sketch a solution rooted in their grind. Maybe it’s an AI that predicts delays based on patterns — alerting the tech before a client fumes, or flagging the nurse’s overdue chart with a quiet nudge. Prototype it fast: A dashboard that surfaces urgent tasks, a flow that cuts clicks, a tool that learns their rhythm. Test it raw — watch them curse the clunky bits, then refine. Feedback loops tighten it: Real-time pings kill overlaps, filters save hunt time, ambient aids pull data without distraction.</p><p>Launch it, and the win lands — chaos drops 30%, errors vanish, humans nod: “This gets my day.” Add value-first AI: Predictive smarts sniff bottlenecks, suggesting fixes that feel intuitive, not pushy. Without that human-first dive? It’s just noise — annoying predictions or bloated features. My toolkit’s “design with, not for” shines here: Co-create with the chaos, or it flops.</p><h3>Problem-First: Your Only Path to Value</h3><p>Bosses storm in — “AI dashboard!” — no pain named? It’s a trap: Tech as savior, humans as afterthought. Breeds flops — features ignored, cash wasted. My toolkit’s plea: “People over processes.” Same here.</p><p>Problem-first is your shield. Embed in the mess — shadow techs, nurses, parents. Catch their gripes, map their slog. That’s your target. Why it wins:</p><ul><li><strong>Kills Dead Ends</strong>: Shiny AI with no purpose? Trash it early.</li><li><strong>Finds Gold</strong>: Actions reveal what surveys miss — silent “save me” cries.</li><li><strong>Rallies The Room</strong>: Show bosses value — “This saves an hour, lifts retention 25%.” Ego? Gone.</li></ul><p>Miss it? AI’s just hype — people smell it, ditch it. Dig deep — workflows, frustrations, wants — and you hit moments that matter. Value-first: Humans over buzz, solutions over specs. I’ve seen teams pivot from “AI everywhere” to human wins when a prototype eased a nurse’s shift. Build for impact, not cheers.</p><h3>Cut The Hype, Deliver The Win</h3><p>AI’s a deafening roar, but you make it matter. Turn pressure into purpose, use AI’s vagueness to focus on value, craft UX that solves real shit, turn any case into a human win, and always — <em>always</em> — start with the problem. My toolkit begged: Design for people, not data. If your AI doesn’t make lives better, it’s a failure.</p><p>Audit your work now: What pain’s staring you in the face? Fix it, or you’re part of the hype. Your take below: What’s the worst AI gimmick you’ve seen? How’d you fix it problem-first? Spill — we’re building better, together.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0bbf0f8a7fed" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/stop-chasing-ai-hype-build-something-people-actually-need-0bbf0f8a7fed">Stop Chasing AI Hype — Build Something People Actually Need</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>