How to use technology radars to make transparent tech decisions
summary
Medic documents technology choices for a 100‑person global team with two public radars — CHT Technology Radar for Implementers and CHT Technology Radar for Contributors — built atop ThoughtWorks and AOE open‑source tools and hosted on GitHub. The radar encodes adoption rings (adopt trial assess stop), links each entry to the rationale, and triggers six‑monthly reviews. Outcomes: faster onboarding, clearer alignment, uncovered a Kubernetes skills gap that prompted training, and sustained community contributions when maintainers enforce documentation.
AI-written summary · about
chapters (8)
- 0:00Technology radars introduction
- 2:26Technology radars solve docs gaps
- 3:52Adopting tech radar at Medic
- 5:58Two tailored tech radars
- 6:40Culture of documented tech choices
- 7:43Reviewing established tools
- 8:24Transparency in tech decisions
- 9:28Lessons from tech radar
related talks
41mMaking strategic technology choices in a fast moving world
12mThe Art of Building Teams — a Mindset Radar
25mSteering through technological change
36mHow to make technical decisions?
24mRadical Transparency: Leading Engineering With Openness
40mDo we need it?
43mThinking Architecturally
41mUnpacking Technical Decisions