A technology stack that grows from individual team enthusiasm accumulates heterogeneity without proportional gain. Every technology adopted by one team creates training, maintenance and integration cost that the next team did not factor in. In three years, the portfolio has fifteen languages, twenty frameworks and thirty managed services nobody has fully mapped. Heterogeneity compounds maintenance cost and reduces the ability to move engineers across teams.
Subcapability 04 of 05 · Enterprise Architecture
Technology Radar
Technology Radar four-ring model adapted to organizational context that distinguishes Adopt from Hold with evidence, managing obsolescence risk and controlling stack complexity by intention.
What is at stake
The technology portfolio grew by each team's decision. Today there are languages, frameworks and tools that nobody chose deliberately for the organization. Each additional technology has a training, maintenance and integration cost that does not appear in any budget line. It appears as complexity that increases the cost of every new initiative.
What it is, in practice
How we work
Inventory of the current technology portfolio
We map all technologies in use across the organization, including those informally adopted by individual teams, to have complete visibility of what exists before defining what should exist.
Classification in four rings
We evaluate each technology against Adopt, Trial, Assess and Hold criteria based on evidence of real use in organizational context, not market benchmarks, ensuring the classification reflects what works here.
Explicit criteria for moving between rings
We define what is needed to move a technology from Assess to Trial, from Trial to Adopt and from Adopt to Hold, making the portfolio evolution process predictable and evidence-based.
Publication and communication with teams
We make the radar accessible to all engineering teams, so that classifications guide local decisions without requiring architect consultation for every new technology choice.
Quarterly review cycle
We keep the radar current with quarterly cadence, incorporating evidence of real use, ecosystem changes and new technologies under evaluation, so that the document reflects the current state of the organization and the market.
Measurable gains
What changes in the result when this subcapability matures.
Decision time for adopting a new technology
With explicit criteria and an accessible radar, the decision to adopt a new technology takes days, not months of internal debate. The evaluation process follows documented criteria and produces a decision with traceability.
Training investment concentrated on technologies that will remain in the portfolio
A radar that distinguishes what is in Adopt from what is in Hold directs training investment to technologies with a future in the portfolio, eliminating training on technologies that will be replaced.
Portfolio heterogeneity over time
A deliberate adoption process with explicit criteria reduces the rate of new technology entry without organizational justification, controlling complexity that today grows by inertia.
Obsolescence risk in critical systems
Technologies in Hold identified in the radar with critical system dependencies receive a modernization plan before reaching the point where specialists become scarce and maintenance costs spike.
Frequently asked questions
Does Technology Radar work for smaller companies, not just large consultancies?
The four-ring, four-quadrant format is scalable. An organization with ten engineers needs the same explicit adoption criteria as one with a thousand. The smaller radar has fewer technologies, a simpler review process and a less formal structure, but the benefit of having documented criteria is the same: technology decisions stop depending on who is in the room.
Who should participate in the Technology Radar review?
Technical representatives from each domain or team with real usage evidence of the technologies being evaluated, plus the architect or tech lead responsible for portfolio coherence. The review needs people with practical experience, not the highest hierarchy. Decision by expertise, not by position.
What to do when half the team wants a technology in Adopt and the other half wants it in Hold?
The divergence is evidence that usage context matters. The same technology can be Adopt for one domain and Hold for another. The radar can have context-specific classifications when the usage difference justifies it. What does not resolve the issue is leaving the classification open because the team did not reach consensus.
How to handle vendors pushing for adoption of specific technologies?
The radar is the institutional response to that pressure. With a defined Assess criteria, any technology proposed by a vendor enters Assess first. Moving to Trial requires evidence of real use in organizational context, not a vendor demonstration. This process slows pressure-driven adoption without creating organizational resistance to new technologies.
How to integrate the Technology Radar with the software procurement process?
The radar should be consulted before any approval to purchase new technology. Technology in Hold does not receive purchase approval. Technology in Assess requires a Trial plan before any significant budget commitment. This integration with the procurement process is what gives the radar teeth.
Other subcapabilities in this capability
Systems Anti-Overlap
Portfolio rationalization through the TIME framework that shows the CFO where duplicate licensing, maintenance and integration consume budget without delivering incremental value.
Technical Governance
Architecture Decision Records and fitness functions as code that enable technical autonomy within explicit criteria, replacing the approval committee with verifiable systemic coherence.
Business Capability Mapping
TOGAF Business Capability Planning and Wardley Mapping that expose the financial consequence of each technology gap and transform investment prioritization from urgency-driven to impact-sequenced.
Legacy Modernization
Six Rs migration strategy with Strangler Fig incremental decommissioning that eliminates legacy maintenance and opportunity cost without a big bang project that paralyzes the business for two years.
Want clarity on where to invest first?
A complete technology capability assessment with an evolution roadmap connected to financial result.