Leading a digital transformation without smothering the engineering team
Across Société Générale CIB, GRTgaz, the French Ministry of Justice and Groupe Casino, I've seen the same pattern repeat under different labels: a digital transformation decided in a steering committee collides with an engineering team's real capacity when nobody connects the two. That connection is the subject of my MBA thesis at École Polytechnique. Here are the three principles that keep showing up, regardless of the industry.
Sequence it, don't transform everything at once#
A transformation plan that attacks architecture, process, and tooling all at once leaves no delivery capacity during the transition, which erodes the rest of the company's trust before any result shows up. Sequencing means choosing an order where each step funds the next, keeping visible delivery capacity on the existing scope while the transformation advances on another front.
Translate transformation metrics into shippable increments#
A steering committee objective ("cut deployment lead time by 40%") isn't actionable as stated for an engineering team. Translating it into concrete increments, a pipeline to automate, a dependency to decouple, a test to write before touching a fragile module, is the work most often missing between strategy and execution. Without that translation, the team receives a goal it doesn't know how to reach, and leadership receives a status update it doesn't know how to interpret.
Use a real technical win as proof, not as a footnote#
The first flow successfully migrated, the first incident avoided thanks to a test that didn't exist before, isn't just a line in a progress report: it's the argument that unlocks trust and budget for what comes next. A transformation that doesn't capitalize on its early concrete technical wins stays a promise on a slide, until someone starts doubting it's achievable.
What this changes in practice#
A transformation strategy that ignores the real capacity of the team that has to execute it isn't a strategy, it's an intention. The role most often missing from these engagements is neither purely technical nor purely strategic: it's the one that translates in both directions, and stays on the ground long enough to check that the translation holds against the reality of execution.
