Algorithms Communication & Stakeholder Relations 2 — Questions and Answers
Question 1: A project manager asks why the team switched from bubble sort to merge sort for a large dataset. What is the most effective way to communicate this technical decision?
- Explain using Big-O notation and complexity theory
- Show a before-and-after runtime comparison with actual data (Correct answer)
- Say the old algorithm was 'too slow'
- Refer them to the algorithm's Wikipedia page
Correct answer: Show a before-and-after runtime comparison with actual data
Concrete performance benchmarks are the most persuasive and accessible evidence for non-technical stakeholders.
Question 2: During a sprint review, a stakeholder questions why the search feature takes O(log n) time. How should the developer respond?
- Ignore the question and move on
- Explain with a visual analogy such as finding a name in a phone book (Correct answer)
- Provide the full mathematical derivation
- Say it is the best possible solution with no further context
Correct answer: Explain with a visual analogy such as finding a name in a phone book
Analogies bridge the gap between technical concepts and non-technical understanding.
Question 3: A client insists that a simpler O(n²) algorithm is 'good enough' for their current scale. What is the best stakeholder response strategy?
- Agree immediately to avoid conflict
- Overrule the client and implement the better algorithm anyway
- Acknowledge their current needs while documenting scalability risks for the record (Correct answer)
- Refuse to implement any algorithm below O(n log n)
Correct answer: Acknowledge their current needs while documenting scalability risks for the record
Documenting trade-offs respects the client's authority while ensuring risks are formally recorded.
Question 4: When presenting algorithm trade-offs to a mixed audience of engineers and executives, what communication approach is most effective?
- Use only mathematical notation to maintain precision
- Tailor the depth of explanation to each audience segment (Correct answer)
- Simplify everything to business outcomes only
- Delegate all communication to the engineering team
Correct answer: Tailor the depth of explanation to each audience segment
Effective communicators adjust technical depth based on the audience's background and needs.
Question 5: A stakeholder demands a feature be built using a specific algorithm they read about online, but a better option exists. What is the recommended approach?
- Implement their suggestion to maintain stakeholder trust
- Refuse and explain they lack technical knowledge
- Listen to their reasoning, present evidence for the alternative, and seek consensus (Correct answer)
- Escalate to management immediately
Correct answer: Listen to their reasoning, present evidence for the alternative, and seek consensus
Collaborative problem-solving with evidence builds trust and leads to better technical outcomes.
Question 6: What is the purpose of maintaining an algorithm decision log during a project?
- To satisfy compliance requirements only
- To provide an audit trail of technical choices and their rationale for all stakeholders (Correct answer)
- To slow down the development process
- To replace verbal communication in team meetings
Correct answer: To provide an audit trail of technical choices and their rationale for all stakeholders
Decision logs create transparency, enabling stakeholders to understand and revisit technical choices.
Question 7: A new stakeholder joins mid-project and disagrees with an algorithm choice made three months ago. What is the most professional response?
- Tell them the decision is final and cannot be revisited
- Walk them through the original decision context, constraints, and trade-offs considered (Correct answer)
- Immediately switch algorithms to accommodate their preference
- Exclude them from future technical discussions
Correct answer: Walk them through the original decision context, constraints, and trade-offs considered
Providing historical context helps new stakeholders understand past decisions before forming opinions.
A project manager asks why the team switched from bubble sort to merge sort for a large dataset.
What is the most effective way to communicate this technical decision?