<?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 Paul Chang on Medium]]></title>
        <description><![CDATA[Stories by Paul Chang on Medium]]></description>
        <link>https://medium.com/@paulbchang?source=rss-8162ce5d8ee9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*wsublph9Gh4armDBQxp4kw.png</url>
            <title>Stories by Paul Chang on Medium</title>
            <link>https://medium.com/@paulbchang?source=rss-8162ce5d8ee9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 19:48:11 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@paulbchang/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[Stagecoach Privacy Policy]]></title>
            <link>https://medium.com/@paulbchang/stagecoach-privacy-policy-0d60705ea3dc?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/0d60705ea3dc</guid>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Wed, 01 Apr 2026 05:49:57 GMT</pubDate>
            <atom:updated>2026-04-01T05:49:57.569Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Effective Date: April 1, 2026</em></p><p>This Privacy Policy describes how 2ejk (“we,” “us,” or “our”) collects, uses, and protects your information when you use the Stagecoach mobile application (“the App”). By using Stagecoach, you agree to the practices described in this policy.</p><h3>1. Information We Collect</h3><h4>1.1 Information You Provide</h4><ul><li><strong>Account information: </strong>When you create an account, we may collect your name, email address, and authentication credentials.</li><li><strong>Presentation content: </strong>The topics, titles, descriptions, and narrative content you enter while using the App to develop your talk tracks and presentation narratives.</li><li><strong>Feedback and communications: </strong>Any feedback, bug reports, or messages you send to us through the App or via email.</li></ul><h4>1.2 Information Collected Automatically</h4><ul><li><strong>Usage data: </strong>How you interact with the App, including features used, session duration, screens viewed, and actions taken.</li><li><strong>Device information: </strong>Device type, operating system version, app version, unique device identifiers, and general diagnostic data.</li><li><strong>Crash and performance data: </strong>Error logs and performance metrics to help us identify and fix technical issues.</li></ul><h4>1.3 Information We Do Not Collect</h4><p>We do not collect your precise location, contacts, photos, microphone or camera data, health data, or financial information through the App.</p><h3>2. How We Use Your Information</h3><p>We use the information we collect for the following purposes:</p><ul><li><strong>Providing the service: </strong>To generate AI-powered narrative coaching, talk track suggestions, and presentation frameworks based on your input.</li><li><strong>Improving the App: </strong>To analyze usage patterns, diagnose technical issues, and improve the quality and relevance of our AI-generated content.</li><li><strong>Communications: </strong>To respond to your inquiries, send important service updates, and provide information about new features (with your consent where required).</li><li><strong>Safety and compliance: </strong>To detect and prevent fraud, abuse, or violations of our Terms of Service.</li></ul><h3>3. AI Processing and Third-Party Services</h3><p>Stagecoach uses artificial intelligence to help you develop presentation narratives. When you enter content into the App, that content may be sent to third-party AI service providers for processing. These providers process your data solely to generate responses and do not use your content to train their models.</p><p>We may also use the following categories of third-party services:</p><ul><li><strong>Cloud infrastructure: </strong>For hosting and storing application data.</li><li><strong>Analytics services: </strong>To understand how the App is used and to improve user experience.</li><li><strong>Crash reporting: </strong>To identify and resolve technical issues.</li></ul><p>All third-party service providers are bound by contractual obligations to protect your data and use it only for the purposes we specify.</p><h3>4. Data Retention</h3><p>We retain your presentation content and account information for as long as your account is active or as needed to provide you with the service. If you delete your account, we will delete or anonymize your personal data within 30 days, except where we are required by law to retain it.</p><p>Automatically collected usage and diagnostic data is retained in aggregate form and is not linked to your identity after anonymization.</p><h3>5. Data Security</h3><p>We implement industry-standard security measures to protect your information, including encryption of data in transit (TLS/SSL) and at rest, secure authentication mechanisms, and access controls limiting who can view your data within our organization.</p><p>No method of transmission or storage is 100% secure. While we strive to protect your data, we cannot guarantee absolute security.</p><h3>6. Your Rights and Choices</h3><p>Depending on your jurisdiction, you may have the following rights regarding your personal data:</p><ul><li><strong>Access: </strong>Request a copy of the personal data we hold about you.</li><li><strong>Correction: </strong>Request correction of inaccurate or incomplete data.</li><li><strong>Deletion: </strong>Request deletion of your personal data, subject to legal retention requirements.</li><li><strong>Data portability: </strong>Request your data in a structured, commonly used format.</li><li><strong>Opt out: </strong>Opt out of non-essential communications at any time.</li></ul><p>To exercise any of these rights, contact us at privacy@2ejk.com.</p><h3>7. California Residents</h3><p>If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA), including the right to know what personal information we collect and how it is used, the right to request deletion of your personal information, and the right to opt out of the sale of personal information.</p><p><strong>We do not sell your personal information. </strong>To submit a request under the CCPA, contact us at the email address listed below.</p><h3>8. International Users</h3><p>If you access the App from outside the United States, please be aware that your information may be transferred to, stored, and processed in the United States or other countries where our service providers operate. By using the App, you consent to the transfer of your information to these jurisdictions, which may have different data protection laws than your country of residence.</p><p>If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, we process your personal data based on your consent, contractual necessity, or our legitimate interests in operating and improving the App.</p><h3>9. Children’s Privacy</h3><p>Stagecoach is not directed at children under the age of 13 (or the applicable age of consent in your jurisdiction). We do not knowingly collect personal information from children. If we learn that we have collected data from a child without parental consent, we will delete that information promptly. If you believe a child has provided us with personal data, please contact us immediately.</p><h3>10. Changes to This Privacy Policy</h3><p>We may update this Privacy Policy from time to time. When we make material changes, we will notify you through the App or by other appropriate means before the changes take effect. Your continued use of the App after the updated policy takes effect constitutes your acceptance of the revised policy.</p><p>We encourage you to review this policy periodically for any updates.</p><h3>11. Contact Us</h3><p>If you have questions, concerns, or requests regarding this Privacy Policy or our data practices, please contact us at:</p><p><strong>2ejk</strong></p><p>Email: privacy@2ejk.com</p><p><em>Last updated: April 1, 2026</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0d60705ea3dc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design as Infrastructure: Building Systems That Build Themselves]]></title>
            <link>https://medium.com/2ejk/design-as-infrastructure-building-systems-that-build-themselves-a2b29a13914e?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a2b29a13914e</guid>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[scaling-up]]></category>
            <category><![CDATA[ai-design-patterns]]></category>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Fri, 22 Aug 2025 15:42:28 GMT</pubDate>
            <atom:updated>2025-08-25T00:43:33.129Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7n-1I_GNkhvH08xUS1W09A.png" /></figure><p>In 2009, Fast Company profiled <a href="https://www.linkedin.com/in/imdavidbutler/">David Butler</a>, Coca-Cola’s then vice president of design, who faced a fragmented brand. Across the globe, Coca-Cola’s visual identity had drifted as local teams and vendors improvised. Butler’s answer wasn’t a rigid rulebook but a new mindset: treat design as infrastructure.</p><p>He reduced Coca-Cola to its essentials: the red disc, the wave, the script, and reassembled them into a flexible system. Less a style guide and more a Lego set, it allowed employees to produce and vendors to build their own signage while keeping brand coherence. The goal wasn’t control but consistency through shared tools.</p><p>This Lego-like approach extended to Coke’s Freestyle machines, which let consumers mix their own drinks. The company no longer dictated flavor releases; it built a platform for others to design experiences. Design shifted from surface decoration to structural system. From something made to something that makes.</p><p>The analogy in software is even stronger. Infrastructure here means modular systems: tokens, components, interaction patterns that can be endlessly recombined. A design system becomes generative.</p><p>Add AI, and agents become the worker bees. They handle the construction tasks once done manually: coding interfaces, generating content, linking workflows. Infrastructure sets the grammar; agents compose with it. Teams can sketch intent, and agents assemble details while staying coherent because the system guides them.</p><p>The payoff is scale with coherence. Just as Butler enabled thousands of Coca-Cola touchpoints to remain on brand without micromanagement, software infrastructure plus AI agents could let organizations move at exponential speed without chaos. Infrastructure sets the rules of play; agents bring the energy.</p><p>This reframes design not as artifact-making but as laying tracks. Once the tracks exist, trains run, freight moves, commerce flows. Designers ensure coherence and resilience. Agents keep it in motion. Together they form a living infrastructure — one that builds not just things, but the capacity to keep building.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a2b29a13914e" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/design-as-infrastructure-building-systems-that-build-themselves-a2b29a13914e">Design as Infrastructure: Building Systems That Build Themselves</a> was originally published in <a href="https://medium.com/2ejk">2ejk</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 fix your tech debt, but what’ll fix AI’s?]]></title>
            <link>https://medium.com/2ejk/ai-can-fix-your-tech-debt-but-whatll-fix-ai-s-a68632dd5801?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a68632dd5801</guid>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Thu, 07 Aug 2025 20:20:05 GMT</pubDate>
            <atom:updated>2025-08-07T20:20:05.221Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XU2RZOi3_dGDVPn7aLGtNg.png" /></figure><p>Tech debt are the unwanted soot sprites of every software stack, lingering in dark corners, multiplying silently, and demanding attention at the worst possible moments — and, I might add, the bane of any designer hoping to create an imagined future state.</p><p>But with AI, we’ve stumbled on a curious opportunity: not just to clean house, but to install a self-dusting system. AI can help resolve long-standing tech debt by automating refactors, exposing hidden dependencies, and translating brittle legacy code into modular frameworks. For teams who’ve been kicking the can for years, that’s nothing short of a gift.</p><p>But before we declare victory, we have to ask: what kind of debt is AI creating in return?</p><p>This next-gen debt is subtle, even invisible. It lives in biased training data, aging foundation models, and black-box logic that resists inspection. It doesn’t throw 500 errors, it quietly distorts user experiences, misguides teams, and erodes trust. Are we ready for tech debt that isn’t just technical, but ethical and systemic?</p><p>As AI embeds deeper into our systems, tech debt becomes “meta.” It hides in the models we inherit, the prompts we forget to update, the assumptions we never question. So how do we maintain system health when the system is reasoning for itself? Is better documentation enough? Stricter reviews?</p><p>Probably not.</p><p>We’ll need AI that’s reflexive and antifragile: able to audit its own logic, recognize when its priors are stale, and flag when it’s building on shaky ground. Guardrails can’t just be static, they must adapt, evolve, even grow stronger under pressure. Can we design AI to carry its own quality assurance process in its psyche?</p><p>Because if we don’t, we’re just trading one kind of chaos for another.</p><p>Yes, AI might finally help us address the mess we’ve made. But we can’t afford to outsource our vigilance. The next wave of tech debt won’t look like spaghetti code. It’ll look like faulty cognition. And the only way forward is to embed a conscience in the machine.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a68632dd5801" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/ai-can-fix-your-tech-debt-but-whatll-fix-ai-s-a68632dd5801">AI can fix your tech debt, but what’ll fix AI’s?</a> was originally published in <a href="https://medium.com/2ejk">2ejk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How AI may reshape the product-design-engineering triad]]></title>
            <link>https://medium.com/2ejk/how-ai-may-reshape-the-product-design-engineering-triad-0fa996dbdfbd?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/0fa996dbdfbd</guid>
            <category><![CDATA[ai-philosophy]]></category>
            <category><![CDATA[product-triad]]></category>
            <category><![CDATA[they-took-our-jobs]]></category>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Fri, 18 Jul 2025 22:07:23 GMT</pubDate>
            <atom:updated>2025-07-18T22:08:01.065Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d3Cokgnro07UWip7eP2eAg.png" /></figure><p>In product development, we often talk about product, design, and engineering as a balanced triad, each contributing their unique expertise, while influencing both partners. While ideally balanced, they don’t quite tackle the same kinds of problems.</p><p>One way to look at the difference is by considering <em>how open-ended</em> their work is.</p><p>Product tends to operate in the widest space, deciding <em>what</em> to pursue and <em>why</em>, based on fuzzy signals from the market, user behavior, and business goals. Design narrows the field, working to define <em>how</em> we might solve those problems in ways that are intuitive, elegant, and usable. Engineering typically works in the most constrained domain: <em>how do we build this well?</em> — a tough challenge, but often with clearer parameters.</p><p>This isn’t a value judgment. It’s just the nature of the work.</p><p>Now enter AI.</p><p>It’s not surprising that AI is showing early strength in engineering. It’s well-suited to technical, structured tasks: code generation, testing, optimization. These jobs live in the cleanest, most bounded problem spaces.</p><p>But when those are handled by machines, engineers get more room to think bigger. More integration and architecture. More systems-level work. More early-stage shaping. And, increasingly, a toe dipped into the design side.</p><p>Zoom out again: as AI begins to assist designers with pattern recognition, visual exploration, and user-interface generation, designers may find themselves pulled further into strategic territory — service design, product thinking, market fit.</p><p>What we’re seeing isn’t job loss, rather it’s role expansion.</p><p>As AI moves up the stack, it relieves pressure at the base. That gives humans space to climb. Engineers become more design-aware. Designers ask more business-shaped questions. Product managers think more deeply about the entire experience, not just the roadmap.</p><p>There’s a well-worn saying that AI won’t eliminate jobs — it’ll <em>elevate</em> them. This may be what that looks like for the product-design-engineering triad.</p><p>The work doesn’t go away. It just gets more interesting.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=0fa996dbdfbd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/how-ai-may-reshape-the-product-design-engineering-triad-0fa996dbdfbd">How AI may reshape the product-design-engineering triad</a> was originally published in <a href="https://medium.com/2ejk">2ejk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The last unplugged generation]]></title>
            <link>https://medium.com/2ejk/the-last-unplugged-generation-d50ee2461cd2?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/d50ee2461cd2</guid>
            <category><![CDATA[family-unplugged]]></category>
            <category><![CDATA[ai-philosophy]]></category>
            <category><![CDATA[generation-x]]></category>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Fri, 18 Jul 2025 22:04:49 GMT</pubDate>
            <atom:updated>2025-07-18T22:04:49.046Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*udyO4f33wKtMViWAh1jhqQ.png" /></figure><p>Some of the best movies stick with us because we get to witness a real character arc: someone changes, grows, figures things out. That same kind of arc is what I think about when I reflect on growing up without and then with computers.</p><p>I was born before they were a thing. My early years were screen-free. That meant boredom, unstructured time, and figuring out how to entertain myself. It wasn’t always easy, but it built creativity, resourcefulness, and patience. There was no back button, just trial and error.</p><p>Computers arrived slowly. In my teens, they were more novelty than necessity. In college, they became useful. In grad school, the internet showed up in earnest. It was clunky and slow, but it changed everything. Suddenly, research, collaboration, even career possibilities looked different. I remember feeling the shift. This wasn’t just a new tool, it was a new context.</p><p>Then came the iPhone. For those of us already in the workforce, it landed as a productivity boost, not a social fix. We’d had just enough analog in our lives to use tech with intention, not impulse.</p><p>Now, we’re watching AI enter the picture, and it promises to be the biggest shift yet. I feel lucky to be at a stage where I have enough experience to put it in perspective, but still enough curiosity to dive in. I get to understand it not just from the outside, but from inside the work.</p><p>Not everyone gets to grow up with nothing and still catch the front wave of everything. Early Gen X is a weird, wonderful sweet spot, and I’m grateful to have a front-row seat.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d50ee2461cd2" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/the-last-unplugged-generation-d50ee2461cd2">The last unplugged generation</a> was originally published in <a href="https://medium.com/2ejk">2ejk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The cost of focusing on your competition]]></title>
            <link>https://medium.com/2ejk/the-cost-of-focusing-on-your-competition-a29a8d28aca1?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/a29a8d28aca1</guid>
            <category><![CDATA[innovation-mindset]]></category>
            <category><![CDATA[product-strategy]]></category>
            <category><![CDATA[customer-centricity]]></category>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Fri, 27 Jun 2025 20:43:52 GMT</pubDate>
            <atom:updated>2025-06-27T20:43:52.332Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8MAENL4BJ7AKeRf1H2_aHg.png" /></figure><p>In <em>The Fountainhead</em>, Ayn Rand introduces the idea of “second-handers”: individuals who derive their direction not from their own judgment, but from the approval or actions of others. While her critique focused on people, the idea finds a quiet echo in today’s business world.</p><p>In highly competitive markets, it’s natural, almost reflexive, for companies to track what others are doing. But when competitive awareness becomes the primary compass, organizations risk losing touch with what matters most: their customers. The question subtly shifts from “What problems are we uniquely positioned to solve?” to “What are our rivals doing? And, how fast can we follow?”</p><p>Consider the well-documented contrast between Microsoft and Apple in the early 2000s. Microsoft often responded to Apple’s moves — sometimes directly, sometimes through positioning campaigns. Meanwhile, Apple appeared to be less reactive, focusing instead on delivering tightly integrated products that addressed latent user needs. It wasn’t just about speed to market — it was about clarity of purpose.</p><p>This isn’t to say competitor-awareness is bad. It’s essential. But if it overshadows customer-centric vision, it can lead to derivative work and missed opportunities for meaningful innovation.</p><p>As we enter a new era shaped by artificial intelligence, this lesson becomes even more critical. Success won’t come from being the first to ship an AI feature, but from using AI to solve real, often unglamorous customer problems in elegant, effective ways. The race isn’t to be first — it’s to be right.</p><p>The takeaway? Inspiration can come from many places, but conviction should come from within. Build with your customers in mind, not your competitors in sight.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a29a8d28aca1" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/the-cost-of-focusing-on-your-competition-a29a8d28aca1">The cost of focusing on your competition</a> was originally published in <a href="https://medium.com/2ejk">2ejk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Leveling up isn’t just about skill — it’s about perspective and curiosity]]></title>
            <link>https://medium.com/2ejk/leveling-up-isnt-just-about-skill-it-s-about-perspective-and-curiosity-eeaaf60b9b02?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/eeaaf60b9b02</guid>
            <category><![CDATA[design-career]]></category>
            <category><![CDATA[curious-mindset]]></category>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 19:19:45 GMT</pubDate>
            <atom:updated>2025-06-19T19:42:42.803Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0FJv3MPODak_MehDcmLALA.png" /></figure><h3>Leveling up isn’t just about skill — it’s about perspective and curiosity</h3><p>The NBA Finals are underway, and as always, I’m watching closely — not just for the highlight reels, but the moments between them: the adjustments, the mental grit, the players who rise when it matters most.</p><p>It brought me back to my own years playing basketball — not at an elite level, just as an average college player — but enough to see what separates those who rise from those who plateau. And it struck me — that arc mirrors what we face in product design.</p><p>In youth basketball, it’s all about fundamentals — dribbling, passing, rebounding, and shooting. In design, it’s visual foundations and user interfaces: grids, alignment, hierarchy, components. You build control through repetition and intent.</p><p>As you move up, the game gets more complex. You read the floor, play within a system, and make decisions in motion. For designers, this is the shift from crafting screens to thinking in systems and solving problems. You collaborate, absorb feedback, and balance user needs with business realities.</p><p>At the college level, it’s no longer just about individual skill — it’s how you elevate the people around you. On the court, that means leadership, anticipation, and adaptability. In design, it means taking ownership, driving clarity through ambiguity, and thinking systematically. Your impact is measured less by execution, and more by your ability to align teams and shape outcomes.</p><p>I never made it to the next level, but I saw glimpses of what it took. The players who advanced weren’t just talented — they adapted, stayed coachable, and never stopped learning. The same is true for the best designers and leaders I know. They’re sharp — but more importantly, they’re curious. Open. Always scanning the floor, always evolving.</p><p>Wherever you are in your journey, the next level will demand something new: sharper skills, better communication, broader thinking, deeper resilience. But always — always — it will require perspective. And curiosity.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=eeaaf60b9b02" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/leveling-up-isnt-just-about-skill-it-s-about-perspective-and-curiosity-eeaaf60b9b02">Leveling up isn’t just about skill — it’s about perspective and curiosity</a> was originally published in <a href="https://medium.com/2ejk">2ejk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI doesn’t replace insight. It rewards it.]]></title>
            <link>https://medium.com/2ejk/ai-doesnt-replace-insight-it-rewards-it-8f91567a3f0c?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f91567a3f0c</guid>
            <category><![CDATA[human-centered-ai]]></category>
            <category><![CDATA[responsible-ai]]></category>
            <category><![CDATA[product-thinking]]></category>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Thu, 19 Jun 2025 19:16:35 GMT</pubDate>
            <atom:updated>2025-06-19T19:17:44.657Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XvN8m93VqileIpoPdlLTxw.png" /></figure><p>It’s easy to get swept up in the hype. AI can generate, optimize, predict, personalize — sometimes faster than we can even explain what we’re trying to do. But in all this momentum, have we paused to ask: Are we solving the right problem?</p><p>AI is impressive, but it’s not magic. It’s a tool — a powerful one — but still just a tool. It doesn’t define strategy, understand your customers, or know what success looks like. That’s still on us.</p><p>With AI in the mix, there’s a subtle trap: we start with the capabilities, not the needs. “What might we do with this model?” quickly turns into “What should we do with it?” — and sometimes skips over “What problem are we actually trying to solve?”</p><p>Let’s be honest, it’s tempting to let the shiny object take the wheel. But if we chase the tech without a clear destination, we risk building clever things that don’t matter. Or worse, things that create noise instead of value.</p><p>The fundamentals haven’t changed. We still need to be rigorous in identifying real user pain points. We still need to validate whether our ideas are meaningful, usable, and valuable. AI can help us do that faster — but it won’t do it for us.</p><p>So ask yourself and your team:</p><p>Are we letting the tool dictate the direction?</p><p>Have we gotten clearer on the problem — or just fancier with the solution?</p><p>If AI weren’t available, would this still be worth building?</p><p>The promise of AI is real. But it’s only as good as the clarity behind it. Strategy still matters. Critical thinking still matters… at least for now :)</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8f91567a3f0c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/ai-doesnt-replace-insight-it-rewards-it-8f91567a3f0c">AI doesn’t replace insight. It rewards it.</a> was originally published in <a href="https://medium.com/2ejk">2ejk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI then and now: how past insights resonate in the age of GenAI]]></title>
            <link>https://medium.com/2ejk/ai-then-and-now-how-past-insights-resonate-in-the-age-of-genai-01b9158b3a5a?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/01b9158b3a5a</guid>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[desıgn]]></category>
            <category><![CDATA[trust]]></category>
            <category><![CDATA[gen-ai-revolution]]></category>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Fri, 14 Feb 2025 04:45:14 GMT</pubDate>
            <atom:updated>2025-02-14T04:45:14.734Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HsSleM0Q5TUws2eICV3Bhw.jpeg" /></figure><p>In 2019, AI was already transforming industries, but generative AI and large language models were still emerging concepts. Today, those technologies are reshaping the way we work, create, and interact. This series of articles from that time explores AI’s potential and challenges — discussions that remain just as relevant, if not more so, in the era of GenAI.</p><h4>In AI we trust?</h4><p><em>How might we design intelligent systems that inspire trust?</em></p><p>We’re presently experiencing a major shift in technology led by developments in artificial intelligence (AI). While we place our trust in technology every day, with AI, we’re starting to receive recommendations by machines. As a result, our perceived risks, whether real or imagined, raise new questions that must be answered before we can trust these systems: <em>Does the system value the same things that I do? How does it make decisions? Am I safe?</em></p><p><a href="https://medium.com/dish/in-ai-we-trust-75a7f3b38269">Read the full article</a>.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*l6Nt7eMpWZfaRQCm3NgosA.png" /></figure><h4>Design for trust: principle #1</h4><p><em>User expectations and perceived risks drive trust requirements.</em></p><p>Here, we dive deeper into the first principle, grounded in empathy for our user with respect to how their mental models manifest as expectations and perceived risks.</p><p><a href="https://medium.com/dish/design-for-trust-principle-1-352ae935728c">Read the full article</a>.</p><h4>Design for Trust: Principle #2</h4><p><em>Trust is a dynamic relationship. It is tentatively granted, then tested over time.</em></p><p>Here, we dive deeper into the second principle that addresses the dynamic and tenuous nature of trust during the customer journey.</p><p><a href="https://medium.com/@paulbchang/design-for-trust-principle-2-822cc01801e9">Read the full article</a>.</p><h4>Design for Trust: Principle #3</h4><p><em>When building trust, motivation is more powerful than demonstration or explanation.</em></p><p>Here, we dive deeper into the third principle that explores visceral trust, how it is ingrained and how it can make interaction more smooth.</p><p><a href="https://medium.com/@paulbchang/design-for-trust-principle-3-3827da3b5866">Read the full article</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=01b9158b3a5a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/ai-then-and-now-how-past-insights-resonate-in-the-age-of-genai-01b9158b3a5a">AI then and now: how past insights resonate in the age of GenAI</a> was originally published in <a href="https://medium.com/2ejk">2ejk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Ten Principles for Patient-centered Design]]></title>
            <link>https://medium.com/2ejk/ten-principles-for-patient-centered-design-e6fed89e49b8?source=rss-8162ce5d8ee9------2</link>
            <guid isPermaLink="false">https://medium.com/p/e6fed89e49b8</guid>
            <category><![CDATA[clinical-trials]]></category>
            <category><![CDATA[patient-experience]]></category>
            <category><![CDATA[design-principles]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[patient-centricity]]></category>
            <dc:creator><![CDATA[Paul Chang]]></dc:creator>
            <pubDate>Thu, 06 Jun 2024 06:22:22 GMT</pubDate>
            <atom:updated>2024-06-06T06:22:22.262Z</atom:updated>
            <content:encoded><![CDATA[<h3>10 Principles of Patient-Centered Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TbC3PI2dQUKFYmDegi78QQ.png" /></figure><p>In 2019, I had the privilege of working with <a href="https://www.linkedin.com/in/aliciastaley/">Alicia Staley</a>, patient advocate and three-time cancer survivor, to develop a workshop that would eventually evolve into a Patient Insights Board where she and our design team engage with patient advocates to gain insights on important patient-centered topics. Through these workshops, we’ve been able to appreciate the challenges that patients face with their healthcare journey and specifically when joining clinical trials.</p><p>Our childhood memories of jabs, pills and procedures inform our visceral response to doctor’s visits. In the best case, we‘re going for a preventative checkup. In other cases, there’s a problem — and the visit can be stressful. Beyond medical visits, clinical trials present a lifeline when standards-of-care have proven inadequate. Some of us, like Alicia, have been through the process, while many of us know someone who’s reached this crossroad. Sometimes the outcome of a trial may not benefit them directly, yet they’re driven by the desire to help others who may follow. We hear stories and witness bravery, optimism, resilience—heroism.</p><p>The 10 principles of patient-centric design are for these heroes. The principles have been developed over five years of interactions with patients, patient advocates, healthcare professionals, and clinical trial administrators. They’re meant to guide contributors to the patient experience, to be the calm in the chaos of each patient’s healthcare journey. We hope you find them useful.</p><h4>Principle #1 Build trust</h4><p><em>Trust is a dynamic relationship. It is tentatively granted, then tested over time. Manage patients’ expectations and perceived risks throughout their experience.</em></p><p>Transparency is often referenced as a key ingredient to trust building and it’s no different here. Be open and honest about personal information and data sharing, potential conflicts of interest, and the risks and benefits of participation. Educate patients of anticipated burden, both financially and with respect to time commitment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9iXFtiSheba3I2QeGlLtBA.png" /><figcaption>Build trust by providing easily scannable resources to help patients understand what they’re getting themselves into.</figcaption></figure><p>Build trust by opening channels for feedback and communication. This demonstrates a willingness and capacity to listen, learn and support.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*kYrbvcM8En2Rb8xHETmjnQ.png" /><figcaption>Regular patient connections with a clinician, whether through televisits or in-person visits, are crucial for building trust during clinical trials by fostering rapport and clear communication.</figcaption></figure><p>For a design deep dive, see how we <a href="https://medium.com/@paulbchang/building-patient-trust-83499357d24d">create trust empathy maps </a>to identify trust-building opportunities.</p><h4>#2 Develop a good bedside manner</h4><p><em>Put patients at the heart of everything you do. Make the patient feel cared for, comforted and human before, during, and after their treatment or trial.</em></p><p>Start with a step-by-step agenda and provide the patient with a sense of place and time. This may seem elementary, but there are many examples where the patient is left to wonder “what’s next?” or “how much longer?”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1LR_wmk-sJ0uXK5aIoli2w.png" /></figure><p>Inevitably, despite every effort to guide and nurture the patient through an experience, some will inevitably lose their way. In these cases, show the human on the other side by providing convenient help and support.</p><h4>#3 Be inclusive</h4><p><em>Good design is accessible to all.</em></p><p>Patient diversity is essential in developing meaningful outcomes in clinical and medical research because it ensures that findings are applicable across abilities, backgrounds, medical conditions and cultures, leading to more accurate and effective healthcare interventions.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*aeGNWv5qugvOgirgzaHSwg.png" /><figcaption>Be explicit about patient limitations supported (Source: <a href="https://inclusive.microsoft.design/">Microsoft Inclusive Design</a>).</figcaption></figure><h4>#4 Empower with knowledge</h4><p><em>Keep the patient informed and educated about their options so they can make good decisions.</em></p><p>Patients should be prepared to participate. This means providing educational resources during the decision making process and at touch points throughout the process. And, don’t assume that the patient understands. Always confirm their understanding.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QQjLc33EsUv9apt5tulutg.png" /><figcaption>Provide a no-pressure comprehension checkpoint.</figcaption></figure><p>When the process or procedure is complete, be sure to share data back to the patient in a format that’s easy to understand, draw insights from, and allows the patient to share data with selected family members, their primary care provider and healthcare teams.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1TtC8_9YbkxCYzUd02Pxhg.png" /></figure><h4>#5 Give the patient control</h4><p><em>Allow the patient to move at their own pace. Encourage interaction and dialogue, including feedback.</em></p><p>Empower patients to control their healthcare journey by providing them with flexibility to participate on their terms, choosing where, when and how they engage. Allow adequate time for patients to ask questions and to make informed, shared decisions with their loved ones and healthcare team.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0KXKe7UY6PJd2FY8pVyVkg.png" /><figcaption>Embracing multi-channel access empowers users with flexibility, enabling them to engage with the experience on their own terms, whether through web, mobile, or other platforms.</figcaption></figure><h4>#6 Celebrate wins</h4><p><em>Acknowledge patient achievements and motivate their next steps.</em></p><p>When a process is completed, don’t just move on to the next task. Take the time to recognize each milestone in the process — high five! In gaming terminology, that’s called celebrating “win states.”</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9Jikk5zclt9i5zP_81JGYg.png" /><figcaption>Celebrating accomplishments at various checkpoints throughout the patient’s journey is important as it acknowledges progress, boosts morale and reinforces the significance of each milestone (Win-state diagram source: <a href="https://octalysisgroup.com/2015/02/the-strategy-dashboard-for-gamification-design/">Octalysis</a>)</figcaption></figure><h4>#7 Don’t make them think</h4><p><em>Every element of a design should be in service of the intended patient action or outcome.</em></p><p>Reduce cognitive load whenever possible. While you may think a designed interaction makes perfectly good sense, it’s but one of many tasks in a patient’s busy day. They’re not reading, they’re scanning during a spare moment. Pursue simplicity relentlessly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bPGJJI9mBrhtgSfFAhRYng.png" /><figcaption>On the myMedidata platform, the patient experience has been distilled to a single “Next Activity” at any point in their clinical trial journey.</figcaption></figure><h4>#8 Don’t reinvent the wheel</h4><p><em>When possible, use standard patterns and conventions.</em></p><p>Utilize familiar design patterns to tap into patients’ pre-existing mental models, offering a sense of comfort and ease of use. There are places to be creative, but navigation and typical computer interactions are not two of them.</p><p>On the other hand, intuitive patterns go beyond familiarity by anticipating patients’ needs and behaviors, often employing innovative or unconventional design solutions that feel natural and effortless.</p><p>Pay attention to when familiar will suffice and when non-standard yet intuitive designs are warranted.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dsrhsWLNN1fkfGpDtSZYBA.png" /><figcaption>Utilizing spatial and visual cues tailored to patients’ mental models enhances comprehension and interaction by providing intuitive pathways, fostering engagement, and reducing cognitive load.</figcaption></figure><h4>#9 Choose words carefully</h4><p><em>Messaging and instructional content are critical to the patient experience.</em></p><p>Writing is often overlooked in the design process, yet it’s one of the most critical. It’s the aspect of our designs that patient advocates have commented on most often.</p><p>Speak in natural, non-technical language. Find the balance between casual, friendly language and a tone that respects context.</p><p>And, consider how certain words may fall upon patients’ ears. Historically, participants in clinical trials have been referred to as “subjects.” This terminology still exists and fails to acknowledge the patient’s voluntary role as a participant and partner in the process.</p><blockquote>Am I data, or am I going to be seen as a real person?*</blockquote><blockquote>When I hear the word subject, I think of a criminal.*</blockquote><blockquote>I feel like one in a <strong>million</strong>, not <strong>one</strong> in a million.*</blockquote><blockquote>I think of an inanimate object—something that isn’t a person.*</blockquote><p>*Quotes from Medidata Patient Insights Board members</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*4GNg2kRZ3Hp2yayzcPQG3w.png" /><figcaption>Friendly, human language goes a long way towards building trust and engagement.</figcaption></figure><h4>#10 Pay attention to the details</h4><p><em>Proper typography and consistent design elements are critical to a trustworthy experience.</em></p><p>A consistently designed experience, from branding, to communication style, right down to font selection, all play a role in providing a trustworthy experience. Patients may enter the system from a variety of touchpoints (posts, email, notifications, etc.) and you want them to know they’ve come to the right place.</p><p>Beyond consistency, quality is essential. If you don’t bother to dot your i’s and cross your t’s literally, what does that say for your healthcare practices?</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jyB-T3NGiAEgF4ie7-QzaA.png" /><figcaption>The design style changes in this handoff from clinician to patient, keeping the patient in an environment consistent with the rest of their experiences.</figcaption></figure><h4>Final thoughts</h4><p>Patient-centered design is a powerful approach to improving the patient healthcare journey. Trust building is the foundation on which all future interactions unfold. It’s built through transparency, listening and learning—by showing that there are humans on the other side. From here, patient empowerment is constructed through knowledge and control, and only through inclusivity can we ensure better outcomes for all.</p><p>We would love to hear your thoughts on how these principles resonate with your experiences, whether as a provider, designer or patient. Your feedback is invaluable in refining our approach and ensuring that future solutions truly meet patient needs.</p><h4>Acknowledgements</h4><p>Special thanks to Alicia Staley and the Patient Insights Board at Medidata for their time, dedication and inspiration; to Ben Berte and the Patient Cloud design team for their pursuit of better patient experiences, facilitation of patient-centered design workshops, and to Jesi Zhang for the design examples presented here. In memory of Linnea Olson and Sheila Johnson whose perspectives greatly influenced our understanding and development of these principals.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=e6fed89e49b8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/2ejk/ten-principles-for-patient-centered-design-e6fed89e49b8">Ten Principles for Patient-centered Design</a> was originally published in <a href="https://medium.com/2ejk">2ejk</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>