<?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 David Robinson on Medium]]></title>
        <description><![CDATA[Stories by David Robinson on Medium]]></description>
        <link>https://medium.com/@davidrdesign?source=rss-b03ad02cc448------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*WPAhkXDCXU-QWfFJpEOOZQ.jpeg</url>
            <title>Stories by David Robinson on Medium</title>
            <link>https://medium.com/@davidrdesign?source=rss-b03ad02cc448------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 18:34:28 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@davidrdesign/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[the x-ray]]></title>
            <link>https://davidrdesign.medium.com/the-x-ray-0a4298a54976?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/0a4298a54976</guid>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Thu, 14 May 2026 19:04:37 GMT</pubDate>
            <atom:updated>2026-05-14T19:04:37.253Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_XS4U6iHK26J8h0iKtg2Qw.jpeg" /></figure><p>The hard part about talking honestly about figures like this is that nobody really wants to. People flatten them into symbols before the conversation starts. Hero or monster. Both readings miss it. Men like this don’t drop out of the sky. They aren’t bugs in the American system. They’re features.</p><p>They come from a culture that spent decades trading substance for spectacle, competence for confidence, thinking for feeling. Entertainment and politics didn’t blur, they dissolved into each other, and charisma quietly took over the job rigor used to do. That wasn’t one election. It built up through hollowed-out institutions, sensationalist media, underfunded schools, and algorithms that print money off outrage.</p><p>Democracies don’t collapse because one charismatic figure hypnotizes a sharp public. They collapse when enough people lose the patience to tell emotional satisfaction apart from actual governance. Once that’s gone, politics stops being about what gets done and becomes about who you resent and who puts on the better show. The loudest person starts sounding like the strongest.</p><p>This is why education runs deeper than test scores. School is supposed to teach people to weigh information, spot a con, and reach for something more than the nearest slogan. A country that stops teaching that becomes easy prey for whoever can hold attention longest, with or without anything underneath.</p><p>And that’s where this stops being about one man. Take him out and someone else slides into the slot, because the machinery hasn’t moved. None of this means everyone who backs a populist is stupid. Plenty of people are reacting to things that are genuinely broken — wages that don’t keep up, towns that emptied out, the sense that the system runs on autopilot and you’re not on the manifest. That frustration is real. But it doesn’t explain why the conversation keeps rewarding the simplest version of every question. That’s a society that’s gotten worse at thinking together.</p><p>These figures aren’t the illness. They’re the x-ray. The interesting question isn’t how one guy got this powerful. It’s what kind of country keeps making that power look appealing.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0a4298a54976" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Idolatry of Innovators]]></title>
            <link>https://davidrdesign.medium.com/the-idolatry-of-innovators-c1a42a0c2cf8?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1a42a0c2cf8</guid>
            <category><![CDATA[historians]]></category>
            <category><![CDATA[innovation]]></category>
            <category><![CDATA[philosopher]]></category>
            <category><![CDATA[futurist]]></category>
            <category><![CDATA[technology]]></category>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Wed, 13 May 2026 15:25:19 GMT</pubDate>
            <atom:updated>2026-05-13T15:25:19.169Z</atom:updated>
            <content:encoded><![CDATA[<p>One thing I keep thinking about is the idolatry of innovators (I’ve heard this term before but it recently came back to me through Scott Galloway on a episode of PIVOT). Not innovation itself, which is obviously important, but the weird cultural thing where we’ve started treating innovators like they’re automatically philosophers, moral leaders, historians, futurists, all at once. Somewhere along the way success stopped meaning “this person built something effective” and started meaning “this person understands reality better than everyone else.”</p><p>You can see it everywhere in tech culture. Founders aren’t really talked about like businesspeople anymore. They get discussed like prophets or world-historical figures. Product launches have this almost religious energy around them. Every new app is supposedly “changing humanity” or “reinventing connection” or whatever. And people absorb that language without even noticing it. Wealth gets mistaken for wisdom. Confidence gets mistaken for truth. Fast movement gets mistaken for intelligence.</p><p>The thing that bothers me most is how much of society starts orienting itself around this idea that disruption is inherently noble. Like if you break an old system you must therefore be insightful or morally ahead of everyone else. Meanwhile the people actually holding society together usually aren’t innovators at all. Teachers, nurses, social workers, maintenance workers, parents, caregivers, craftsmen, community organizers. People whose contribution is consistency instead of disruption. None of that scales exponentially so culturally it starts feeling invisible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Z7437HJR1jM4ex8xlxKI5Q.png" /></figure><p>But honestly, the critique itself can become its own kind of performance if you’re not careful. “The idolatry of innovators” sounds persuasive because it compresses a lot of recognizable patterns into one clean narrative. You can immediately think of examples. TED Talks, founder worship, venture capital mythology, keynote stages, billionaire podcasts, all of it. The framework <em>feels</em> true almost instantly.</p><p>That doesn’t necessarily mean it’s fully proven though.</p><p>There’s a risk that the whole argument stays at the level of synthesis instead of evidence. Like, once you adopt the frame, everything starts confirming it automatically. Admiration becomes “worship.” Influence becomes “cultural domination.” Excitement becomes “ideology.” At that point the critique can turn into the exact thing it’s accusing others of doing: taking a compelling narrative and treating it as self-evident because it sounds smart and emotionally resonant.</p><p>And honestly I think that’s what makes the whole thing interesting. The critique is probably directionally right. There <em>is</em>something quasi-religious about the way modern culture talks about innovation and founders. But the argument is strongest when it admits its own limits instead of pretending it’s airtight sociology. Otherwise it risks becoming another myth explaining all other myths.</p><p>The circle of circles.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1a42a0c2cf8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who gives a shit?]]></title>
            <link>https://davidrdesign.medium.com/who-gives-a-shit-7f07016009b1?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f07016009b1</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[outcomes]]></category>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Wed, 01 Apr 2026 22:10:30 GMT</pubDate>
            <atom:updated>2026-04-01T22:10:30.534Z</atom:updated>
            <content:encoded><![CDATA[<p>I do.</p><p>Craft and business outcomes aren’t at odds. They work best together. The reality is that the kind of work we actually want to do, work with real integrity and care, has to live within business strategy and measurable goals. A design world that separates craftsmanship from what the business needs and how we measure success isn’t a world any of us really want to build in.</p><p>What we’re actually after is something different: spaces where the best design thinking is baked into how we define success in the first place.</p><p>Where we’re measured on outcomes that matter, sure, but where those outcomes include things like delight, clarity, and craft. Where the business gets smarter because design is strategic, and design gets better because it has to solve real problems.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*y3d0jCAZhGpJP24Z8AKKGg.jpeg" /></figure><p>The tricky part is that this mindset has to be mutual. Designers have to show up with rigor and business thinking. The organization has to make space for craft as a strategic asset, not an afterthought. It means involving design early, protecting time for quality, and measuring things that matter beyond just conversion rates.</p><p>That’s the world worth fighting for. Not one where designers compromise their standards, and not one where business gives a shit only about the metrics. A place where craft and strategy fuel each other. Where the work we do matters both to the people using it and to the people building it. Where excellence isn’t a luxury we can’t afford, it’s the whole damn point.</p><p><em>Aaaanyway, that’s what I’m working on. What about you?</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f07016009b1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Houston, we have a (memory) problem.]]></title>
            <link>https://davidrdesign.medium.com/houston-we-have-a-memory-problem-e597074019a1?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/e597074019a1</guid>
            <category><![CDATA[state]]></category>
            <category><![CDATA[pricing]]></category>
            <category><![CDATA[attachment]]></category>
            <category><![CDATA[memories]]></category>
            <category><![CDATA[travel]]></category>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Wed, 01 Apr 2026 19:34:22 GMT</pubDate>
            <atom:updated>2026-04-01T20:25:11.758Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*4lc_cNvpEnizh1in" /><figcaption>Photo by <a href="https://unsplash.com/@omarsabra64?utm_source=medium&amp;utm_medium=referral">OMAR SABRA</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Houston, we have a (memory) problem.</p><p>Here we are.</p><p>Everyone loves to say attachment is a pricing problem. It’s not.</p><p>You can discount the hotel. You can badge it, rank it, highlight it, bundle it. Doesn’t matter. If your system forgets what the user is doing, they’re gone.</p><p>This is a memory problem.</p><p>State is just memory. And most travel products have the memory of a goldfish.</p><p>You see it in the little moments. Someone spends real time picking a flight. Comparing times, layovers, prices. They finally commit, click through to hotels… and either the session dies or the system suddenly acts like it’s never met them before.</p><p>Dates? Gone. Destination? Gone. Travelers? Gone.</p><p>Now they’re typing it all back in.</p><p>That’s not just friction. That’s disrespect. You’re telling the user their time didn’t matter.</p><p>So they bounce.</p><p>And it’s not just travelers.</p><p>Watch a TMC agent juggle three bookings at once. Watch an executive admin trying to coordinate a multi-city trip for someone else. They live in tabs, notes, copy paste, half remembered details. When the system drops state, they don’t just get annoyed. Their whole workflow collapses.</p><p>They’re the ones doing the workaround dance. Rebuilding context from scratch. Double checking everything because they don’t trust the system to remember it.</p><p>That’s expensive. In time, in errors, in patience.</p><p>Even when nothing “breaks,” the damage still happens. If booking a hotel feels like starting over, the brain reframes it. Flight is done. Hotel is a separate chore.</p><p>“I’ll do it later.”</p><p>They won’t.</p><p>The whole game here is momentum. Once you lose it, you don’t get it back.</p><p>When state is done right, you can feel it immediately. You pick a flight, hit hotels, and everything’s already there. Same dates, same place, same people. It feels like the product is paying attention.</p><p>That feeling matters more than you think.</p><p>Good systems don’t just remember inputs. They remember context. Arrival time, trip type, patterns. If I land at 3pm, don’t show me a random grid of hotels. Show me places that make sense for that arrival. Near where I usually stay. Near where people like me tend to go.</p><p>That feels like help instead of work.</p><p>And for agents and EAs, it’s even bigger than that. It means the system remembers who they’re booking for, what that traveler prefers, what’s in policy, what usually gets approved. It means less second guessing, fewer Slack messages, fewer “just confirming” emails.</p><p>It means they can move fast without breaking things.</p><p>Pricing hits different too. Not separate line items, but a running total. Flight plus hotel, updating in real time. You’re not selling pieces anymore. You’re letting someone watch their trip come together.</p><p>That creates gravity. It’s harder to walk away from something that already feels half built.</p><p>A lot of products try to be “stateful” and still mess it up. You get stuck in a modal flow, halfway through picking a hotel, and if you want to double check your flight you risk losing everything.</p><p>That’s not good state. That’s a cage.</p><p>Good state is visible and forgiving. Your flight is locked in one place. Hotels scroll next to it. There’s a sticky summary that keeps track of what you’ve built. You can move around without fear of losing progress.</p><p>The product feels stable. Like it has your back.</p><p>Then there’s policy, which is where things really fall apart. You pick a flight that’s in policy. You add a hotel. Suddenly you get a red warning that the whole thing is out of policy.</p><p>Cool. Why?</p><p>Most systems don’t tell you. They just throw the error and make it your problem.</p><p>A better system shows its work. Flight is fine. Hotel is fifty bucks over the nightly limit. Now you know what to fix. Now you stay in the flow.</p><p>For agents and admins, this is the difference between confidence and anxiety. Clear state means they can explain decisions. Broken state means they’re guessing and hoping it doesn’t blow up later.</p><p>This is where AI actually starts to matter, but not in the way people pitch it.</p><p>AI isn’t here to slap a chatbot on top of a broken experience. It’s here to make the system feel like it actually remembers and understands what’s going on.</p><p>Right now, most systems treat state like a checklist. Dates, destination, traveler count. Pass it along, hope for the best.</p><p>AI lets you treat state like a story.</p><p>You searched for Boston. That probably means something. Maybe it’s a work trip. Maybe you always stay in the same area. Maybe you have a price range you stick to without thinking about it.</p><p>A good system should pick up on that without making you say it out loud every time.</p><p>And for agents, it should remember patterns across travelers. Who prefers aisle seats. Who always goes over policy but gets approved anyway. Who needs to be near the office versus near the airport.</p><p>That’s real leverage.</p><p>It should also be able to recover when things go wrong. Session times out, you come back later, and instead of a blank slate you see your trip, mostly intact, with a few smart nudges to keep going.</p><p>That’s a completely different feeling. The product stops being fragile.</p><p>It also gets ahead of problems. Instead of letting you build a trip that breaks policy at the end, it can warn you early. Or better, steer you toward options that keep everything clean.</p><p>Less surprise. Less frustration. More completion.</p><p>The best systems already act like this, even without calling it AI. They treat the trip as one thing that evolves over time. Everything stays visible. Nothing disappears. You can tweak it without starting over.</p><p>AI just makes that model smarter. Better memory, better guesses, better timing.</p><p>If you want one metric that cuts through all the noise, look at how often people go from picking a flight to actually looking at hotels without interruption.</p><p>When that drops, it’s almost always a state problem.</p><p>Not pricing. Not supply. Not intent.</p><p>Memory.</p><p>People don’t abandon because they don’t want the hotel. They abandon because the product forgot them at the exact moment they needed it to keep up.</p><p>Fix that.</p><p>Aaaaaaanyway, that’s what I’m working on. What about you?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e597074019a1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI in Product Design: Where we are now in 2026]]></title>
            <link>https://davidrdesign.medium.com/ai-in-product-design-where-we-are-now-in-2026-a71bceada2d8?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/a71bceada2d8</guid>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Wed, 04 Feb 2026 14:55:31 GMT</pubDate>
            <atom:updated>2026-02-05T13:38:33.584Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GULbodsOtuTgs6UUpATV1A.jpeg" /><figcaption>Image by <a href="https://www.instagram.com/vivalunaar/">https://www.instagram.com/vivalunaar/</a></figcaption></figure><h3>The Shift That Actually Happened</h3><p>Looking back at where we thought AI would take us in 2024–2025 versus where we actually landed, it’s less dramatic and more useful than predicted. AI didn’t replace designers. What it did was absorb the tedious parts of our workflow and force us to get serious about design systems. The biggest shift? <strong>Design systems are no longer built for designers. They’re built for AI.</strong> If your tokens aren’t machine-readable, if your component logic isn’t documented in a way that an LLM can parse, you’re leaving performance on the table.</p><h3>What’s Actually Working</h3><h4>Figma’s Evolution</h4><p>Figma Make is out of beta and it’s changed how we can approach early-stage work. The prompt-to-prototype path is genuinely useful now, not for finished work, but for testing ideas faster than we can sketch them. The real unlock is that it pulls from your design libraries. Finally, AI-generated UI that actually uses your components instead of inventing random ones.</p><p>The new image editing tools (Erase object, Isolate object, Expand image) have quietly become essential. No more round-tripping to Photoshop for basic edits. Small thing, huge time saver.</p><p>Where Figma really moved the needle: the MCP server integration. You can now pipe Figma design context directly into coding tools like Cursor, VS Code, or Claude. For those working on developer experience, this closes a gap that’s existed forever, design specs that actually translate to code without interpretation loss.</p><h4>MCP: The Protocol That Connected Everything</h4><p>If you’re not paying attention to Model Context Protocol yet, you should be. It’s become the standard for connecting AI tools to actual work. Files, databases, design systems, dev environments.</p><p>The Figma MCP app launched in late January. It lets you generate FigJam diagrams from conversations in Claude. More importantly, it’s part of a larger pattern: AI tools are now interoperable in ways they weren’t a year ago. OpenAI adopted MCP. Google DeepMind is using it. The “N×M integration problem” is actually getting solved.</p><p>For teams building documentation or developer portals, this matters. Your design system can become machine-readable context that coding assistants reference in real-time.</p><h4>Design Systems as AI Infrastructure</h4><p>The biggest mindset shift of 2026: design systems aren’t libraries anymore. They’re the intelligence layer that AI uses to stay on-brand.</p><p><strong>Token standardization is mandatory.</strong> DTCG (Design Tokens Community Group) standards are the baseline. If your tokens can’t export to JSON and be consumed by any platform, you’re creating friction for every AI workflow you’ll build.</p><p><strong>Documentation needs to be machine-readable.</strong> Static PDFs and Notion pages don’t cut it. If an AI agent can’t query your system, it can’t enforce it. Tools like Supernova are pushing documentation that serves both humans and AI, searchable, structured, live-synced with code.</p><p><strong>AI governance is now a real thing.</strong> High-performing teams are using AI agents that scan repositories for design drift before it reaches production. The system self-enforces. This is where we’re headed: autonomous design QA.</p><h3>The Practical Playbook</h3><h4>For Workflow Automation</h4><p>Let AI handle the tasks you hate: layer naming, realistic placeholder content, batch image edits, responsive variants. Figma’s AI features do this well now. Free up your headspace for actual design decisions.</p><h4>For Early-Stage Work</h4><p>Use Figma Make or Stitch to generate first drafts. The 70–80% rule is real. AI can get you most of the way to a wireframe, and your job becomes refinement instead of blank-canvas struggle. This is especially useful when you’re exploring multiple directions fast. Don’t trust the output. Always apply your design system, check hierarchy, fix accessibility issues. AI generates; you design.</p><h4>For Design-Dev Handoff</h4><p>Code Connect in Dev Mode is production-ready. Components surface with code snippets. The Figma MCP server pushes design context to AI coding tools. The handoff friction that’s plagued us for years is finally being addressed with real tooling.</p><h4>For Collaboration</h4><p>FigJam AI is genuinely helpful for workshop facilitation, generating templates, mind maps, and diagrams from conversation. The ChatGPT plugin that converts discussions into flow charts works. It’s not magic, but it eliminates the “staring at a blank FigJam” problem. For documentation, AI meeting assistants (Tactiq, Fireflies, and now native integrations in most tools) capture decisions that would otherwise evaporate. Less manual documentation, more shared context.</p><h4>What AI Still Can’t Do</h4><ul><li><strong>Context.</strong> AI doesn’t understand your users, your business constraints, or the political dynamics of your organization. It generates; you strategize.</li><li><strong>Taste.</strong> AI outputs are competent but generic. The difference between a good product and a great one is still human judgment.</li><li><strong>Accessibility at depth.</strong> AI can flag contrast issues, but it doesn’t understand how real users navigate complex interfaces. Testing still matters.</li><li><strong>Novel problem-solving.</strong> AI excels at patterns it’s seen. Novel interaction design, new mental models, genuinely innovative work — that’s still us.</li></ul><h4>What I’m Watching</h4><p><strong>MCP Apps.</strong> The protocol now supports interactive UI components inside AI conversations, dashboards, forms, multi-step workflows. This is the first official MCP extension and it’s live in ChatGPT, Claude, and VS Code. The implications for documentation and developer tools are significant.</p><p><strong>Agentic design systems.</strong> We’re moving from systems that document rules to systems that enforce them autonomously. AI agents that detect brand drift, flag accessibility violations, and generate compliant components in real-time. It’s early, but the trajectory is clear.</p><p><strong>Multi-tool orchestration.</strong> The best work is coming from designers who chain multiple AI tools together, one for ideation, another for generation, another for code. No single tool wins. The skill is in the combination.</p><h4>The Bottom Line</h4><p>AI in 2026 is infrastructure, not novelty. The design teams who thrive aren’t the ones using the most AI tools or the ones avoiding them. They’re the ones who know when to generate, when to refine, and when to step in with judgment that machines can’t replicate. Your design system is now a product that serves two audiences: humans and AI. Build it accordingly.</p><p>Stay alert, stay safe and keep doing the work. That’s still where the real craft lives. I believe in you and I’m available if you want to talk about it.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a71bceada2d8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Monkey Gourmet Club]]></title>
            <link>https://davidrdesign.medium.com/monkey-gourmet-club-35be5d637e47?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/35be5d637e47</guid>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Tue, 06 Jan 2026 02:47:39 GMT</pubDate>
            <atom:updated>2026-01-07T16:13:35.359Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*CYWoibT4gOivNcTIXsfiuw.jpeg" /></figure><p>So picture this: there’s this smart monkey on a little Japanese island, right? And this monkey’s just had it with eating sandy sweet potatoes. Nobody likes that crunchy grit in their food, and this little genius figures, “Hey, I can just rinse this thing off in the ocean.” So she does, and boom, now she’s having a way better snack.</p><p>Now, instead of this being just a one-monkey culinary revolution, her friends start catching on. They see what she’s doing and they’re like, “Okay, that looks like a solid idea.” So pretty soon, you’ve got this wave of monkeys all washing their potatoes and enjoying the good life. It’s like the monkey version of a foodie trend going viral.</p><p>And here’s the kicker. The story goes that once enough monkeys got on board, like some kind of magic number of them, monkeys on other islands just started doing the same thing out of the blue. It’s like the potato-washing idea just popped up everywhere once they hit that tipping point.</p><p>Now, sure, it might just be a tall tale rather than hard science, but it’s a pretty great way of thinking about how ideas spread. It’s a reminder that sometimes when enough people (or monkeys) get a good thing going, it just sort of takes off everywhere.</p><p>So, just like those monkeys hit that magical moment where the potato-washing trend just took off, you can think of tech startups the same way. There’s that tipping point where enough people or businesses adopt a new way of doing things, and suddenly it’s not just a cool idea, it’s the new normal.</p><p>For something like Spotnana, you can think of it as that clever monkey that came up with a smarter way to handle travel and corporate bookings. At first, maybe it’s just a handful of companies that get on board. But once you hit that critical number (your own “hundredth monkey” moment) everyone’s wondering how they ever managed travel without it. It becomes second nature and before you know it, it’s just the way everybody does things.</p><p>So in the end, we know we’re not sitting here with all the answers in our pockets. We’re not claiming to have the magic formula that works for everyone right away. What we do have is a lot of curiosity, a willingness to learn from each step, and a commitment to keep improving. Just like those monkeys figured out a better way to enjoy their sweet potatoes, we’re all figuring out better ways to solve the challenges we face. And we’re here to keep learning right alongside everyone else.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35be5d637e47" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[When We Can’t Agree on What’s Real; The False Ontology]]></title>
            <link>https://davidrdesign.medium.com/when-we-cant-agree-on-what-s-real-the-false-ontology-f6ecee737fa4?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/f6ecee737fa4</guid>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Fri, 19 Dec 2025 18:37:03 GMT</pubDate>
            <atom:updated>2026-01-20T20:22:28.871Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*yHZQr8uUl7YvuU1iSGyFYQ.jpeg" /></figure><p>As software product design leaders, we spend our days shaping systems that translate reality into interfaces. Dashboards, feeds, alerts, recommendations. Each one is a claim about what matters, what is true, and what deserves attention.</p><p>Lately, it feels like we are designing inside a deeper problem. We no longer share a common agreement on what reality is.</p><p>This is what I think of as a false ontology. A fractured understanding of the world where facts, narratives, and experiences no longer sit on the same foundation. Instead of disagreement about solutions, we are disagreeing about the ground itself.</p><h3>The product problem beneath the cultural one</h3><p>Most modern software assumes something fundamental. That users operate from a shared baseline of reality. Data represents facts. Language carries intent. Signals mean roughly the same thing to everyone.</p><p>That assumption is breaking down.</p><p>Two users can look at the same interface, the same chart, the same sentence, and walk away with entirely different interpretations of what is real. Not preferences. Not opinions. Reality.</p><p>This is not an abstract philosophical issue. It shows up in product metrics, customer trust, and system behavior every day.</p><ul><li>A notification meant to inform becomes a provocation.</li><li>A neutral data point becomes evidence of bias.</li><li>A design choice intended to simplify becomes a signal of manipulation.</li></ul><p>When reality itself is contested, software becomes an accelerant.</p><h3>How false ontologies get designed into systems</h3><p>False ontologies rarely appear because of bad intent. They are often the byproduct of optimization.</p><p>We optimize for engagement, speed, personalization, and scale. In doing so, we fragment the shared world into individually curated realities. Each feed reinforces its own internal logic. Each algorithm rewards coherence within a bubble, not alignment across bubbles.</p><p>Over time, users stop encountering reality as something external and shared. Reality becomes something delivered.</p><p>From a design perspective, this creates a dangerous illusion. Interfaces feel confident. Systems feel authoritative. Yet the foundation beneath them is unstable.</p><p>We are not designing tools that help people understand the world. We are designing environments that replace it.</p><h3>The responsibility of design leadership</h3><p>Design leadership has always carried ethical weight, but this moment raises the bar.</p><p>Our responsibility is not only usability or conversion. It is epistemic. We are shaping how people come to know what is real.</p><p>That does not mean designers become arbiters of truth. It means we take responsibility for how our systems frame, distort, or obscure reality.</p><p>Some questions I believe design leaders need to ask more often:</p><ul><li>What assumptions about reality does this product encode?</li><li>Where does this system collapse complexity into false certainty?</li><li>What does this interface encourage users to believe is important, normal, or true?</li><li>Where are we mistaking personalization for understanding?</li></ul><p>These are not academic questions. They are product questions with real downstream impact.</p><h3>Designing for shared reality, not manufactured certainty</h3><p>Rebuilding a shared sense of reality does not require heavy-handed controls or moralizing UX. It requires humility in design.</p><p>It looks like:</p><ul><li>Making uncertainty visible instead of hiding it behind precision.</li><li>Showing context alongside data, not after it.</li><li>Designing for reflection, not only reaction.</li><li>Allowing friction where meaning matters.</li><li>Treating language as a design material, not filler text.</li></ul><p>Good design does not eliminate ambiguity. It helps people navigate it without collapsing into false clarity.</p><h3>A quieter, harder kind of leadership</h3><p>The false ontology problem will not be solved by a new feature, framework, or AI model. It will be shaped by thousands of small decisions made by product teams every day.</p><p>Design leaders set the tone for those decisions.</p><p>Do we reward speed over sense-making?<br>Do we celebrate engagement without asking what is being engaged with?<br>Do we treat users as endpoints or as participants in a shared world?</p><p>The future of software is not only about intelligence or automation. It is about whether our systems help repair a shared reality or continue to fracture it.</p><p>Design has always been about making the invisible visible. Right now, what is invisible is the cost of pretending reality is settled when it is not.</p><p>That is the work. And it starts with how we choose to design.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f6ecee737fa4" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Helping People Find Their Power: The Role of UX in Connected Fitness]]></title>
            <link>https://davidrdesign.medium.com/helping-people-find-their-power-the-role-of-ux-in-connected-fitness-043ae1f4b576?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/043ae1f4b576</guid>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Tue, 08 Apr 2025 18:00:59 GMT</pubDate>
            <atom:updated>2025-04-08T18:00:59.392Z</atom:updated>
            <content:encoded><![CDATA[<p>by David “D-Rob” Robinson, Design Leader Who’s Definitely Skipped a Few Workouts</p><p>Let’s be honest: most people aren’t trying to become athletes. They’re trying to feel better in their own skin. Move a little more. Get their energy back. Show up for themselves, not just physically, but mentally too.</p><p>But actually doing it? That’s the hard part.</p><p>As someone who has been designing software experiences for connected fitness products, I think about this <em>all the time</em>. Not just how to get people to click buttons or finish workouts but how to help them <em>believe in themselves enough to start</em>.</p><p>Because here’s the thing: people already know moving their body is good for them. They don’t need more data. They don’t need more guilt. What they need is an experience that makes them <em>feel powerful</em>. And that’s exactly where UX can make or break the whole thing.</p><p><strong>Procrastination Isn’t the Problem — It’s the Symptom</strong></p><p>Most of us don’t skip a workout because we’re lazy. We skip it because we’re tired, overwhelmed, or already convinced it’s not gonna work anyway.</p><p>So when a connected fitness app pops up with some perfectly curated workout, and all we can think is “Ugh, not today,” that’s not failure, that’s a design’s opportunity.</p><p>The goal isn’t to guilt people into moving. It’s to design a moment that reminds them: <em>hey, you’re already doing something good just by showing up here.</em></p><p>If we can help someone feel a small win early on, even just a 3 minute movement session or a “you made it today” nudge, we’re starting to chip away at that invisible resistance. And once someone finds <em>their</em> power? That’s when consistency shows up too.</p><p><strong>Designing for Real People, Not Fitness Fanatics</strong></p><p>Here’s a few ways we’ve seen UX make a real difference in how people engage with connected fitness products:</p><p><strong>1. Give Them a Win Right Away</strong></p><p>Don’t make people dig for a 10-minute low-effort option — just give it to them. Better yet, <em>recommend it based on their mood</em> or energy level. Showing people something they can actually do right now builds confidence.</p><p><em>Feeling designed: “Okay, maybe I can do this.”</em></p><p><strong>2. Progress That Actually Feels Good</strong></p><p>Stop only celebrating weight loss or miles. Start celebrating <em>consistency</em>. Let people see streaks, effort, mood tracking. Whatever helps them feel like they’re showing up for themselves.</p><p><em>Feeling designed: “I’m not perfect, but I’m trying. And that counts.”</em></p><p><strong>3. Design Like a Human, Not a Robot</strong></p><p>Your tone, buttons, error messages — even the colors you use — can feel warm or cold, encouraging or critical. If it doesn’t feel like a supportive coach or a friend, it probably feels like a spreadsheet.</p><p><em>Feeling designed: “This app actually gets me.”</em></p><p><strong>4. Make the Next Step Obvious</strong></p><p>Decision fatigue is real. “What should I do today?” is often the very thing that causes people to just close the app. So… take that away. Suggest the next best step. Default to something doable.</p><p><em>Feeling designed: “That was easier than I thought.”</em></p><p><strong>5. Let Them See Who They’re Becoming</strong></p><p>Fitness isn’t just about changing your body. It’s about changing your <em>story</em>. The right copy, visuals, and progress tracking can help someone go from “I’ll never be consistent” to “I’m actually becoming someone who moves.”</p><p><em>Feeling designed: “I like who I’m becoming.”</em></p><p><strong>When People Feel Their Power, They Come Back</strong></p><p>And yeah, from a business perspective, that’s engagement.</p><p>Not just clicks or logins or time in-app, but <em>real</em>, intentional engagement. The kind where someone doesn’t need to be nudged to come back, they want to come back, because the app helps them feel better than they did before they opened it.</p><p>UX isn’t just about usability. It’s about identity. And when we design to help people <em>feel capable</em>, <em>seen</em>, and <em>in control</em>, we’re not just reducing procrastination. We’re building habit. Confidence. Change.</p><p>And yes, that’s good for business. But it’s also just good for <em>people</em>.</p><p><strong>TL;DR:</strong></p><p>• People don’t want to be athletes. They want to feel better.</p><p>• Procrastination is emotional, not rational.</p><p>• UX that helps people feel powerful leads to commitment.</p><p>• Make the next step easy, warm, human, and worth it.</p><p>• When people believe in themselves, they come back — and not just for your product, but for themselves.</p><p>If you’re building connected fitness experiences and want to talk more about how UX can help people become who they want to be — let’s chat. I’ve got opinions (and probably a few typos).</p><p>✌️</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=043ae1f4b576" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Powering Down by The Layoffs]]></title>
            <link>https://davidrdesign.medium.com/powering-down-by-the-layoffs-6e1872c88faf?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/6e1872c88faf</guid>
            <category><![CDATA[the-end-of-the-world]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[music]]></category>
            <category><![CDATA[midjourney]]></category>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Tue, 02 May 2023 17:35:30 GMT</pubDate>
            <atom:updated>2023-05-02T17:54:09.887Z</atom:updated>
            <content:encoded><![CDATA[<iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FsHeUdpKDJPU%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DsHeUdpKDJPU&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FsHeUdpKDJPU%2Fhqdefault.jpg&amp;key=a19fcc184b9711e1b4764040d3dc5c07&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/9c52d8215501cd0ed7dcf7a6920509d7/href">https://medium.com/media/9c52d8215501cd0ed7dcf7a6920509d7/href</a></iframe><p>“Powering Down” by The Layoffs is a poignant and introspective song that delves into the emotions of being laid off from a remote job. The lyrics, written by ChatGBT, were inspired by a New York Times article that covered the chaos and angst surrounding remote job cuts during the pandemic. The song captures the sense of isolation and disconnection that many remote workers experienced when they received the news of their layoffs via emails, Slack messages, or video calls. As the song’s title suggests, the act of “powering down” one’s computer becomes a metaphor for the abrupt end of a job and the loss of a sense of purpose and community. The Layoffs use an eclectic mix of musical styles and instrumentation to create a unique sound that matches the raw emotion of the lyrics. “Powering Down” sets the tone for the band’s debut album, which is being hailed as the first of its kind and showcases their ability to turn the pain of job loss into beautiful and meaningful music.</p><p><a href="https://linktr.ee/thelayoffsmusic">The Layoffs | Twitter, Instagram, TikTok | Linktree</a></p><p>The music video for “Powering Down” by The Layoffs was created using <a href="https://www.instagram.com/explore/tags/midjourney/">#Midjourney</a>, and it brings the song’s emotions to life in the style of an Edward Hopper painting. The video captures the sense of isolation and disconnection that comes with remote job cuts, and it’s a visual masterpiece that perfectly complements the song’s raw emotion.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6e1872c88faf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Friday around noon.]]></title>
            <link>https://davidrdesign.medium.com/saturday-around-noon-2d6b9111683a?source=rss-b03ad02cc448------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d6b9111683a</guid>
            <dc:creator><![CDATA[David Robinson]]></dc:creator>
            <pubDate>Fri, 28 Jan 2022 04:15:35 GMT</pubDate>
            <atom:updated>2022-01-30T19:47:41.077Z</atom:updated>
            <content:encoded><![CDATA[<p>My mom passed away on Friday around noon, we were very close and I will miss her until the end of time. Every sibling has a bonding story with a parent and I’m no different. My mother is my heart. It’s where my foundations were born and where they live to this day. She is everything about who I am and who I aspire to be. She is my hero. She is my mom.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/297/1*e1mfCp4gbYEz0hY6L3kZPA@2x.jpeg" /></figure><p>Our family hasn’t been able to get together much over the past couple years because of fucking COVID but we all got to be there when she passed so I’m grateful for that. I don’t usually share the feels out loud on the internet but I’m in the airport on my way home and thought I’d write some notes down.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*NfwhO200SsQWLFn2tdYwFQ@2x.jpeg" /></figure><p>Beverley was a kind mother and wife, touch was her superpower. She was an artist, a painter, an interior decorator and a therapist to many. She has an identical twin sister named Barbara and they’ve done literally everything together for their whole lives. They even built a 2nd house on the property so they could stay close as they got older.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*BAT_JIcNpHzKdpN9eFa20Q@2x.jpeg" /></figure><p>Beverley was a very generous person and a real kick-in-the-pants at a party. My most watched <a href="https://vm.tiktok.com/TTPdh5naKF/">TikTok</a> is of her nailing it during a game of beer pong. She liked to do surprising, over-the-top stuff. She once bought my dad a real life baby lamb for his birthday not as a joke but for real.</p><p>Mom’s passing was surprisingly sudden. It happened over the course of weeks. She developed a lump on her jaw that grew quickly. Her team of doctors prescribed 5 weeks of radiation and then a “wait 5 weeks and see what happens” kind of treatment. She hated that, a lot. All of it. She was always afraid to get old and to lose control of her body. She used to say “if they put a feeding tube in me and have to wipe my ass just end it for me” - much like her father, Lloyd. We tried to get the <a href="http://www.bccancer.bc.ca/health-info/coping-with-cancer/medical-assistance-in-dying#q02">MAiD</a> paperwork done so she wouldn’t have to experience the pain and humiliation of laying on her deathbed losing control of her body while everyone watched (I’ve learned so much). Her doctor told us not to bother with the MAiD paperwork because she wouldn’t last long enough. That was when I accepted the fact that she wasn’t going to leave this room we were all in, this was it. For the first time we would return to the dream home that my parents built together, along the waters edge on Vancouver Island, after my father retired from a life long career of persistence and determination — fulfilled and happy in Mill Bay, British Columbia, paradise on earth (run-on sentence I know, give me a break, my mom just died).Alone together we sat for the first time, it was heartbreaking.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8T4uPzVH7qd3U4ul-f5YRg@2x.jpeg" /></figure><p>MAiD is the one thing she wanted most and the one thing we couldn’t give her. I don’t blame myself or anyone else for that. We didn’t have a terminal diagnosis at the time, in fact, we had the opposite diagnoses. Why would she want to die with so much life left? Didn’t make sense then but now it does and it’s a lot to process.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zIbk9oc7SzTUH4AsV4gpQQ@2x.jpeg" /></figure><blockquote>Mom a the end of her radiation treatments. The thing she’s holding is the mounding they strapped her into so she didn’t move while being zapped by the radiation gun.</blockquote><p>Something started to not feel right after the 5 weeks of radiation, she started to feel weak and sleep all the time. My sister Julie, who’s been taking care of everything, said “she’s not the same, she’s angry and knows something is off.”</p><p>Mom kept telling everyone that something was not right, she went to the ER 3 times. Each time they scanned her head and each time they sent her home and told her that there were no signs of cancer left in her head. She had lots of life left in her and that she just needed to recover.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*e45MkS9hL4YM5wR374JqAQ@2x.jpeg" /></figure><blockquote>Mom, dad and Benji</blockquote><p>Welp, as it turns out, that wasn’t the case. When she woke up last Wednesday dad texted that she was having a hard time breathing we told him to call 911. They took her to the ER and I caught a flight out the next morning. When they got her to the ER they did a CT scan of the body (not just the head) and she lit up like a Christmas tree. Cancer everywhere.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*JVlrv7J0rVJKnEME3Nz6IQ@2x.jpeg" /></figure><p>My brother Danny picked us up at the airport and we made our way to the hospital. I was surprised at how skinny she was and how ashen her skin looked, I was on my heels. We had some good moments on Thursday, she exhibited some signs of strength. I used her superpower of touch to keep her eyes focused up on me. She wanted to “go” and I told her it was ok but not yet, we just needed a little more time, she said “ok.” We were looking forward to spending the next day with her.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*9AqW-c3WdeONDcz2l6uBRA@2x.jpeg" /></figure><blockquote>Beverley and Allan. Mom and dad.</blockquote><p>The next morning we got a call from the hospital that we needed to come to her room quickly. I arrived with aunt Barbara and texted my brother Danny to drive faster. It was time! The hospital staff was trying to enforce the 2 people in the room max rule but my cousin Leslie fixed that quickly — Leslie is a badass. We all stayed in the room with her. She left us around noon on Friday.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/320/1*wSxVM6yJ1pzk9xy1Z0iuDg@2x.jpeg" /></figure><blockquote>She loved a good martini.</blockquote><p>Like I said up top, I don’t normally let out the feels like this but it felt like something I needed to do. I guess I’m still processing. Thank you to everyone who reached out, apologize for not answering the phone but I just couldn’t.</p><p>I believe in you just like she believed in you.</p><p>— DRob</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d6b9111683a" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>