Every platform team has the same graveyard: a portal full of outdated docs, dead links, and tutorials that were accurate at some point in 2022. Engineers stop trusting it. They Slack someone instead.
We blame the tooling. We blame the writers. We run doc sprints. Six months later, the graveyard grows.
The uncomfortable truth: the portal isn't broken. The approach is.
Platform teams think in systems, services, and SLOs, not about real developers who'll bail the moment your golden path costs more time than it saves.
This talk treats the portal as a symptom. The real problem is platform teams that ship infrastructure rather than build products. We'll get into what that shift looks like: talking to developers like a PM, building adoption metrics that matter, and writing roadmaps that stakeholders outside your team actually care about.
This isn't a talk about portals. It's about what happens when a team starts asking, "Would someone choose this?" instead of "Did we ship it?"