Catalog
method#Software Engineering#Governance#Architecture#Product

ThoughtWorks Radar

The ThoughtWorks Technology Radar classifies technologies, tools and practices and recommends adoption strategies. It serves as a recurring decision and governance instrument for technology direction.

The ThoughtWorks Technology Radar is a regularly updated framework that classifies technology trends, tools, and practices and recommends adoption strategies.
Established
Medium

Classification

  • Medium
  • Organizational
  • Architectural
  • Advanced

Technical context

Architecture board meetingsWikis and knowledge repositoriesRelease and product roadmaps

Principles & goals

Transparency of decision rationaleRegular, time-boxed reviewPractical rationales instead of pure opinions
Discovery
Enterprise, Domain

Use cases & scenarios

Compromises

  • Over-centralization of decisions
  • Ignoring contextual specifics of individual teams
  • Stale recommendations without regular reviews
  • Small, recurring reviews instead of large occasional updates
  • Document rationales and evidence transparently
  • Ensure broad participation from different teams

I/O & resources

  • Proposals from engineering teams
  • Results of prototypes and PoCs
  • Market analysis and community feedback
  • Published radar release with rings and recommendations
  • Decision documentation for architecture boards
  • Recommended experiments or migration plans

Description

The ThoughtWorks Technology Radar is a regularly updated framework that classifies technology trends, tools, and practices and recommends adoption strategies. It supports decisions by assigning entries to rings (Adopt, Trial, Assess, Hold) with concise rationale. Typical uses include architectural reviews and shaping technology roadmaps.

✔

  • Increased visibility of technical decisions
  • Better alignment between teams and leadership
  • Faster decision-making through clear recommendations

✖

  • Subjective assessments can influence outcomes
  • Maintenance effort required to stay current
  • Not all organizations have the required governance structures

  • Adoption rate

    Share of recommendations adopted within a time period.

  • Time to decision

    Average time from proposal to decision.

  • Coverage of technology areas

    Share of relevant topics covered by the radar.

Public ThoughtWorks Radar

The regularly published ThoughtWorks Radar presents industry recommendations and categorizations.

Bank's internal radar

Internal version adapted to compliance and security requirements to steer platform decisions.

Architecture board uses radar as decision basis

The architecture board references radar recommendations for technology selection and deprecation plans.

1

Define scope and involve stakeholders.

2

Collect candidates, document evidence and prioritize.

3

Establish review loop, assign rings and publish.

4

Implement continuous maintenance with fixed review cycles.

⚠️ Technical debt & bottlenecks

  • Outdated technology recommendations in the radar
  • Unaddressed technical fragmentation
  • Missing integration efforts in roadmaps
Evidence collectionCuration effortStakeholder alignment
  • Forcing radar recommendations blindly without context checks
  • Using it as a substitute for technical evaluations
  • Publishing without documented evidence
  • Unclear classification criteria lead to inconsistency
  • Too broad a scope makes maintenance difficult
  • Lack of follow-up on recommendations
Technology scouting and market awarenessFacilitation and consensus buildingStakeholder communication
Transparency of technical decisionsReduction of technical fragmentationRapid assessment of new tools and patterns
  • • Requires cross-disciplinary inputs
  • • Regular resources needed for maintenance
  • • Scope must be clearly defined