Practise vocabulary for technology radars: Adopt/Trial/Assess/Hold quadrants, radar rings, technology blips, and communicating radar decisions.
0 / 10 completed
1 / 10
A technology radar organises technologies into quadrants (Techniques, Tools, Platforms, Languages) and ___ indicating adoption maturity.
A technology radar (popularised by ThoughtWorks) uses four rings: Adopt (recommended for production), Trial (explore with caution), Assess (worth researching), Hold (avoid or phase out). Rings communicate maturity and risk.
2 / 10
A technology in the ___ ring of a tech radar is recommended for all teams to use in production — it's proven and mature.
Adopt means the organisation endorses this technology for production use. It's been proven in production environments, has internal expertise, and is preferred over alternatives. Moving to Adopt is a significant organisational endorsement.
3 / 10
Placing a technology on ___ signals the organisation recommends against adopting it — either because it creates technical debt, has alternatives, or has proven problematic.
Hold means: don't adopt this for new work. It may still be used in existing systems but should not be expanded. Technologies move to Hold when they've been superseded, created significant problems, or conflict with the organisation's direction.
4 / 10
A technology ___ is an individual entry on the radar — representing a specific tool, technique, platform, or language.
A blip is a single technology entry on the radar. Each blip has a name, quadrant (type), ring (maturity), and a description explaining why it's positioned there. Blips move between rings as the technology matures or is proven.
5 / 10
When communicating a tech radar decision to an engineering team, the key information to convey alongside the recommendation is ___.
The radar's value is its reasoning, not just the verdict. 'We moved X to Hold because it has poor operational characteristics at scale and we've standardised on Y' gives teams the context to apply the decision intelligently and explain it to their stakeholders.
6 / 10
Sarah from the Frontend team sent this Slack message during a code review:
'The `debounce` function in this PR is implemented using a simple setTimeout. Shouldn't we be leveraging a library like Lodash for better performance and maintainability?'
Which of the following best describes Sarah's comment regarding 'debounce'?
Sarah's comment highlights the importance of considering performance optimization. While custom implementations are sometimes acceptable, suggesting a well-established library like Lodash (which often provides optimized versions) demonstrates an understanding of best practices and potential improvements. The key is that Sarah isn't simply criticizing setTimeout; she's advocating for a more robust solution.
7 / 10
During a standup meeting, you're discussing the 'CloudWatch Logs Insights' technology with your team. You state: 'We're moving CloudWatch Logs Insights into the 'Tools' quadrant because it's widely used and provides excellent visibility into our applications.' What is the primary reason for placing a tool like CloudWatch Logs Insights in the 'Tools' quadrant of a tech radar?
The 'Tools' quadrant on a tech radar signifies maturity and widespread adoption. Technologies here are generally well-established, readily available, and supported across different teams – making them suitable for immediate use without requiring substantial investment or strategic alignment. Placing it in this quadrant reflects its practical value as a supporting tool.
8 / 10
You're drafting a pull request description for a new feature that uses GraphQL. You want to accurately reflect the technology's position on the tech radar. Which of the following statements is most appropriate?
The 'Techniques' quadrant denotes a technology that is gaining traction but isn't yet fully mature. Describing GraphQL as 'promising' acknowledges its potential while avoiding over-hyping or suggesting immediate production readiness. It's important to avoid overly enthusiastic claims about technologies in early stages of adoption, aligning with the tech radar's purpose.
9 / 10
A developer points out that a technology listed on the Tech Radar is now in the 'Declining' quadrant. What does this generally indicate?
A 'Declining' quadrant signifies that the technology's usage and support are decreasing. This often means it faces challenges such as lack of community support, reduced vendor investment, or the emergence of superior alternatives—making continued adoption risky and potentially leading to technical debt. It's a signal for caution regarding future investments.
10 / 10
During a discussion about a new data streaming platform, the team decides to recommend it to 'Experiment' teams only. What key information should be included in the tech radar documentation alongside this recommendation?
When recommending a technology to an 'Experiment' team – signifying low maturity – the focus should be on realistic expectations. Providing information about vendor support and roadmap updates is crucial for managing those teams' limited resources and understanding the long-term viability of the platform. Guarantees of scalability or seamless integration are often unreliable at this stage, adding unnecessary risk.
What will I learn from the "Tech Radar Vocabulary" exercise?
Practise vocabulary for technology radars: Adopt/Trial/Assess/Hold quadrants, radar rings, technology blips, and communicating radar decisions.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to use with no account, sign-up, or paywall required.
How many questions are in this exercise?
This set contains 10 multiple-choice questions, each with a detailed explanation shown after you answer.
Do I need to create an account to track my progress?
No account is required. Your progress bar and score reset each time you reload the page, but you can retry the exercise as many times as you like.
Who is this Staff Engineer Communication exercise for?
This exercise is built for IT professionals and non-native English speakers who need to read, write, and discuss staff engineer communication topics confidently at work.
What happens if I answer a question incorrectly?
You will see the correct answer highlighted along with a detailed explanation of why it is correct -- so every wrong answer becomes a learning moment, not just a lost point.
Can I retry this exercise?
Yes -- click "Try again" on the results screen at any time to reset your score and go through all the questions again.
How long does this exercise take to complete?
Most learners finish all 10 questions in under 10 minutes, since each question is answered by clicking a single option.
Where can I find more Staff Engineer Communication exercises?
See the full Staff Engineer Communication exercises hub for more vocabulary drills on this topic.
Is this exercise mobile-friendly?
Yes -- the exercise works on any device with a modern browser, including phones and tablets, with no app download required.