From Fear to Function: Rethinking Engineering Processes | Stytch’s Julianna Lamb
Why your team’s biggest bottleneck might be your fear of process - and how to fix it.
Most developers (ourselves included) want to run for the hills when they hear the words “engineering process.” But it turns out, the biggest danger to your team may not be having enough process.
You don’t have to just take our word for it. This week’s guest drew from her experience to show us what’s possible, and we’re confident her insights will resonate with you too.
Julianna Lamb, co-founder and CTO of Stytch, understands that engineering processes can be a sensitive subject for developers. But she argues that the right amount of process can actually boost your team's velocity and empower them to take ownership. Julianna shares insights on how to right-size processes for teams, implement effective project life cycles, and address friction points to ensure smooth workflows.
Process is often a bad word in engineering teams and carries a lot of negative connotations… but I also think sometimes people are suffering from not enough process and it can be good and really comes down to finding what works for you.
The Download
Just like your Thanksgiving leftovers, The Download is packed with all the best bites. 🦃
1. Does GitHub Copilot actually make your code better? 🤔
GitHub’s latest research suggests Copilot can help developers produce code faster and with fewer bugs, but is it always helpful? With the rise of bot-generated pull requests now accounting for 13.3% of all PRs how can engineering teams effectively manage this influx to reduce workload and improve developer experience in 2025? Tools like Copilot are undoubtedly powerful, and leveraging their full potential requires the right mindset and processes to integrate them seamlessly into team workflows.
Read: Does GitHub Copilot improve code quality? Here’s what the data says
2. How Okta links software quality to business success 🔗
Okta’s Quality Maturity Model (QMM) outlines 14 actionable strategies to bridge the gap between quality and productivity. This framework for cross-functional teams ties code quality improvements directly to business outcomes, giving your team a blueprint for success. Check out the summary from LinearB.
Read: 14 Insights Into What Drives Software Quality at Okta
3. How European startups are embracing AI tools to do the boring work so their devs can focus ⛵️
A recent study by Index Ventures found that European startups using AI tools saw higher productivity without cutting jobs. Instead, companies are hiring more engineers to tackle complex projects while AI handles repetitive tasks: a clear sign that AI is helping (not replacing) developers.
Read: AI tools do not cost jobs – they boost productivity, say start-ups
2025 Engineering Benchmarks Insights 📊 (sponsored)
Level up your engineering team’s performance in 2025.
LinearB’s latest Engineering Benchmarks Report, analyzing over 6 million pull requests from 3,000 organizations worldwide, reveals the ins and outs of the software industry’s most successful teams.
Missed the webinar on last week? No problem! You can still grab the recording and learn how to improve your team’s DORA metrics, pull request workflows, and predictability.
Watch: On-demand recording of November 20th webinar
4. How better processes can make your code more human 👥
Reflecting on your approach to engineering processes? In this related video, GitHub’s Director of Engineering, Christina Entcheva, shares how effective workflows can break down silos, foster collaboration, and bring a human touch to your codebase. If you’re looking to make your team more effective and connected, this one’s worth a watch.
"fear to function" is a good band name idea.