The Standardization Struggle
Imagine a city where every contractor builds roads using whatever material they personally prefer — asphalt, cobblestone, gravel, or poured concrete. The roads might all technically work, but maintenance becomes a nightmare. Every repair crew needs different tools, different expertise, and different supply chains. This is exactly what happens to software organizations without technology governance.
In a company with 500 developers, if you don't provide guidance, you will end up with 15 different programming languages and 8 different database types. Why? Because developers love learning new things. They often pick a technology because it looks good on their resume — a pattern called Resume-Driven Development (RDD) — not because it's the right tool for the business problem at hand.
The hidden cost of RDD is enormous. Every new technology added to the fleet requires new hiring pipelines, new CI/CD tooling, new security scanning rules, new on-call runbooks, and new institutional knowledge. A team that adopts a niche framework because it's exciting in 2024 may leave the company in 2026, leaving behind a service that nobody else can maintain.
The Tech Radar
The Tech Radar is a governance tool — pioneered by Thoughtworks and now widely adopted across the industry — that visualizes your organization's technology portfolio. It answers the question: "What technologies are we betting on, and what should we avoid?"
It is not a static list of "Allowed" vs. "Banned." It is a living map that acknowledges technology evolves. What is "Adopt" today might be "Hold" tomorrow. The radar gives every developer in the organization a shared vocabulary for discussing technology choices, and it gives leadership a mechanism to steer the portfolio without micromanaging individual teams.
The radar is typically divided into four quadrants (Languages & Frameworks, Platforms, Tools, Techniques) and four rings (Adopt, Trial, Assess, Hold). Each technology appears as a dot placed in the appropriate quadrant and ring. When the organization's view of a technology changes, the dot moves.
Interviewers at platform-engineering-focused companies often ask: "How do you prevent teams from adopting whatever technology they want?" A weak answer is "we have a policy." A strong answer describes a Tech Radar with a guild-driven governance process, explains the four rings and what each means operationally, and connects the radar to Golden Paths — making the "Adopt" ring the path of least resistance by providing first-class tooling support for it.