Synthesize user needs

Definition and scope

Organize research observations into reviewable user problem statements.

Domain: Product

L0 · Hypothesis — original editorial defaults, not empirically verified

AI-assisted editorial review; independent domain review and empirical validation remain pending.

Typical inputs

Consented, minimized research notes and study scope

Expected outputs

Need statements with observation references

Proposed success criteria

1. Each need identifies a user problem and supporting observation or is labeled an assumption.

2. Unverified claims, missing context and required authorizations are explicit; the artifact does not certify external completion.

Evidence expectations

For criterion 1: De-identified observation references and a separate assumption register.

For criterion 2: Reviewer-visible scope, unresolved questions and authorization requirements attached to the versioned artifact.

Risks and authority

A biased sample can misrepresent the user population.

Planning defaults only. Confirm scope, permission and human approval before instantiation; this record authorizes no action.

These are context-dependent planning considerations, not legal advice or execution permissions.

Provenance and quality

Release ordien-world-2026-09-07-v2; revision 1; recorded 2026-09-06.

L0 · Original proposed definition and defaults. Design hypotheses, not empirical findings or universal process requirements. Source: Ordien — Ordien Phase 6 editorial proposals. Scope: Phase 6 original curation, exact subject identified by canonical ID. Inspected 2026-09-06.

L1 · The guidance separates research-supported user problems from internal assumptions and recommends refining needs through continuing research. Source: UK Government Digital Service — Learning about users and their needs. Scope: Writing user needs; Validating user needs. Inspected 2026-09-06.

Source-supported statements do not validate the proposed workflow, automation performance or economic outcomes. Adapt defaults to the organization's requirements and authority.

Related intelligence

Requires: User need discovery. Relationship quality: L0; applicability requires review.

Contributes to: User need discovery. Relationship quality: L0; applicability requires review.

Proposed dependent: Plan need validation. Relationship quality: L0; applicability requires review.