Platforms before portals, build the roads before you buy the GPS

Platform engineering teams often rush to build or buy a developer portal before their underlying platform is ready to support one. Using a GPS-and-roads analogy, the argument is that a portal only amplifies what already exists — if the foundations are inconsistent or fragile, the portal makes those problems more visible, not less. Solid platform foundations (standardization, governance, self-service workflows, reliable pipelines) must come first. Portals do have genuine value, particularly for service discoverability at scale, but most teams aren't ready for them yet. A practical self-check: if you built a portal today and couldn't fill it with working, valuable capabilities, there's more platform work to do first.