4 exercises — reporting a missed OKR with a recovery plan, structuring a concrete headcount ask, pairing risks with mitigations, and opening a product update with quantified achievements.
0 / 9 completed
1 / 9
You are writing the OKR review section of a board deck and need to report a missed target concisely. Which phrasing is most standard?
'Missed due to [specific cause]; on track to close the gap [timeframe]' is the standard board-deck pattern for reporting a miss — it names the cause precisely and immediately pairs it with a forward-looking recovery plan: 'Missed due to a delayed vendor integration; on track to close the gap next quarter.' 'Didn't quite hit the number, for various reasons' is vague and avoids naming a cause. 'It's complicated' signals a lack of command over the topic. 'Things didn't go as planned, sadly' is emotional rather than analytical. Board decks require concise cause-and-recovery framing, not narrative explanation.
2 / 9
You need to write the 'ask' slide of a board deck requesting additional headcount. Which phrasing is most direct and board-appropriate?
'The ask for this quarter is [specific request] to [specific outcome]' is the standard board-deck structure for requests — it names exactly what is being requested and ties it to a business outcome: 'The ask for this quarter is two additional senior engineers to de-risk the migration timeline.' 'It would be great if we could maybe get some more people' is too tentative for a board-level request. 'We're a bit short-staffed, to be honest' describes a problem without making a concrete ask. 'Hiring is something we should probably think about' provides no decision for the board to act on. Board asks must be specific, quantified, and tied to outcomes so the board can approve or decline a clear proposal.
3 / 9
You are writing the risk section of a board deck and need to present a technical risk alongside its mitigation. Which format is most standard?
'Risk: [specific exposure]. Mitigation: [specific plan and timeline]' is the standard board-deck risk format — it names the exact exposure and pairs it directly with a concrete mitigation and timeframe: 'Risk: single-region database creates an availability exposure. Mitigation: multi-region failover planned for Q3.' 'There's a risk, but we're looking into it' is vague on both the exposure and the plan. 'A bit concerning' is imprecise and non-quantified. 'We might have a problem at some point' lacks urgency and specificity. The Risk/Mitigation pairing is the board-standard structure because it lets directors assess exposure and response in a single glance.
4 / 9
You need to open the product update section of a board deck with a concise summary of what was achieved. Which phrasing is most effective?
'We achieved [specific, quantified result]' is the standard opening pattern for a board-deck product update — it leads with a concrete, measurable statement: 'We achieved 94% of the roadmap and shipped the enterprise SSO feature ahead of schedule.' 'We did a lot of stuff, honestly' is vague and unquantified. 'The team worked really hard' focuses on effort rather than outcome, which is not what boards evaluate. 'Too much to summarise, but overall okay' fails to summarise at all, which is the entire purpose of the slide. Board decks reward concise, quantified achievement statements over narrative or effort-based framing.
5 / 9
John from the Frontend team is reviewing your PR. He comments: 'This section uses `fetch` directly – consider abstracting this into a reusable function for better testability and maintainability.' What's the most professional response to acknowledge his feedback while proposing a solution?
The best response demonstrates openness to feedback and actively seeks clarification. Option 1 is dismissive, while option 3 directly rejects valuable advice. Option 2 invites collaboration and learning, and option 4 focuses on testing rather than the broader design concern raised by John. This shows you value his expertise.
6 / 9
You're drafting a Slack message to announce that the deployment of the new authentication service failed due to an unexpected dependency conflict. Which phrasing best conveys urgency and provides necessary information?
This response immediately communicates the failure and includes a crucial detail (dependency conflict). The use of ⚠️ adds emphasis. Option 1 is too vague, option 2 provides context and an estimated time to resolution, and option 3 lacks urgency while option 4 is entirely misleading. Clear communication is vital in high-pressure situations.
7 / 9
You're writing the description for a Pull Request introducing a new API endpoint for retrieving user profiles. Which of the following best describes the level of detail required?
A good PR description should clearly state the purpose of the change. Option 1 is too brief, option 3 lacks detail, and option 2 provides a clear explanation of what the endpoint does and its key fields. This helps reviewers understand the impact of the changes without needing to delve deep into the code.
8 / 9
During a standup meeting, you're reporting on your progress. A teammate asks: 'What's the biggest blocker for this feature?' You respond: 'I'm still waiting for the database schema changes to be finalized.' What's the most effective way to frame this dependency?
This response clearly identifies the dependency (the database team) and explains its impact – delaying your work. Option 2 provides more context than is necessary, option 3 simply states the block, and option 4 avoids taking responsibility. Framing dependencies accurately is crucial for transparent communication.
9 / 9
You're preparing a slide for a board deck outlining a key performance indicator (KPI) that was missed this quarter: 'User Activation Rate'. The slide should include a concise explanation. Which phrasing is MOST effective?
Option 1 is blunt and lacks context. Option 2 provides a clear explanation of why the target was missed, including relevant details (12% vs 18%, product launch). Option 3 is too simplistic, and option 4 is overly emotive. A board-level update needs to be factual, analytical, and focused on the impact.
What will I practice in "Board Deck & Investor Update Language — Presentations English Exercises"?
This is a Technical Presentations exercise set. It walks through 9 scenario-based multiple-choice questions built around real usage of technical presentations terminology that IT professionals encounter on the job.
Is this exercise free to use?
Yes. Every exercise on CoderSlingo, including this one, is free to complete with no account, sign-up, or paywall.
How many questions are in this exercise?
This set contains 9 questions. Each one shows immediate feedback and a detailed explanation after you answer, so you learn the correct usage right away rather than waiting for a final score.
Do I need prior experience to complete this exercise?
No prior experience is required. Each question includes a full explanation covering the reasoning behind the correct answer, so the exercise itself teaches the technical presentations vocabulary as you go.
Can I retry the exercise if I get questions wrong?
Yes — use the "Try again" button on the results screen to reset your answers and go through all the questions again. There is no limit on attempts.
Is my progress saved?
Your answers and score for the current session are tracked in the browser as you go. No account or login is needed, and there is nothing to install.
What if I don't understand a term used in a question?
Read the explanation shown after you answer each question — it breaks down the correct term in plain English with a real-world example. You can also check the site Glossary for quick definitions.
How is this different from reading a blog article on the topic?
Exercises like this one are interactive drills that test and reinforce specific vocabulary through multiple-choice questions, while blog articles explain concepts in prose. Practising here after reading builds active recall, not just passive recognition.
Where can I find more Technical Presentations exercises?
See the Technical Presentations exercises hub for the full set of related pages, or browse all exercise categories from the main Exercises index.
Can I use this exercise to prepare for a technical interview?
Yes — technical presentations vocabulary comes up often in technical discussions and interviews. Pair this exercise with our dedicated Interview Preparation section for role-specific practice.