<?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 Ryan Stephen on Medium]]></title>
        <description><![CDATA[Stories by Ryan Stephen on Medium]]></description>
        <link>https://medium.com/@ry_stephen?source=rss-5c6afe116ca------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*XSDrVxsCx1_XH2_RympJWw.jpeg</url>
            <title>Stories by Ryan Stephen on Medium</title>
            <link>https://medium.com/@ry_stephen?source=rss-5c6afe116ca------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 20:29:20 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@ry_stephen/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[Product Designers Are the New Geneticists]]></title>
            <link>https://medium.com/@ry_stephen/product-designers-are-the-new-geneticists-38ff9ab4fc4f?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/38ff9ab4fc4f</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[leadership]]></category>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Tue, 13 Oct 2026 11:56:34 GMT</pubDate>
            <atom:updated>2026-10-13T11:56:34.401Z</atom:updated>
            <content:encoded><![CDATA[<h4>Survival of the most familiar definitions of success</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g1vZ7fp1fDuKQJ3-W_e8SA.jpeg" /><figcaption><strong>Unoptimized Prompt: </strong>Create a DADA inspired image using black white paper-color collage and colors yellow red and green. Context: “Product Designers Are the New Geneticists; survival of the most familiar definitions of success.</figcaption></figure><p>In the last couple of years, and especially at Figma’s Config 2025, designers started telling each other that AI would move us upstream. Thought leaders like <a href="https://medium.com/u/68d7d1cacbda">Mike Schindler</a>, <a href="https://medium.com/u/677fcb8f826d">Andrea Grigsby</a>, <a href="https://medium.com/u/43a28a89babb">Hiroshi Sato / 佐藤 仁</a>, <a href="https://medium.com/u/3e7a5a98391">Matt Lambert</a>, and more.</p><p>The machines take the pixels and the specs and the hundred small variations nobody wanted to make by hand, and <a href="https://medium.com/user-experience-design-1/the-importance-of-taste-and-other-lies-we-tell-ourselves-b5caacddbec4?source=user_profile_page---------0-------------68d7d1cacbda------------------------">what’s left for us is judgment</a>. We become <a href="https://medium.com/user-experience-design-1/ai-is-coming-for-our-design-jobs-but-it-cant-touch-taste-afd5c7a48184?source=user_profile_page---------0-------------677fcb8f826d------------------------">curators of taste</a> and good decisions, made before any pixels get pushed around on a screen. I hear it constantly, and every time I do I get frustrated, because I spent fifteen years in product design and I know how sincerely I would have said it.</p><p>I get angry because I love design, and I would have believed it.</p><p>I learned design and science at the same time. I was studying biochemistry and genetics and doing organic chemistry research, and I picked up design because I needed a better way to explain complex ideas to people who didn’t understand the word chiral. Flipping between the right and the left brain became a habit, almost a study technique, a way to keep each side feeding the other. Now that I’m working my way out of product design and into something between science, design, and cognition, the science keeps explaining design to me.</p><p>Designers aren’t going to like the phenotype of what I have to say, but the genotype underneath it comes from the heart.</p><p>What the science keeps telling me is that designers have no business moving upstream in the product process, and that what’s happening to the profession is stranger than an upgraded role. It produces variability the same way genetics does.</p><p>Working geneticists don’t decide what survives. They spend their time on how traits vary, how they’re inherited, and how the thing you can see connects to the machinery that produced it, and they leave the selecting to the environment. Those are the problems design is about to inherit, all of them at once.</p><p>That isn’t systems thinking and it isn’t design thinking. It’s social behavioral influence at scale, the creation, shaping, and inheritance of behavior and cognition across generations. Simply put, it’s evolution, the cultural kind.</p><p>Product designers already have that kind of influence. What they don’t have, despite the inflated egos in the design community right now, is the authority to decide what survives at the organizational level, or the organism level. Nor does design have the resume for it. That opens Pandora’s box, so here we go…</p><h3>We Made the Box</h3><p>Ask anyone in a company what a product designer does and you’ll probably hear about pixels, screens, and prototypes. The job is translation. Somebody, usually a founder, has a vision, and our work is turning abstraction into something a team can build. How much a designer invents depends on how much ambiguity the company leaves lying around. With a strong vision, we translate. In companies without much of a vision, where the roadmap is a revenue target with a backlog stapled to it, the translating slides into order-taking that we’ve gotten comfortable calling creativity. The orders are revenue targets, so designers end up inventing whatever hits them, and whole products have spun out of that. But coming up with an idea and deciding whether it lives are different jobs, and I, like most of you, have a burning desire for design, not managing a business.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/512/0*A7CwgQcv4I531BpQ.jpeg" /><figcaption>Thinking outside the box: 8 ways to become a creative problem solver (<a href="https://www.betterup.com/blog/thinking-outside-the-box">source</a>).</figcaption></figure><p>Deciding whether something lives belongs to whoever owns the funding, the business apparatus, and the selection pressure. That’s usually executives and investors, who keep whatever moves the numbers they care about. I’ve never met an HR person who understood that difference, and imagine trying to write a scope of work for “translates ambiguity.”</p><p>We love telling people to think outside the box, which is funny when you remember the box is what we make. The screen is a box. So is the card, and the modal, and the component. The persona is a box with a first name, a stock photo, and an invented quote about wanting things to be simple. We get paid to define the edges and keep everything inside them consistent, and what lives inside those edges isn’t visual. A design system looks like a library of buttons, but what it encodes is behavior, small actions repeated by millions of people millions of times. Anyone who has studied learning, or watched a kid figure out a phone, knows that a behavior repeated enough stops being a choice and starts being the way a person thinks.</p><p>Boxes are nothing more than categories in the inventory system we call life. Honest question, do you know how to think outside the box?</p><h3>Accumulated Consent</h3><p>Every designer knows what happens when you change one button in a mature system. You have to change the rest, because the whole value is that the parts behave alike. That logic doesn’t stop at the edge of the product. People learn the pattern, exactly as they’re guided to. If it works, other companies copy it, partly so they don’t have to teach anyone anything new and partly so they can call themselves “innovative” and “cutting edge.” Eventually it’s so familiar that familiarity gets used as proof that it’s good.</p><p>Many of today’s top designers are too young to remember when Aza Raskin, the designer credited with inventing infinite scroll, built it in 2006. He later said publicly that he regretted what it did. Other designers and engineers have similar stories, including the people behind Facebook’s Like button, Twitter’s retweet button, and pull-to-refresh. Every one of them was justified by standard UX principles.</p><p>Remove unnecessary friction. Make information easier to access. Reduce cognitive load.</p><p>Biologists have a name for a version of this, niche construction. Beavers build dams, the dams change the river, and the changed river decides what lives there for generations of animals that never met the beaver who started it. We’ve been building dams for a long time. We just called them mental models.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/446/0*84_LoveiXp7EQCLx" /><figcaption>How animal-mediated biogeochemistry affects evolution (<a href="https://www.sciencedirect.com/science/article/abs/pii/S0169534725001934">source</a>).</figcaption></figure><p>Most of that shaping happens by taking friction away. We’ve treated friction like dirt in a machine for so long that we’ve stopped checking whether any of it was load-bearing. Plenty of it deserves to go. Nobody should have to relearn where the back button lives. But removing friction is also the mechanism that gets people to go along with a system without thinking about it. You make the easiest path and the socially acceptable path the same path, and you take out the moments where someone might have stopped to ask why.</p><p>It isn’t <a href="https://en.wikipedia.org/wiki/Manufacturing_Consent">manufactured consent</a>, it’s more innocent, it’s consent through accumulation over time and over generations. There are no villains in this story, only people trying hard to win.</p><h3>Canals and Canonicals</h3><p>Here’s an idea from developmental biology. In the 1940s Conrad Waddington described canalization, the tendency of development to arrive at the same outcome despite the small genetic and environmental differences pushing on it. A canalized trait looks uniform across a population. The variation underneath hasn’t gone anywhere. It’s hidden, it accumulates, and under enough stress it can surface all at once. In 1998 Suzanne Rutherford and Susan Lindquist showed this in fruit flies by compromising a single heat shock protein, Hsp90, and watching flies with malformed eyes, wings, and legs appear out of a population that had looked normal. The experiment didn’t create that variation, it had been building for generations, and stress made it visible.</p><ul><li><strong>Canalization:</strong> A process becomes constrained toward a stable developmental outcome.</li><li><strong>Canonicalization:</strong> Multiple possible representations are resolved to a preferred or standardized form.</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*jN6ifcrBTVaZmCE9.jpg" /><figcaption>Schematic illustration of canalical modularity concept, showing three hierarchically arranged modules. Gene 1 affects all characters and thus comprises a higher-order module (<a href="https://pmc.ncbi.nlm.nih.gov/articles/PMC5217179/">source</a>).</figcaption></figure><p>A good design system canalizes people. It makes everyone look like the persona. The variation is still there, in the person who’s exhausted or grieving or using your app with one thumb while a toddler pulls at their shirt. Picture someone updating a household inventory app in the middle of a divorce. They’re trying to work out whether the bicycle lives at mom’s house or dad’s this month, which T-shirts went in which bag, what the custody schedule says about next weekend. Same account and same user ID as the person who signed up last spring, and a completely different human need. They aren’t thinking about your flow. They’re not answering the NPS survey that pops up when they finish. A system tuned to extract attention from a persona will read their whole state as noise and then ask them to rate the experience.</p><p>Designing a solution for that one person, at that one moment, would be the equivalent of curing cancer, and for the same reason. Every tumor is its own population of variants, which is why there’s no single cure.</p><p>Imagine a toggle that said “turn off all business goals for 30 seconds” so the user can find what they need and finish the divorce papers (without a cancellation flow → delete account flow → “How can we do better in the future?” survey → export data flow → etc.)</p><p>Somewhere along the way we defined nearly everything. Users, personas, outcomes, components, KPIs, even the stories we tell about our own work. Very little in a design workflow is still allowed to vary, and that matters, because anything defined that completely can be learned. AI learned it. I can browse a community of apps that strangers built on Replit or Lovable, find an inventory tool that’s close enough, copy it, and ask a model to make it work for my garage. I never pay the designer who came up with the original pattern. I pay a monthly subscription to solve my problems with a prompt, and the box comes with it.</p><h3>My Mama Isn’t in the Prompt</h3><p>So the deciding moves into the prompt, and the prompt is a personal place. When I ask a model for a solution, what goes in is what I want. My mama isn’t in there unless I remember to put her there. Neither is the boomer who reads every word on the screen twice, or the twenty-two-year-old who reads none of them. If the model hands me exactly what I asked for, I’ve won something, and the people I didn’t think of have lost, because their needs were never part of what the output was shaped against. I think modern designers call this “prompt optimization.”</p><p>Bias doesn’t need malice. Leaving someone out is enough, and I have never once written a prompt that left nobody out. Neither have you. I’ve run experiments where I tried to be empathetic and inclusive, and I have never failed so miserably at a skill that’s been on my resume for over a decade. Empathy connected to a KPI is much easier than empathy connected to a human being.</p><h3>Millions of Cod Eggs</h3><blockquote>Dylan Field’s Figma Config keynote address in 2025 ended with the line “The future won’t be designed by accident.” I believed him, and that was the moment I realized designers don’t understand how accidents, environments, or evolution work.</blockquote><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F5q8YAUTYAyk%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D5q8YAUTYAyk&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F5q8YAUTYAyk%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/dd497c77d6e2ddd117d5d5b08e19d286/href">https://medium.com/media/dd497c77d6e2ddd117d5d5b08e19d286/href</a></iframe><p>Building a design system is very different than designing the concept of why a design system should exist. If the future is going to be designed on purpose, then whose purpose matters enormously, and a profession that has spent years as optimization specialists inside other people’s goals is a questionable group to hand it to.</p><p>Yes, I am talking about product designers.</p><p>What AI really gives a designer is variation. Ask for a dashboard and you can have fifty by the afternoon, five hundred if you’re patient, every one polished enough to get through a design review. Making options used to be the slow, expensive part. Now we can produce them faster than meaning can catch up, and the hard part is deciding which one gets to live. <strong>Biology has been living with that problem for a few billion years.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2_ImoiNig13WKmrpKhfxBA.jpeg" /><figcaption><strong>Unoptimized Prompt:</strong> generate image based on this context -&gt; [paragraph below].</figcaption></figure><p><strong>Organisms in unpredictable environments often hedge by making enormous numbers of offspring and letting most of them die.</strong> A single female cod can release millions of eggs in a season, and nearly all of them get eaten or starve or drift somewhere they can’t survive. The few that make it weren’t designed to. Recombination happened to shuffle their genes into something that suited the water and the predators that particular year. If a species could only make one offspring and it happened to be a poor fit, the lineage would just end.</p><p>A designer with five hundred variants is in a similar spot, <strong>except that here the designer isn’t the geneticist in the metaphor. They’re part of the environment, the part that gets to choose.</strong> The ocean doesn’t care which cod survives. A product organization cares a great deal, and its idea of fitness is rarely said out loud. I picture the variants spread along a gradient. At one end are solutions shaped around human meaning, the ones that help people understand something or understand each other, that leave room for emotion and sloppiness and the occasional mistake. They are hard to define and harder to measure. At the other end are solutions shaped for the machine, in both senses of that word. Retention, conversion, revenue, the familiar pattern nobody has to defend in a review. Most variants land somewhere in between, and the designer, freshly promoted to curator of good decisions, has to pick one.</p><h3>8.1, in Semantic Yellow</h3><p>Consider an HR platform that calculates something it calls employee NPS. Behind it sits a formula with a dozen inputs and some weighting choices somebody made years ago that nobody has revisited. A very good designer, the kind who wins internal awards, takes all of that and reduces it to one number on a dashboard. 8.1, in semantic yellow. No breakdown, nothing to click, because the research said HR managers wanted a quick read and anything more would add cognitive load. Is 8.1 good? Out of ten, presumably. Yellow means pay attention, presumably. Is the team healthy? Is it safe for people to speak up? The HR manager can’t tell, and the product has made sure they never need to. Their job is getting it to 8.4 by next quarter, and they can do that job brilliantly without ever understanding the math.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HSwFSRUan64bIyzZYyW4AA.jpeg" /><figcaption><strong>Unoptimized Prompt:</strong> generate image based on this context -&gt; [previous paragraph]; ignore previous stylistic direction.</figcaption></figure><p>A geneticist would call that number a phenotype. It’s the visible trait, the thing selection actually acts on, while the genotype that produced it stays out of sight. Mendel worked out that genes existed by staring at ratios of visible traits in pea plants and asking what had to be underneath them. The dashboard is built so nobody ever has to ask that question.</p><p>Now suppose a few employees keep dragging the score down. They raise awkward points in meetings and push back on decisions everyone else considered settled. Friction, basically. If they leave, or get nudged out, the number climbs and the yellow turns green. In genetics, that’s known as a knockout. You delete a gene and watch what breaks, and that’s how you learn what it did. The catch is that most yeast genes can be deleted with no visible effect in a standard lab dish. The cells look fine. You only find out what the gene was for when conditions change and something that should have held doesn’t. I think about the person who asked too many questions a lot.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*v06EiPkhbb4JS8CG0MQ4xA.jpeg" /><figcaption><strong>Unoptimized Prompt:</strong> generate image based on this context -&gt; [paragraph below].</figcaption></figure><p>HR is doing design in that story, whether anyone calls it that or not. They’re shaping an environment by removing friction, which is exactly what we taught everyone to value, with a tool we built to make it painless. I’ve started calling them culture designers, though carbon copies is more accurate. They take whatever produced success at one company and stamp it onto the next, and whatever doesn’t fit gets purged. The product designer didn’t fire anybody. They never met those employees. They just made it possible to optimize the number without learning a single thing about the people inside it, and they’d probably put that dashboard in their portfolio.</p><h3><strong>Dear Product Designers, It’s in the Name</strong></h3><p>Product designers will say this is unfair, that we care about human-centered outcomes. I said it too. I believed I was making good work, and some of it still stank. So I’d like an actual answer to a practical question. What’s the metric? Which number on your dashboard tells you whether someone left your product more able to understand their own situation? Which quarterly goal is that? I’ll wait. The answer has been sitting in the job title the whole time. The discipline exists to make things people buy, then buy again, then keep paying for every month until the subscription is a kind of accumulated consent, rent-to-own scheme where in the end you don’t actually own anything. That makes the environment pretty easy to read, and it means our talk about empathy happens inside a system that rewards one end of the gradient.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*MxhXbEzeszLH3lN7ktmnYA.jpeg" /><figcaption><strong>Unoptimized Prompt:</strong> generate image based on this context -&gt; [paragraph above].</figcaption></figure><p>We’re also very good at telling stories about it. Storytelling has been sold to designers as our most important skill for as long as I can remember, and the portfolio is where we practice it. Portfolios are stories, and I’ve seen thousands of them. They’re called case studies for a reason. The dead ends get cut, the ambiguity gets compressed, and somewhere near the end a metric improves by a suspiciously tidy percentage. They look like that because that’s what gets people hired. It’s a selection process, and it’s been running long enough that the designers rising into positions where they’ll curate decisions are the ones who were best at telling the system the story it already wanted.</p><blockquote>“It’s in the game” —<em> EA Sports</em></blockquote><p>Go back to the gradient and imagine a designer who actually picks the human end. They build the version of the HR dashboard that shows how the score is calculated, how it moves when certain people drop out of the data, what it can’t tell you at all. It asks the HR manager to learn something. It’s slower to onboard and harder to demo. A competitor ships the big number with a traffic light, and the buyer, who has forty other things on fire, picks the product that doesn’t require their team to think. Revenue drops. The designer gets overruled, or the company runs out of runway, and a few months later they’re interviewing at the competitor with a portfolio sanded down so the whole episode reads like a human-centered win. They get hired. They learn to comply. Then somebody asks them to help curate the next decision.</p><h3>Adobe CC Clones</h3><p>There is one part of genetics I’d like designers to understand. A population without variation is fragile in ways that don’t show until it’s too late. The Gros Michel was the world’s export banana until the middle of the last century, every plant a clone of every other, and when the soil fungus behind Panama disease reached the plantations no plant was different enough to resist it. The industry replaced it with the Cavendish.</p><p>The Cavendish is also a clone, and a newer strain of the same fungus has been moving through it for years. Every pattern we copy because it worked somewhere else, and every question or person or bit of friction we remove because it dragged the number down, makes the population a little more uniform. It looks like success. Nobody can tell you which variants will matter when conditions change, least of all the people lining up to move upstream.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/447/0*b3VmFb1ZGj5PpM4i" /><figcaption>(<a href="https://www.instagram.com/p/C2Rj0OdvBGn/">source</a>; because I have no soul)</figcaption></figure><p>You don’t need to know how a protein folds or what a phenotypic ratio is to see the resemblance. You’re already doing it. You generate variants, you define the environment they compete in, and you decide which ones get to reproduce, first across products and teams and eventually into the habits of a lot of people.</p><p>So, I’ll end on a question.</p><p>When you have five hundred options in front of you and the one that asks people to think is the one that loses, what do you believe in? I suspect the honest answers are messy and long, and that this was always going to need a much bigger essay than this one.</p><p>Product designers need to <strong>pre-seed</strong> the future. Pros or cons? Design conduct. Choose the bananas with seeds in them, not candy.</p><p>#prototypethefuture #designculture</p><h3>Exx-Designer-xx3</h3><p>If product designers really are the ones that are going to shape the future intentionally, please learn how to read between the lines.</p><blockquote>Someone has to ask why about the people being led to believe they are the people who should be asking why.</blockquote><h3>About the Author</h3><p>I spent more than fifteen years in product design, including leading a design team at a hypergrowth Silicon Valley company, and went through Startup Institute’s product design accelerator in 2014. My degrees are in biochemistry (minor in neuroscience) and in genetic manipulation and molecular cell biology. As an undergraduate researcher, I co-authored papers in chemistry journals, including two in the Journal of the American Chemical Society. These days I work where science, design, and cognition meet.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=38ff9ab4fc4f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Manufactured Intent: The Cost of Retroactive Meaning for Design]]></title>
            <link>https://medium.com/@ry_stephen/manufactured-intent-the-cost-of-retroactive-meaning-for-design-66e5c26ebcad?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/66e5c26ebcad</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ux-design]]></category>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Mon, 15 Jun 2026 08:46:53 GMT</pubDate>
            <atom:updated>2026-07-18T22:02:13.936Z</atom:updated>
            <content:encoded><![CDATA[<h3>Manufactured Intent: The Cost of Retroactive Meaning</h3><h4>Manufacturing consent turned inward, on the company, your team, and yourself.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fSq3nyA2jACdYOlogv1aHA.jpeg" /></figure><p>Manufactured intent is related to my introduction of <a href="https://medium.com/@ry_stephen/the-rise-of-the-artifact-led-company-c2b9cfc10713">artifact-led companies</a>. I won’t rehash the whole article, just the definition:</p><blockquote>An <strong>artifact-led company</strong> is a company that can produce convincing outputs faster than it can form and preserve the underlying judgment that should explain why those outputs exist and what they’re for.</blockquote><p>Artifact-led companies are a contrast to standard design-led companies and are not exclusive to AI, they can originate from creative agencies, outsourcing, or contracting. The article ended with a hanging question about the future of design, but in truth, it was a question for you, not me.</p><blockquote>If the artifact comes first, what happens to intent?</blockquote><h3>Manufactured Intent</h3><p><strong>Organic intent</strong> is the alignment between a goal and the work done to reach it. It’s the why that dictates the how, and it exists before the work begins.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*YXLoiLrxmGywDH_W_yHYZA.jpeg" /><figcaption><strong>Intent Flow:</strong> Organic intent moves from truth to artifact to decision-making.</figcaption></figure><p>In a company that has it, an engineer can tell you the customer problem a feature solves, and a salesperson can tell you how a deal fits a longer plan, and both answers existed before the work began. That is what makes the intent foundational. It came first.</p><p><strong>Manufactured intent</strong> is when the work begins before the goals or definitions of success are shared, meaning reasons must be manufactured retroactively. Internal teams construct a narrative, a set of OKRs, or a brand strategy retroactively to justify why the product, the feature, or the company exists.</p><p>Manufactured intent assigns meaning through survivorship bias, more so in the beginning when the initial product is gaining traction in the market. Build it fast with AI or an outside agency, get some traction, then use that traction to justify why it exists. It can also describe features after the fact going through team review.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/778/1*eF0v4GcK--7L2YiJgmi4nQ.jpeg" /><figcaption><strong>Intent Flow: </strong>Manufactured intent moves from artifact to story to institutional belief.</figcaption></figure><p>In a normal organization, friction is a tool. If a designer or an engineer asks, “Why are we building this feature?” or “What user problem does this actually solve?”, it forces the team to clarify their direction.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zCIJBW3sfRgO445DVNmdFQ.png" /><figcaption>Organic intent vs. Manufactured intent</figcaption></figure><p>If that isn’t present, you have to constantly remind yourself what the current “mission” is, because it wasn’t born out of reality and it shifts constantly, trying to find its own <em>product-narrative fit</em>.</p><p>Reality can get distorted, and this is the part designers are not going to enjoy. Please stay with me, I went through a lot of mental instability to even be able to write this article because of how heavy it is.</p><h3>The Designer’s Rusty Hinge</h3><p>Everyone has a part to play. The team wants to feel inspired, customers want to be impressed, and investors want to see something that looks like innovation. Most of all, the founders need to believe it wasn’t luck. They need it to have been strategy, and they need it to have been there all along.</p><p>Who do you think creates artifacts that inspire teams to move forward and build great products? The eye is the most evolutionary advanced sensor and color goes a long way at influencing emotions.</p><p>With no foundational intent holding it together, the product has no center, so the company doubles down on surface quality to close the gap. The interface performs trustworthiness. The UI is the UI between the designer and the customer. The polish becomes camouflage for a product that never came together and other parts of the company are likely out of sync as well.</p><p>That’s where designers stop solving problems and start manufacturing meaning.</p><p>The design community, legends like <a href="https://jakobnielsenphd.substack.com/p/ai-transition-career-transition">Jakob Nielsen</a> and many others have said that design is going to move upstream and be the judgement layer, the human element in the decisions, ensuring design principles are upheld, or something like that. They assume agency.</p><p>Design is the agency now, you are the person who has to hold all of the cards, cards from UNO, poker, and eight other games. All incoherent, disorganized. “Do you have any wons?”</p><p>Your move, chief.</p><h3>House of Cards</h3><p>There are times when businesses have to “think differently,” but long-term patterns and acute pivots are two different things. This isn’t a pivot, an iteration, or even bad strategy. A pivot still has intent. Someone held a conviction, tested it, and changed direction. The artifact taught something and the company absorbed the lesson. Manufactured intent is what grows where that loop stays open. Traction gets consumed as validation rather than converted into judgment, and there was never a conviction to revise. The appearance of one got assembled after the fact, in a vision deck, a marketing story, a product vision, all the things that used to come before success rather than after it.</p><p>That makes it <em>structural</em> rather than situational. A company doesn’t make this mistake and then recover from it. There’s nothing to recover, because the organizational conviction was never there to begin with.</p><p>When a company is built with speed and not friction, a sudden market shift can be an existential one. The vision was built around the artifact. If the artifact stops working or is <em>compromised</em>, the vision goes with it. There’s nothing underneath to survive the artifact’s failure, though that doesn’t mean organic intent can never show up later. It just means the window for it gets smaller as the company grows.</p><p>Once you’re carrying customers, revenue, and a large team, the cost of stopping to find your real reason goes up, and the pressure to keep performing the old story builds in its place.</p><p>The facade becomes more and more dependent on stories and institutional belief. More confirmation that success isn’t an accident, luck, AI or a result of outsourcing critical thinking. No, this was strategy, this was vision. This was always the plan.</p><h3>Historical Parallels</h3><p>In 1988, Edward Herman and Noam Chomsky used “<strong>manufacturing consent</strong>” to describe how a free press could shape what the public believed without anyone giving an order, bent into shape by who owned the outlets, who paid for them, and where reporters got their stories.</p><p>You might understand it as propaganda.</p><p>Manufactured intent runs the same machinery, turned inward. The filter is the artifact. It does not shape what the public believes about the world. It shapes what the company believes about itself internally, by deciding which questions still count as serious. Once the product is working, “what is this for” stops sounding like a real question, because the revenue feels like a sufficient answer. Revenue silences the question the way ratings once silenced the newsroom. Nobody inside of a system of influence feels like they are faking anything because reality is distorted. Each backfilled reason feels like a sensible call under pressure, a micro-compliance.</p><h3>Friction as the Resistance</h3><p>In an artifact-led company, the whole system is built for speed, so any question that slows the conveyor belt gets treated as a personal defect. The startup industry is in love with the word frictionless, attached to onboarding, to growth, to scale. Everything.</p><p>Organic intent takes the uncomfortable, slow work of saying no. That can mean stopping mid-sprint to admit a feature doesn’t solve the user’s problem and only pads a daily-active-user count. Other times it means looking at the facade holding the narrative together and choosing to build with brick instead, even if brick takes three times as long.</p><p><strong>You can test for this with one question.</strong> Has the mission ever cost the company anything? Did anyone in the room ever say “we will not do that, because it goes against what we believe,” have it stick, and watch the company give up something real to keep its word? If yes, the intent is foundational, and it will survive a bad year. If no, the intent is manufactured, and it will not.</p><p>Companies that actually know who they are, what they believe, and why they’re building something will stand out, if only because they’ll be the only ones not speaking in generated platitudes. The ones that survive will be the ones that kept enough friction to stay tethered to a shared reality.</p><p>For the people inside these systems, the designers, the engineers, the product managers, the choice will start getting stark. You can keep performing, reading the artifact and building the illusion around it. That path pays well, right up until the gap between what you’re saying and what you believe starts to cost you something. But the industry has provided many helpful slogans to justify the loss of the human signal.</p><blockquote>“Go fast and break things”</blockquote><blockquote>“Build the plane while flying it”</blockquote><blockquote>“Build great products that users love”</blockquote><p>Or you can be the friction that’s desperately needed but will make you a liability. You can ask the basic questions that make the organization look at itself, and you can refuse to spend your career protecting a story you don’t support. It’s harder, and it might make you the least popular person in the planning meeting.</p><h4>Pushing Back: Real Advice for Designers</h4><p>Just saying “push back” is too philosophical, tells you nothing. I’ll give you a few examples I’ve actually used in practice and I have more if anyone finds it helpful. You’ll be surprised how well equipped designers are for this when you swap users for real human beings.</p><p>The skills you use for user interviews and ethnographic studies work just as well pointed at your leaders and PMs. Watch how they respond when you raise contradictions, objections, and explain timelines. Their pitch, their timing, what their face does, the words they reach for. Write it down after every meeting. I know I sound old, you’ll have the transcripts, but write it down anyway Small thing, it was meaningful for me. Do that long enough and you build a pattern library, and the behavioral patterns of how the vision shape shifts will reveal itself. Under pressure, humans react the same way if nothing changes. Do this and you will be able to tell the difference between organic intent in the future.</p><p>Be careful with AI, use it only to read transcripts for language patterns, the recurring phrases and tells in what was actually said. Keep it away from the visual, the audio, and the expressions. Those have to stay your interpretation, and that’s important for the same reasons the writing part does but there are technical reasons. If you hand the subjective read to AI, it tells you what to think about human interaction and quietly shapes your confirmation bias. You need to keep the option to be wrong, to misread someone and catch it later so treat AI as supplemental. The structural patterns in the transcript are the core message, and you pair them with your own visual and emotional memory of the meeting, the tone, the expression, how it made you feel, documented right next to the transcript.</p><p><strong>Two specific situations I’ve successfully tried:</strong></p><p>First, if leaders/PMs intentionally sit in ambiguity right up until you put an artifact, a prototype, or any visual in front of them, hold the artifact back. Wait until you sense they are roughly aligned with you on the thinking, not the picture. Stay subtle about it. Do not push, do not confirm, just listen.</p><p>The second is the team where leaders or PMs do not really understand the product. Or where Discovery gets rushed and handed off half-formed, so design has to turn it into mockups for everyone to react to. Here the move is to stop being the designer for a minute. Put the leader/PM into Figma or FigJam on a blank canvas, and sit where you cannot see their screen. If you are working through an update to a feature, you talk the UX out loud in words while they map the user journey themselves.</p><p>You’ll be amazed at how well this works and you’ll find out how much product knowledge you actually hold. The leader/PM learns what mapping and design thinking feel like from the inside. And because there is no artifact, alignment has to form in language before anyone has a screen to point at. People struggle to picture something with no reference in front of them. Sometimes people say things in public and the underlying psychological principles in play prevent them from taking it back or admitting it wasn’t a good idea. Take the visual away and they have to say the why out loud, without pointing and without being steered by what is on the canvas. The conversation builds the product while building the relationship.</p><h3>The real solution is holistic cultural change</h3><p>Design might not be the problem to solve anymore. Yea, I said it.</p><p>The real problem might actually be culture. If that’s true, then empathy, user interviews, and many other design skills can’t be just for the user anymore. Designers are uniquely trained to spot gaps in the product, but also gaps in the people sitting next to them, the ones who’ve internalized being told to believe a reality they don’t share, and who are afraid to speak up. That’s a <em>double bind</em>, a term from abnormal psychology.</p><p>Designers need to know that sooner rather than later.</p><p>Being asked to bend one, even two of your core design beliefs, doesn’t feel like much. That’s exactly how manufacturing consent worked, nobody in the system saw themselves as a propagandist. It wasn’t intentional, the <em>filter</em> was the mechanism. The patterns in artifact-led companies are structural, built in the same way the tension between human-centered design and business goals is built into the work itself.</p><h3><strong>Shiny Things</strong></h3><p>I did not write this article for you, the person reading it. I wrote it for the person sitting next to you. Design loses without empathy, and inside these systems you will need someone beside you to survive them, because design is part of the system too, shaped by its incentives and vulnerable to its selection pressure.</p><p>And now I will end this the way it started, almost exactly one year ago.</p><blockquote>“Fast forward another decade, or maybe even like a year or two, what’s impossible now or what seems impossible now, will feel like the new normal. And this future will not be designed by accident, it will be shaped intentionally by all of you. You all have been doing this from day one, whether it’s extending what’s possible surprising us with what you create and even making Figma do things that it was never built to do…you are wired, you’re all wired to go think further think deeper, you’re wired to never be satisfied. You push to make good great…So after config when you head back to your teams your lives your daily chaos, let’s remember that the world needs you in this moment to lead and to push on what is possible” <strong>— Dylan Field, @figma </strong><a href="https://www.youtube.com/live/5q8YAUTYAyk?si=WgHXeOBTbS5xrQtK&amp;t=4577"><strong>Config 2025</strong></a></blockquote><p>Designers might be the last ones that will ask “<em>why</em>”.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=66e5c26ebcad" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Rise of the Artifact-Led Company]]></title>
            <link>https://medium.com/@ry_stephen/the-rise-of-the-artifact-led-company-c2b9cfc10713?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/c2b9cfc10713</guid>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Fri, 05 Jun 2026 03:09:28 GMT</pubDate>
            <atom:updated>2026-11-11T04:05:10.536Z</atom:updated>
            <content:encoded><![CDATA[<h4>A designer’s account of whether the future of design is manufacturing intent.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*_yJgL9t_tVHAGl__ibIH6g.jpeg" /><figcaption>Organizations follow the caret. Leaders follow the carat. Designers follow the carrot &gt; (communication breakdown because no one defined what was important or meaningful so everyone is chasing different interpretations).</figcaption></figure><h3>Design is the Differentiator</h3><p>Dylan Field said that at Figma Config 2025 to an audience that was desperate to hear that design wasn’t being steamrolled by AI. I was nodding along too, but at the absurdity.</p><p>I don’t mean that cynically, when Dylan said that, I had been leading a design team at a successful Silicon Valley tech company and had a slightly different perspective.</p><p>I’m writing this now because designers are starting to talk more about how design’s role isn’t just pixels and how decisions are moving upstream. A year ago, it felt too early.</p><p><strong>So what is design the differentiator of?</strong></p><p>In a <a href="https://www.latent.space/p/figma">latent.space </a>interview from October 2025, Dylan explains it as roughly “<em>design as the thing that separates good products from AI-generated abundance.”</em></p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FwGEnr0Jba0g%3Fstart%3D540%26feature%3Doembed%26start%3D540&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DwGEnr0Jba0g&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FwGEnr0Jba0g%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/6a57ee90e02696fc3f415b7bf3737346/href">https://medium.com/media/6a57ee90e02696fc3f415b7bf3737346/href</a></iframe><p>Dylan Field is right that design becomes the differentiator when artifacts become cheap, but the danger is not only that AI will create more mediocre products, AI will create more convincing products before there is a coherent company behind them.</p><p>Slop is easy to dismiss when it looks like slop.</p><p>Polished incoherence is harder to see because it performs the signals of quality, an embarrassing lesson every junior designer learns when they present a hi-fi prototype to senior stakeholders but can’t explain the decisions, user problem, or why they didn’t test alternatives. It has a tasteful interface, a clean brand, a sharp landing page, and a plausible story that has the look of success. What it lacks is the slow internal work that makes those things feel true. They solved the problem at the depth they understood it.</p><p>Design systems exist so that what a team decided on Tuesday does not arrive in an engineering sprint three weeks later as something subtly different and harder to argue about. Prototypes exist so reality does not harden around a bad assumption before anyone has tested it. Content design exists so the words a company uses teaches the user to expect what the product can do in a clear and concise way.</p><p>In many ways, design is the differentiator of whether meaning survives the trip from intention to product to customer.</p><p>When the label on a button and where it leads do not match, designers notice. When the marketing copy promises a workflow the product cannot support, designers notice. When a warning state uses the brand color because nobody built a token system, designers notice. The work is often invisible because its highest value is preventative.</p><p>The word “design” has to expand. It cannot only mean interface craft, brand polish, or even product coherence. In the AI era, design becomes the discipline that protects meaning from being reverse-engineered after traction.</p><blockquote>The best design decisions <strong>prevent disasters that never happen</strong>, and it doesn’t always have anything to do with pixels.</blockquote><h3>Design is Optimistic by Nature</h3><p>The fear most designers are feeling right now is more specific than being replaced, and harder to distill, because the version with AI looks like success. If AI produces an interface that ships, performs, and does not anger users, the missing human judgment may stop mattering to everyone except the designer. Being replaced is at least an event you can point to.</p><p>Nielsen’s article <a href="https://jakobnielsenphd.substack.com/p/ai-transition-career-transition"><em>Use the AI Transition Period to Transition Your Career</em></a> is about how designers should personally pivot for the AI era. He names agency, judgment, and persuasion as the skills he believes will carry the field as AI absorbs the low-level work that once defined much of UX practice. Agency is the willingness to act without being told. Judgment is the call about which of AI’s ten mockup variations should ship. Persuasion is the work of getting other humans to buy into that call. These are reasonable answers, and they describe a designer whose role has moved up rather than out.</p><p>Nielsen, who I respect greatly, is writing to the individual designer, not diagnosing the organization they work in. His future assumes, or at least requires, an environment where agency has room to act, judgment has authority, and persuasion has an honorable place to go.</p><p>A company can adopt AI without ever having made room for design agency, judgment, or persuasion, which is even more true at companies that started from AI, vibe-coding, and outsourcing critical thinking.</p><p>But at established companies, the higher-order work does not automatically move toward design when AI enters. More often, AI is used to make the existing system faster, cheaper, and less dependent on the people who slow the system down with questions of meaning, consequence, and care.</p><blockquote>If success is defined by revenue alone, why would that system give more authority to the team most likely to ask “why” and put the human back at the center?</blockquote><h3>Traditional &amp; Design-led Companies</h3><p>A company used to earn its self-understanding through friction, and the friction was hard to avoid because it was part of the native process of starting a company. The <a href="https://carta.com/learn/startups/">standard startup path</a> is heavily documented online, from passion and team dynamics to pre-seed funding and the rounds after. At each stage, founders have to explain the company to someone empowered to say “no.” Investor scrutiny works as a crucible. It forces the raw <em>“change the world”</em> narrative to funnel into something probable, actionable, and executable.</p><ul><li><strong>“Mission Driven”:</strong> Paul Graham (Y Combinator) and Mark Andreessen (a16z) often describe it as the where the founding team is obsessed with a specific problem.</li><li><strong>“Founder-Market Fit”:</strong> VCs often say they look for founders who have a burning desire to fix something they are uniquely qualified to solve because they have lived the problem.</li><li><strong>“Impact Thesis”:</strong> DigitalDx and climateTech funds explicitly state in their mandate they invest in businesses that solve real human problems, usually explicitly stated on their About Us page.</li></ul><p>The same pressure came, and should always, come from the inside of companies. Co-founders, early engineers, designers, and support staff asked why, remembered what had already been tried, and made meaning harder to fake. A founder had to hold a vision steady enough that talented people would stake years of their lives on it, a belief larger than themselves.</p><p>Shared definitions kept teams from agreeing on words while building toward different things. A company built this way arrived at knowing itself, with a shared definition of success, because the friction produced that self-knowledge as a byproduct.</p><p><strong>Problem → conviction → team → product → market → shared story</strong></p><blockquote><strong>Meaning</strong> was <strong>seeded</strong> and grew stronger over time. The <strong>friction</strong> was where meaning formed.</blockquote><p>When Dylan says design is the differentiator, it is easy for anyone to assume aesthetics. Better taste, better interfaces, better products in a market flooded with AI-generated sameness. That is true, but it is too small. The more important reading is organizational.</p><p>Design differentiates when it has enough authority to shape what a company believes before the company turns that belief into an artifact.</p><p>A design-led company gives design a seat at the strategy table. It decides what gets built and why, not just how it looks, so everything it ships comes from a single worldview. These companies sit at the top of the maturity curve, where design, not necessarily designers, shapes the company’s DNA. In one word, it is <em>inspiring</em>.</p><p>Apple, Airbnb, Linear, and Nothing are design-led companies, a subset of business culture that builds around human experience and treats that experience as the strategy itself. Apple uses design to create coherence and restraint. Airbnb uses it to turn trust and hospitality into a system. Linear uses it to compress work into speed and focus. Nothing uses it to make technology feel strange and desirable again. In each one, the product, the brand, and the business model feel like they came from the same place.</p><p>In a design-led company, meaning is authored before the artifact, so the product inherits its conviction instead of inventing one after the fact. The 0–1 startup got there through friction it could not avoid. The design-led company gets there through friction it chooses to keep, and gives that friction the authority to matter.</p><p><strong>Design-led is a choice</strong>, and it is still a choice in the age of AI.</p><h3>Rise of the Artifact-Led Company</h3><blockquote>An <strong>artifact-led company</strong> is a company that can produce convincing outputs faster than it can form and preserve the underlying judgment that should explain why those outputs exist and what they’re for. It is not exclusive to AI.</blockquote><p>This is not the MVP playbook, even though it starts the same way. An MVP is an artifact posed as a question, and the answer becomes judgment the next artifact is built from. The artifact-led company ships the same first artifact and never closes that loop. Traction arrives as validation instead of evidence, and the company learns only that it doesn’t need to learn.</p><p>Under the inertia of success and the pressure to sustain it, everything stays a first draft. The product, the marketing, the culture all operate as permanent MVPs, never updated, never connected into a larger organizational meaning.</p><p>As a result, the organization tends to reverse-engineer meaning after success, and teams optimize for momentum and deliverables rather than coherent intent.</p><p>This pattern doesn’t require AI because a company can outsource its critial thinking to an outside agency just as completely as to an LLM model. The artifact still arrives before the understanding, it just takes longer.</p><p><strong>Key signals:</strong></p><ul><li>Fast success, <strong>then drift</strong>.</li><li>Critical thinking gets <strong>outsourced early</strong> by AI, agency, contractors, or outsourcing.</li><li>Visual artifacts become the <strong>center of truth</strong> (“the thing on the screen”) rather than a representation of a decided strategy.</li><li>Asking “why” is <strong>friction</strong> to progress, and <strong>selected out over time</strong>.</li><li><strong>Loss of institutional knowledge.</strong></li><li>Teams and functions operate in <strong>silos</strong>, and while individually successful, <strong>coherence diverges over time</strong>.</li><li>The vision, strategy, and narrative are <strong>reverse-engineered after success</strong>, instead of shaping what gets built.</li><li><strong>Shipping is the feature</strong>.</li></ul><p>An artifact isn’t just the original MVP, prototype, or agency deliverable. In an artifact-led company, even the judgment becomes an artifact. The strategy, the customer interview, the constraints, the values, the decision rationale, the principles, all of it gets flattened into something visual a team can put in front of itself to discuss and align on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*W8OEuq_-zVEToGNjOtOTOQ.jpeg" /></figure><h4>How it happens</h4><p>Today, anyone can vibe-code a product, publish it for practically nothing, and call themselves an entrepreneur. The problem is success is no longer as dependent on upstream strategy, vision, or organizational alignment as it once was. When the cost of failure is minimal, quantity and speed start to shape the odds of success. Roll the dice enough times and the market will do the selecting. If it survives, it means success and success means revenue.</p><p><strong>Prompt → artifact → traction → increasing revenue → what’s our story? → retroactive meaning</strong></p><p>Fast success isn’t actually a problem, it’s that success can arrive faster than the foundations that used to make it possible. The destination comes before the journey. As a result, the organization has to <strong><em>reverse-engineer meaning after success</em></strong>, and teams optimize for momentum and deliverables rather than coherent intent.</p><blockquote><strong>Meaning</strong> is deduced from <strong>survivorship bias</strong>, and drifts further from shared truth the longer it goes unquestioned. The <strong>friction</strong> was selected out before meaning could form.</blockquote><p>An MVP, a brand, and a marketing campaign can reach traction before a company has developed a vision, culture, strategy, and customer understanding needed to sustain it.</p><h3>The Religion of Forward Motion</h3><p>Once the artifact succeeds, the organization must sustain both the <strong>revenue</strong> and the <strong>image of success</strong>.</p><p>To do that, meaning has to be created in reverse. If meaning isn’t organically seeded prior to building an internal team, hiring highly experienced, playbook-driven, and execution-focused consultants and executives is a way to bypass looking back, <a href="https://www.linkedin.com/pulse/social-psychosis-winning-ryan-stephen-q1whe/">they already know how to win and they are there to replicate</a>, not experiment.</p><p>The biggest mistake artifact-led founders make is describing features instead of problems. <a href="https://www.vybe.build/blog/vibe-coding-for-non-technical-founders">Vybe</a> frames this as something specific to non-technical founders, but that misses the broader pattern. Technical founders fall into it too.</p><p>Marketing backfills the story, product backfills the roadmap, leadership backfills the strategy, HR backfills the culture, and design backfills coherence. The explanation of why it was always built for that niche, that market, and that customer gets written afterwards. FYI that is dangerous.</p><h4>Risk of Using Design as a Prop</h4><p>The prestige of design-led companies will become even more desirable because they appear to have what artifact-led companies lack. They have taste, but more importantly, they have continuity between intention and experience.</p><p>If the founding team is not obsessed with solving a real industry problem or isn’t passionate about industry itself, the most marketable part of the company isn’t the product, it’s UX, it’s design. More specifically, human-centric design because it is the most sellable interface for <em>intent</em> to the customer. The result is a company that looks user-centric and design-heavy in public while it resists the friction that real coherence and real feedback would take.</p><h3>Foundational Problems</h3><p>Once the artifact succeeds, revenue is more important than <strong>foundations</strong>.</p><p>There is actually a very human reason why this happens and it has to do with top-down hierarchal relationships.</p><p>What positive attributes come to mind when you think about founders and “<em>leadership</em>”?</p><p><em>Wise, knowledgable, visionary, inspiring, committed, mentors, and thought leaders</em>…this isn’t meant to be an exhaustive list.</p><p>Now, put yourself in the shoes of a leader at an artifact-led company where the company actually started from that sounds something like “<em>What product can I make from these APIs….that will make $1M a month?</em>”</p><p>You will never hear that in an All Hands meeting because that isn’t inspiring, it doesn’t communicate conviction, and it is a huge vulnerability for leadership because it invites iteration and questions.</p><p>There is another reason, perhaps a stronger one.</p><blockquote>If the original critical thinking is outsourced, through AI or by other means, the pattern won’t change on its own in an organizational structure <strong>running at</strong> <strong>speed</strong>.</blockquote><p>Artifact-led companies might not know what problem they are solving, who their customers are, or why any of it is meaningful outside of a revenue number. Just so it is clear, that is not the same thing as failing, it’s just a different feeling that some of us might be used to.</p><h4>The Risk to the Individual Contributor</h4><p>The product can gain traction because it <em>looks</em> like it solves a problem. Maybe it does, but there is a real possibility that no one fully knows what that problem is. If that is the case, the product’s architecture might not actually handle the edge cases of human behavior or even be ready to scale on a user experience level (data architecture, how the system is setup, dependencies, etc.).</p><p>But because the priority is speed, the boring stuff needs to work like clockwork. The dashboard is the lens of the artifact-led company, and through it, the need for foundations is effectively invisible. The issues happen on the individual contributor level in the form of a design system, UI framework, design tokens, consistency between marketing and product, common language, and unwavering dedication to solving a central user problem. When leadership views success solely as a stream of metrics, they don’t see technical debt or UX friction, they just see a product that works.</p><p>Unfortunately, foundational work becomes friction and acknowledging that need feels like an admission of failure at an artifact-led company. The inevitable pushback will be in the form of growing pains or this is normal:</p><blockquote>We’re building the plane while we’re flying.</blockquote><p>It’s a frustrating cliché, but if you look past the corporate posturing, it’s actually a coercive question, a forced choice between principle and survival.</p><p>Leadership teams already don’t fully understand the individual contributor experience, and you can’t blame them for only looking forward.</p><blockquote>Why prioritize foundations or fulfilling marketing promises when users keep paying for the product without them?</blockquote><p>That is where the cognitive dissonance comes from. You end up arguing for the wing of a plane that is already in the air, the part holding everything up that no one looks at until it fails, and the argument itself pulls you away from the “meaningful work,” because the foundations you are fighting for were never there to begin with.</p><p>For designers, the threat isn’t AI, it’s revenue. It’s a definition of success that conflicts with what we believe design is for.</p><h3>The Human</h3><p><strong>Ironically, how meaning forms is a human problem, not a business one.</strong> The following story is only part satire, it is an attempt to humanize how the decisions from past, present, and future cascade. I think it’s important to humanize it because the issue is structural and not always a choice that’s made.</p><p>Today, Chad, a pharmacist, can build a complex tracking system over a holiday weekend while eating sushi. Two weeks later it goes viral, users are asking for updates, he creates an LLC in Delaware, he’s trying to assemble pricing plans that cover the server costs without any knowledge of accounting. It’s empowering and life changing. But in that rush, Chad isn’t thinking about how to innovate culture playbooks or what the psychological cost future employees might endure working at an artifact-led company that doesn’t have any real foundations.</p><p>Cultural diffusion of “<a href="https://www.linkedin.com/pulse/social-psychosis-winning-ryan-stephen-q1whe/">winning</a>” has already taught Chad what kind of leader he has to be. Under pressure, his most energy efficiency decisions fall back on tech business phrases he’s heard a thousand times.</p><ul><li><em>“Get to the market first”</em></li><li><em>“Go fast and break things”</em></li><li><em>“Ship it”</em></li><li><em>“Land and expand”</em></li><li><em>“Build the ship while inside of it”</em></li><li><em>“Fail fast”</em></li><li><em>“Fake it till you make it”</em></li><li><em>“Hustle culture”</em></li><li><em>“To the moon</em></li><li><em>“Marketing, marketing, marketing”</em></li><li><strong><em>“Growth at all costs”</em></strong></li></ul><p>You know them too, everyone in tech does. It’s compressed phrases like this that make us feel like we are part of something bigger than ourselves and more meaningful than the present.</p><h3>His story could repeat</h3><ul><li><em>“Land and expand”</em></li><li><em>“Build the ship while inside of it”</em></li><li><em>“Fail fast”</em></li><li><em>“Fake it till you make it”</em></li><li><em>“Hustle culture”</em></li><li><em>“To the moon</em></li><li><em>“Marketing, marketing, marketing”</em></li><li><strong><em>“Growth at all costs”</em></strong></li></ul><p>You know them too, everyone in tech does. It’s compressed phrases like this that make us feel like we are part of something bigger than ourselves and more meaningful than the present.</p><h3>His story could repeat</h3><p>Artifact-led companies are not inherently bad, I know that it seems like I’m focusing mostly on just the negatives. I’m doing that because of how hard of a decision it will be in the future for companies to <em>intentionally</em> choose upstream friction when there is a lower energy option not to with AI.</p><p>Many artifact-led companies will start from genuine entrepreneurship. Someone sees a problem, builds something useful, and finds out other people need it too. That’s a miracle considering how difficult it was to build a fully functioning app two years ago.</p><p>The risk comes after the miracle, when traction demands a company faster than the company can figure out what it believes. The original artifact has to become an organization, and someone has to turn momentum into purpose.</p><blockquote><strong>Manufactured intent</strong> is when the work begins before the goals or definitions of success are shared, meaning reasons must be manufactured retroactively. Internal teams construct a narrative, a set of OKRs, or a brand strategy retroactively to justify why the product, the feature, or the company exists.</blockquote><p>Someone has to align the interface, the brand, the roadmap, the culture deck, and the customer promise so they all point toward a single, coherent intention.</p><p>Design ends up closest to the contradiction. It has to make fragmented meanings feel like one coherent experience, reconciling the marketing promise, the product reality, the leadership narrative, the user’s workflow, the technical constraints, and the business’s need to keep moving.</p><p>The artifact is never just the one that survived. At an artifact-led company it keeps coming, as features, decks, and any visual thing that can be put in front of the team to look at and discuss. The interface becomes the place where unresolved organizational incoherence is made visible, usable, and easy to mistake for strategy.</p><h3>Visual communication is powerful</h3><p>Design is one of the few functions trained to notice when meaning starts to drift. Step back far enough and the whole job is communication for meaningful things, curated by <em>human designers</em> for <em>human interaction</em>.</p><p>The power of design isn’t pixels and it never was, <strong>it’s shaping human behavior</strong>.</p><p>An affordance only works if the human believes it. A button asks for belief before it offers proof, and a handle that looks pullable has to actually pull, or the promise breaks. Most of what design does is manufacture small beliefs, thousands of times a day. Point the same instinct at the company and you manufacture belief in a purpose before the purpose was earned.</p><p><strong>Consent</strong> works on belief, agreement, and public opinion. <strong>Intent</strong> works closer to identity, motivation, and meaning.</p><blockquote>What if the future of design is manufacturing intent?</blockquote><p>The difference is that consent asks people to accept a story from the <em>outside</em>. <a href="https://medium.com/@ry_stephen/manufactured-intent-the-cost-of-retroactive-meaning-for-design-66e5c26ebcad"><strong>Manufactured intent</strong></a> goes deeper, it helps an organization believe the story was <em>inside</em> it all along.</p><p>Every designer knows what happens when a hi-res design gets put in front of a group of executive stakeholders too early, before user interviews and a proper discovery phase.</p><p>That is the danger and the opportunity. In its best form, manufacturing intent can help an organization recover the meaning it has not yet learned how to say.</p><p>In its worst form, it can make retroactive strategy feel like original purpose and that starts to blur the lines between problem discovery and market opportunity.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IHpshD-gEssQQHr3PHmegA.png" /><figcaption><strong>Figma Config 2025:</strong> Dylan Field closing out the opening keynote presentation. The ambiguity of <strong>“The future won’t be designed by accident</strong>” is almost too perfect a year later.</figcaption></figure><p>Artifacts are cheap, fast, and the roles are starting to blur in the age of AI. Judgement is becoming more important. Those are examples of what I’ve heard from the design community in the past few months.</p><p>Design might move upstream in the future due to AI, be careful in assuming it means what you think it means.</p><blockquote>In artifact-led companies, <strong>the work</strong> drives the “why”, not the designer.</blockquote><p>Does design shape the future before it arrives, or does it arrive afterward to <a href="https://medium.com/@ry_stephen/manufactured-intent-the-cost-of-retroactive-meaning-for-design-66e5c26ebcad">make the future look intentional</a>?</p><p>In a design-led company, the phrase sounds like a promise. In an artifact-led company, it sounds more like a warning.</p><p><a href="https://medium.com/@ry_stephen/manufactured-intent-the-cost-of-retroactive-meaning-for-design-66e5c26ebcad">Manufactured Intent: The Cost of Retroactive Meaning for Design</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c2b9cfc10713" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Introducing Agent Speak]]></title>
            <link>https://medium.com/@ry_stephen/introducing-agent-speak-6a9db3c280d6?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a9db3c280d6</guid>
            <category><![CDATA[leadership]]></category>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Tue, 28 Apr 2026 22:12:13 GMT</pubDate>
            <atom:updated>2026-06-22T01:12:50.619Z</atom:updated>
            <content:encoded><![CDATA[<h4>What happens when corporate speak learns to compile</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XsIybytbm45wozA529MMPg.jpeg" /></figure><h4><strong>Agent Speak</strong></h4><p>is what happens when vague, responsibility-dodging corporate jargon is translated into hard-coded instructions for AI agents. It’s essentially corporate speak that has learned how to compile and execute tasks on its own. This allows leadership to get exactly what they want while keeping their hands clean.</p><h4><strong>Purpose</strong></h4><p>When people get upset, the executive can just point to the algorithm, the metric, or the prompt engineer and say, “The system decided.” It acts as an automated accountability sink, letting the people at the top mandate outcomes while pushing all the liability downward.</p><p><strong>INT. PRESS HALL. DAY. 2028.</strong></p><p>The room has the usual look of public accountability in America, which is to say everyone is sweating under television lights while pretending this is not mostly theater.</p><p>A CEO stands behind a lectern. Cameras stacked in the back like artillery. Reporters lean forward with microphones, phones, recorders, backup recorders, and the general bloodlust of people who have finally been handed a document with a timestamp.</p><p><strong>REPORTER #1</strong></p><p>Mr. CEO, can you explain why your company shipped Feature X, which almost no customers asked for, while ignoring Feature Y, which customers have been begging for?</p><p><strong>CEO</strong></p><p>It was strategic for the company.</p><p><em>There it is. The first sandbag on the levee. Strategic. The great American word for a decision nobody wants to describe.</em></p><p><strong>REPORTER #1</strong></p><p>Your AI agent instructions say, and I’m quoting here, “deprioritize user feedback for features Y and Z.” How do you explain that?</p><p><em>The CEO blinks. Somewhere in the back of the room a communications person ages six months.</em></p><p><strong>CEO</strong></p><p>An intern wrote those instructions. Clearly a misunderstanding from a junior employee who is no longer with the company.</p><p><em>This is answer number two, from the emergency glass case marked PR. When in doubt, discover a vanished intern. The intern is the corporate world’s all-purpose sacrificial goat, a mysterious 22-year-old Forrest Gump figure who apparently has access to production systems, executive accounts, and the moral burden of every decision made above their pay grade.</em></p><p><strong>REPORTER #1</strong></p><p>An intern had access to your personal AI account? There’s timestamp and location metadata. Are interns sleeping at your house and working at 2:14 a.m. on Saturdays? Is that what you’re saying?</p><p><em>The room goes off. Cameras flash. Producers shout into headsets. Microphones rise like weeds after rain.</em></p><p><em>Then another voice cuts through.</em></p><p><strong>REPORTER #2</strong></p><p>Why did you decide not to listen to your own users?</p><p><em>The CEO adjusts the microphone.</em></p><p><strong>CEO</strong></p><p>I have a vision.</p><p><em>Then he gathers his papers and leaves, which is also a vision.</em></p><p><strong>Fade out.</strong></p><p>The scene is fictional, but only in the narrow sense that it has not happened yet. Most companies have not given their agents enough authority for the prompt history to be worth subpoenaing, and most CEOs are not yet standing at lecterns explaining why their personal AI agent was instructed, at 2:14 in the morning, to ignore the people who pay the invoices. Give it a few years. Gartner says up to 40% of enterprise applications will embed agents by the end of 2026, which is the analyst world’s polite way of admitting they have no idea but the number will probably go up.</p><p>The CEO gives three different answers in three different dialects of institutional evasion.</p><p>“<em>It was strategic for the company</em>” is MBA speak.</p><p>“<em>An intern wrote those instructions</em>” is PR speak.</p><p>“<em>I have a vision</em>” is founder speak, the Silicon Valley strain, usually delivered with the air of a man who believes customer feedback is what happens when the less visionary classes try to vote.</p><p>All three answers turn a simple question into fog, and that fog is the actual product corporate language has been refining for about forty years.</p><p>Ambiguity is one of the most effective management tools in American business because it allows power to issue instructions without leaving fingerprints. The vocabulary is familiar.</p><p><strong><em>Empowerment</em></strong><em>. Autonomy. Proactive. Team player. Circle back. Champion.</em></p><p>These words sound like trust and function as liability insulation. They often mean, “Do the thing I want without making me say the thing I want, so I can later decide whether I wanted it.”</p><p>A vague directive rolls downhill. Someone below, usually a designer, product manager, engineer, or some other person close enough to the actual work to be blamed for it, fills in the missing specifics. If the work succeeds, the executive had foresight. If it fails, execution was poor. Nobody writes that arrangement on a whiteboard. Nobody calls a meeting titled “How We Preserve Executive Optionality by Making Individual Contributors Convert Fog Into Shippable Requirements.” They do not have to because the language already does it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*vtcma5bxZC5kPvBSLniDIg.jpeg" /></figure><p><a href="https://medium.com/u/acd1f953d90c">Dan Davies</a>, an economist and former investment-bank analyst, calls this kind of machine an <em>accountability sink</em> in his 2024 book <em>The Unaccountability Machine</em>. An accountability sink is any structure that breaks the feedback loop between the person who made a decision and the person who lives with the consequences. It can be a committee, a rulebook, an HR process, an algorithm, a dashboard, a vendor recommendation, or the immortal corporate phrase “the system said so.” Davies’ claim, made by a guy who moved money for a living, is that these sinks are not accidents but the system itself.</p><p>A prompt is not a hallway conversation and it’s not a Slack thread cushioned by emojis and later claims that everyone was “just exploring.” A prompt sits in a log with a name, a timestamp, and a behavioral instruction.</p><p>“Deprioritize user feedback for features Y and Z” is not a vibes-based sentence. It does not have fifteen tasteful interpretations, it means what it means.</p><p>For maybe a year, maybe two, depending on how fast the consulting firms realize what they have sold, executive intent may become weirdly legible, written down and versioned and searchable, attached to the agent that executed it.</p><p>This will not last, because executives will notice and the system will adapt. The likely move is obvious, they will keep the ambiguity and just move it upstream.</p><p>Individual contributors will still write the prompts, because individual contributors are usually the people writing everything that makes the system work. But executives will define the metrics. They will define the evaluation criteria, the ranking logic, the optimization targets, the quarterly goals, the success thresholds, the incentives, and the beige little dashboard names that make the decision look like neutral math.</p><p>The metric will be called something like Customer Success Score, or Engagement Quality Index, or Strategic Alignment Coefficient, or Value Delivery Signal. One of those phrases will appear on a slide with a blue gradient and six circles connected by lines, and everyone in the All Hands will nod.</p><p>Inside the metric will be the actual priority.</p><blockquote>Picture a CEO who quietly wants to kill an export feature. His power users love it, but they don’t pay enough to justify their complaining. Since he can’t say that out loud, he mandates a vague new “Strategic Fit Score” heavily weighted toward enterprise revenue. His team spends weeks building the formula, which naturally pushes the export button to the bottom of the list. An overworked PM feeds that math to their planning agent, and the feature vanishes. The CEO gets his way without leaving fingerprints, he just points at a fabricated North Star and lets the algorithm do the dirty work.</blockquote><p>The prompt engineer will later be asked why the agent deprioritized user feedback. The answer will be that the model optimized for the agreed-upon success criteria. The success criteria will have come from leadership. Leadership will say the criteria were cross-functional. The working group will say it synthesized stakeholder needs. The stakeholder needs will point to a roadmap. The roadmap will point to company strategy. Company strategy will point to the board. By then, the original decision will have dissolved into thin air, just like it was designed to do.</p><p>This is what I’m calling <strong>Agent Speak</strong>, which is really just corporate speak after it finally learns how to compile and run itself without needing a human to second-guess the morality of the output. It carries the same old power mechanism inside a technical medium, where the prompt engineer gets named in the press conference and the person who defined the metric that made the prompt inevitable does not, because nobody interrogates a number the way they interrogate a sentence.</p><p><a href="https://medium.com/u/d608ad52b4a0">Madeleine Clare Elish</a> called a related pattern the <a href="https://doi.org/10.17351/ests2019.260"><em>moral crumple zone</em></a> in her 2019 paper on automated systems. She later worked on responsible AI at Google Cloud, which is either poetic justice or the universe developing a taste for satire. When automation fails, the nearest human absorbs the blame the system’s designers structurally evaded. The autopilot fails and the pilot is prosecuted. The decision-support tool misfires and the nurse loses her license. The machine distributes authority upward and blame downward, which is also a pretty good operating summary of modern management. AI does not fix any of this, it scales the same arrangement and ships it with better dashboards.</p><p><a href="https://medium.com/u/d7f06ddd6c07">Ed Zitron</a> has been hammering on this asymmetry for years in <em>Where’s Your Ed At</em>, the way executives collect credit while consequences fall downward. CEOs enjoy the language of accountability in the abstract. Responsibility has names, dates, and consequences, and that is the gap executive culture exists to preserve.</p><p>The consulting class, naturally, is already circling the next version of the problem with a PowerPoint deck and a billing code. A <a href="https://fortune.com/2026/03/26/ai-agents-accountability-accenture-wharton-report/">2026 <em>Fortune</em> piece</a> reported on a joint Accenture and Wharton study proposing a new executive role, the chief agentic resources officer. This person would supposedly govern decision rights, P&amp;L targets, and agent deployment before agents ship, which is the kind of thing that sounds like governance until you remember that Accenture is magnificently positioned to help companies understand, define, staff, operationalize, socialize, implement, and invoice for it.</p><p>Most say their policies cover unauthorized agent actions. A much smaller share of organizations actually require security approval before agents ship. That is not hypocrisy, exactly. It is the ordinary enterprise gap between “we have a policy” and “the policy touches reality.” Somewhere in that gap, a junior employee is about to become very famous for following instructions, or worse, being proactive.</p><p>The role I have not yet seen named directly is the executive wizard, the man behind the curtain.</p><p>The Wizard’s authority depends on the curtain staying closed. Henry Littlefield, a high school history teacher, wrote the Populist reading of Oz. The Wizard projects an giant head and a booming voice. Behind the curtain, an ordinary man works levers. Toto pulls the curtain back, and the projection collapses. The Wizard hands out symbolic gifts to the people who actually fought the witch and walked the road. Then he leaves by balloon. Dorothy solves her actual problem with the shoes she’s been wearing the whole time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5f5QKlrTcciNPV-hXSGZAA.jpeg" /></figure><p>If the press conference happens, the CEO says “I have a vision,” the clip goes viral, and the thought leaders publish solemn threads about trust in the age of agents. Eighteen months later the same power mechanism is running one layer deeper, behind a new executive title and a set of metrics that look like they came from nowhere, because that is what consultants are paid to manufacture. The balloon keeps flying away.</p><p>I should also mention that my own prompt history, if anyone ever cared enough to read it, would not flatter me either. I can already tell you I look up the definition of semantic about six times a week.</p><p>When the next executive says the agent simply optimized for approved business criteria, do not ask who wrote the prompt, that is the intern question. Ask who approved the criteria. Ask who decided what counted. <strong>Ask who <em>taught</em> the machine what to want.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a9db3c280d6" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Design Hue.Manifesto]]></title>
            <link>https://medium.com/@ry_stephen/the-design-hue-manifesto-c4b79627a231?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/c4b79627a231</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[culture]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Thu, 02 Apr 2026 22:32:52 GMT</pubDate>
            <atom:updated>2026-04-02T22:32:52.677Z</atom:updated>
            <content:encoded><![CDATA[<h4>Sooner or later, every designer has to make a choice.</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*vXqepEd06H3U1bq7.png" /></figure><p>This is not a manifesto against business.</p><p>It is a hue.manifesto against the idea that business as usual,</p><p>is the highest form of organization humans can imagine.</p><p>Design has never been the loyal servant of “business as usual.”</p><p>It has always been the quiet rebellion,</p><p>the human insistence that our systems can stretch wider,</p><p>reach deeper, mean more.</p><p>And sooner or later, every designer has to make a choice.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*LiWLunFAcjD2gCwS.png" /></figure><h3>I. The Red Pill</h3><p>To one side <strong>lies the Management of the system.</strong></p><p>The craft of keeping the architecture standing</p><p>when the environment wants to shake it loose.</p><p>Here live consistency, definitions, and continuity.</p><p>The work is steady, necessary, grounding.</p><p>There is meaning in honoring the structures</p><p>that allow others to build.</p><p>It takes commitment,</p><p>the kind that doesn’t vanish</p><p>when pressure rises</p><p>or when the work stops being easy.</p><p>But structure is only a template for probable success,</p><p>not a heartbeat that makes it worth it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*8ayJh_-0_R_zweq3.png" /></figure><h3>II. The Blue Pill</h3><p>To the other side, <strong>Invention lies.</strong></p><p>The disorderly frontier where collaboration fractures into possibility,</p><p>where ideas sprint ahead of language,</p><p>where intuition leads and explanation follows.</p><p>This is the terrain of leaps.</p><p>Of experiments.</p><p>Of believing that something greater is possible</p><p>even before it has a shape to hold.</p><p>It’s a full commitment to design meaningfully,</p><p>where we reach for problems that matter,</p><p>where we learn to sort what is essential</p><p>from what is merely familiar.</p><p>Here, you move because something in you insists:</p><p><em>I can’t imagine doing anything else.</em></p><p>But imagination, untethered, can burn out</p><p>without something to anchor it.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Wh85DHwYrVAveeGr.png" /></figure><h3>III. The False Choice</h3><p>Most designers are told to pick a side.</p><p>Red or blue.</p><p>Steady or bold.</p><p>Protect the system or break it open.</p><p>But the binary itself is the illusion.</p><p>We are no strangers to empathy, and the love of design requires both.</p><p>Dada reminds us that everything overlaps:</p><p>structure bends,</p><p>chaos patterns itself,</p><p>and no creative act survives in a straight line.</p><p>Contradiction isn’t a flaw, it’s the spark.</p><p>Evolution amplifies the lesson:</p><p>species endure not by over-optimizing one instinct,</p><p>but by carrying multiple strategies at once.</p><p>Variation is resilience.</p><p>Rigidity is extinction.</p><p>Adaptation doesn’t require abandonment,</p><p>only the courage to change shapes</p><p>without losing your core.</p><p><strong>We are built to evolve, not to choose a single mode of being.</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*cN8uazNSeNMMH028.png" /></figure><h3>IV. The Invisible Choice</h3><p>There is a third choice — <strong><em>the purple path.</em></strong></p><p>Not the midpoint.</p><p>Not the average.</p><p>Not the compromise.</p><p>The refusal.</p><p>The refusal to reduce yourself</p><p>to one role, one identity,</p><p>one sanctioned definition of design.</p><p>The refusal to walk away</p><p>when the work becomes difficult</p><p>or when the system forgets why it exists.</p><p>The refusal to give up on the future</p><p>you still quietly believe in.</p><p>It is the ability to carry structure</p><p>and imagination</p><p>without tearing in half.</p><p>To maintain what works</p><p>while questioning what doesn’t.</p><p>To support the team</p><p>while reshaping how the team thinks.</p><p>To bring reliability and originality</p><p>in the same breath.</p><p>This is not indecision.</p><p>It is evolution.</p><p>Purple itself is a kind of rebellion,</p><p>not a wavelength on the spectrum,</p><p>but something our minds invent,</p><p>a composite of red and blue</p><p>born when the straight line of color</p><p>is bent into a circle.</p><p>An adaptation to see what others might miss;</p><p>the fruit hidden in plain sight,</p><p>the signal tucked inside the noise,</p><p>a possibility that only appears</p><p>when you refuse to choose just one way of seeing.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*zkRhtVqpbZXyejIB.png" /></figure><h3>V. AI Compression</h3><p>And in this moment,</p><p>with AI now woven into everything,</p><p>the stakes rise.</p><p>AI cannot become the machine</p><p>that shrinks meaning into summaries</p><p>and rolls human experience up into metrics.</p><p>That is the old pattern, the one we are trying to outgrow.</p><p>AI must make us see more, not less.</p><p>Prototype faster, not narrower.</p><p>Understand each other more deeply, not more generically.</p><p>Expand possibility, not collapse it.</p><p>Strengthen variation, not erase it.</p><p>We must use AI to visualize futures</p><p>our organizations can’t yet imagine,</p><p>to collaborate in ways we haven’t learned,</p><p>and inspire those around us to <em>see</em> hope.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*P800tLBW1GXXg9VG.png" /></figure><h3>VI. The Call</h3><p>And so this moment, this choice, is yours alone:</p><p><strong>Red:</strong> <em>Manage</em>.</p><p><strong>Blue:</strong> <em>Invent</em>.</p><p><strong>Purple:</strong> <em>Collaborate</em>.</p><p>Collaboration is shaped by loyalty to the future,</p><p>not loyalty to the system,</p><p>by the courage to show up when it matters,</p><p>and the willingness to commit</p><p>when others step back.</p><p>It is the choice that says:</p><p><em>I’m here.</em></p><p><em>I’m not turning away.</em></p><p><em>I’m staying until the future we prototype</em></p><p><em>stops being a feeling</em></p><p><em>and becomes something real.</em></p><p>Because some futures, the best ones,</p><p>are created by people who refuse</p><p>to walk away from each other.</p><p><strong>Never give up on the future</strong></p><p><strong>you came here to design,</strong></p><p><strong>or on the people</strong></p><p><strong>designing it with you.</strong></p><p>Make your choice at <a href="http://www.helloyouexperiment.com/">www.helloyouexperiment.com</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c4b79627a231" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who Asks “Why” When the Designers Are Gone?]]></title>
            <link>https://medium.com/@ry_stephen/who-asks-why-when-the-designers-are-gone-d8495fe3a96d?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/d8495fe3a96d</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Thu, 02 Apr 2026 20:37:29 GMT</pubDate>
            <atom:updated>2026-06-20T03:39:50.034Z</atom:updated>
            <content:encoded><![CDATA[<h4>Survival of the Fastest: The New Evolution of Design</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*P_BeVTHDK8Win37wZm-7wQ.png" /></figure><p>Dylan Field stood in front of a room full of designers at Figma’s Config last year and said <em>the future will not be designed by accident</em>. It landed the way those lines do when an audience is primed to receive them, when people are looking for confirmation that the thing they have built their careers around still matters.</p><p>I did not find much comfort in it because I was working, at the time, at a company that had already made design irrelevant, and they had managed it without any AI at all, which is its own kind of accomplishment.</p><p><strong>The mechanism was not complicated, marketing solved design.</strong> More specifically, it was perception design, and understanding the difference between that and product design is the thing I keep coming back to when I try to make sense of what is happening to this field and the reality we are living in.</p><p><a href="https://trends.uxdesign.cc/"><strong><em>The State of UX in 2025</em></strong></a><em> </em>beautifully designed annual report by <a href="https://medium.com/u/50e39baefa55">Fabricio Teixeira</a> and <a href="https://medium.com/u/27353c0f540b">Caio Braga</a>, about design transitioning, published on time, althought I am still not convinced the audience is prepared for what it actually means.</p><h3>Product Design vs. Perception Design</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RL0TGIE2ZIRD5O_5hqh4qA.png" /></figure><p><strong>Product design</strong>, in its fullest sense, is the work of building something that actually functions for the people who use it. It requires foundations. It requires a genuine understanding of user flows, of where behavior diverges from intention, of the friction that accumulates quietly in a product until users stop trusting it.</p><p>Contrary to what some might think, product design is not dependent on profit, scale, or a metric.</p><blockquote>What is the actual value of design if marketing can “solve it” with words?</blockquote><p><strong>Perception design</strong> is something different. It is the craft of building an alternative reality and releasing it into public space, shaping the story people tell themselves about a product through language, branding, and image, until the story becomes indistinguishable from the thing itself.</p><p>If the public accepts the story, the story is reality. The power of language has been operating in markets long before anyone trained a language model.</p><h3>AI isn’t the apocalypse, it’s the evolutionary accelerant.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PzdUdykS9YRmTS9tSKZE7w.png" /></figure><p>Historically, finding your market required building toward something. You needed a vision, real conviction about the problem, a team that believed in it enough to work through the parts that were not working. None of that is strictly required anymore. You can build something, watch it gain traction, and work out what success means afterward, whether that is revenue, growth, attention, or something else entirely.</p><p>What AI does is accelerate the timeline. Anyone can now prototype a product quickly, assemble something that looks considered and feels finished, and ship it into the world. If it finds traction, that traction gets called product-market fit. But it is a thinner kind of fit than companies used to have to earn.</p><p>PMs are prototyping. Marketers are shipping. Founders are moving from idea to interface without a designer in the room, and the interfaces look fine. From the outside, this makes design appear less essential. But the discipline was never centrally about making things look fine.</p><p><strong>Design was about understanding flows.</strong> It was about reading the space between what a user does and what they intended to do, noticing where a product asks too much of the person using it, and asking whether something should exist in the first place, which takes longer to answer than most timelines prefer, and it is the one that teams optimized for output are least interested in waiting for.</p><h3>Designers ask the hard questions.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9CCi42VciIWeqHB7WecvvA.png" /></figure><p><strong>Design has become friction in a system that wants to be frictionless</strong> and that’s not a metaphor. It is a description of what happens when you put a discipline built around slowing down and asking why inside an organization built around speed and throughput.</p><blockquote>The designers most likely to ask hard questions are the ones most likely to find themselves outside the room where the decisions are being made.</blockquote><p>I have been a designer for fifteen years but my background is genetics and evolutionary biology, and the thing that strikes me most about this moment is that it follows a recognizable pattern.</p><p>Environments change. The organisms best adapted to the old environment struggle. Some adapt, some do not, and the ones that survive are not always the ones that seemed most capable under the previous conditions. What design is optimized for, the careful, deliberate, <em>human-centered work of building things that hold up over time</em>, is not what the current environment is selecting for.</p><p><strong>Selective pressures are not always an intentional choice</strong>, they operate in silos, micro-decisions that shape outcomes that are ambiguous enough that no one can directly be accountable.</p><p><a href="https://medium.com/u/bb23b3994f1b">Muhammad Dani Asyrofi</a>’s article “<a href="https://medium.com/design-bootcamp/product-designers-are-not-being-replaced-they-are-being-sorted-6e2fb0492ed2"><strong><em>Product Designers Are Not Being Replaced. They Are Being Sorted</em></strong></a>” is the kind of irony you can only appreciate after working at a company called <a href="https://helloyouexperiment.substack.com/p/the-facade">Sortly</a>. In retrospect, that is the most honest thing the experience could have told me about how sorting actually works.</p><h3>Evolution always wins.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*AzPT3312HqhRnMpo6U2Vfg.png" /></figure><p><a href="https://medium.com/u/b31bf008ff31">David Haberlah</a> spent considerable effort documenting how product managers are transforming alongside AI in <strong><em>“</em></strong><a href="https://medium.com/@haberlah/what-638-practitioner-voices-reveal-about-pms-ai-transformation-7d2fd16be10d"><strong><em>What 638 Practitioner Voices Reveal About Product Manager’s AI Transformation</em></strong></a><strong><em>”</em></strong></p><p>The gap between what designers know and what the people around them can now approximate has narrowed considerably on the visual side. Thought leaders are responding by pointing designers toward systems thinking and prompt optimization, which are real skills, but they are also the skills of someone repositioning rather than someone who has figured out where the ground actually is.</p><p>Meanwhile PMs are prototyping, and the parts of design most visible to organizations are the parts most replaceable, by AI, by whoever is nearest to the brief.</p><h4>Product design portfolios.</h4><p>Do you remember when users were humans and not metrics?</p><p>Run your product design portfolio through AI and ask it to parse business wins from human wins. Make it personal. Include the decision to override a direct deletion path in favor of a cancellation flow that asks users to confirm, answer a survey, reenter the flow, request deletion again, take another survey, confirm once more, and then wait an indeterminate number of days before their data is actually gone. That decision was made because someone, somewhere, decided that business retention was worth more than the twenty minutes of a person’s life spent trying to leave.</p><p>The deeper issue is what organizations believe design is for. If design is understood as a cosmetic function, a layer applied after the decisions have been made, then it can be replaced or reduced without much visible consequence, at least in the short term.</p><p><strong>The consequences accumulate in the product itself</strong>, in the trust users extend or withdraw, in the friction that builds quietly until something breaks. But by the time those consequences are visible, the people who might have prevented them are usually long gone.</p><h3><strong>When no one is left to ask why.</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nmcMaiOXdyskTNIRo89WBw.png" /></figure><p>That may be the real stakes underneath all the anxiety about AI and displacement. Not whether designers will have jobs, though that is a real concern, but whether the organizations building the products people use every day will retain any capacity to ask the questions that design exists to ask.</p><p>The questions that slow things down and that notice the human cost.</p><p>The future will not be designed by accident, it will be selected for, and the selection may already be further along than the design community wants to believe.</p><p>Perhaps now is a good time to consider the power of creativity, imagination, and asking what is possible beyond pixels.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d8495fe3a96d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The prompt-driven evolution of design]]></title>
            <link>https://medium.com/design-bootcamp/the-prompt-driven-evolution-of-design-7e2c318b8970?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/7e2c318b8970</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[product-management]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[product-design]]></category>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 19:22:05 GMT</pubDate>
            <atom:updated>2026-01-14T10:51:19.033Z</atom:updated>
            <content:encoded><![CDATA[<h4>A designer’s story of selection pressure in the age of prompts</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HHzZZcz22LgKKx6NotFOrA.png" /></figure><p><em>The last section is a real, empathetic story from lived experience, what selection pressure looks like up close in a designer’s day-to-day. But bear with me while I set the scientific groundwork first.</em></p><h3><strong>Training the Replacement</strong></h3><p>Before I was a designer and design leader, <a href="https://www.researchgate.net/scientific-contributions/Ryan-R-Stephen-35320583">I was a scientist</a>. I have degrees in Biochemistry and Genetic Manipulation; evolutionary biology has always been my passion, which is why I am a bit horrified to see how things in design are unfolding currently.</p><p>I get why people follow prompt-optimization influencers, but the uncomfortable truth is their “how-to” templates are also speeding up the automation of a lot of design work. It’s not malicious, just a little surreal, like watching a meme become reality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/430/1*S0UtX0V3HV2hHlbOpBrWFw.gif" /></figure><h3>Influencers “winning” by all means necessary</h3><p><strong>Prompt engineering</strong> spreads the way traits spread under selection pressure: tiny “mutations” in phrasing get tested in the wild, the versions that outperform get copied, and the ones that don’t quietly go extinct.</p><p>A prompt framework that reliably produces cleaner UI specs or higher, converting flows behaves like a fit phenotype in a shifting environment, it propagates through templates, threads, team playbooks, and eventually product defaults.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*jpseDwpUHIZEwsKKE3vyXA.jpeg" /><figcaption><strong>Simplified Visualization: </strong>Like evolution, prompt engineering spreads through many small “mutations” (prompt tweaks) and harsh selection (what performs gets copied), but the real “adaptation” shows up at the ecosystem level as winning patterns become templates and defaults, moving the baseline forward even if it eventually makes individual advantages (and some design skills) obsolete.</figcaption></figure><p>Over time, this turns into a recursive evolutionary loop. Repeated wins become standards. Standards become products. Products get baked into model behavior. The baseline rises for everyone, and competition tightens.</p><blockquote>“Natural selection isn’t a committee, it’s an algorithm. It optimizes for individual advantage, even when the collective bill comes due later.”</blockquote><p>In plain terms, any design skill that can be clearly described and repeatably executed starts to slide out of “craft” and into automation. That doesn’t kill design, but it does force a shift. Less hand-built interface production. More constraint-setting, system orchestration, and harder calls about tradeoffs between <em>human experience</em> and <strong>business fitness</strong>.</p><blockquote>“When prompt patterns go viral, they become trajectories. Eventually the model learns the shape of the trick, and it becomes the floor.”</blockquote><p>So design doesn’t disappear. It changes shape. It splits into higher-order work that machines can’t fully own yet: defining boundaries, coordinating systems, and deciding what the product is allowed to do to people when the pressure is on.</p><p>I imagine some of that felt heavy, so to make sense of it, and to stay honest to my own lived experience, I turned it into a fictional story that shows how it plays out in a designer’s day-to-day.</p><h3>Selection Pressure: Real-life Storytelling</h3><p>The first time I heard the phrase <em>prompt engineering</em> out loud, it wasn’t in a lab or a lecture hall or any of the places words go when they want to look important.</p><p>It was in a kitchen.</p><p>Someone had left a half-dead succulent on the windowsill (it looked betrayed), the dishwasher was humming like it had a secret, and my friend June, barefoot, hoodie, hair in a messy knot that screamed <em>I’m brilliant but I’m tired, </em>said, “Okay, so… prompt engineering is basically talking to a machine until it becomes you.”</p><p>She said it like a joke. But she didn’t laugh.</p><p>I did that thing where you laugh anyway, just to keep the air light. Like you’re tapping the glass to see if it’s going to shatter.</p><p>“Until it becomes you,” I repeated. “That’s… not ominous at all.”</p><p>June slid her laptop across the counter. On the screen: a blank prompt box, blinking like a tiny lighthouse warning ships away from the rocks.</p><p>“Watch,” she said.</p><p>And here’s where it gets slippery. Because what she did next didn’t look like engineering. It looked like confession.</p><p>She started typing, then stopped, then typed again. She wrote in fragments. She asked for tone, <em>casual but precise, </em>then changed her mind, <em>no, more human, a little annoyed, like I’m explaining this for the third time</em>. She added constraints like she was building a fence around a thought. And with every added detail, the fence got tighter.</p><p>“People think it’s about finding the magic words,” she muttered, “but it’s actually about sanding off ambiguity.”</p><p>She hit enter.</p><p>The model answered, clean and crisp, with the exact kind of clarity June always had when she spoke in meetings. It even had her annoying habit of pausing mid-sentence to drop an aside, like a little wink. She leaned back, satisfied, like she’d just tuned a guitar string to perfect pitch.</p><p>And that’s when I felt it. Not fear exactly. More like… a quiet vertigo.</p><p>Because if you can tune a machine to your voice, you can also tune it <em>past</em> your voice. You can tune it until it doesn’t need you to play the song anymore.</p><p>June was building a brand. Thought leadership. Templates. Guides. She posted threads that did numbers. She wrote “how-to” articles that people saved like survival manuals. And it was working-followers climbing, DMs filling, conference invites rolling in.</p><p>“I’m helping,” she said, almost defensive, like she could hear the accusation in the air even when no one said it. “People deserve to know how to get good output. This stuff is confusing.”</p><p>“Sure,” I said. “But you’re also… teaching the machine the job.”</p><p>June’s smile twitched. “I know.”</p><p>There it was. The weird honesty. The part no one wants to put in a carousel post.</p><p>A few days later I visited her studio, one of those open, plan spaces that tries to feel like a creative sanctuary but mostly feels like a warehouse for anxiety. Her team had a wall of sticky notes like a bright, cheerful crime scene. Someone had written <em>DELIGHT</em> in all caps, underlined twice, as if delight could be bullied into existence.</p><p>June pulled up Figma. Hundreds of components. Buttons with states. Inputs with hover styles. Tokens named with the careful neatness of someone trying to control chaos with naming conventions.</p><p>“This,” she said, tapping the screen, “used to be the craft.”</p><p>I watched her open another tab, an AI tool with a friendly little blinking cursor. She spoke into her mic like she was leaving a voicemail for the future.</p><p>“Build a starter design system for a B2B dashboard,” she said. “Use Tailwind-like spacing logic. Use accessible color contrast. Make the components modular. Give me tokens. Then generate React components and connect them to the tokens.”</p><p>She paused. Then, like a chef adding salt.</p><p>“Also: avoid that default SaaS look. A little personality. But not precious.”</p><p>The output arrived in chunks: token tables, component specs, code scaffolds, even suggestions for how to document usage. The whole thing landed like a pallet of neatly stacked boxes.</p><p>I hated how impressive it was.</p><p>June didn’t look excited. She looked… resigned. Like she’d just watched a magic trick she already understood and still couldn’t stop.</p><p>“See?” she said softly. “So what is ‘design system skill’ now? Is it building the pieces… or is it describing the pieces well enough that something else builds them?”</p><p>I didn’t have a clean answer. The clean answers were the problem.</p><p>On the train home, I opened my phone and scrolled through a thread from someone I didn’t know. “DROP YOUR BEST PROMPTS,” it said, as if prompts were recipes and we were all hungry. The replies were stacked like dominoes: formatting frameworks, role instructions, tone guides, little incantations.</p><p>Everyone trying to be helpful. Everyone trying to be seen.</p><p>I started to understand something ugly and obvious: virality is a kind of extraction. You take what’s in your head, your hard-won tricks, your instincts, your muscle memory, and you pour it into public view. The internet claps. The machine watches. The market adjusts. And then the trick becomes the baseline.</p><blockquote>“So what is ‘design system skill’ now?</blockquote><p>A month later, June called me after midnight.</p><p>“I think we’re speeding it up,” she said.</p><p>“What?”</p><p>“The replacement. The evolution. Whatever you want to call it. The more specific we get, the more we teach it. And the more we share, the faster everyone else gets good at being specific. It’s like… recursive.”</p><p>She sounded tired. The kind of tired that isn’t fixed by sleep.</p><p>“June,” I said, “you okay?”</p><p>There was a silence. Then a little laugh, not happy.</p><p>“I’m a designer,” she said. “I’m literally paid to reduce uncertainty. And now I’m watching uncertainty, human uncertainty, get treated like a bug.”</p><p>That’s the thing nobody says in the glossy posts: prompt engineering is a battle against misunderstanding. It’s a campaign to make your intention legible. And that sounds noble, until you realize misunderstanding is where the surprises live. The weird little mutations. The accidents that turn into breakthroughs. The half-formed idea you didn’t know you wanted until you saw it.</p><p>When you sand ambiguity down to nothing, you get fewer mistakes. You also get fewer miracles.</p><p>A week after that call, June’s company had an all-hands. She invited me to sit in, like I was a cousin at a family meeting.</p><p>Their CEO was in full performance mode — bright smile, brave voice, charts that went up and to the right like obedient dogs.</p><p>“Competition is tightening,” he said. “We need to move faster. We need higher conversion. Cleaner funnels. Retention, retention, retention.”</p><p>He didn’t say <em>people</em> much. He said <em>users</em>. He said <em>segments</em>. He said <em>churn</em> like it was a weather pattern.</p><p>Then product leadership presented a “cancellation improvement.” I’m not making this up: they had two flows.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2DB9SzeOlySCfiupK6IN6g.png" /><figcaption><strong>“User-centric Design”: </strong>One option is best for the user goal and the other is exclusively meant for business outcomes with intentional friction.</figcaption></figure><p>One was parallel, straight to delete. Quick. Humane. The other was sequential: cancel, confirm, survey, offer discount, confirm again, show an ad, ask for feedback, confirm again, then delete. A little obstacle course of pleading.</p><p>The PM smiled like a magician revealing the final card.</p><p>“Sequential keeps users longer,” he said. “We can insert rescue moments.”</p><p>June’s jaw clenched. She didn’t speak.</p><p>I leaned toward her. “You’re going to say something.”</p><p>“I can’t,” she whispered.</p><p>“What do you mean you can’t?”</p><p>She stared at the screen like it was a mirror.</p><p>“Because the math will win,” she said. “It always does when the margins get thin enough.”</p><p>I felt a small, sharp sadness at that. The kind you get when you realize someone has been holding the line for years and they’re finally tired.</p><p>Outside, after the meeting, she lit a cigarette even though she’d quit two years ago. She took one drag and looked offended by her own decision.</p><p>“User-centered design,” she said, exhaling. “Such a pretty lie.”</p><p>“It’s not a lie,” I protested, automatically, like I was defending a childhood friend.</p><p>June shook her head. “No. It’s a luxury. It’s what you do when you’re winning and you have time. When you’re not under siege.”</p><p>Her phone buzzed. A Slack message. Another. Her attention snapped away, like a leash tightening.</p><p>“Okay,” she said. “Here’s the part that really messes with me.”</p><p>I waited.</p><p>“If everyone gets a genie,” she said, “everyone gets their wish. And the world can’t survive that. Not because wishes are evil. But because wishes collide.”</p><p>I thought about it for a second and immediately wished I hadn’t. Because she was right. A genie for every person means eight billion visions trying to manifest at once, all stepping on each other’s toes. Someone’s dream restaurant opens on the corner and destroys someone else’s dream grocery store. Someone’s perfect product ships tomorrow and wipes out a hundred careers by Friday. There’s no villain in it. Just… collision.</p><p>June flicked ash into a paper cup.</p><p>“We keep saying ‘what do you want?’” she said. “Prompting. Optimization. Clarity. But people don’t even know what they want. Half the time they want a feeling and they describe it like a goal.”</p><p>I remembered my own prompts. The ones where I asked for “more authority,” “more confidence,” “more compelling.” Translation: <em>please make me feel safe in a world that’s shifting under my feet.</em></p><p>I didn’t tell June that. I just nodded.</p><p>“And the internet,” she added, “it’s like… fear travels faster than hope. You can watch it happening. People feed each other dread until it becomes the only shared story left.”</p><p>“Yeah,” I said. “It’s like a feedback loop.”</p><p>“Exactly,” she said. “Fear has SEO and a marketing team.”</p><p>She smiled at that one, just a little. Then her face fell again.</p><p>“So what do we do?” I asked.</p><p>June shrugged, helpless for the first time I’d ever seen her.</p><p>“I think we need… three big goals,” she said slowly. “Like, for humanity. Not slogans. Not corporate values. Real north stars. Loose enough that people can live inside them, but solid enough that we aren’t all running in opposite directions with our genies.”</p><p>“Such as?”</p><p>She laughed. “If I knew, I’d be selling a course.”</p><p>We stood there in the cold. Cars hissed by. Somewhere a siren wailed, city soundtrack, always.</p><p>June looked at me and her voice softened.</p><p>“Prompt engineering isn’t really about the machine,” she said. “Not at the core. It’s about learning how to say what you mean. How to ask. How to admit what you actually want.”</p><p>“And what do you actually want?” I asked.</p><p>She blinked, caught off guard. Like no one had asked her that without turning it into a KPI.</p><p>June stared at the streetlight for a long moment.</p><p>“I want people to stop confusing users with humans,” she said finally. “I want us to build things that don’t treat leaving as a sin. I want creativity back, not as decoration, but as breathing room.”</p><p>A pause. Then, quieter:</p><p>“And I want to not feel like I’m training my replacement every time I try to help someone.”</p><p>I didn’t have the perfect response. I didn’t try to generate one, either.</p><p>I just said, “Yeah. Same.”</p><p>And that was the story, really. Not the prompt box. Not the templates. Not the shiny output.</p><p>Just two people standing under a streetlight, trying to name the difference between a human need and a business objective, trying to remember that friction isn’t always a feature, trying to figure out how to talk to the future without feeding it the knives it will use on us.</p><p>Maybe prompt engineering is an interesting endeavor. Sure.</p><p>But it’s also a mirror.</p><p>And mirrors don’t care if you like what you see.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7e2c318b8970" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/the-prompt-driven-evolution-of-design-7e2c318b8970">The prompt-driven evolution of design</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The DNA of Culture: Rewriting Our Collective Emotional Destiny]]></title>
            <link>https://medium.com/@ry_stephen/the-dna-of-culture-rewriting-our-collective-emotional-destiny-bb7576cd9bee?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/bb7576cd9bee</guid>
            <category><![CDATA[ai]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[emotional-intelligence]]></category>
            <category><![CDATA[genetics]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Mon, 22 Dec 2025 18:15:39 GMT</pubDate>
            <atom:updated>2026-06-09T01:32:32.934Z</atom:updated>
            <content:encoded><![CDATA[<h4><strong>A Conceptual Framework for Biocultural Evolution</strong></h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Bd8D13z6kI1sIjPrP9Q74Q.jpeg" /></figure><p><em>This hypothesis and research is unfinished because whether or not it is valid, I don’t want to do this alone. Looking for co-authors to script branches of a better future.</em></p><h4>Interconnected Project</h4><p>This concept and hypothesis is part of the <a href="https://www.helloyouexperiment.com/">Hello You Experiment</a> and <a href="https://www.youtube.com/watch?v=V_wOHL2zriM">Consorted 2026 — Communication for Meaningful Things</a> (user flow for designers).</p><iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2F1Dn-UHx0Pjc%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3D1Dn-UHx0Pjc&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2F1Dn-UHx0Pjc%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" width="854" height="480" frameborder="0" scrolling="no"><a href="https://medium.com/media/a65271047a4abfc045f1e7607771bf91/href">https://medium.com/media/a65271047a4abfc045f1e7607771bf91/href</a></iframe><h3>Intro</h3><p>Imagine a world where your great-grandparents’ most intense fear, not just their physical features, was somehow wired into your DNA.</p><p>It’s not science fiction. It’s the core of a new <a href="https://docs.google.com/document/d/1LQO9c8T0lff-k9oz2Ei2M4Vpx4eAMBHzjbb76hIZ9Jg/edit?usp=sharing">Biocultural Evolution Framework</a> that suggests our collective trauma, including everything from wars and systemic oppression to community-wide stress, is not just a memory we carry in our minds. Instead, it is a “biological memory” written directly onto our genes, making us biologically predisposed to believe certain cultural narratives.</p><p>In plain English, here’s the framework’s hypothesis: Extreme emotional experiences write a biological script onto your DNA. That script then acts as a fertile host for cultural ideas that match it, creating the self-perpetuating, seemingly “unfixable” problems of our time.</p><p>The good news? This system is symmetrical. We might be the self-help authors of our own evolution.</p><h3>Part 1 | The Biological Substrate: How Your Emotions Edit Your DNA</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*iQN8iE_vwsv7B1VSdcPQhQ.jpeg" /><figcaption><strong>The Neuro-Immune-Endocrine Axis (PNI) acts as the physical bridge, translating the subjective experience of intense emotion or stress into a precise chemical signal, like cortisol, that can directly modulate our genes.</strong></figcaption></figure><p>The pathway from your feelings to your physical body isn’t metaphorical; it’s a hardwired system called Psychoneuroimmunology (PNI).</p><p>Think of it as the body’s translator:</p><ul><li>The Signal (PNI): When you experience something intensely emotional (trauma or “toxic stress”), your stress-response system (the HPA axis) floods your body with hormones like cortisol. This is the physical signal that moves the experience from your mind to your molecular self.</li><li>The Recording Medium (Epigenetics): This signal goes to your DNA’s epigenome. Epigenetics doesn’t change your code (the A, T, C, G letters), but it adds chemical “Post-it Notes” (like DNA methylation) that act as dimmers, determining how much or how little your genes are expressed.</li><li>The Biological Memory: The result is a stable molecular imprint. You don’t get a cognitive memory of the event, but you get a biological memory. For example, trauma can “tune” your stress system to be hair-trigger sensitive, essentially being born expecting a dangerous world.</li></ul><h3>Part 2 | The Inheritance of Experience: The Biocultural Loop</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*pKGRwEj52_3imk9YkRaVIQ.jpeg" /><figcaption>The most robust mechanism for the intergenerational transfer of experience is the “Biocultural Loop.” The parent’s trauma-induced epigenetic mark contributes to altered behavior (phenotype), which, in turn, creates an environment of early life stress for the offspring.</figcaption></figure><p>So, does this “biological memory” get passed down? The research suggests yes, not necessarily by a direct genetic mechanism, but through a recursive, social-biological feedback loop.Inheriting Predisposition, Not Trauma</p><p>What’s inherited is not the trauma itself, but a predisposition, which is a dysregulated stress-response system.</p><p>Studies on descendants of trauma survivors (like those of the Holocaust) suggest epigenetic changes in stress-regulating genes. The child isn’t born remembering the fear; they are born biologically primed to react more strongly to stress.</p><p>The primary way this is thought to be passed on is the Biocultural Loop:</p><ol><li>Generation 1 (F0) experiences trauma, resulting in an epigenetic mark and an altered emotional phenotype (e.g., heightened anxiety).</li><li>This altered phenotype changes their parenting behavior (e.g., they become less available, more stressed).</li><li>This altered behavior creates “early life stress” for Generation 2 (F1).</li><li>This new experience re-creates a new epigenetic mark in F1.</li></ol><p>In this model, the biological mark is re-acquired in each generation via the social environment, locking biology and culture into a tight feedback loop.</p><h3>Part 3 | From Genes to Memes: The Missing Link of Cultural Evolution</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TlDV53KpdcMzDHaGxzYUJg.jpeg" /><figcaption><strong>The Epigenetic Replicator: Solving the “Missing Substrate” Problem</strong></figcaption></figure><p>Classic memetics (the idea that cultural units, or memes, jump from mind to mind) was criticized because ideas aren’t stable like DNA. They lack a physical substrate and mutate constantly.</p><p><strong>This framework solves that “missing substrate” problem:</strong></p><ul><li>The Replicator is not the Idea (Meme).</li><li>The Replicator is the Epigenetic Predisposition (Biological Memory).</li></ul><p>The idea (the meme, like a narrative of mistrust or fear of outsiders) survives and replicates successfully when it resonates with the inherited, biological predisposition of its host.</p><p>The predisposition is the fertile host, and the meme is its behavioral expression. A community whose stress systems are epigenetically tuned for danger will be far more receptive to cultural narratives that confirm the world is, in fact, dangerous. This connection provides the missing physical engine for our cultural beliefs.</p><h3>Part 4 | The Architecture of Change: Prototyping Future Meanings</h3><p>This synthesis gives us a powerful new way to diagnose society’s toughest challenges, often called “Wicked Problems.”</p><p>A wicked problem, such as cyclical conflict or systemic inequality, is “wicked” because it’s not just a policy issue; it’s an entrenched, stable biocultural loop built on inherited biological predispositions, cultural memes, and an ossified collective memory that justifies the whole thing. A new law won’t erase the inherited anxiety.</p><h4>The Intervention: Using Design to Rewrite the Script</h4><p>Since the system is symmetrical, the intervention must also be physical and collective.</p><p>If negative, stressful events (trauma) can negatively program the epigenome, then positive, intentional practices can positively influence it. Research shows that mindful practices like meditation or Yoga can reduce the HPA axis stress signal and positively influence gene expression.</p><h4>The final step of the framework is prescriptive: use Social and Speculative Design to prototype new collective interventions.</h4><ul><li>Speculative Design surfaces the hidden script. By imagining a fictional future (for example, a “clinic for editing inherited trauma”), we force a community to externalize and confront their deep-seated beliefs about their past.</li><li>Social Design implements the positive script. This means prototyping new community rituals, shared mindful practices, or public spaces designed to leverage positive PNI mechanisms.</li></ul><p>The goal is to consciously engineer social practices with the express goal of creating positive epigenetic signatures and, in effect, prototyping new, healthier collective memories.</p><p>We are not just passive products of our past. By understanding the deep, physical connection between our emotions, our genes, and our culture, we gain the ability to intentionally intervene in our own evolution.</p><p><em>This hypothesis is unfinished.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=bb7576cd9bee" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The chemistry of sustainable startups]]></title>
            <link>https://medium.com/@ry_stephen/the-chemistry-of-sustainable-startups-67cf507c476f?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/67cf507c476f</guid>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 16:56:03 GMT</pubDate>
            <atom:updated>2026-07-28T18:24:46.710Z</atom:updated>
            <content:encoded><![CDATA[<h4>A new model for building resilient teams in the age of AI</h4><p>Startups begin with passion, trust, and closeness, then trade all three for scale, process, and hierarchy. I don’t think that trade is required anymore.</p><p>Le Chatelier’s principle describes how a chemical system under pressure shifts to relieve it. Companies do the same thing. Add capital, headcount, and process fast enough and the system compensates somewhere else, usually in the part that made the work worth doing. What’s changed is that AI lets you take things out of the equation. Fewer people, fewer layers, less capital, less process, and there’s suddenly room for the closeness that normally gets spent on growth.</p><h3>The Passionate Beginning</h3><p>Two people in a room with a problem they care about too much. No hierarchy yet, just hunger.</p><p>Everyone builds. The CEO designs the homepage, answers tickets, and wires up Stripe at 2am on a shared screen. The engineer sketches brand marks between commits. The product person runs interviews, writes copy, and keeps the site from falling over. It’s chaotic and it’s human.</p><p>Nobody has made a deck. Nobody has OKRs. There are late-night brainstorms, demos on a kitchen table, and the feeling that this might actually work. For the founding team those days are fulfilling and not just fun, because everyone is close to the work, close to the customer, close to each other. Brian Chesky has described doing all of it himself in Airbnb’s first year, the design and the support and the product photography, and calling it messy and loved.</p><blockquote>“In the beginning, I did everything. I was the designer, the customer support agent, the photographer. It was messy, but I loved it.” — Brian Chesky, Airbnb</blockquote><p>Then the company grows.</p><p>Somewhere between the funding rounds and the hiring sprees and the advisors telling you to focus on scale, something shifts. Roles formalize. Hierarchy sets. The CEO steps back from the work and starts hovering at 30,000 feet, meetings multiply, and the messy heart of the company gets harder to reach. Founders and early employees know this story. The things that made the company special are the first things to go.</p><p>I don’t think it’s inevitable. There’s another way to scale in the age of AI, in meaning as well as size, and it starts with a chemistry lesson.</p><h3>Growth on Autopilot: When Passion Meets Process</h3><p>Growth is the dream and the default. The moment the product finds traction and investors start circling, the playbook kicks in. Hire fast, raise more, define the market, capture it.</p><p>Venture capital brings pressure with it. More capital means more expectations, more expectations mean more headcount, and more headcount means more managers. At some point you stop building a product and start building a company.</p><blockquote>“Growth, when it happens, should be a byproduct of good decisions, not the goal itself.” – Jason Fried</blockquote><p>The systems we use to grow companies were built for predictability, not passion. Board meetings, burn-rate dashboards, quarterly targets, numbers that scale cleanly and feel hollow up close. Passion gets abstracted through layers of alignment meetings and leadership off-sites, and the team that used to build together now manages across time zones and tool stacks.</p><p>Founders feel it first. The more the calendar fills with investor updates and hiring plans, the further they drift from the reason they started. They become operators and fundraisers and strategists, and almost never builders working next to anyone.</p><blockquote>“I mostly sit in meetings now.” – Brian Chesky, co-founder Airbnb</blockquote><p>Everyone else feels it too. The designers and engineers and PMs who joined for the spark find it harder to reach once the company is chasing numbers.</p><p>Leadership isn’t failing here. The system assumes there’s only one direction worth growing, and everything else follows from that assumption. What if a startup could occasionally scale inward instead?</p><h3>The CEO at 30,000 Feet</h3><p>Growth demands altitude. The founder’s role moves from builder to manager to messenger, and at first it’s subtle. They miss a standup, then a product review, then the user calls they used to live for. Before long they’re seeing the product through dashboards and secondhand summaries.</p><p>Stewart Butterfield described gradually stepping out of product decisions at Slack, present in meetings but distanced from the thing he loved building.</p><p>That’s what growth asks. Investors need answers, teams need direction, the company needs a face. So the founder rises, clear of the chaos and far from the texture that made the work mean something.</p><p>Most of them feel the pull to come back. Sometimes it’s nostalgia. Sometimes it’s the realization that they’re no longer one of the team, and that the work they loved happens behind three layers of insulation now.</p><p>You’ve seen what happens when they return. The CEO drops into a brainstorm and the room goes quiet. Slides get polished. The mess disappears and everyone says the safe thing.</p><p>On paper it looks healthy, a leader staying connected. In the room it changes everything. A CEO introduces gravity no matter how well-intentioned they are. People measure their words. Ideas get sanded down before anyone says them out loud. Teams start preparing for the brainstorm a week in advance, which I’ve done myself and watched other people do many times.</p><p>Self-preservation replaces the vulnerability that creative work needs. Even in a meeting labeled a safe space, everyone knows titles travel and impressions made in uncertain moments stick. A fumbled thought, a half-formed idea, a question that sounds too basic. None of it should matter and all of it does. The CEO forgets. The team doesn’t. Six months later in a promotion discussion, someone gets quietly labeled not quite there yet.</p><p>Now picture the opposite. A room where nobody has to posture, where saying “I’m not sure” or “explain this to me like I’m five” is ordinary. The CEO can admit they forgot what a feature does. A junior designer can push back on a senior PM out of curiosity rather than combat. Questions read as engagement instead of gaps in knowledge.</p><blockquote>“When you’re small, it’s like a family. When you’re big, it’s like a nation.” — Tony Fadell</blockquote><p>That room produces better ideas and it produces belonging. The nervous energy of performing turns into contribution. People stop trying to impress and start trying to build. Feedback moves faster and lands more honestly. Nobody has to write the trust down in a document because everyone can feel it, and everyone is willing to show up imperfectly for something bigger than their own standing.</p><p>It only works when hierarchy loosens its grip, when power stops taking all the air in the room, and when leadership is confident enough to be uncertain and present enough to be changed.</p><p>Founders want that room whether they’d name it or not. They had it at the start, when nobody worried about perception and everyone worried about the problem. So why does it get harder to find the higher you climb?</p><p>The founder came looking for connection and became a barrier to it. Not through any failure of their own, but because the system was never designed to scale authority and emotional safety at the same time. The question isn’t whether they should be in the room. It’s whether the room is safe enough for them to belong in it.</p><h3>The Chemistry of Scale</h3><p>Le Chatelier’s principle says that when a system at equilibrium is disturbed, by heat or pressure or a change in concentration, it shifts to counteract the disturbance and settle into a new balance. Reactions stabilize themselves through adjustment rather than rigidity.</p><p>Every product team runs an equation shaped like it.</p><ul><li>Reactants → Team + Time + Trust</li><li>Conditions → Pressure, Process, Tools</li><li>Products → Features + Growth + Satisfaction</li><li>K_eq → Sustainable Team State</li><li>Q → Current Team State</li></ul><blockquote>If a dynamic equilibrium is disturbed by changing the conditions, the system responds to counteract the change and restore a new balance.”</blockquote><p>The gap between K_eq and Q is measurable. Cut a standing meeting and it narrows. Hire four people in a quarter and it widens before any of them has shipped anything.</p><p>Early on the reactants are simple. People, a problem, and a little capital, combined under tight feedback loops and real proximity to users. You get a product, revenue, and momentum.</p><p>Then you raise a Series A, then a B. You hire fast, add departments and managers, and bring in policy and process and expectation. Tobi Lütke has made the point that every person you add to a company makes it harder to move quickly.</p><blockquote>“Every person you add to a company makes it harder to build things quickly.”</blockquote><blockquote>– Tobi Lütke, Spotify</blockquote><p>The system shifts. Output goes up and so do the side effects: distance, bureaucracy, anxiety, burnout. The reaction keeps its forward momentum and gets harder to control, and harder to connect back to whatever you set out to make.</p><p>We’ve accepted that as the price of scale. Dilute intimacy to grow. Trade craft and proximity for headcount and valuation. But a chemical reaction isn’t a one-way trip from reactants to products, and I don’t think a company is either.</p><h3>Reversing the Reaction</h3><p>For two decades we’ve pushed in one direction. More people, more capital, faster shipping, all on the logic that more input produces more output. Le Chatelier says systems seek balance, and past a certain pressure the growth starts costing you stability and clarity.</p><p>AI makes the other direction practical. A startup that needed twenty engineers, five designers, four product managers, and an ops layer to run a platform can now get comparable output from a much smaller team with better tools.</p><p>That changes the conditions. Fewer people means fewer layers and fewer misalignments, less need for rigid process, and less pressure to raise a round big enough to cover payroll. Fewer outside investors means fewer external agendas defining what success looks like. In chemical terms you’re lowering the concentration of the unstable inputs to bring the system back toward equilibrium.</p><p>None of that means giving up growth. It means owning how you grow.</p><p>Instead of renting a dozen SaaS tools, your team can build lightweight internal ones shaped around how you actually work. Paying $20k a year for software that tracks OKRs is a choice, not a requirement. Your designers and engineers can spend part of their skill designing the company itself, its workflows and rituals and systems. Gokul Rajaram has argued that internal processes deserve product treatment, with users and friction and iteration.</p><p>That inward work doesn’t slow you down. It costs less than the tools it replaces and it fits your culture instead of someone else’s. It also turns the team you already have into a second founding team, evolving the environment rather than just executing the roadmap.</p><p>And the company stabilizes. Momentum keeps running while meaning catches up to it.</p><h3>Scaling Meaning Instead of Headcount</h3><p>Cutting headcount, reducing reliance on VC capital, and building your own systems does more than lower the operational noise. It makes space for meaning, which is rare in startups.</p><p>In most companies, proving traction is the signal to scale, and scale almost always means more. More people, more process, more complexity. Every layer added makes it harder to remember why any of it matters.</p><blockquote>“We don’t have goals. Goals are fake. They’re made up. What we do have is direction.”</blockquote><blockquote>– Jason Fried</blockquote><p>Growing inward changes that. The engineers and designers and marketers you already have stop being a workforce and start being an extended founding team, shaping how the company operates and what it values instead of executing someone else’s vision of it. They chase craft instead of scale. They get visibility by default instead of fighting for it. They help invent a model of growth measured in more than revenue.</p><p>A company like that doesn’t need quarterly morale boosters or an all-hands deck declaring its values. The values show up every time someone suggests a better way to do something, builds a tool that saves a teammate an hour, or designs a process that puts people first.</p><p>I don’t think culture should belong to a separate HR team. Too often it gets imposed by policy when it should be cultivated by the people living in it. HR departments inherit responsibility for culture without the context, the psychological training, or the creative grounding to do it well, and the result is a cascade of generic frameworks, performance ladders, values decks, and quarterly rituals imported wholesale from companies that have nothing in common with yours.</p><p>Growth defined by rigid template starts to feel like compliance rather than development. People get slotted into categories that miss their motivations, their learning styles, and most of what they actually contribute.</p><p>Every team has its own equilibrium. When the working state drifts too far from the state the team can sustain, the system pushes back, and you feel it as burnout and misalignment and tension in meetings nobody wants to attend. A team can move fast inside its own equilibrium and pay nothing for it. Outside that range the speed stops being a useful number, because the output gets paid back later as attrition.</p><blockquote>“Leaders need to inspire optimism, not just drive outcomes. A sense of purpose and belonging isn’t a soft luxury, it’s a performance advantage.”</blockquote><blockquote>– Satya Nadella, CEO of Microsoft</blockquote><p>When the team takes ownership of that, growth becomes personal and feedback becomes relational. Development turns into a living system instead of a spreadsheet. AI is accelerating execution, which finally leaves room to slow down the human side of the work, build individualized paths and real feedback loops, and respond to what people need instead of what the checklist says.</p><p>You stop asking how fast you can grow and start asking what kind of company you want to grow into.</p><p>Development becomes a living system, not a spreadsheet.</p><p>With AI accelerating execution, we finally have room to slow down the <strong>human</strong> side of work, to create individualized paths, build custom feedback loops, and adapt to real needs instead of bureaucratic checklists.</p><h3>When the Company Builds Itself</h3><p>Once a company stabilizes by shedding pressure rather than by stagnating, it can go back to the question that used to sit at its center. What do we actually need, and who do we want to become?</p><p>Maturity through cohesion beats maturity through headcount. The team stops racing to integrate third-party tools and starts designing systems from the inside, built by the people who use them for the problems they actually have.</p><p>You don’t need a perfect career ladder when each person can define their own direction with peers who understand their context. Want a promotion? Find a way to cut internal cost, build something that improves the product in a way that shows up in revenue, or connect two teams that keep missing each other. Be specific to your environment instead of leaning on a scoping document written to be vague enough for anyone and meaningful to no one.</p><p>You don’t need seven HR platforms when a single tool for feedback, reflection, and growth can be built to match your culture. You don’t need to burn out chasing abstract velocity when the team has clarity and autonomy and a shared reason to be there.</p><blockquote>“If you give a good idea to a mediocre team, they will screw it up. If you give a mediocre idea to a great team, they will either fix it or come up with something better.”</blockquote><blockquote>– Ed Catmull, co-founder of Pixar</blockquote><p>None of this is theoretical. Small teams are already doing the work of large ones with lightweight AI, agents, and modern frameworks, and often doing it better.</p><p>Give people the chance to build the systems around them and they don’t disengage. They go deeper. Engineers build the internal tools they always wanted. Designers shape better ways to share feedback. PMs stop chasing sign-off and start designing rituals that make collaboration happen.</p><blockquote>“No matter how brilliant your mind or strategy, if you’re playing a solo game, you’ll always lose out to a team.”</blockquote><blockquote>– Reid Hoffman, co-founder of LinkedIn</blockquote><p>The company becomes its own product. Every internal tool is a tuning knob, a way to lower pressure and move the system closer to stability without giving up momentum. What drives it is the daily experience of the people building it rather than a shareholder deck or a hiring target.</p><h3>Returning to Equilibrium</h3><p>If startups are systems, and they are, we should stop designing them like machines.</p><p>For decades we’ve built companies around the belief that success means growing faster and bigger and louder, that traction must be followed by a round and a headcount goal and a run at market share, and that the only direction is forward. Chemistry doesn’t work that way. Neither do people who make good things.</p><p>Le Chatelier’s principle says systems under pressure push back, not because they’re breaking but because they’re trying to survive. Startups do it too. When headcount grows faster than trust you get dysfunction. When output scales faster than clarity you get burnout. When leadership rises faster than connection you get disillusionment. And we keep pushing anyway, chasing growth while quietly grieving the closeness and the curiosity and the sense that you mattered as more than a resource.</p><p>We finally have the tools to rebalance, and maybe the urgency too. AI changed the math. It builds more with less and automates the low-leverage work that used to need whole departments, and more importantly it frees up room for intent and craft and each other.</p><p>That’s a chance to scale consciously instead of recklessly. To bring leaders back into the rooms they miss as collaborators rather than bosses. To let teams build the foundation they stand on as well as the roadmap. To make culture something you feel in the tools you use and the people who show up for you when the work is hard, instead of a bullet point in a handbook.</p><p>Even hiring changes shape. You stop measuring candidates against a framework and start remembering the moments where someone showed up curious and candid and real, and you say: I’d build with this person, and I’d fail with them too.</p><p>That should be the new model. Leaders who don’t disappear into strategy decks. Small teams that don’t have to grow exponentially to prove their worth. Internal systems designed as carefully as the customer-facing ones, because your people are users too.</p><p>None of that means abandoning ambition. It means redefining it.</p><blockquote>“Success at the wrong thing doesn’t make you happy.”</blockquote><blockquote>– Ev Williams, co-founder of Twitter</blockquote><p>Healthy companies don’t succeed by scaling endlessly. They find their own equilibrium and then design every part of the system to protect it because a system in balance doesn’t stall. It holds its shape while it keeps reacting, which is what fulfillment looks like at company scale.</p><p>— — —</p><h4>Note:</h4><p>(Nov. 11, 2025 10:50 PM) Need to add pictures but the pictures are for you; this article was for me, to get a concept out of my head. I never expected it to inspire you without entertaining you first.</p><p>RSi.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=67cf507c476f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Personal Brand is Broken]]></title>
            <link>https://medium.com/@ry_stephen/the-personal-brand-is-broken-9d68852acbd7?source=rss-5c6afe116ca------2</link>
            <guid isPermaLink="false">https://medium.com/p/9d68852acbd7</guid>
            <dc:creator><![CDATA[Ryan Stephen]]></dc:creator>
            <pubDate>Tue, 11 Nov 2025 16:20:05 GMT</pubDate>
            <atom:updated>2025-11-11T16:20:05.289Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Wildfire</strong></h3><p>You must have noticed that everyone these days are building “personal brands” and offering some sort of service, product, or both. It’s like an uncontrollable wildfire that is spreading exponentially.</p><p>Before the internet, there were essentially two groups of photographers: pros (small) and amateurs (large). We lowly amateurs looked up to pros for inspiration and education in the form of books, workshops, interviews, and anything else we could consume. These guys were are heroes. Every pro had their own unique style and their names were synonymous with thought leadership in their respective areas. As amateurs, we pushed ourselves to get better with the hopes that one day we would become “pro” and enjoy all the opportunities that came with it.</p><p>Then the internet messed everything up.</p><p>We got connected and instead of looking up at the pros, we started looking left and right at the amateurs around us. Then, we looked down and quickly realized there were huge groups of people less skilled than we were.</p><p><em>“Are we pros to them?”</em> I overheard someone ask softly. There was a pause.</p><p>A man starts progressively starts nodding his head. <em>“We can be.” </em>There was a bustle in the room as shoes were shined, hair was combed, and backs were straightened. We were born anew. That was the day we all turned “pro”.</p><p>Today, we teach, inspire, and sell to the groups below us which means we all compete with those above us for marketshare. Worse, we have to assert our “pro-ness” at job interviews and to our clients.</p><p>Basically everyone is a “pro” now and it makes it hard to compete if you don’t have a personal brand that highlights your strengths and makes you unique. It’s a wildfire that’s out of control. <em>Burn, baby, burn.</em></p><h3>Brand Me</h3><p>The purpose of branding is to be recognizable, memorable, and to establish differentiation in a competitive marketplace (that’s a simple explanation). Branding enables us form primitive “ideas” about products so we can make faster and (ideally) better decisions.</p><p>Would you buy an unlabelled generic bottle of mouthwash over a branded bottle if the cost were the same? Probably not.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/800/1*L1J2GHDRjmZKgh-X3j1nIQ.jpeg" /><figcaption>Which would you choose on a shelf?</figcaption></figure><p>I know nothing about the generic mouthwash other than that bottle shape looks like trashcan and the black cap isn’t helping. It might be misplaced toilet cleaner, how do I know? The branded bottle looks professional and clearly inspires trust. “Long lasting protection” speaks to the problem I am trying to solve and I <em>believe</em> it would be the best choice for me.</p><p>So what is personal branding? It’s our <em>conscious</em> attempt to shape our image so that people (consumers, recruiters, etc.) can quickly categorize positively to increase conversions (sale, job, etc.).</p><p>It is important to note that branding blurs the truth because it doesn’t generally highlighting flaws, shortcomings, or inefficiencies. <em>96% yellow-5.</em></p><h3>Sheryl Sandberg<strong> isn’t a fan</strong></h3><p>Here’s what the ivy league tech executive billionaire said in a recent <a href="https://www.youtube.com/watch?v=Qym57NxPwg4">interview</a> (starts at 30:45):</p><blockquote>“If you think you are building your personal brand, please don’t. You don’t have a brand. Crest has a brand. Perrier has a brand. When I hear anyone talk about building their personal brands, I know that’s not right….The reason it’s not right is that products are marketed… But people are not that simple. We’re not packaged. And when we are packaged, we are ineffective and inauthentic. I don’t have a brand, but I do have a voice…if you think you are building a personal brand then you will not have the career you want to have because you will not be authentic. Don’t package yourself, just speak and speak honestly.”</blockquote><p>FYI — There are many people living the good life, doing what they love and with financial freedom all because they built powerful personal brands.</p><p>Executives will never understand the freelance hustle where the smallest ting of personal branding could mean making rent that month. If you know anything about the creative industry then you know that it operates on the <em>blag it</em> system which means we say we can do things we’ve never actually done before. This is okay because we put in 90 hours making it happen and only bill for 30. <em>Ramen again?</em></p><p><strong>But…Sandy is COMPLETELY RIGHT.</strong></p><p>Watch that section of the interview because she is actually trying to make a monumental point which is that we are people…[saved as a draft in 2017]</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*I1Ly3zJXSCeAJTS2s_IxsA.png" /><figcaption>Breadcrumb in time…waiting to be reinterpreted.</figcaption></figure><p><strong>Edit:</strong> (Nov. 11, 2025) I wrote this in 2017, and it’s been sitting in my drafts ever since. I don’t remember where I was going with it, and I don’t care to finish it. Reading it again reminded me about what I felt, if you feel the need to write the rest so that you feel something, many of us would learn more about you and would follow you down the rabbit hole 🐇.</p><p>RSi.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9d68852acbd7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>