Description
A structured way to respond to stakeholder requests by asking why and making trade-offs explicit, backed by a steady communication cadence with the people who commission work.
Requests come from customers, sales, executives, engineers and designers, and none can simply be brushed off. Crumlish's protocol responds to a roadmap request without negating its value: thank the requester, ask what problem it solves and what alternatives were considered, review current priorities and their link to strategy and OKRs, ask which agreed commitment should give way, and compare evidence. If overruled, define success metrics and later report both the outcome and the cost of dropped work. LeMay warns against falling in love with 'no'; the aim is to ask why first. Nolis and Robinson add four tenets for ongoing relationships: learn each stakeholder's goals, communicate constantly on a fixed weekly or fortnightly cadence, keep deliverables consistent in structure and storage, and build rapport.
Attributes
- Discipline
- Design & Product Practice
- Loss type
- Active
- Stage
- Strategy, Definition
- Data
- Qualitative
- Effort
- Hours
Steps
- Thank the stakeholder and ask what problem or opportunity the request addresses, the expected outcome, the risk of not doing it and the alternatives considered.
- Offer to research the problem space further where the request is not yet understood.
- Review the current Now priorities with them and show how each connects to strategy and OKRs.
- Ask which agreed commitment should be set aside to make room, noting that any change must be re-reviewed by all stakeholders, and ask for supporting data while having your own ready.
- If overruled, define success metrics for the new item, measure its impact and later report the outcome and the cost of the dropped priorities.
- For ongoing work, learn each stakeholder's goals and likely reactions to results, and bring in a senior colleague when delivering bad news.
- Hold a recurring weekly or fortnightly meeting, send roughly weekly updates, and standardise deliverables (objective and data first, conclusions and next steps last, one format and one storage place).
Sources
- Product Management for UX People (Crumlish, 2022)
- Build a Career in Data Science (Nolis & Robinson, 2020)
Also known as
- Stakeholder request handling ('saying no' protocol)
- Saying no to stakeholders
- Roadmap request triage
- Ask why before yes or no
- Stakeholder management for data and research teams
- Four tenets of working with stakeholders
- Stakeholder communication cadence
Categories
- Design
- Design & Product Practice