Scoping Research (SCOPE)

Code: SCOPE

Scoping research strategy defines the research's how, when, reach, impact, process and methods. The scope is also determined by the shorter-term task-orientated execution versus longitudinal holistic strategy.

SCOPE 1.0.0 Planning and scoping user research activities for an organisation

G

SCOPE 1.0.1

Guidance on Planning Research

This section applies to an organisation, research team, or individual tasked with defining a user research study scope.

Scoping activities must bring together stakeholders, constraints, risks and research questions into a coherent plan that is proportionate to the decisions being made and the potential impact on users.

SCOPE 1.1.0 Foundational scoping principles, rules & governance conditions

P

SCOPE 1.1.1

Principles of Research Scoping

  • Research scope must be proportionate to risk, impact and intended outcomes.
  • Scope must be shaped through early dialogue with product, policy, operational and technical stakeholders.
  • Researchers must consider equity, accessibility and inclusion when defining who research should reach.
  • Scoping must recognise organisational constraints: time, capability, tooling and ethical boundaries.
  • Research must be scoped to maximise learning efficiency, not to expand artefacts unnecessarily.
P

SCOPE 1.1.2

Method Selection Principle

Select research methods based on question type, risk category, accessibility needs and operational feasibility.

Method selection must be documented with a justification demonstrating alignment to study goals, constraints and ethical considerations.

P

SCOPE 1.1.3

Interdependency Mapping Principle

Research planning must map interdependencies across teams, digital services, data flows and policy constraints.

Identified interdependencies influence scope, risk and required approvals. Where dependencies are unclear, scoping must include time to discover and document them.

R

SCOPE 1.1.4

Research Risk Assessment Rule

Every study must undergo a risk assessment covering participant risk, researcher risk, data sensitivity, environmental risk and operational dependencies.

High-risk studies require formal sign-off, documented mitigation actions and clearly identified escalation routes.

R

SCOPE 1.1.5

Scalability and Right-Sizing Rule

Research scope must be sized proportionately to the decision it informs.

Studies may be scaled up or down depending on urgency, required certainty and resource availability. Oversized studies that do not change decisions should be challenged.

R

SCOPE 1.1.6

Stakeholder Management Requirement

Research planning must identify all relevant stakeholders, define their involvement and record expectations.

Stakeholder engagement must be maintained throughout the study lifecycle, including planning, fieldwork, analysis and decision-making.

R

SCOPE 1.1.7

Cross-Team Governance Rule

Where research spans multiple teams or services, governance must ensure shared ownership, review checkpoints and agreed processes for handling cross-service insight impacts.

Responsibilities for acting on findings must be clearly assigned and documented.

SCOPE 1.2.0 Tactical and strategic research types

G

SCOPE 1.2.1

Tactical Research

Tactical research solves immediate delivery questions. It is narrow, fast and context-specific.

Guidance:

  • prioritise operational needs
  • minimise artefacts
  • optimise speed and clarity

Tactical work is effective when it unblocks decisions without attempting to be strategic.

G

SCOPE 1.2.2

Strategic Research

Strategic research focuses on long-term vision, cross-service impact and underlying user needs.

It requires greater depth, mixed methods and synthesis across multiple data sources. Outputs may include insight frameworks, opportunity maps and service-level risk registers.

SCOPE 1.3.0 Research planning, programmes & pipelines

G

SCOPE 1.3.1

Strategic Research Planning Processes

Establishing a strategic plan for user research ensures that research activities are not just reactive, but proactively aligned with the organisation's long-term objectives.

  • Create a research roadmap that links research initiatives to business goals over the next 6 to 12 months.
  • Align research planning with product and business planning cycles so research supports key milestones.
  • Co-create the research agenda with stakeholders, prioritising questions that unlock strategic decisions.
  • Balance exploratory and evaluative work to support both immediate delivery and long-term opportunity finding.
  • Review and adjust the plan regularly to respond to changing organisational priorities.
G

SCOPE 1.3.2

Research Programme Management and Pipelines

As demand for research grows, a structured programme management approach is required to handle multiple projects efficiently.

  • Standardise research requests through an intake form capturing aims, timelines and constraints.
  • Maintain a visible research backlog and calendar showing proposed, in-progress and completed work.
  • Prioritise projects based on strategic impact, urgency and readiness of teams.
  • Coordinate cross-functional resources such as recruitment, tools and specialist support for each study.
  • Monitor progress, adjust the pipeline as priorities change and communicate trade-offs transparently.

SCOPE 1.4.0 Templates, methods & agile research

G

SCOPE 1.4.1

Templates and Method Guidance

Providing templates and clear method guidance streamlines studies and supports consistent quality.

  • Maintain a central library of templates for plans, screeners, discussion guides, surveys and reports.
  • Create concise playbooks for common research methods, with when-to-use guidance and practical steps.
  • Embed ethical and legal prompts within templates, including risk considerations and consent requirements.
  • Version-control templates, assign ownership and update them based on feedback and emerging practice.
  • Onboard new staff to the template library and playbooks as part of research training.
G

SCOPE 1.4.2

Agile Research Planning

In fast-moving teams, research must integrate with agile delivery without losing rigour.

  • Embed research tasks into sprints and planning cycles, not as a separate track.
  • Use lean, just-enough studies that can be run and analysed within sprint timescales.
  • Maintain a rolling research backlog aligned to product backlogs and release plans.
  • Synchronise research milestones with key design and development decisions.
  • Favour rapid debriefs and lightweight deliverables that feed directly into the next iteration.

SCOPE 2.0.0 Defining reach and impact

G

SCOPE 2.0.1

Guidance on Reach and Impact

This section applies to defining a study's organisational reach and the impact its findings may have across services, policies and operations.

SCOPE 2.1.0 Reach and impact principles & cross-service implications

P

SCOPE 2.1.1

Principles of Reach and Impact

  • Research must intentionally reach users who are most affected by the service, including edge-case and underserved groups.
  • Impact must be considered beyond the immediate product team, spanning policy, operations and adjacent services.
  • Findings must be communicated in ways that support decision-making at multiple levels of the organisation.
G

SCOPE 2.1.2

Document Cross-Service Implications Early

When research uncovers insights affecting multiple teams or services, document these early.

This enables coordinated decision-making and prevents duplicated effort. Cross-service implications often reveal hidden policy impacts or operational dependencies.

R

SCOPE 2.1.3

Cross-Service Impact Recording Requirement

Where research uncovers implications for other teams, services or policies, researchers must:

  • record cross-service implications in the research log
  • notify responsible product or service owners
  • escalate risks relating to legality, equity or operational feasibility

Glossary & Definitions

Tactical Research
Short-term, focused studies aimed at unblocking specific delivery questions.
Strategic Research
Long-term, cross-cutting studies that explore broader needs and risks.
Research Roadmap
A time-based plan linking research activities to strategic questions and delivery milestones.
Research Programme
A portfolio of coordinated research activities managed collectively.
Research Backlog
A prioritised list of research questions and studies awaiting exploration.

Templates & Artefacts

Use the following templates to support SCOPE activities:

Change History

Version Date Summary of Changes Author / Owner
0.2-draft 2025-12-11 Introduced Principles and Rules for SCOPE 1.0.0 and 2.0.0; corrected numbering to 1.x.0 and 2.x.0 pattern; added governance conditions for scoping; clarified cross-service impact rules; grouped tactical, strategic, programme and agile guidance into topic areas. ResearchOps Governance Team