Designers vs. The Machines
from Insanely Generative Hosted by Paul Henry Smith
I want you to picture a very specific person, because this is not a philosophical debate. This is a career situation. You’re a UX designer. You love Figma. You love the feeling of turning a messy problem into clean, tasteful UI. You love speed. You love craft. You love being the person who can crank out a polished flow while everyone else is still arguing about what the feature even is. Your portfolio is screens, screens, screens—beautiful, consistent, modern screens—and hiring managers love you for it. They barely read anything. They scroll. They nod. They go, “Yep. This person can ship.” That person might be you. It might be your teammate. It might be half the industry. Now here’s the moment that made me stop and stare at the wall for a while: I saw a job posting from PayPal that wasn’t shy about where this is going. It wasn’t “AI-assisted design tooling.” It wasn’t “copilot for designers.” It was basically: we want to automate the production of UI and connect it directly to live business inputs—revenue, conversion, telemetry, trends, real-time analysis, prediction—and then generate solutions continuously. In plain English: the system sees a signal and changes the interface. Constantly. All day and all night. And if PayPal is willing to say that in public—if they’re comfortable putting that vision in a job description—then you should assume everybody else is thinking it too, even if they’re being quieter about it. Because nobody wants to be the second company on earth to admit they’re trying to automate a whole profession. They want to be the first company to quietly succeed and act like it was “obvious.” So if you’re sitting there thinking, “Yeah, but they can’t replace me, I have taste,” I need you to understand something, and I’m going to say it bluntly because it’s kinder than letting you keep believing it: Taste is not a moat when your taste has already been turned into rules. Most modern design teams spent the last decade doing something that was genuinely smart: standardizing. Tokens, components, pattern libraries, accessibility rules, spacing systems, interaction conventions. It made teams faster. It made products more consistent. It reduced chaos. But it also did something else—something we didn’t want to think about because it ruins the vibe. It made the work legible. If your product has a design system that dictates what “good” looks like, then a lot of downstream UI design becomes: pick the correct component, apply the correct pattern, follow the rules, don’t break anything. That’s not an insult. That’s how you scale. But it also means the work is learnable in the way machines love: lots of examples, lots of constraints, lots of “approved vs rejected,” lots of history. You don’t need a machine that understands beauty. You need a machine that predicts what will pass design review. And we have built an entire industry around making that prediction easier. Now, before you get mad at me, let me be fair to everyone involved, including the so-called “Figma farmers.” A lot of designers didn’t choose to be trapped in UI polish. They were trained into it. They were hired into it. They were rewarded for it. They got promoted for it. And they got hired in the first place because that’s what our hiring processes selected for. This part matters, and it’s not comfortable: during the pandemic hiring boom—when everyone was hiring like drunk sailors—UX teams didn’t scale by carefully selecting for deep systems thinking. They scaled by selecting for what could be evaluated quickly. Screens. We did it. I did it. I sat in interview loops. I watched people scroll portfolios like they were browsing Zillow. “Look at the craft.” “Look at the polish.” “Look at the number of flows.” “Look how fast they can produce.” And bootcamps, being rational businesses, trained people to win that game. They didn’t train “how to kill a feature with a principled argument.” They trained “how to present a case study with a gorgeous Figma flow.” Because that’s what got interviews. So it’s not that product and engineering forced design into a corner and design heroically endured. The uglier truth is that design, under pressure and incentives, overselected for visible output. We trained ourselves to prove our worth with artifacts. And now the artifact factory is being automated. That’s the part that should piss you off—not at the designers, but at the incentive structure we all participated in, because it’s about to cash out. Now let’s get to the real heart of it, because if this were just “AI makes pretty UI,” it’d be annoying but manageable. The real thing PayPal is going after is latency. Traditional UX is slow in a very specific way. Not because designers are slow. Not because teams are dumb. Because the loop is human. A metric moves. Someone notices. Someone convinces others it matters. Research happens. A fix is designed. It gets reviewed. It gets built. It ships. The world changes again. PayPal’s vision is: skip the human noticing-and-coordinating part. Wire the system directly into the signals. Let it propose and implement UI changes continuously. That is a very different world. In that world, “being fast in Figma” is not a flex. It’s like bragging that you’re the fastest person alive at hand-washing dishes while the restaurant installs an industrial dishwasher. You’re standing there, sleeves rolled up, like, “Guys, watch me go!” and management is like, “Yeah… cool… anyway…” Now, this is where people either get defensive or go numb, so let me ground it in two very real anecdotes, because otherwise this stays abstract and you can keep comforting yourself. When I worked at AWS, an old friend called me and said—exact words—“Why does setting up IAM roles make me want to commit murder?” Now, was he being dramatic? Sure. But he wasn’t wrong. IAM is not confusing because the buttons are ugly. It’s confusing because the system’s mental model—the way it thinks about identity, permissions, relationships—does not map cleanly onto how humans think about responsibility and access. It’s architecture-first. You, the user, are being asked to understand the machine’s view of the world and behave accordingly. And what does the organization do with that? It doesn’t say, “Let’s rethink how permissions should be modeled for human beings.” It says, “UX, make it clearer.” Which often means: build explanatory UI around an unchanging architecture. Make it navigable. Make it survivable. The second story: I did research with music students using SmartMusic. Teenagers, yes, moody, yes—but listen to what they said. “SmartMusic makes me want to slit my wrists.” And then, quieter but worse: “SmartMusic is what made my brother quit music.” That isn’t about UI polish. That’s about the interaction contract: what the system demands from you, what it remembers, what it punishes, what it rewards, and how it makes you feel while you’re trying to learn. It’s cognitive and emotional architecture. The interface is just the messenger. These two stories are extreme versions of something every designer has seen: the “UX problem” is often that the product was built around the system’s mental model, not the user’s. The UI is then asked to translate the system’s worldview into something humans can tolerate. That’s explanatory UI. And yes, it is real work. It’s hard work. It takes skill. It is not trivial. But it is exactly the kind of work that an AI system—given enough examples—can start doing at scale, because it lives downstream of decisions that are already made. And here’s the crucial point, which is the one that actually matters if we’re talking about a future where machines generate interface all day: the real design work is not just “should we build it or not.” It’s designing the dance between system and person. It’s deciding what the system should know and remember, and what the human should know and remember. That sounds subtle until you realize it’s basically the whole game. If your product makes the user remember fifteen things the system could eas… Get full access to The Generative Gazette at generativegazette.substack.com/subscribe
Embed this episode
No transcript yet.