User needs patterns
A path for working definitions, failure modes and governance questions around user needs, civic needs and evidence-to-decision traceability.
What this path is for
This is a holding area for a larger cluster of thinking about user needs: how they are discovered, written, governed, distorted, erased, superseded and connected to civic outcomes.
These are Happygeneralist working definitions. They are part of the theoretical underpinning of Civic Design Intelligence, not settled external standards or widely established design terminology.
Why this category is necessary
User needs are often treated as small delivery artefacts: statements for backlogs, content pages, service assessments or product decisions.
That is useful, but too narrow. In public-service work, user needs sit inside a larger ecology of evidence, civic obligations, institutional constraints, policy choices, lived experience and operational realities.
If that ecology is not made visible, user needs can become decorative: present in language, weak in power.
Core distinction
A user need names what a person must be able to accomplish, understand, decide, access, maintain or resolve.
A civic need names what the system or institution must make possible, protect or repair.
A central problem in this cluster is that these concepts are often collapsed into tasks, features, content, policy aims, outcomes or organisational priorities.
Early pattern map
User needs erasure
A need is ignored, minimised, reframed, individualised or made illegible inside a policy, project, strategy, speech or service design.
User needs drift
A need remains visible, but its meaning moves away from the evidence, context or outcome that originally made it useful.
User needs collapse
The distinction between user needs and other concepts breaks down. A need becomes treated as a task, feature, content requirement, user story, service output, policy aim or organisational priority.
Civic needs erasure
Civic obligations, justice floors, public value or structural duties are pushed out of view when needs are framed only as individual tasks or transactional service moments.
Needs as traceable objects
A more positive pattern: user needs and civic needs are treated as persistent, traceable, supersedable knowledge objects.
Relationship to Civic Design Intelligence
Civic Design Intelligence is connected to this cluster because it is trying to solve a practical version of the same problem.
If needs only live in reports, workshops or backlogs, they are easy to lose. If they become structured knowledge objects, they can be inspected, connected and challenged.
User needs entries
These cards are generated from Notebook entries tagged or themed around user needs.
User needs are vectors, not labels
A small interactive sketch showing how small changes in user-need wording can rotate the implied solution space.
Civic AI and computable needs
A working argument that civic AI systems need a stronger model of human, civic and institutional needs than correlation, sentiment or delivery efficiency alone can provide.
LLM training and user needs
A stub for a working definition about how LLMs often reproduce weak, product-centric models of user needs unless explicitly corrected.
The Blame Trap
A stub for a working definition about people being led to blame themselves for failures that originate in flawed systems.
User needs collapse
A stub for a working definition about user needs being collapsed into tasks, features, content requirements, policy aims or organisational convenience.
User needs drift
A stub for a working definition about the progressive misalignment between validated user needs and the actual outputs of service delivery.
User needs erasure
A stub for a working definition about needs being ignored, minimised, reframed or made illegible inside institutional processes.
To develop later
- Short standalone entries for each pattern.
- Examples from public-service work.
- A clearer distinction between user needs, civic needs and organisational needs.
- Evidence patterns that indicate drift, erasure or collapse.
- A taxonomy of needs failure modes.
- Links to Civic Design Intelligence object types.
- Guidance for writing needs that survive translation into decisions.