User Research Playbook

User Research Playbook is a practical transparent research programme for Executives, Operators, Founders, Functional leaders. It connects user research playbook to evidence, ownership, implementation controls, measurable outcomes, and a repeatable review cycle.

By Rusaka Research · Published 2026-07-27 · Updated 2026-07-27 · 10079 words

Introduction

User Research Playbook helps teams make a consequential problem selection, experience design, prioritisation, or product investment decision without confusing a polished document or tool with reliable evidence. The resource is designed for Executives, Operators, Founders, Functional leaders and provides a structured path from a bounded question to an accountable decision, controlled implementation, and measurable review.

Use this resource as a working system. Adapt it to the organisation, but retain the evidence fields, owners, dates, assumptions, limitations, controls, and approval points. The objective is not uniform paperwork. It is to make decisions easier to inspect, challenge, operate, and update as conditions change.

Problem definition

The recurring problem in UI UX and Product Design is not a shortage of ideas. It is the distance between an attractive idea and the evidence required to act responsibly. Teams may begin with undefined scope, mixed units, weak baselines, optimistic benefits, or technology choices made before requirements are clear.

That creates solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. A recommendation can sound precise while hiding who owns the outcome, which claims are verified, what happens when assumptions fail, and how the organisation will operate the result after launch. User Research Playbook closes those gaps by making the decision chain explicit.

The correct starting point is user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. If that baseline cannot be assembled, treat the absence as a finding. Do not replace missing evidence with a more elaborate model. Define the minimum evidence needed for the next reversible step and assign responsibility for obtaining it.

Why it matters

A well-governed transparent research programme reduces rework because scope, evidence, ownership, and acceptance criteria are agreed before expensive execution. It also improves review quality: specialists can challenge the assumptions relevant to their discipline without reconstructing the entire decision from meetings and messages.

The business value should be visible through task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. These measures need calculation rules, owners, data sources, and review dates. Activity measures may help manage delivery, but they should not be presented as proof that the intended organisational or user outcome has been achieved.

Core concepts

  1. Delivery sequencing

    Order work by dependency and learning value so the team can validate critical assumptions before making irreversible commitments. In User Research Playbook, this means linking the recommendation to user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes, then recording how it affects problem selection, experience design, prioritisation, or product investment. The concept is useful only when it produces an observable decision, control, artefact, or measure.

  2. Vendor and partner assessment

    Compare external providers against explicit requirements, evidence quality, portability, support, security, and total cost. In User Research Playbook, this means linking the implementation choice to user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes, then recording how it affects problem selection, experience design, prioritisation, or product investment. The concept is useful only when it produces an observable decision, control, artefact, or measure.

  3. Measurement system

    Define leading and lagging indicators, data owners, calculation rules, reporting frequency, and thresholds that trigger action. In User Research Playbook, this means linking the recommendation to user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes, then recording how it affects problem selection, experience design, prioritisation, or product investment. The concept is useful only when it produces an observable decision, control, artefact, or measure.

  4. Quality assurance

    Set acceptance criteria, independent review points, test evidence, exception handling, and release authority before execution begins. In User Research Playbook, this means linking the implementation choice to user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes, then recording how it affects problem selection, experience design, prioritisation, or product investment. The concept is useful only when it produces an observable decision, control, artefact, or measure.

  5. Change management

    Plan communication, training, adoption support, role changes, feedback loops, and resistance handling as delivery work. In User Research Playbook, this means linking the recommendation to user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes, then recording how it affects problem selection, experience design, prioritisation, or product investment. The concept is useful only when it produces an observable decision, control, artefact, or measure.

  6. Documentation

    Maintain a durable decision record containing assumptions, sources, approvals, changes, limitations, and the current operating procedure. In User Research Playbook, this means linking the implementation choice to user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes, then recording how it affects problem selection, experience design, prioritisation, or product investment. The concept is useful only when it produces an observable decision, control, artefact, or measure.

