From Hostile to Rewired: How Descript CEO Drives AI Adoption | Laura Burkhauser, CEO of Descript
Descript CEO Laura Burkhauser shares how she maps her team’s AI readiness, why “two X productivity” is the wrong pitch for AI, and a two-by-two framework that might be the best AI adoption tool.
Before Laura Burkhauser was the Descript CEO, she was a customer first. She loved the product so much that she knocked on founder Andrew Mason’s door and asked to work on it with him.
Before Descript, Laura built her product career at Le Tote and Rent the Runway, a path that taught her that “what got you here genuinely won’t get you there,” especially when you’re suddenly the most senior product person in the room with no one left to learn from.
In this episode, we talk about:
Why fast-moving careers can leave you stranded at the director level — and what to do about it
The four-stage framework Laura uses to assess how every person on her team feels about AI (from “hostile” to “rewired)
Why automating a broken system just gives you broken results faster
And a two-by-two for AI adoption that starts with the most human questions first: What do you hate doing? And what do you want to do more of?
1. What got you here won’t get you there (05:49)
Out of business school, Laura joined Le Tote, a startup she was already a customer of. She excelled almost immediately both as a product manager and a people manager.
Then came Rent the Runway and the director title. She was good. But being a product director is a fundamentally different job than being a great PM — and she had no one around her to show her what that looked like.
“There was no one to kind of tell me, ‘This is what a product director does. This is how you think about resource allocation. This is how you think about influencing the business strategy. This is how you start thinking about working on the business and not just working in the business.’”
She was the most senior product person at the company, and there were no peers, no models of excellence nearby, and no map for her to learn from.
The lesson she learned: when you’re the most senior person in the org chart, your growth has to come from outside the org chart.
2. The four-stage tech acceptance framework (21:39)
Most conversations about AI adoption treat it as binary: people either get it or they don’t.
The framework Laura applies at Descript tracks four distinct stages:
Hostile — “I don’t want to use this. I think it’s bad.”
Skeptical — “I’ll try it, but I think it’s going to suck. Last time I tried, it did.”
Converted — “I believe. I know it works. I remember to use it sometimes, and I’ve got a couple of systems down.”
Rewired — You think AI-first. When a new problem lands on your desk, your first instinct is to ask how AI can help you.
When Laura and her team ran their company-wide AI hackathon last year, the goal wasn’t to move everyone from “zero” to “rewired” overnight. It was to honestly assess where people were and design the right intervention for each stage.
Product takeaway: Before you design an AI adoption program, map your team against these four stages. “Hostile” people need a different intervention than “converted” people. A one-size mandates help no one.
3. “Struggle with your art, not with your tools” (15:31)
Descript has been an AI-native product since before “AI-native” was a buzzword. The original concept — to be able to edit video like you edit a document — made LLMs a natural fit the moment they arrived. When you’re editing the text, you’re editing the video.
But when the team built Underlord, their AI editing companion, they grounded it in a belief Laura says has “aged like wine”:
“The purpose of AI should be to take the struggle out of the tools that you use — and not out of you thinking about what you wanna say. Thinking about what your vision is finding your voice.”
She adds:
“AI is definitionally a derivative technology. It works by taking a statistical average of what is most likely to happen next. Without a lot of input from you — without a vision, without a director who matters — you’re gonna get derivative content.”
Product takeaway: If you’re building with AI, be specific about which part of the struggle you’re trying to remove. Removing tool friction for your users should be your goal. Removing the creative struggle removes the whole point.
4. The durability problem: What happens when your AI processes aren’t operational? (26:31)
There’s a pattern Laura has watched play out across companies: someone becomes a beacon for AI. They figure out how to use the tool(s) brilliantly and become 5x, 10x more productive. Leaders notice. And then nobody can quite figure out how to transfer what that person did.
“If that person left, none of that is durable. None of that endures.”
Laura draws a sharp contrast with how human-built systems tend to work. Bring in a great head of product, they set up product review, design review, meaningful human processes. Even if they go on leave for five months, the systems outlast their absence.
But the way most companies are building AI right now?
“If the employee who created the AI system were to leave, the AI system just leaves with them. It’s gone. Because it’s their own personal setup.”
Product takeaway: AI adoption isn’t just a people change — it’s a systems architecture problem. Build for durability from the start. If your AI capability could disappear when one employee leaves, you don’t have an AI capability. You have an AI dependency.
5. The two-by-two that actually gets people on board (29:22)
When Laura ran her product team’s AI offsite, she didn’t start with tools or capabilities or a productivity pitch. She started with the most human question she could think of:
What do you hate doing?
Specifically: looking back at the last four weeks of work, what sucked? What do you wish you could do less of? And — crucially — what do you wish you could do more of?
That’s the first axis of the two-by-two: stuff you love doing vs. stuff you hate doing.
The second axis: is AI actually good at this yet?
Because here’s the problem with pitching AI adoption as “two X productivity” to your ICs: it sounds like twice the work.
Product takeaway: The missing ingredient in most AI rollouts is the dream. Before you talk about tools, get your team to separate what they hate doing from what they love doing. Then let that map guide where AI fits — and how you talk about it.
Chapters
00:00 Intro
02:23 Laura's career journey: From fashion startups to finding her path to product
05:49 The "what got you here won't get you there" moment
08:26 Finding peers and mentors when you're the most senior person in the room
15:31 "Struggle with your art, not with your tools" — Descript's AI philosophy
21:39 The tech acceptance framework: From hostile to rewired
26:30 Pitfalls of AI adoption: Cost, durability, and automating broken systems
29:22 The two-by-two framework for getting your team AI-pilled32:24 Conclusion
Links
What does LogRocket do?
LogRocket’s Galileo AI watches user sessions for you and surfaces the technical and usability issues holding back your web and mobile apps. Understand where your users are struggling by trying it for free at LogRocket.com.