User needs drift
A stub for a working definition about the progressive misalignment between validated user needs and the actual outputs of service delivery.
Stub
User needs drift is a working term for the progressive misalignment between real, validated user needs and the actual outputs of service delivery.
It describes what happens when “start with user needs” remains present as a principle or assessment phrase, but the work gradually shifts towards delivery artefacts that no longer preserve the underlying need.
The drift is usually a movement away from stable, solution-agnostic needs towards solution-proximate artefacts: user stories, content pages, backlog items, features, service scripts or governance evidence.
Working definition placeholder
User needs drift occurs when design and delivery diverge from validated research, or when the original needs were never accurately captured in the first place.
A high-level need such as “establish eligibility without financial risk” may drift into narrower artefacts such as “upload payslips” or “read a page explaining eligibility”. Those artefacts may be useful, but they are not the same as the need.
Why it matters
Small changes in user need wording can change the solution vector.
For example, these are not the same need:
- need to know options
- need to compare options
- need to judge which options are realistic
- need to decide which route to take
- need to protect future options
If a project treats one of these as if it were another, it can deliver activity without delivering public value.
Likely mechanisms to explore
- policy-led override
- measurement bias
- toolchain inheritance
- translation loss
- linguistic capture
- local optimisation
- conflation of user needs with user stories
- assessment optics
Link to Civic Design Intelligence
This is one of the theoretical problems Civic Design Intelligence may help expose by keeping needs, evidence, outcomes and decisions more traceable.
To develop later
- review and strengthen the definition
- decide whether “solution-vector sensitivity” should be its own entry
- add carefully chosen examples
- explore UK public-sector causes without overclaiming
- turn the corrective governance ideas into a separate checklist or tool