Who has not seen a team constantly fixing bugs but still facing more bugs? A team that struggles to release new features quickly, that doesn't have time to maintain its stack or codebases, and even less time to experiment with new technologies? Maybe this is your current situation?

We often talk about "technical debt" as if it were inevitable. "It's old code. Every change is time consuming, and it breaks with every release." Meanwhile, we see startups releasing features every week: "It's easy for them; they don't have any legacy."

Is it really inevitable? I like to believe it's not. I joined WP Media in 2023, at a time when the release pace was slowing down, each version was causing fear among the Product and QA teams, and developers were spending more time investigating bugs and finding the right approach rather than adding value to our products. Far from having solved all the problems, the teams have significantly reversed the trend thanks to a few principles and ideas that can be applied (almost) anywhere:
- optimized feedback loops in Tech team workflows,
- tactics to foster ownership and teamwork,
- the role of experts in teams,
- the self-service approach,
- the "diamond team" approach.

Come and discover this feedback and some proposals that might (or might not) help to unlock your team!

Target audience:
This talk is mostly designed for developers, product owners, scrum masters, team leads and engineering managers. More senior tech profiles can also benefit from the feedbacks shared in this talk.

More information:
https://mathieulamiot.com/empowering-teams-navigating-complexity-for-engineering-leaders/