Problem Statement - The Elicitation Technique for Internal Business Requirements
The Problem Unlike Product Requirements that are very straightforward (like a new User Story or an enhancement to an existing one), from time to time we get ambiguous and partial business requirements internally (i.e. not customer or partners) that are typically buried in solutions - “We need to be compliant with GDPR regulation”, “There is a vendor who is willing to offer services at a lower price point”, “We need to start this internal team blog and being transparent about what we do ” Which on analysis boils down to: “We need to focus on Compliance as we are majorly exposed to the risk of a Regulatory Audit”, “We should focus on cost savings as we are running low on funding”, “We need to reduce tension and conflict with other teams”. Source These sort of one liners will often come from a senior role like a Director, VP or SVP, and as the Product Manager deciding or recommending items for Roadmap there is a slight apprehension coz it’s….well a senior role and they’ve probably thoug...