Product Description Communication & Stakeholder Relations 3 — Questions and Answers
Question 1: A product manager must choose between two features: one requested by the loudest stakeholder and one supported by user research. Which should generally take priority?
- The loudest stakeholder's request to maintain the relationship
- The feature supported by user research as it represents validated user need (Correct answer)
- Whichever feature is faster to build
- Neither — wait for more stakeholder input
Correct answer: The feature supported by user research as it represents validated user need
User research provides evidence of real user need, which should outweigh individual stakeholder influence in product decisions.
Question 2: What is a RACI matrix used for in the context of product stakeholder management?
- Tracking customer satisfaction scores
- Clarifying who is Responsible, Accountable, Consulted, and Informed for each decision (Correct answer)
- Prioritizing features by business value
- Documenting user stories
Correct answer: Clarifying who is Responsible, Accountable, Consulted, and Informed for each decision
A RACI matrix defines decision-making roles so that stakeholders know exactly when and how they will be involved.
Question 3: During a product launch, the marketing team sends communications that contradict the product team's messaging. What process failure does this indicate?
- A technology integration failure
- Lack of a shared messaging brief and cross-team alignment before launch (Correct answer)
- A legal compliance issue
- Poor engineering documentation
Correct answer: Lack of a shared messaging brief and cross-team alignment before launch
Inconsistent external messaging signals that teams did not align on a single source-of-truth messaging document before launch.
Question 4: Which type of stakeholder typically requires the most frequent and detailed product updates?
- Passive stakeholders with no direct role
- Hands-on execution teams like engineering and design who need daily context (Correct answer)
- Board members who only care about annual results
- External vendors with no integration work
Correct answer: Hands-on execution teams like engineering and design who need daily context
Teams actively building the product need frequent detailed updates to make decisions and stay unblocked.
Question 5: A product description for a B2B SaaS tool needs to address both IT administrators and business end users. What is the best approach?
- Write a single generic description that ignores role differences
- Create separate messaging sections that address each persona's specific concerns (Correct answer)
- Focus only on IT administrators since they control purchasing
- Focus only on end users since they use the product daily
Correct answer: Create separate messaging sections that address each persona's specific concerns
Different stakeholder personas have distinct concerns, so layered or segmented messaging addresses both audiences effectively.
Question 6: What is the risk of over-communicating with stakeholders by sending too many updates?
- Stakeholders become too well-informed to push back
- Important signals get lost in noise and stakeholders start ignoring communications (Correct answer)
- Legal liability increases with more documentation
- Engineering velocity decreases
Correct answer: Important signals get lost in noise and stakeholders start ignoring communications
Excessive communication volume leads to alert fatigue, causing stakeholders to miss or dismiss critical updates.
Question 7: A product manager presents a product roadmap to stakeholders who immediately ask for features not on the plan. What is the most effective response?
- Add all requested features to the roadmap on the spot
- Dismiss the requests to protect the current plan
- Acknowledge the requests, explain the prioritization criteria, and offer a process for submitting them formally (Correct answer)
- Cancel the roadmap presentation and reschedule
Correct answer: Acknowledge the requests, explain the prioritization criteria, and offer a process for submitting them formally
Acknowledging requests while explaining the prioritization framework shows respect for stakeholder input without making unvetted commitments.
A product manager must choose between two features: one requested by the loudest stakeholder and one supported by user research.
Which should generally take priority?