> Markdown version of [/videos/1461-building-developer-experience-brick-by-brick?t=0](https://www.wearedevelopers.com/videos/1461-building-developer-experience-brick-by-brick?t=0). Every page supports `.md` or `Accept: text/markdown`. Links point to the HTML versions so they work for humans too. Agent guide: [/agents.md](https://www.wearedevelopers.com/agents.md).

---

# Building Developer Experience - Brick by Brick

Scaling to 1,200 engineers left Lego's developers drowning in severe cognitive overload. Discover how they eliminated fragmented toolchains by building a unified internal developer portal.

- **Speakers:** [Rasmus Hald](https://www.wearedevelopers.com/@rasmus-hald)
- **Event:** World Congress 2025
- **Published:** August 20, 2025
- **Duration:** 28:07
- **URL:** https://www.wearedevelopers.com/videos/1461-building-developer-experience-brick-by-brick

## Summary

The Lego Group has evolved into a massive digital organization, scaling up to 1,200 engineers across more than 200 highly autonomous DevOps product teams. While these developers initially appreciated their technical flexibility, internal surveys like the "Voice of the Developer" revealed a significant growing pain: severe cognitive overload. Engineers struggled with fragmented toolchains, duplicative efforts, and hidden or outdated documentation. Furthermore, relying on an informal "old boys network" to find domain experts simply failed to scale in a rapidly expanding engineering culture.

To combat these inefficiencies, Lego centered its developer experience (DevEx) strategy around three pillars: discoverability, documentation, and communication. The cornerstone of this effort is "Baseplate," a highly customized internal developer portal built on Spotify's Backstage. Baseplate unified the developer ecosystem by natively linking APIs, approved tooling, architectural documentation, and the responsible personnel into a single interface. Recognizing that an API-first architecture is useless if internal teams cannot find the APIs, Lego heavily prioritized API discoverability. The portal also embeds continuous observability data, surfacing product health and SLO metrics to enforce baseline engineering hygiene.

Complementing the portal, Lego invested heavily in organic communication efforts to cultivate a thriving engineering community. Initiatives ranged from volunteer-curated technical newsletters to a large-scale internal developer conference that generated over 7,500 learning hours. Looking forward, the DevEx team intends to approach AI-augmented software development with deliberate caution, implementing specific developer metrics to ensure these new tools continuously reduce—rather than inadvertently increase—engineers' workloads. As part of its future maturity, the organization is also pushing to normalize inner-sourcing while expanding its open-source footprint through partnerships with the CNCF.

**Keywords:** developer experience strategy, spotify backstage implementation, cognitive overload management, internal developer portal, internal developer conference, technical documentation visibility, API discoverability, autonomous product teams, engineering culture scaling, inner sourcing practices, voice of the developer survey, CNCF open source, AI augmented development, product health observability, toolchain standardization

## Chapters

1. **Evolving from legacy manufacturing to digital product organization** (00:00) — The organization navigated digital transformation by scaling autonomous DevOps product teams within a legacy framework.
1. **Measuring developer satisfaction and identifying cognitive pain points** (04:30) — Annual surveys revealed that while software engineers enjoy high autonomy, they suffer from cognitive overload and poor information discoverability.
1. **Centralizing API and product discoverability using Spotify Backstage** (09:48) — Creating a centralized developer portal unified fragmented data sources and simplified the navigation of internal APIs and cross-functional teams.
1. **Tracking technical documentation and defining paved tooling paths** (17:26) — Engineering leadership tracks documentation telemetry to acknowledge contributors and establishes supported paved paths to limit tool fragmentation.
1. **Fostering engineering culture through internal events and communications** (20:18) — The organization cultivates a cohesive developer community by leveraging internal tech conferences, cross-location meetups, and curated newsletters.
1. **Shaping future work with AI augmentation and inner sourcing** (23:41) — Future experience initiatives balance generative coding tools against data-driven metrics while expanding internal and open source contribution models.

## Related Moments

- [Summarizing the organizational benefits of platform engineering](https://www.wearedevelopers.com/videos/885-platform-engineering-vs-devops-why-not-both) (from "Platform Engineering vs. DevOps Why not both?")
- [Addressing developer productivity challenges with internal tooling](https://www.wearedevelopers.com/videos/1118-developer-experience-in-the-age-of-ai) (from "Developer Experience in the Age of AI")
- [Designing internal developer platforms and product team responsibilities](https://www.wearedevelopers.com/videos/1614-ai-augmented-devops-with-platform-engineering) (from "AI-Augmented DevOps with Platform Engineering")
- [Building authentic developer community touchpoints](https://www.wearedevelopers.com/videos/1748-emergency-discussion-can-t-hire-the-right-developers-here-s-what-everyone-else-misses) (from "Emergency Discussion: Can’t Hire the Right Developers? Here’s What Everyone Else Misses")
- [Identifying the four core pillars of developer experience](https://www.wearedevelopers.com/videos/727-the-abc-of-dx) (from "The ABC of DX")
- [Measuring developer experience to drive team productivity](https://www.wearedevelopers.com/videos/1121-forget-developer-platforms-think-developer-productivity) (from "Forget Developer Platforms, Think Developer Productivity!")

## Related Articles

- [Why developer experience matters](https://www.wearedevelopers.com/magazine/514-why-developer-experience-matters)
- [How Engineering Hubs Build Visibility at Developer Conferences like WeAreDevelopers World Congress](https://www.wearedevelopers.com/magazine/720-how-engineering-hubs-build-visibility-at-developer-conferences-like-wearedevelopers-world-congress)
- [Exploring AI: Opportunities and Risks for Developers](https://www.wearedevelopers.com/magazine/522-exploring-ai-opportunities-and-risks-for-developers)
- [Dev Digest 121 - AI goes offline](https://www.wearedevelopers.com/magazine/456-dev-digest-121-ai-goes-offline)

## Related Jobs

- [Tribe Lead - ( Software) Engineering Centre of Excllence](https://www.wearedevelopers.com/jobs/ext/1475530-tribe-lead-software-engineering-centre-of-excllence) at **SD Worx**
- [Principal Software Engineer, Enterprise AI Platform](https://www.wearedevelopers.com/jobs/ext/1467292-principal-software-engineer-enterprise-ai-platform) at **GitHub**
- [Principal Product Manager, Agent Platform](https://www.wearedevelopers.com/jobs/ext/277541-principal-product-manager-agent-platform) at **GitHub**
- [Staff Software Engineer, Copilot Experiences](https://www.wearedevelopers.com/jobs/ext/164361-staff-software-engineer-copilot-experiences) at **GitHub**
- [Senior Software Engineer, Enterprise Products](https://www.wearedevelopers.com/jobs/ext/1841248-senior-software-engineer-enterprise-products) at **GitHub**
- [Staff Developer Advocate, GitHub Security Lab](https://www.wearedevelopers.com/jobs/ext/1921051-staff-developer-advocate-github-security-lab) at **GitHub**