Step-by-step implementation

  1. 1. Scale — User Research Playbook

    During scale, use User Research Playbook to answer a bounded question through reproducible methods and evidence. Start with user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it.

    Required output: a protocol, source set, analysis record, findings, and limitations.

  2. 2. Operations — User Research Playbook

    During operations, use User Research Playbook to answer a bounded question through reproducible methods and evidence. Start with user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it.

    Required output: a protocol, source set, analysis record, findings, and limitations.

  3. 3. Discovery — User Research Playbook

    During discovery, use User Research Playbook to answer a bounded question through reproducible methods and evidence. Start with user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it.

    Required output: a protocol, source set, analysis record, findings, and limitations.

  4. 4. Design — User Research Playbook

    During design, use User Research Playbook to answer a bounded question through reproducible methods and evidence. Start with user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it.

    Required output: a protocol, source set, analysis record, findings, and limitations.

  5. 5. Pilot — User Research Playbook

    During pilot, use User Research Playbook to answer a bounded question through reproducible methods and evidence. Start with user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Name the accountable owner, the evidence reviewer, the decision deadline, and the output that proves this stage is complete. Record exclusions and unresolved questions rather than allowing them to disappear into narrative. The stage closes only when its evidence can be reproduced by someone who did not prepare it.

    Required output: a protocol, source set, analysis record, findings, and limitations.

Worked example: applying User Research Playbook

Consider a product team choosing which user problem to solve and how to measure whether the release materially improves the user outcome. The team first writes the decision in one sentence, identifies the accountable executive, and records the current baseline. It separates confirmed facts from estimates and creates named base, downside, and stop scenarios rather than blending uncertainty into one headline number.

The team then uses the transparent research programme to compare options. Each option is assessed against outcome, feasibility, cost, time, control, reversibility, and operating ownership. Material assumptions are assigned to reviewers. A recommendation is accepted only when the evidence pack and the decision record tell the same story.

During the pilot, the team measures task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. It records exceptions and user or operator feedback, then decides whether to stop, revise, repeat, or scale. The example is intentionally hypothetical: organisations should replace every assumption with their own evidence and obtain review from product, design, research, accessibility, engineering, analytics, and customer-facing specialists as applicable.

Best practices

  1. Scenario analysis

    Test a defensible base case and named downside cases without hiding weak assumptions inside a single blended forecast. Apply the practice with a named owner, evidence location, completion date, and exception process. Keep the control proportionate to the consequence of error and confirm that it still works after the initial implementation team has moved on.

  2. Security and resilience

    Design least privilege, recovery, monitoring, incident ownership, and continuity measures in proportion to the consequence of failure. Apply the practice with a named owner, evidence location, completion date, and exception process. Keep the control proportionate to the consequence of error and confirm that it still works after the initial implementation team has moved on.

  3. Data governance

    Assign data ownership, permitted uses, quality rules, retention, lineage, access controls, and deletion responsibilities. Apply the practice with a named owner, evidence location, completion date, and exception process. Keep the control proportionate to the consequence of error and confirm that it still works after the initial implementation team has moved on.

  4. Capability and resourcing

    Map the skills, capacity, external support, budget, and leadership attention required to sustain the intended outcome. Apply the practice with a named owner, evidence location, completion date, and exception process. Keep the control proportionate to the consequence of error and confirm that it still works after the initial implementation team has moved on.

  5. Scale readiness

    Identify which controls, processes, interfaces, and cost drivers change materially as users, transactions, geographies, or data volumes grow. Apply the practice with a named owner, evidence location, completion date, and exception process. Keep the control proportionate to the consequence of error and confirm that it still works after the initial implementation team has moved on.

  6. Review and renewal

    Set a dated review cycle and define the regulatory, market, technology, performance, or organisational changes that require earlier reassessment. Apply the practice with a named owner, evidence location, completion date, and exception process. Keep the control proportionate to the consequence of error and confirm that it still works after the initial implementation team has moved on.

  7. Decision boundary

    Define the decision this work must support, the choices that are genuinely open, and the conditions that would require escalation. Apply the practice with a named owner, evidence location, completion date, and exception process. Keep the control proportionate to the consequence of error and confirm that it still works after the initial implementation team has moved on.

  8. Stakeholder map

    Identify the accountable owner, affected operators, subject-matter reviewers, control functions, and people who will use the output. Apply the practice with a named owner, evidence location, completion date, and exception process. Keep the control proportionate to the consequence of error and confirm that it still works after the initial implementation team has moved on.

