From Fear to Function: Rethinking Engineering Processes | Stytch’s Julianna Lamb
Nov 26, 2024
auto_awesome
Julianna Lamb, Co-founder and CTO of Stytch, dives into the often-dreaded topic of engineering processes. She argues that the right processes can actually accelerate team efficiency and empowerment. Julianna discusses finding the perfect balance between structure and flexibility, enhancing communication between engineering and product teams, and the importance of clear documentation. She shares innovative strategies for implementing effective process changes that foster collaboration without overwhelming teams, transforming fear into functional workflows.
Implementing the right amount of engineering process can significantly enhance team velocity and empower developers to take ownership of their tasks.
Engaging team members in the development of new processes fosters collaboration and reduces resistance, improving overall productivity and workflow efficiency.
Deep dives
The Value of Engineering Processes
Process can carry negative connotations in engineering teams, leading to resistance among developers. When implemented poorly, processes can hinder productivity and slow down project velocity, making it essential to evaluate their effectiveness regularly. Teams often face the issue of too many processes that become burdensome rather than helpful, focusing more on adherence than on delivering value and impact. On the contrary, a lack of sufficient process may leave teams struggling with coordination and dependency management, which can lead to frustrations and inefficiencies during project execution.
Right-sizing Processes for Teams
Determining the right amount of process is crucial for optimizing team performance, and this often involves ongoing evaluation and adjustment. Teams with too much process may experience delays due to excessive approvals and metrics tracking, while teams lacking sufficient process may find themselves unaligned with cross-team dependencies. Implementing a quarterly planning framework enables teams to balance the need for coordination without overburdening them with excessive planning. Striking this balance ensures that engineers can focus on core tasks such as coding and designing solutions rather than getting bogged down in administrative processes.
Feedback and Collaboration in Process Changes
Engaging team members in the development and implementation of new processes enhances buy-in and mitigates resistance to change. It is essential to communicate the purpose and benefits of the process changes clearly, allowing for feedback during and after the rollout phase. Regular check-ins help to assess the value of the processes and allow for necessary adjustments based on team experiences and insights. By promoting a culture of collaboration around process refinement, teams can create systems that genuinely support their work and improve overall productivity.
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 take our word for it. This week’s guest made a believer out of us and we’re willing to bet she’ll make a believer out of 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.