technology-radar
Technology Radar
Systematically evaluate technologies and track them on a radar (Adopt, Trial, Assess, Hold) to manage technology portfolio.
Context
You are evaluating technologies. Establish a technology radar as organizational consensus on what to use, experiment with, evaluate, or avoid.
Domain Context
Based on Thoughtworks Technology Radar and tech governance:
- Adopt: Use for new projects; well-proven, low risk
- Trial: Experiment in bounded contexts; promising but unproven at scale
- Assess: Evaluate before committing; interesting but uncertain
- Hold: Don't use; superceded or risky
Instructions
- Assess Technology: Maturity, support, community, performance, cost, learning curve
- Plot on Radar: Where does it belong?
- Define Transition: How to move from Trial to Adopt (or obsolete)?
- Communicate: Publish radar; align team on tech direction
Anti-Patterns
- Adopting Too Quickly: Use new shiny tech before proven. Result: regret. Guard: New tech starts in Assess/Trial.
- Radar Never Updates: Published once, ignored after. Guard: Review quarterly.
Further Reading
- Thoughtworks Technology Radar — published tri-annually
- Technology Strategy Books by various authors
More from sethdford/claude-skills
api-test-automation
Expert approach to api-test-automation in test automation. Use when working with .
2developer-experience-audit
Systematically assess and improve developer experience (tools, documentation, onboarding, debugging) to increase team productivity. Use in roadmapping or when noticing developer friction.
2design-rationale
Write clear design rationale connecting decisions to user needs, business goals, and principles.
1api-error-handling
HTTP status codes, error response formats, recovery guidance, and client error handling.
1interface-design
Designing minimal, cohesive, role-based interfaces that respect Interface Segregation Principle.
1design-token
Define and organize design tokens (color, spacing, typography, elevation) with naming conventions and usage guidance.
1