Common mistakes

  1. Treating decision boundary as implicit

    Do not assume that experienced participants share the same definition, evidence threshold, or risk tolerance. In User Research Playbook, make the decision boundary decision visible, identify its owner, and record the evidence. Mistake 1 is resolved only when the correction appears in the operating artefact, not merely in meeting notes.

  2. Treating stakeholder map as implicit

    Do not assume that experienced participants share the same definition, evidence threshold, or risk tolerance. In User Research Playbook, make the stakeholder map decision visible, identify its owner, and record the evidence. Mistake 2 is resolved only when the correction appears in the operating artefact, not merely in meeting notes.

  3. Treating current-state baseline as implicit

    Do not assume that experienced participants share the same definition, evidence threshold, or risk tolerance. In User Research Playbook, make the current-state baseline decision visible, identify its owner, and record the evidence. Mistake 3 is resolved only when the correction appears in the operating artefact, not merely in meeting notes.

  4. Treating evidence design as implicit

    Do not assume that experienced participants share the same definition, evidence threshold, or risk tolerance. In User Research Playbook, make the evidence design decision visible, identify its owner, and record the evidence. Mistake 4 is resolved only when the correction appears in the operating artefact, not merely in meeting notes.

  5. Treating operating model as implicit

    Do not assume that experienced participants share the same definition, evidence threshold, or risk tolerance. In User Research Playbook, make the operating model decision visible, identify its owner, and record the evidence. Mistake 5 is resolved only when the correction appears in the operating artefact, not merely in meeting notes.

  6. Treating architecture and integration as implicit

    Do not assume that experienced participants share the same definition, evidence threshold, or risk tolerance. In User Research Playbook, make the architecture and integration decision visible, identify its owner, and record the evidence. Mistake 6 is resolved only when the correction appears in the operating artefact, not merely in meeting notes.

  7. Treating risk and compliance as implicit

    Do not assume that experienced participants share the same definition, evidence threshold, or risk tolerance. In User Research Playbook, make the risk and compliance decision visible, identify its owner, and record the evidence. Mistake 7 is resolved only when the correction appears in the operating artefact, not merely in meeting notes.

  8. Treating economics and value as implicit

    Do not assume that experienced participants share the same definition, evidence threshold, or risk tolerance. In User Research Playbook, make the economics and value decision visible, identify its owner, and record the evidence. Mistake 8 is resolved only when the correction appears in the operating artefact, not merely in meeting notes.

Detailed field guide

Delivery sequencing during Scale

User Research Playbook should treat delivery sequencing as a working decision discipline during scale, not as a documentation exercise completed afterwards. Order work by dependency and learning value so the team can validate critical assumptions before making irreversible commitments. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 1 is complete when the decision record and supporting artefacts agree.

Vendor and partner assessment during Scale

User Research Playbook should treat vendor and partner assessment as a working decision discipline during scale, not as a documentation exercise completed afterwards. Compare external providers against explicit requirements, evidence quality, portability, support, security, and total cost. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 2 is complete when the decision record and supporting artefacts agree.

Measurement system during Scale

User Research Playbook should treat measurement system as a working decision discipline during scale, not as a documentation exercise completed afterwards. Define leading and lagging indicators, data owners, calculation rules, reporting frequency, and thresholds that trigger action. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 3 is complete when the decision record and supporting artefacts agree.

Quality assurance during Scale

User Research Playbook should treat quality assurance as a working decision discipline during scale, not as a documentation exercise completed afterwards. Set acceptance criteria, independent review points, test evidence, exception handling, and release authority before execution begins. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 4 is complete when the decision record and supporting artefacts agree.

Change management during Scale

User Research Playbook should treat change management as a working decision discipline during scale, not as a documentation exercise completed afterwards. Plan communication, training, adoption support, role changes, feedback loops, and resistance handling as delivery work. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 5 is complete when the decision record and supporting artefacts agree.

Documentation during Scale

User Research Playbook should treat documentation as a working decision discipline during scale, not as a documentation exercise completed afterwards. Maintain a durable decision record containing assumptions, sources, approvals, changes, limitations, and the current operating procedure. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 6 is complete when the decision record and supporting artefacts agree.

Scenario analysis during Scale

User Research Playbook should treat scenario analysis as a working decision discipline during scale, not as a documentation exercise completed afterwards. Test a defensible base case and named downside cases without hiding weak assumptions inside a single blended forecast. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 7 is complete when the decision record and supporting artefacts agree.

Security and resilience during Scale

User Research Playbook should treat security and resilience as a working decision discipline during scale, not as a documentation exercise completed afterwards. Design least privilege, recovery, monitoring, incident ownership, and continuity measures in proportion to the consequence of failure. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 8 is complete when the decision record and supporting artefacts agree.

