Part 5 of 5 ·
Shared AI assets fail without an adoption path
Why shared AI assets need an adoption path, and a practical lifecycle for turning libraries into reusable organizational capability.
Topic
Leading teams through hard technical change: splitting monoliths, merging teams, building shared systems, and now guiding engineers through AI transformation.
The interesting part of engineering leadership is rarely the technology. It’s the people and the change: how you split a twenty-year-old monolith without stalling delivery, how you merge frontend teams without breaking them, and how you build systems many teams can share.
These posts come from doing that work, including the newest version of it: helping engineers find their role as AI reshapes how software gets built.
Part 5 of 5 ·
Why shared AI assets need an adoption path, and a practical lifecycle for turning libraries into reusable organizational capability.
Part 4 of 5 ·
Executives can sponsor AI and employees can experiment, but team-level leaders decide whether AI becomes real operating practice.
Part 2 of 5 ·
When AI makes implementation cheaper, engineering leadership shifts from coordinating output to shaping judgment, quality, shared workflows, and team learning.
Part 3 of 3 ·
How we decomposed a decades-old monolithic application into focused services — without derailing ongoing project delivery.
Part 2 of 3 ·
When merging frontend teams, the hardest part isn't the tech stack — it's getting teams to actually want to make it work.
Part 1 of 3 ·
How we built a shared design system for all IONOS customer frontends — and what it took to make UX and engineering actually share ownership of it.