How GitHub’s developer experience team has evolved | Liz Saling (GitHub)

GitHub’s Developer Experience organization prioritizes internal engineering health by treating developer workflows as a product. To address reliability and efficiency, the company paused feature development for an entire quarter, using DORA metrics and internal surveys to identify critical friction points like fragmented documentation and slow CI build times. This initiative led to the implementation of a decoupled merge queue and a centralized source of truth for engineering information. To prevent backsliding, the organization maintains a rigorous monthly review process, ensuring clear service ownership and continuous feedback loops. By fostering "manufactured serendipity" through remote-first communication tools and maintaining a tight partnership between product and engineering, GitHub ensures that developer satisfaction remains a core business driver, ultimately enabling more effective software delivery for both internal teams and external customers.