Data governance during Scale

User Research Playbook should treat data governance as a working decision discipline during scale, not as a documentation exercise completed afterwards. Assign data ownership, permitted uses, quality rules, retention, lineage, access controls, and deletion responsibilities. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 9 is complete when the decision record and supporting artefacts agree.

Capability and resourcing during Scale

User Research Playbook should treat capability and resourcing as a working decision discipline during scale, not as a documentation exercise completed afterwards. Map the skills, capacity, external support, budget, and leadership attention required to sustain the intended outcome. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 10 is complete when the decision record and supporting artefacts agree.

Scale readiness during Scale

User Research Playbook should treat scale readiness as a working decision discipline during scale, not as a documentation exercise completed afterwards. Identify which controls, processes, interfaces, and cost drivers change materially as users, transactions, geographies, or data volumes grow. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 11 is complete when the decision record and supporting artefacts agree.

Review and renewal during Scale

User Research Playbook should treat review and renewal as a working decision discipline during scale, not as a documentation exercise completed afterwards. Set a dated review cycle and define the regulatory, market, technology, performance, or organisational changes that require earlier reassessment. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 12 is complete when the decision record and supporting artefacts agree.

Decision boundary during Scale

User Research Playbook should treat decision boundary as a working decision discipline during scale, not as a documentation exercise completed afterwards. Define the decision this work must support, the choices that are genuinely open, and the conditions that would require escalation. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 13 is complete when the decision record and supporting artefacts agree.

Stakeholder map during Scale

User Research Playbook should treat stakeholder map as a working decision discipline during scale, not as a documentation exercise completed afterwards. Identify the accountable owner, affected operators, subject-matter reviewers, control functions, and people who will use the output. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 14 is complete when the decision record and supporting artefacts agree.

Current-state baseline during Scale

User Research Playbook should treat current-state baseline as a working decision discipline during scale, not as a documentation exercise completed afterwards. Record the present process, cost, timing, quality, risk, and service level before proposing a future state. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 15 is complete when the decision record and supporting artefacts agree.

Evidence design during Scale

User Research Playbook should treat evidence design as a working decision discipline during scale, not as a documentation exercise completed afterwards. Specify which facts require primary evidence, how evidence will be dated, and where assumptions must be labelled instead of presented as facts. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 16 is complete when the decision record and supporting artefacts agree.

Operating model during Scale

User Research Playbook should treat operating model as a working decision discipline during scale, not as a documentation exercise completed afterwards. Clarify ownership, decision rights, hand-offs, service expectations, and the review cadence needed after implementation. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 17 is complete when the decision record and supporting artefacts agree.

Architecture and integration during Scale

User Research Playbook should treat architecture and integration as a working decision discipline during scale, not as a documentation exercise completed afterwards. Describe system boundaries, interfaces, dependencies, failure modes, and the minimum observability required to operate safely. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 18 is complete when the decision record and supporting artefacts agree.

Risk and compliance during Scale

User Research Playbook should treat risk and compliance as a working decision discipline during scale, not as a documentation exercise completed afterwards. Translate material legal, security, privacy, model, financial, and operational risks into named controls with accountable owners. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 19 is complete when the decision record and supporting artefacts agree.

Economics and value during Scale

User Research Playbook should treat economics and value as a working decision discipline during scale, not as a documentation exercise completed afterwards. Separate one-time and recurring costs, quantify benefits conservatively, and make timing, attribution, and uncertainty visible. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 20 is complete when the decision record and supporting artefacts agree.

Delivery sequencing during Operations

User Research Playbook should treat delivery sequencing as a working decision discipline during operations, not as a documentation exercise completed afterwards. Order work by dependency and learning value so the team can validate critical assumptions before making irreversible commitments. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 21 is complete when the decision record and supporting artefacts agree.

Vendor and partner assessment during Operations

User Research Playbook should treat vendor and partner assessment as a working decision discipline during operations, not as a documentation exercise completed afterwards. Compare external providers against explicit requirements, evidence quality, portability, support, security, and total cost. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 22 is complete when the decision record and supporting artefacts agree.

Measurement system during Operations

