Developer Experience as a Strategic Advantage
Onboarding went from 30 days to 30 minutes. Innersource became the default. DevEx is not a perk — it is the compound interest of an engineering organisation.
There is a metric I care about more than velocity charts: how long does it take a brand-new engineer to get credentials, write code, and push something to a sandbox? We call it ideation-to-productivity. When we first measured it honestly, the answer was thirty days — a month of a motivated person’s enthusiasm spent on access requests and tribal knowledge. Today it is thirty minutes. That change was not one project; it was a decision to treat developer experience as infrastructure.
One platform, zero ceremony
We consolidated a fragmented landscape of code hosts onto GitHub Enterprise Cloud, with onboarding automated end to end from Active Directory — SSO in, team memberships mapped, first repository reachable before the welcome meeting ends. CI/CD standardised on GitHub Actions with reusable pipeline templates, and security stopped being a gate at the end: GitHub Advanced Security and SonarQube scan every push, so the finding arrives while the code is still warm in the developer’s head.
Innersource by default
The most contested decision was also the most valuable: repositories are open across departments by default. R&D can read manufacturing’s code; IT can send a pull request to a data science repo. The objections were predictable — and the outcome was the opposite of the fear. Duplication fell because teams could find prior art. Quality rose because code written in the open is written differently. And a manufacturing engineer’s fix to a shared library stopped requiring a steering committee.
Siloed code is deferred rework. Innersource is just admitting the company is one team with one codebase.
AI pair programming, early and measured
We were an early enterprise adopter of GitHub Copilot, and we instrumented it rather than evangelised it: routine syntax and boilerplate time down more than 45%, developer satisfaction at 85%. The satisfaction number is the strategic one. In a market where every company is competing for the same engineers, the day-to-day feel of shipping code here is a recruiting asset with a measurable retention yield. GitHub later featured our transformation as a global customer case study — but the case study I quote internally is simpler: new engineers now commit on day one, and they remember it.