CAPM Practice: Determine how to gather requirements

Design thinking's empathy phase uses deep user research (shadowing, in-depth interviews, journey mapping) to understand users' true experiences. This produces requirements grounded in real human needs rather than organizational assumptions, particularly valuable for innovative products where requirements aren't yet known.

**Why not A:** Empathizing with each other's workload is a team wellness concern, not the empathy phase of design thinking. The empathy phase focuses outward on understanding the end users' emotional experiences, daily contexts, and unmet needs through direct observation and interviews.

**Why not B:** The empathy phase applies to all types of software and product development, not just consumer products. Enterprise users have emotional experiences, frustrations, and contextual needs that deeply affect requirements quality. Understanding these needs improves enterprise software just as much as consumer products.

**Why not C:** Empathy in design thinking does not mean agreeing with all stakeholder requirements. It means deeply understanding the user's perspective, which may reveal that some stated requirements do not address the real underlying need. Empathy informs better requirements, not automatic acceptance of every request.