User Research Playbook should treat measurement system as a working decision discipline during operations, not as a documentation exercise completed afterwards. Define leading and lagging indicators, data owners, calculation rules, reporting frequency, and thresholds that trigger action. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 23 is complete when the decision record and supporting artefacts agree.

Quality assurance during Operations

User Research Playbook should treat quality assurance as a working decision discipline during operations, not as a documentation exercise completed afterwards. Set acceptance criteria, independent review points, test evidence, exception handling, and release authority before execution begins. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 24 is complete when the decision record and supporting artefacts agree.

Change management during Operations

User Research Playbook should treat change management as a working decision discipline during operations, not as a documentation exercise completed afterwards. Plan communication, training, adoption support, role changes, feedback loops, and resistance handling as delivery work. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 25 is complete when the decision record and supporting artefacts agree.

Documentation during Operations

User Research Playbook should treat documentation as a working decision discipline during operations, not as a documentation exercise completed afterwards. Maintain a durable decision record containing assumptions, sources, approvals, changes, limitations, and the current operating procedure. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 26 is complete when the decision record and supporting artefacts agree.

Scenario analysis during Operations

User Research Playbook should treat scenario analysis as a working decision discipline during operations, not as a documentation exercise completed afterwards. Test a defensible base case and named downside cases without hiding weak assumptions inside a single blended forecast. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 27 is complete when the decision record and supporting artefacts agree.

Security and resilience during Operations

User Research Playbook should treat security and resilience as a working decision discipline during operations, not as a documentation exercise completed afterwards. Design least privilege, recovery, monitoring, incident ownership, and continuity measures in proportion to the consequence of failure. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 28 is complete when the decision record and supporting artefacts agree.

Data governance during Operations

User Research Playbook should treat data governance as a working decision discipline during operations, not as a documentation exercise completed afterwards. Assign data ownership, permitted uses, quality rules, retention, lineage, access controls, and deletion responsibilities. For Executives, Operators, Founders, Functional leaders, the practical test is whether another accountable person can inspect the evidence, understand what was decided, and identify the next action without relying on undocumented context.

Apply this to UI UX and Product Design by starting from user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Connect each material statement to a source, owner, date, unit, and review status. Where evidence is incomplete, label the statement as an assumption, explain why it is reasonable, and define how it will be tested. This protects the transparent research programme from false precision while keeping progress possible.

The control question is whether this work changes problem selection, experience design, prioritisation, or product investment and whether the proposed action remains acceptable after considering solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement. Monitor task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. If the evidence weakens, a threshold is breached, or the scope changes, return the decision to its named owner instead of silently adjusting the method. Field note 29 is complete when the decision record and supporting artefacts agree.

Review checklist

Summary

User Research Playbook is complete when the organisation can trace a bounded question through evidence, assumptions, options, decision rights, implementation controls, measured outcomes, and a dated review. The downloadable workbook preserves that chain and should be maintained with the operating record.

Start with user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes; assess solving the wrong problem, exclusion, low adoption, delivery waste, incoherent experience, and weak measurement; measure task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion; and obtain review from product, design, research, accessibility, engineering, analytics, and customer-facing specialists as applicable. Use related Rusaka resources to deepen specialist areas without breaking the shared decision record.

Frequently asked questions

Who should use User Research Playbook?

User Research Playbook is designed for Executives, Operators, Founders, Functional leaders. The accountable decision owner should involve product, design, research, accessibility, engineering, analytics, and customer-facing specialists as applicable when the decision touches their area.

What evidence is required before starting?

Begin with user research, journey evidence, behavioural analytics, accessibility findings, support demand, and current product outcomes. Record missing evidence as an explicit gap, with an owner and a plan to resolve or test it.

How should assumptions be handled?

Label every material assumption, record its source and rationale, identify the decision it affects, test a downside, and define the trigger that requires reassessment.

How should results be measured?

Use task success, time to value, adoption, retention, accessibility, satisfaction, and outcome completion. Define calculation rules, sources, owners, frequency, segmentation, and action thresholds before implementation.

How often should this research be updated?

The scheduled frequency is every 6 months. Review sooner after a material regulatory, market, technology, security, performance, or organisational change.

Does this replace professional advice or formal approval?

No. It is an educational and implementation resource. Decisions should be reviewed by product, design, research, accessibility, engineering, analytics, and customer-facing specialists as applicable, and formal organisational approvals remain required.

Authoritative references

Download the User Research Playbook implementation workbook