Engineering Health and Productivity
Maintain high shipping velocity by balancing technical excellence with strategic developer investments.
Help the user with engineering health and productivity using insights from 18 guests and posts across Lenny's Podcast and Newsletter.
How to Help
- Baseline health - Use the Core 4 or DORA frameworks to establish a quantitative and qualitative starting point for team performance.
- Optimize workflows - Identify bottlenecks in the path from code completion to production deployment to unlock hidden velocity.
- Manage technical debt - Frame technical investments as business ROI to secure buy-in for non-feature work.
- Leverage AI tools - Integrate AI into the development lifecycle to shift engineer focus from syntax to architecture.
Core Principles
Evaluate AI by Value over Volume
Chip Huyen: "It's really hard to measure productivity. So, I do ask people to ask their managers, "Would you rather give everyone on the team very expensive coding agent subscriptions or you get an extra head count?" Almost every one, the managers will say head count."
Compare the cost and output of AI tools against the value of additional headcount rather than just looking at raw productivity gains.
Shift Focus to Architecture
Inbal S: "The user of the AI tools to develop software needs to form a different thinking. You need to start figuring out how are you using these AI tools to help you be successful. And it's no longer just the actual code writing, it's really evolving your thinking to the big picture, to the connected experience, to connected systems."
Use AI to handle manual syntax so engineers can spend more time on high level system design and product understanding.
Modernize Internal Tooling for AI
Mike Krieger: "We really rapidly became bottlenecked on other things like our merge queue. We had to completely re-architect it because so much more code was being written and so many more pull requests were being submitted. Over half of our pull requests are Claude Code generated."
Internal tools like merge queues must be re-architected to handle the massive increase in pull request volume generated by AI coding.
Measure Multi-Dimensional Productivity
Nicole Forsgren: "So productivity, I think, is basically how much we can get done and how much we can do over time. And I think that's why it's so important to have this holistic measure because we can't just brute force it, right. And so that's why when my team and a bunch of my peers study productivity, we include this community effect because software is a team sport."
Avoid raw output metrics: instead, use a balanced view that includes team dynamics, sustainability, and workflow friction.
Automate the Quality Gate
Sherwin Wu V2: "100% of our PRs are reviewed by Codex daily as well. So basically any code that goes into production that's merged in, Codex kind of has its eyes on and suggests improvements, suggests changes in the PRs."
As code volume increases, implement AI powered automated reviews to maintain quality without creating a manual bottleneck.
Benchmark AI Progress
Dhanji R. Prasanna: "We find engineering teams that are very, very AI forward are reporting about eight to 10 hours save per week. Whenever I hear a stat like this, I think an important element is this is the worst it will ever be. This is now the baseline."
Track weekly hours saved by AI forward teams to establish a performance baseline that will evolve as the technology matures.
Incentivize Code Deletion
Farhan Thawar: "We have a Delete Code Club. We can always almost find a million-plus lines of code to delete, which is insane."
Aggressively remove obsolete code to prevent system complexity from slowing down development velocity.
Treat Tech Debt as Leverage
Gaurav Misra: "I actually think as a startup your job is to take on technical debt because that is how you operate faster than a bigger company. Bigger companies don't take contact technical debt, they pay it usually right away, or they're paying back technical debt from the days when they were a startup."
Deliberately choose to incur technical debt when it provides a significant advantage in shipping speed for new marketable value.
Optimize the Final Mile
From "Increasing team velocity": "Talk to your engineers about opportunities to speed up their review, approval, and deployment process."
Focus on the technical workflow between code complete and deployed to unlock the most significant gains in shipping speed.
Templates & Frameworks
- Core 4 Framework (Introducing Core 4: The best way to measure and improve your product velocity) - A unified developer productivity framework with four dimensions designed to hold each other in tension, providing a balanced view of team performance. Co-author
- DORA Metrics (The Four Keys) (Nicole Forsgren) - Four metrics to measure software delivery performance, split into speed and stability.
- ROI Framing for Engineering Efficiency Investments (Introducing Core 4: The best way to measure and improve your product velocity) - Two complementary frames for presenting the business case for developer experience improvements to leadership.
- Core 4 Baseline Survey Template (Introducing Core 4: The best way to measure and improve your product velocity) - A plug-and-play survey template to send to engineering teams to collect baseline measurements across all four Core 4 dimensions. Responses must be anonymous.
- Unsexy Investment Justification Playbook (Casey Winters) - Tactics to get buy-in for tech debt, performance, and UX improvements.
- Polishing Season (Annual Quality Ritual) (How Linear builds product) - An annual end-of-year ritual where Linear dedicates concentrated time to fixing bugs, paper cuts, and quality issues submitted by users.
- SPACE Framework (Nicole Forsgren) - A framework for measuring complex creative work across five dimensions to ensure balanced metrics.
- Crying Octopus Button (Paper Cuts) (David Singleton) - An internal tool embedded in developer environments to instantly report friction.
- Quarterly Grease Week (How Duolingo builds product) - A dedicated quarterly week where a product team exclusively works on clearing bugs and technical debt
- Technical Debt Runway (Gaurav Misra) - A mental model that treats technical debt like financial leverage, using an 'interest rate' to determine when debt becomes fatal to a startup.
See references/artifacts.md for the full list with details.
Questions to Help Users
- "What percentage of your engineering capacity is currently spent on maintenance versus new features?"
- "How long does it typically take for a piece of code to go from completed to deployed in production?"
- "Have you surveyed your developers to identify the biggest friction points in their daily workflow?"
- "Do you have a clear framework for how you decide to pay down technical debt versus building new features?"
- "How are you currently measuring the impact and adoption of AI tools within your engineering organization?"
- "What are the three biggest paper cuts or UX annoyances currently slowing down your product quality?"
Common Mistakes to Flag
- Measuring raw output over impact - Focusing on lines of code or number of PRs ignores code quality and can lead to burnout and system fragility.
- Treating all debt as a negative - Avoiding all technical debt can prevent a startup from moving fast enough to find product market fit.
- Relying solely on automated metrics - Quantitative data identifies a problem exists but qualitative developer feedback is needed to diagnose specific friction points.
- Under investing in testing as a safety net - Without robust unit testing, engineers lose the confidence to refactor code or move quickly without breaking things.
Deep Dive
For all 21 sourced insights from 18 guests, see references/guest-insights.md
Related Skills
- Writing Prds
- Shipping Velocity
- Ai Assisted Prototyping
- Building With Ai Agents
