Étiquette : CTO
-
48 days without an incident.
2 years ago, that would have been unthinkable. Customers impacted before our monitoring even fired an alert. Teams constantly interrupted. Firefighting. What changed? No massive hiring, nor technical overhaul nor new AI silver bullet. A rigorous approach, clear standards, and a lot of stubbornness. Looking back on 2 years of work.
-
Bugs aren’t inevitable — as long as you really care about them.
What if bugs weren’t inevitable? Often, every issue is handled as a quick fix — and when there are too many, the usual conclusion is: “We need to grow the team!” Really? By applying a genuine problem-solving approach, one of my teams went from 27 bugs to… zero in the very next sprint. That’s what…
-
The CTO’s gemba: lessons learned in the field (2/2)
Like any manager, I thought I knew my teams: their priorities and their difficulties. Until the day I spent a morning with them, without slides or an agenda… just observing and listening. 👀 And that’s when I realised how much I was missing the point. Obstacles I never imagined. Brilliant ideas that were never shared.…
-
The first practice of the CTO: going to the gemba ! (1/2)
How can we stay connected to operations and make informed decisions? How can we ensure that employees can learn and improve their practices from competent leaders? There is a valuable practice that comes to us from Lean: gemba. This Japanese wordmeans “The workplace, where value is created”.