User outcomes, workflow design, and biotech software - product engineering with Swizec Teller
Notas do episódio
Kent talks with Swizec Teller about product engineering for software that serves real businesses and non-developer users: how to learn a domain you did not grow up in, how to spot hidden friction by watching people work, and why the best product work focuses on outcomes, not engineering puzzles.
They talk through biotech, internal tooling, habits users build around buggy software, feature placement, success metrics, and how to widen the pit of success for people who are just trying to do their jobs.
- (00:00) - Intro
- (01:04) - Swizec's path from startups to biotech
- (02:18) - Learning a domain you didn't grow up in
- (05:14) - Widening the pit of success
- (09:46) - Introducing workflow changes without friction
- (12:11) - Feature flags and early feedback loops
- (16:11) - How to find real user needs
- (20:02) - What support tickets tell you about users
- (22:55) - Reading friction as a product signal
- (24:51) - Automation and what it changes for users
- (26:58) - Where to place new capabilities
- (29:26) - Breaking big ideas into shippable pieces
- (33:31) - Defining success before you ship
- (37:27) - Software is valuable for what users can now do
Swizec brings a perspective that broadens the season in a useful way. Instead of developer-facing tools, he has spent years building software that supports biotech, healthcare, and other real-world businesses where the user is trying to get work done, not admire your architecture. That makes the conversation very grounded in observation: shadowing experts, noticing workaround behavior, understanding existing habits, and putting new capabilities exactly where people already look.
The second half of the episode turns that into a practical product loop. Swizec and Kent talk about defining success before you ship, measuring whether a workflow actually improved, and balancing long-range vision with the adjacent possible of what today's technology can support. The result is a strong reminder that software is valuable because of the user's new "superpower," not because the implementation was clever.
Homework
- Spend one hour watching users use your software.
- If you do not have direct access to users, ask your manager or PM to connect you with someone internally, or watch a partner or friend try a real workflow while you take notes.
- Treat every workaround or confusing step you see as a potential product opportunity.
Resources
Guest: Swizec Teller
Host: Kent C. Dodds
Capítulos
Carregando capítulos…