Practise vocabulary for technical strategy documents: north star, guiding principles, horizon planning, and success criteria at an organisational level.
0 / 10 completed
1 / 10
A ___ describes the long-term aspirational state of the technical platform — what 'success' looks like in 3–5 years.
A north star vision provides direction without prescribing implementation details. 'In 3 years, any engineer can deploy a new service to production in under 30 minutes, with security and compliance built in' is a north star that guides all platform investment.
2 / 10
___ are fundamental beliefs that guide technical decisions — for example, 'We prefer boring technology over clever solutions.'
Guiding principles are durable decision-making heuristics. When engineers face trade-offs, principles help align decisions without requiring escalation. 'Prefer managed services over self-operated infrastructure' is a guiding principle.
3 / 10
A ___ planning approach divides the strategy into Now / Next / Later horizons, prioritising near-term foundations for longer-term goals.
Horizon-based planning (H1/H2/H3 or Now/Next/Later) separates near-term execution from medium-term development and long-term exploration. It acknowledges that long-horizon work requires different investment levels and confidence.
4 / 10
The ___ section of a technical strategy defines how the organisation will know if the strategy is succeeding.
Success criteria make the strategy falsifiable and accountable. 'Developer onboarding time decreases from 2 weeks to 2 days' is a measurable success criterion that determines whether the platform strategy is delivering value.
5 / 10
A staff engineer presenting a technical strategy should frame it in terms of ___ first, before discussing technical details.
Business outcome framing connects technical strategy to organisational goals: 'This reduces our deployment risk, enabling faster feature delivery' is more compelling to leadership than 'We're adopting canary deployments'. Start with the business problem, then explain the technical approach.
6 / 10
Sarah, a Senior Developer, is drafting the description for a Pull Request proposing a new caching layer in the API gateway. She needs to articulate the strategic rationale behind this change. Which of the following best captures that rationale? git review
The correct answer highlights the strategic importance of reducing latency and improving user experience. A technical strategy document shouldn't solely focus on features; it must explain *why* that feature is important within the broader context of performance optimization and user satisfaction. Options A and D are insufficient because they lack this strategic framing, while option C is too focused on a specific technical detail without explaining its impact.
7 / 10
During a standup meeting, Mark, the Tech Lead, is discussing the upcoming sprint. He says, 'We're focusing on improving the resilience of our microservices architecture – it's a key element of our technical strategy to ensure we can handle unexpected traffic spikes.' Which aspect of a technical strategy document does this statement primarily represent? technical-vision
Mark's statement describes the high-level vision and goals driving the team's work. A technical strategy document defines the 'what' and 'why', outlining the desired state of the system. The other options represent more granular aspects like a tactical roadmap, operational procedures, or budget allocation—these would be components *within* the overall strategy, not the overarching statement itself.
8 / 10
As a Staff Architect, you're reviewing a draft of a technical roadmap for a new feature. The document outlines 'Phase 1: Proof of Concept', 'Phase 2: Minimal Viable Product', and 'Phase 3: Full Rollout'. This approach aligns with which strategic planning framework? Now / Next / Later
The 'Now / Next / Later' framework is designed to break down strategic initiatives into distinct phases with clear timelines. This phased approach allows for experimentation, learning, and iterative refinement – a core principle of successful technical strategy execution. The other options describe alternative methodologies that don't necessarily prioritize this structured progression.
9 / 10
The 'Metrics & KPIs' section of a technical strategy document is crucial for demonstrating success. Which of the following would be MOST appropriate to include? key performance indicators
The 'Metrics & KPIs' section measures progress against the strategy's objectives. API response times and error rates are directly relevant to performance improvements – a common goal in technical strategy documents. The other options represent operational metrics or resource allocation, which aren't indicators of strategic success.
10 / 10
During a code review discussion, David, the Principal Engineer, is explaining why they chose to use a message queue instead of direct database calls. He says, 'This aligns with our strategy to decouple services and improve system scalability.' What primary element of a technical strategy is David highlighting? non-functional requirements
David's statement focuses on the architectural decisions made to achieve scalability – a key non-functional requirement. Non-functional requirements (performance, reliability, security) are fundamental drivers of technical strategy, while algorithms, timelines, and programming languages represent more tactical implementation details.
What will I learn from the "Technical Strategy Document Language" exercise?
Practise vocabulary for technical strategy documents: north star, guiding principles, horizon planning, and success criteria at an organisational level.
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.