14.2 User Perspective and Need

User Perspective and Need is the practice of framing requirements from the standpoint of the specific person who will use or benefit from a piece of work, capturing not just what that person wants to do but the underlying motivation driving that want, so that a delivery team builds toward genuine value rather than an abstract or generic specification. It forms the foundational discipline behind effective user stories, since a story's usefulness depends heavily on how precisely it identifies the actual person involved and the real need their situation reflects.

Establishing Perspective

Identifying the Specific Role

Effective requirements specify a particular type of user or stakeholder rather than an undifferentiated generic actor, since different roles often have meaningfully different goals, contexts, and constraints that shape what a genuinely useful solution looks like for each of them.

Avoiding Overly Broad Framing

Framing a requirement around an overly generic role, such as simply "a user," risks obscuring important distinctions between groups with different needs, leading to solutions that serve no one particularly well because they attempt to serve everyone identically.

Multiple Perspectives on the Same Feature

A single piece of functionality often serves multiple distinct perspectives, such as an administrator configuring a system and an end user interacting with it, and articulating each relevant perspective separately helps ensure that a solution addresses the genuine needs of every party involved rather than only the most visible one.

Articulating Genuine Need

Distinguishing Need from Stated Want

A stated want often represents a specific, sometimes narrow solution a person has proposed, while the underlying need is the more fundamental problem or goal that solution is meant to address, and effective requirements work distinguishes between the two to preserve flexibility in how the need is ultimately satisfied.

Grounding Need in Context

Understanding a user's broader context — their goals, constraints, and the circumstances in which they will use a given capability — helps clarify why a particular need matters and what form of solution would genuinely satisfy it, beyond a superficial reading of an initial request.

Validating Assumed Needs

Because assumptions about user needs can be inaccurate, particularly for less familiar user groups, validating assumed needs through direct engagement, testing, or observation helps confirm that a requirement is genuinely grounded in reality rather than in unexamined internal belief.

Applying Perspective and Need in Practice

Informing Story Construction

Clearly articulated perspective and need directly shape how a user story is constructed, providing the specific role and underlying motivation that give the story its grounding in genuine value rather than abstract functionality.

Guiding Prioritization

Understanding how significant a given need is, and how many users share it, provides essential input for prioritizing competing pieces of work, helping ensure that limited delivery capacity is directed toward the needs that matter most.

Shaping Acceptance Criteria

A clear understanding of user perspective and need helps define what genuinely constitutes success for a given piece of work, informing acceptance criteria that verify not just technical completion but actual satisfaction of the underlying need.

Techniques for Understanding Perspective and Need

Personas

Developing representative personas that capture the characteristics, goals, and context of key user types provides a consistent reference the team can use when framing requirements, helping maintain a grounded, specific perspective across many individual stories.

Direct Engagement and Empathy Practices

Directly engaging with real users and stakeholders, through interviews, observation, or shared experience, helps build genuine empathy for their perspective and need, reducing the risk of requirements shaped primarily by internal assumption.

Risks of Neglecting Perspective and Need

Building Technically Sound but Irrelevant Solutions

Ignoring genuine user perspective and need risks producing technically well-executed work that fails to address what actually matters to the people it was intended to serve, wasting effort on a solution disconnected from real value.

Homogenizing Diverse User Groups

Failing to distinguish between meaningfully different user perspectives can result in a one-size-fits-all solution that serves no group particularly well, missing opportunities to address the more specific and often more valuable needs of distinct user populations.

User Perspective and Need anchors agile requirements in the concrete reality of who a piece of work is for and why it genuinely matters to them, ensuring that user stories and the work they describe remain connected to authentic value rather than abstract or assumed functionality.