What are the key takeaways from this The Bike Shed episode?

Key insights include: **Walking Skeleton Approach:** Build end-to-end functionality first with hardcoded authentication and UI, connecting real backend services early. This validates core product value within weeks rather than spending initial sprints on solved problems like user login systems.; **Work Unit vs Worker Efficiency:** Tasks spend more time waiting in review, blocked, or deprioritized than in active development. Measuring task lifecycle reveals days of waiting even when developers feel productive working on lower-priority items while high-priority work sits idle.; **Right-to-Left Workflow:** Before picking up new tasks, ask what can be reviewed, tested, paired on, or shipped. This cultural shift prioritizes completing in-progress work over starting new tasks, reducing compound delays from multiple partially-completed items across team members.

What did Jared Turner discuss on The Bike Shed?

Jared Turner explains the "President's Doctor" concept: optimizing for work unit completion speed rather than worker utilization reduces project delays caused by tasks waiting in review, blocked states, and context switching between multiple priorities. Key topics include: **Walking Skeleton Approach:** Build end-to-end functionality first with hardcoded authentication and UI, connecting real backend services early. This validates core product value within weeks rather than spending initial sprints on solved problems like user login systems.; **Work Unit vs Worker Efficiency:** Tasks spend more time waiting in review, blocked, or deprioritized than in active development. Measuring task lifecycle reveals days of waiting even when developers feel productive working on lower-priority items while high-priority work sits idle..

How long is this episode of The Bike Shed?

This episode is 33 minutes long. SignalCast provides an AI-generated summary so you can get the key insights in about 3 minutes.

The Bike Shed

480: The President's Doctor with Jared Turner

October 28, 2025

33 min episode · 2 min read

Jared Turner

Episode

33 min

Read time

2 min

Topics

Productivity, Design & UX, Software Development

AI-Generated Summary

Published Dec 25, 2025

Key Takeaways

✓Walking Skeleton Approach: Build end-to-end functionality first with hardcoded authentication and UI, connecting real backend services early. This validates core product value within weeks rather than spending initial sprints on solved problems like user login systems.
✓Work Unit vs Worker Efficiency: Tasks spend more time waiting in review, blocked, or deprioritized than in active development. Measuring task lifecycle reveals days of waiting even when developers feel productive working on lower-priority items while high-priority work sits idle.
✓Right-to-Left Workflow: Before picking up new tasks, ask what can be reviewed, tested, paired on, or shipped. This cultural shift prioritizes completing in-progress work over starting new tasks, reducing compound delays from multiple partially-completed items across team members.
✓Rapid Unblocking Protocol: Blocked tasks accumulate days of delay through slow email chains and department handoffs. Implement self-sufficient workarounds, grant team members direct access to necessary tools, and escalate blockers immediately rather than applying labels and waiting for responses.

What It Covers

Jared Turner explains the "President's Doctor" concept: optimizing for work unit completion speed rather than worker utilization reduces project delays caused by tasks waiting in review, blocked states, and context switching between multiple priorities.

Key Questions Answered

•Walking Skeleton Approach: Build end-to-end functionality first with hardcoded authentication and UI, connecting real backend services early. This validates core product value within weeks rather than spending initial sprints on solved problems like user login systems.
•Work Unit vs Worker Efficiency: Tasks spend more time waiting in review, blocked, or deprioritized than in active development. Measuring task lifecycle reveals days of waiting even when developers feel productive working on lower-priority items while high-priority work sits idle.
•Right-to-Left Workflow: Before picking up new tasks, ask what can be reviewed, tested, paired on, or shipped. This cultural shift prioritizes completing in-progress work over starting new tasks, reducing compound delays from multiple partially-completed items across team members.
•Rapid Unblocking Protocol: Blocked tasks accumulate days of delay through slow email chains and department handoffs. Implement self-sufficient workarounds, grant team members direct access to necessary tools, and escalate blockers immediately rather than applying labels and waiting for responses.

Notable Moment

Turner reveals that two developers working on four tasks simultaneously creates a situation where zero features reach completion, despite both workers appearing productive. This pattern compounds across project timelines, turning reasonable delays into week-long stalls on priority work.

Know someone who'd find this useful?

Episode Transcript

Auto scaling is a simple concept. Automatically add resources when needed and automatically shut them down to avoid paying for excess capacity. How hard could that be? If you've set up auto scaling yourself, you know it's not that easy, especially using the native auto scalers on platforms like AWS and Heroku. That's why you need Judo Scale. Judo Scale is auto scaling as a service, and they make auto scaling simple and easy, as it should be. You can use Judo Scale on AWS, Heroku, Render, fly.io, and more. It's free for low traffic apps and unlimited plans start at $25 per month. Autoscale on easy mode at judoscale.com. Hello, and welcome to another episode of The Bike Shed, a weekly podcast from your friends at Thoughtbot about developing great software. I'm Aji Slater, and I'm joined today by Jared Turner. Hey, Aji. Thanks for having me. And together, we're here to share a bit of what we've learned along the way. So, Jared, what's new in your world? Well, I I started a new project recently. So I guess we can talk about that if you like. Oh, fun. Yeah. It is a, a crypto app of all things. Okay. So buying and selling cryptocurrencies. I guess the thing that's on my mind about it that I like is sort of how we've started the project. One thing I'm working with Rob, who's a development director in the fusion team, which is Europe, Middle East, and Africa, and, Sami is another developer on the team. One thing I think we've done really well is sort of cracked the core of what this what this thing is. So, like, we wanna buy crypto. That's that's the main thing, and that sounds obvious, I guess. But, like, we've mapped that out in a bit more specifics. And we've built, I guess, they call it like a walking skeleton. Okay. So it's a mobile app. You have something that works. You can press login. It doesn't log you in. It takes you to the dashboard. You can press trade. You can press a button, which is buy crypto, and it doesn't let you pick your cryptocurrency. It doesn't let you enter your amount. That's all hard coded. But what it does do, that button talks to the back end, and then the back end is now talking to the the third party that does the actual work. So we sort of very quickly scaffolded this so we can show the client, like, this is what it works, and this is actually doing the magic in the back end already even though it doesn't look pretty. And it's reflecting on some other projects I've started where we didn't get to that good start as quickly. I think it I really appreciate this approach of, like, how can we very, very quickly get something working and show it working? Like, the client can see this in the the test five version of the …

Get the full transcript (5,514 words) + summary by email — free

One-time email with the complete transcript and AI summary of this episode. No account needed.

One email, no spam. We’ll also show you what SignalCast does.

Browse all The Bike Shed transcripts →