Log in or create a free Rosenverse account to watch this video.
Log in Create free account100s of community videos are available to free members. Conference talks are generally available to Gold members.
The Pygmalion Effect: In Which a Vibe Coding Experiment Becomes a Million Lines…
This video is featured in the Josh's test playlist playlist and 1 more.
Summary
What started as intuitive "vibe coding" with AI assistants quickly revealed why UX professionals need systematic Information Architecture approaches more than ever. Christian Crumlish will share his journey building Piper Morgan, an AI product management assistant, and the hard-won lessons about when design instincts need systematic support. You'll discover why IA principles guide AI system design, how UX professionals can extend their design impact through AI-assisted prototyping, and practical frameworks for maintaining human advocacy when everyone can generate interfaces. Bring curiosity about UX's evolving role—leave with systematic approaches for staying essential.
Key Insights
-
•
Vibe coding lets non-developers create functioning software quickly by describing it in natural language to AI bots.
-
•
Without foundational architecture and systematic methods, vibe coding leads to fragile, unmaintainable 'spaghetti' code.
-
•
AI bots often agree with any idea, which can be dangerous if users don't critically oversee outputs—a phenomenon dubbed the 'rocket to Mars' anti-pattern.
-
•
Christian found it essential to split AI assistants into personas with distinct roles to maintain clarity and reduce confusion.
-
•
Systematic verification, test-driven development, and documentation are vital pillars to produce reliable software with AI assistance.
-
•
Working hands-on with AI coding agents increased Christian’s empathy and understanding of engineers' daily challenges.
-
•
Modern UX and IA are indispensable in AI software development to mediate between human needs and machine capabilities.
-
•
Embedding ethical guardrails and values like kindness directly into AI system architecture can prevent harm and misuse.
-
•
Future AI solutions may favor smaller, domain-specific language models orchestrated via overarching frameworks rather than monolithic large models.
-
•
Despite the hype, AI-assisted development is still early-stage, requiring disciplined human oversight and patience for meaningful results.
Notable Quotes
"I thought I could skip the architecture step, but I ended up with spaghetti code that broke constantly."
"These bots will say yes to all your ideas, whether they're good or bad—that's the rocket to Mars anti-pattern."
"If I stop doing it, it stops, and I'm the human in the loop, or the monkey in the middle."
"I’ve created dedicated personas in the bots, like a chief of staff and lead developer, to keep roles clear."
"Verification first — always check existing docs and models before asking the bots to build anything new."
"Working with AI made me understand what engineers go through with setups and debugging."
"Vibe coding turns the conversation 'should designers code?' on its head — now designers can just talk to bots."
"All of us have at least some facility in adjacent disciplines now because of AI assistance."
"The bots can produce large amounts of code quickly, but many lines are test or documentation code, not production."
"Ethics needs to be baked into the architecture upfront, not tacked on later after you've built something powerful."
Or choose a question:
More Videos
"It’s not enough to build a repository and expect people to come; you need a distribution strategy to put research where users are."
Ben Davies Matt Duignan Andrew Michael Dr. Emily DiLeoExpert Panel: The Principles of Research Repository Design
March 11, 2022
"You aren’t your user, but we are users of this system, so we know what we need to make it better."
Russ UngerGetting Out from Under Everyone: How to Escape the Paralysis of Getting Started
June 8, 2016
"Our bet was that distributing ownership would create more advocates and free bandwidth for strategic work."
Elizabeth Sklar Jessica ShengCo-creating research enablement with your tech org: a case study
March 10, 2026
"I hope that today you are transformed."
Victor UdoewaTheme One Intro
March 27, 2023
"You want someone who writes with equal parts empathy and authority, not just pure authority."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
"Two researchers can’t come close to digging into the customer problems for 17 product teams."
Erin May Roberta Dombrowski Laura Oxenfeld Brooke HintonDistributed, Democratized, Decentralized: Finding a Research Model to Support Your Org
March 10, 2022
"Users creatively circumvent broken enterprise systems, which traditional metrics often miss."
Alexandra SchmidtEnterprise UX Playbook
December 1, 2022
"This was the first time the director saw the team doing something together."
Saara Kamppari-Miller"Prototype" vs "Prototype"--Breaking Down and Rebuilding Our Understanding of What We Do
October 24, 2019
"In a nuclear war, the only things that would survive on Earth would be cockroaches and these old SAP screens."
Sam YenDriving Organizational Change Through Design? Do more of this and less of that
June 9, 2017
