The Product Problem and Market Validation Standard: Proving Need Before Solution

Before investing in a solution, check whether the problem matters enough to the intended users and whether it can be changed. Interviews, waiting lists and prototype reactions help only when their context and limits are known. Use the evidence to proceed, narrow the scope, validate further, defer or stop.

1. The Market Connection Context

The recognisable condition is a leadership meeting in which the solution already has a name, supportive comments are repeated as proof, and delivery pressure is growing, but nobody can show who experiences the underlying problem, what they do today, what the current consequence is, or what evidence would disconfirm the proposal. The organisation may be discussing a new product, an internal platform, a service extension or a digital feature. The validation question is the same: does a defined group, in a defined context, encounter a sufficiently material problem and demonstrate enough reason to change for leadership to authorise a next evidence or investment gate?

The protected path is Market need and investment → adopted, supportable value. The complete mechanism is:

Affected person and context → observed current behaviour → bounded problem claim → consequence worth changing → credible alternative behaviour → evidenced commitment → owned next decision → adopted, supportable value

Value can become stuck when research recruits only enthusiasts, questions invite agreement, reported preferences substitute for observed behaviour, market totals are mistaken for reachable need, current workarounds are ignored, or a product concept becomes the frame before the problem is understood. These weaknesses can expose revenue, margin, cost, capacity, retention, risk, investment efficiency or service value, but the exposure remains REQUIRES VALIDATION until an accepted baseline, population, unit, period and causal mechanism exist.

This method does not prove a universal market or promise product-market fit. It creates a controlled body of evidence for one leadership decision. The decision must name its deadline or decision event, the scope it can authorise, and the evidence that could produce any of these dispositions: validate, change, handoff, defer, stop or retain as context. “Proceed” is only permitted when it names the next bounded gate; it never means build, procure, launch or scale by default.

Use this standard when the underlying problem, affected population, urgency, current alternative, willingness or authority to change remains materially uncertain. Do not use it as a substitute for usability testing of a known design, technical feasibility diligence, a full investment case, market definition for legal or competition purposes, or post-launch adoption analysis. The Evidence Artefact Decision: Prototype, Proof of Concept, Concierge Test or MVP governs which prototype, proof of concept, concierge test or MVP is proportionate to a named uncertainty. The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook governs build, buy, configure, integrate or stop diligence. The Software Investment Business Case: Scope, Total Cost, Risk and Operating Economics owns the full lifecycle business case. The Product Adoption, Operability and Scale Gate: Proving Value after Launch owns post-launch adoption, operability and scale.

Scope and required outcome

The scope is one problem-and-market validation decision, with explicit affected groups, situations, geography or service boundary, current behaviours and alternatives. It includes research design, recruitment, ethical and data controls, existing evidence, observation or interviews, behavioural and commitment evidence, commercial and operating context, contradiction analysis, problem classification, a bounded validation portfolio and an executive disposition.

Material exclusions are production delivery, procurement award, solution architecture, final pricing, legal market definition, statutory assurance, launch approval and a forecast of adoption or commercial return. Any legal, privacy, accessibility, safety, employment, competition, financial or security conclusion requires the organisation's qualified authority.

Expected outputs are a signed validation charter; an authority, population and research plan; a traceable evidence register; a problem-and-alternative model; a validation claim ledger; an evidence-threshold and decision portfolio; accepted measurement definitions; and a dated executive decision with dissent, limitations, ownership and restart or closure conditions. These are decision artefacts, not evidence that a product will succeed.

A decision-grade problem claim

A problem claim is usable only when it states:

The claim is not validated because several people use similar words. It becomes decision-fit when independent evidence supports the relevant parts, contrary cases are visible, sampling and method limitations are accepted, and the pre-agreed threshold for the named decision is met. A statement may be VERIFIED as something a participant said while the prevalence, cause, urgency and future action remain INFERRED or REQUIRES VALIDATION.

2. The Leadership vs. Delegation Boundary

The reader recognises that defensible validation requires research design, behavioural evidence, alternatives, commercial tests, operating context and explicit evidence thresholds.

When the organisation can lead internally

An internal team can run the standard when the sponsor permits a stop decision; a qualified research lead can separate learning objectives from sales or solution advocacy; source owners can provide controlled access; current and likely users, non-users and relevant accessibility needs can be represented; commercial and operating owners can challenge the value claim; and an independent senior participant can test whether the conclusion exceeds the evidence.

A narrower specialist is sufficient when the uncertainty is already isolated. Examples include an experienced researcher for a recruitment or interview design, a statistician for a population inference, an accessibility specialist for inclusive participation, a pricing researcher for a bounded commitment question, or privacy counsel for the research-data basis. The specialist must not be asked to convert a narrow result into a whole-market conclusion.

When independent leadership is justified

An independent senior partner is proportionate when a founder, executive, delivery team or supplier is committed to the solution; research, sales, service and market evidence disagree; the relevant population is hard to reach or vulnerable; business-to-business buying authority is distributed; the decision crosses product, commercial, operations, finance, data and technology; or leadership needs a retained record that another team can challenge and continue.

An external partner may design and facilitate the method, but it cannot approve its own evidence, accept organisational risk, manufacture favourable participants or make later product delivery the only successful outcome. It must disclose research-recruitment, product-build, supplier, platform, referral and implementation interests.

Stop, narrow and escalation conditions

Stop or re-charter when the decision cannot change; participants cannot give meaningful informed agreement; the research purpose or data handling lacks authority; access would expose people or confidential information; a protected or affected group is excluded without an explicit limitation; incentives are contingent on favourable sentiment; the sample cannot support the intended inference; a test creates material service, financial or reputational exposure outside the approved boundary; or no owner exists for the decision that follows.

Escalate disputed representation to the research and affected-person authority; disputed personal-data use to the information officer or qualified privacy reviewer; accessibility exclusion to the organisational accessibility authority; uncertain market or competition conclusions to qualified legal/economic reviewers; economic assumptions to finance; and product investment to the named economic buyer. Record the issue, evidence, limitation, temporary containment, authority and disposition.

Questions for evaluating a provider

1. Which leadership decision and evidence threshold will the validation change?
2. How will you keep the problem frame independent of our preferred solution?
3. How will you represent current users, likely users, non-users, excluded people and relevant accessibility needs?
4. Which methods address behaviour, consequence, alternatives, changeability and commitment, and what can each method not establish?
5. How will recruitment source, incentive, prior relationship and selection bias remain visible?
6. How will observed fact, statement, interpretation, assumption, constraint and evidence gap be kept separate?
7. What contrary evidence will cause you to narrow, change, defer or stop?
8. How will privacy, consent or other lawful basis, retention, access and withdrawal be governed by our qualified authority?
9. How will commercial commitment be tested without coercion, deceptive scarcity or an unauthorised transaction?
10. How will existing alternatives and doing nothing be compared without turning the research into a concept preference test?
11. Which conclusion requires a larger or specialist quantitative design?
12. What artefacts and source records will remain usable by a different team?
13. Where does The Product Problem and Market Validation Standard: Proving Need Before Solution stop, and which later guide owns the next decision?

3. The Step-by-Step Execution Standard

Run the sequence against one decision. Separate materially different populations, use contexts, buying authorities or consequences instead of averaging them into one market story.

Step 01: Charter the validation decision

Purpose and decision served Turn a product proposal into a falsifiable problem-and-market decision that can legitimately end in validate, change, handoff, defer, stop or retain as context.

Accountable owner Product Sponsor or Founder who controls the next resource decision.

Delegated lead and contributors Product Leader or research lead, with commercial, service, operations, finance, data, technology and affected-person representation.

Preconditions, inputs and access The proposal, prior discovery, known commitments, decision forum, decision event, available evidence and a sponsor willing to record a contrary outcome.

Actions

1. Write the decision as “Should we authorise [bounded next action] for [defined group and context] because [problem claim], subject to [evidence and guardrail conditions]?”
2. State the proposed solution separately and mark it PROPOSED rather than embedding it in the problem.
3. Define scope, exclusions, permitted dispositions, resource ceiling, decision event and the evidence that could reverse the sponsor’s current view.
4. List existing commitments, sunk work and political or supplier interests that may distort the research.
5. Create stable claim, evidence, participant-group, test, decision, measure and gate IDs.

Evidence to retain Signed charter, proposal record, prior-evidence index, commitment and conflict log, decision-forum terms and version history.

Decision or scoring rule Proceed only if one bounded decision can change and stop. There is no composite score; an unfalsifiable or already-made decision is stopped or reframed.

Output and template T01 Validation Charter, Authority and Population Plan.

Acceptance gate Pass when the sponsor accepts the problem claim as unproven, the six dispositions and at least one credible disconfirming condition.

Leadership checkpoint The economic buyer confirms what this work may and may not authorise.

Human control point Only the named sponsor can accept the charter and resource boundary.

Failure modes and safeguards Solution-led wording, ceremonial approval and sunk-cost defence are controlled by separate proposal/problem fields, an independent challenger and a visible stop route.

Change, stop or escalation condition Stop if contrary evidence cannot alter scope, option or funding; escalate competing decisions to the economic buyer.

Handoff to the next step Send the accepted charter and conflicts to the authority design.

Step 02: Establish authority, ethics and decision rights

Purpose and decision served Protect participants, organisational information and the independence of the decision before any collection begins.

Accountable owner Product Sponsor, with the organisation’s research, information and affected-person authorities.

Delegated lead and contributors Research lead, privacy or information specialist, accessibility authority, security owner, legal adviser where required and evidence custodians.

Preconditions, inputs and access Accepted charter, intended methods, participant categories, proposed data, recruitment channels, vendors, observers and storage locations.

Actions

1. Assign decision, method, participant-protection, access, source-accuracy, analysis, dissent and stop rights by name or accountable role.
2. Document research purpose, permitted use, lawful or consent basis as determined by qualified authority, minimum data, access, retention, deletion and withdrawal handling.
3. Identify vulnerable circumstances, power imbalances, employee/customer dependencies, accessibility needs, safety risks and incentive effects.
4. Approve observer conduct, recording, transcription, supplier processing, anonymisation and incident escalation.
5. Separate the research team from commercial pressure to produce a favourable outcome.

Evidence to retain Authority matrix, ethics and data decision, participant information materials, access decisions, processor controls, risk assessment and escalation map.

Decision or scoring rule No participant or source activity starts unless every mandatory authority is approved or an authorised narrower method is recorded.

Output and template Authority, ethics, access and retention rows in T01.

Acceptance gate Pass only when participant protection, evidence use and stop authority are explicit and feasible.

Leadership checkpoint The sponsor accepts excluded methods and populations where safe authority cannot be established.

Human control point Qualified organisational authorities, not the delivery partner, decide privacy, legal, accessibility, employment, security and safety sufficiency.

Failure modes and safeguards Generic consent, excessive collection, uncontrolled observers and supplier-owned evidence are controlled by purpose-specific records, minimisation and audit access.

Change, stop or escalation condition Stop the affected activity on missing authority, withdrawal failure, unintended exposure or an uncontainable power imbalance.

Handoff to the next step Give the approved boundaries to population and evidence planning.

Step 03: Define populations, contexts and exclusions

Purpose and decision served Specify whose problem can be inferred from the work and prevent convenient participants from becoming “the market”.

Accountable owner Product Leader.

Delegated lead and contributors Research lead, customer/service owner, commercial owner, accessibility specialist, data analyst and frontline representatives.

Preconditions, inputs and access Charter, authority decisions, customer and service records, relevant external statistics, current segmentation and known channels.

Actions

1. Define eligible affected people or organisations by actual condition, context and behaviour, not by assumed enthusiasm for the product.
2. Map decision-makers, users, buyers, beneficiaries, blockers, non-users, assisted users and service staff where their roles differ.
3. Identify contexts that could change the problem: channel, location, device, capability, frequency, risk, organisation size, workflow or buying arrangement.
4. State exclusions, unreachable groups, likely recruitment bias and the exact inference each limitation prevents.
5. Define purposive qualitative coverage and any separate quantitative population design without inventing a universal sample threshold.

Evidence to retain Population frames, eligibility rules, context map, inclusion requirements, exclusion rationale, coverage plan and inference limits.

Decision or scoring rule Proceed when every intended conclusion maps to a population and method capable of supporting it; otherwise narrow the conclusion or commission specialist design.

Output and template Population, context, recruitment and limitation rows in T01.

Acceptance gate Pass when no material group is silently represented by another group and exclusions are decision-visible.

Leadership checkpoint Leadership accepts which market or stakeholder claims the work cannot make.

Human control point Research and affected-person authorities approve recruitment and inclusion boundaries.

Failure modes and safeguards Customer-only samples, internal proxies and digital-only recruitment are controlled by role mapping, source diversity and explicit exclusions.

Change, stop or escalation condition Re-charter if the relevant population differs materially from the proposal or cannot be reached safely.

Handoff to the next step Use the accepted frames to convert assumptions into evidence questions.

Step 04: Build the claim and evidence plan

Purpose and decision served Match each material uncertainty to evidence capable of changing the decision.

Accountable owner Product Leader.

Delegated lead and contributors Research lead, analyst, commercial and finance owners, service/workflow owner and specialist reviewers.

Preconditions, inputs and access Charter, authority model, population frames, proposal assumptions, existing evidence and decision event.

Actions

1. Decompose the proposed opportunity into claims about affected condition, frequency or recurrence, current behaviour, consequence, alternatives, changeability, buying authority and commitment.
2. Classify each existing claim as VERIFIED, INFERRED, PROPOSED or REQUIRES VALIDATION with source and limitation.
3. Choose methods by question: observation for behaviour, interviews for context and meaning, records for operating patterns, controlled choices for preference, and authorised commitment tests for action.
4. Predefine what each method can establish, what it cannot establish and which contradictory result changes the route.
5. Sequence the smallest safe evidence actions first and prevent later solution artefacts from contaminating problem discovery.

Evidence to retain Claim ledger, assumptions, method rationale, source plan, acceptance thresholds, contradiction rules and evidence sequence.

Decision or scoring rule Every decision-critical claim requires an owner, planned source, method-fit statement and explicit disposition rule; gaps remain visible rather than receiving a default score.

Output and template Source, observation, participant statement, interpretation, alternative, contrary-case, gap, assumption, constraint and finding rows in T02 Problem, Behaviour and Alternative Evidence Register.

Acceptance gate Pass when the plan can disconfirm the proposed problem and distinguishes learning evidence from market inference.

Leadership checkpoint The sponsor confirms that unfavourable evidence will change or stop the next action.

Human control point The research lead approves method fitness; specialised statistical, legal or pricing inferences require their relevant reviewer.

Failure modes and safeguards Method theatre and confirmatory questions are controlled by pre-registered decision rules and a challenge review before collection.

Change, stop or escalation condition Change the plan when a method cannot support the intended inference or the required evidence is disproportionate to the decision.

Handoff to the next step Issue approved source requests and current-state observation instructions.

Step 05: Examine current behaviour and operating evidence

Purpose and decision served Establish what affected people and the surrounding system do now before asking them to react to a solution.

Accountable owner Customer, service or workflow owner.

Delegated lead and contributors Researcher, analyst, frontline staff, process owner, product representative and authorised data custodians.

Preconditions, inputs and access Approved evidence plan, source permissions, behavioural definitions, eligible contexts, system records and observation protocol.

Actions

1. Observe or reconstruct the current task, trigger, sequence, workarounds, assistance, waiting, abandonment, rework and downstream consequences.
2. Examine authoritative service, support, sales, transaction, workflow or usage records without assuming recorded absence means the problem is absent.
3. Record formal and informal alternatives, including spreadsheets, messaging, manual coordination, delegated labour, delay and doing nothing.
4. Capture each item in its native unit, period, population and context; preserve missingness, detection limits and source dependence.
5. Separate directly observed behaviour from reported explanation and researcher interpretation.

Evidence to retain Observation records, event definitions, source extracts, workflow evidence, alternative inventory, exception samples and access logs.

Decision or scoring rule Treat a current-behaviour claim as usable only within the observed or authoritative scope; broader recurrence and cause require additional evidence.

Output and template Current-behaviour, source, event, alternative and limitation rows in T02.

Acceptance gate Pass when each material current-state claim traces to a source and contrary or missing evidence is visible.

Leadership checkpoint Operating leaders confirm source meaning and whether the observed period was atypical.

Human control point Source owners verify definitions and access; affected-person authorities protect observation boundaries.

Failure modes and safeguards Analytics-as-intent, support logs as prevalence and workflow exceptions as universal behaviour are controlled by native definitions and bounded claims.

Change, stop or escalation condition Pause on unauthorised data, ambiguous event meaning or observation that could harm service or participants.

Handoff to the next step Carry current behaviours and alternatives into contextual research.

Step 06: Conduct problem-centred research

Purpose and decision served Understand the conditions, meanings, consequences and trade-offs behind current behaviour without teaching participants the preferred answer.

Accountable owner Research authority or Product Leader where formally delegated.

Delegated lead and contributors Qualified researcher, note-taker, participant host, accessibility support and approved observers.

Preconditions, inputs and access Approved recruitment, participant information, evidence questions, discussion or observation guide, consent/lawful-basis decision and secure recording arrangements.

Actions

1. Recruit against the approved condition and contexts, recording source, incentive, relationship and exclusions.
2. Ask participants to reconstruct recent actual situations, decisions, artefacts, alternatives and consequences before discussing any concept.
3. Probe what triggered action, what they tried, what they tolerated, who influenced the decision and what made change difficult.
4. Capture contrary cases, non-action, successful current alternatives and reasons the proposed problem may not matter.
5. Debrief promptly; tag observations, statements and interpretations separately; remove unnecessary personal or confidential information.

Evidence to retain Recruitment record, participant IDs, approved materials, consent/authority evidence, session notes, artefact references, observer notes, debrief and deletion schedule.

Decision or scoring rule No single session validates a market claim. A finding advances only when its evidence type, recurrence within the bounded sample, contexts, contrary cases and inference limit are explicit.

Output and template Participant, session, observation, statement, interpretation and contradiction rows in T02.

Acceptance gate Pass when research covers the approved contexts sufficiently for the planned qualitative decision and no material ethics or data breach remains unresolved.

Leadership checkpoint Selected decision-makers observe under the research protocol and acknowledge evidence that challenges the proposal.

Human control point The research lead controls questioning, participant welfare, evidence interpretation and session termination.

Failure modes and safeguards Leading questions, courtesy agreement, memory reconstruction and stakeholder domination are controlled through neutral sequencing, recent examples, independent moderation and verbatim evidence.

Change, stop or escalation condition Stop a session on withdrawal, distress, exposure or protocol breach; redesign recruitment when the sample systematically misses a material context.

Handoff to the next step Send bounded findings and alternative behaviours to consequence and commitment testing.

Step 07: Test consequence, alternatives and credible commitment

Purpose and decision served Determine whether the problem matters enough to alter behaviour, resource or priority under realistic constraints.

Accountable owner Product Sponsor with Commercial or Service Owner.

Delegated lead and contributors Research lead, product and commercial specialists, finance, procurement where relevant, operations and participant-protection authority.

Preconditions, inputs and access Bounded problem findings, current alternatives, authorised test boundary, realistic choice conditions and accepted harm safeguards.

Actions

1. Define the commitment appropriate to the context: time, data, workflow change, internal sponsorship, budget process, trial participation or another observable action.
2. Compare the proposed change with current alternatives and no action using the same problem frame and disclosed constraints.
3. Distinguish an expression of interest from completion of the agreed action, and record who held authority to commit.
4. Test consequences in the organisation’s accepted units only where baselines and permissions exist; otherwise record the economic evidence gap.
5. Retain refusals, delays, partial actions, assistance and reasons without recoding them as positive demand.

Evidence to retain Test protocol, offer or choice materials, authority record, action events, refusals, alternative choices, exception log, financial basis and participant safeguards.

Decision or scoring rule A commitment claim passes only for the defined action, actor, context and period. It cannot be generalised to purchase, adoption, retention or market size without a design capable of supporting that inference.

Output and template Commitment, consequence, alternative-choice and exception rows in T03 Validation Claim and Contradiction Ledger.

Acceptance gate Pass when the chosen test is ethical, realistic enough for the question, traceable and interpreted within its limits.

Leadership checkpoint Commercial and finance owners accept what the test does and does not say about value.

Human control point The sponsor and participant-protection authority approve any real commitment, transaction or operational exposure.

Failure modes and safeguards Fake doors, deceptive scarcity, unauthorised prices and vanity sign-ups are controlled by transparent materials, genuine opt-out, authority and event definitions.

Change, stop or escalation condition Stop a test that misleads participants, creates unowned obligation or exceeds the authorised exposure.

Handoff to the next step Bring behaviour, research and commitment evidence into reconciliation.

Step 08: Reconcile evidence and contradictions

Purpose and decision served Create one traceable view of what is known without flattening different methods into a false score.

Accountable owner Product Leader.

Delegated lead and contributors Research lead, analyst, source owners, commercial and operating representatives, and independent challenger.

Preconditions, inputs and access All retained evidence, method notes, population frames, claim IDs, proof statuses, source limitations and contradiction rules.

Actions

1. Link every material claim to individual evidence records rather than slide summaries.
2. Compare evidence by population, context, timing, method and dependence before treating apparent agreement as corroboration.
3. Record contradictions as first-class rows, including plausible explanations and the additional evidence that could distinguish them.
4. Separate observed fact, single-source statement, corroborated interpretation, assumption, constraint and evidence gap.
5. Reclassify claims using VERIFIED, INFERRED, PROPOSED and REQUIRES VALIDATION; preserve previous versions and dissent.

Evidence to retain Claim-evidence links, source relationship map, contradiction ledger, proof-status history, analysis notes and dissent record.

Decision or scoring rule No claim advances because of volume alone. It must meet its pre-agreed evidence threshold, and any unresolved contradiction capable of reversing the decision triggers validation or a narrower claim.

Output and template Evidence-link, contradiction, reconciliation and proof-status rows in T03.

Acceptance gate Pass when every decision-critical claim is supported, bounded, disputed or explicitly unresolved, never silently assumed.

Leadership checkpoint Decision owners review the strongest contrary evidence before seeing the recommendation.

Human control point Named source and method owners approve meaning; the executive retains decision authority.

Failure modes and safeguards Quote counting, duplicate-source corroboration and majority voting are controlled by source identity, method fitness and documented challenge.

Change, stop or escalation condition Reopen collection when a material contradiction is resolvable and decision-relevant; stop when further evidence cannot change the disposition.

Handoff to the next step Use the reconciled claims to classify the problem and market evidence.

Step 09: Classify problem and market fitness

Purpose and decision served Decide which parts of the problem are real enough, consequential enough and changeable enough for the current leadership question.

Accountable owner Product Sponsor.

Delegated lead and contributors Product Leader, research lead, commercial and finance owners, service/workflow owner and independent challenger.

Preconditions, inputs and access Reconciled evidence, decision thresholds, exclusions, market/context boundary and competing explanations.

Actions

1. Assess each problem claim against five separate tests: affected condition, observed behaviour, material consequence, current-alternative limitation and credible reason to change.
2. Classify it as accepted for this decision, validate before use, retain as context, reject as unsupported or retire as no longer relevant.
3. State whether the evidence concerns a user need, an organisational problem, a buying condition or a wider market inference; do not merge them.
4. Identify contexts where the claim does not hold and whether these create a different segment or invalidate the proposition.
5. Record the smallest unresolved uncertainty that could still reverse the route.

Evidence to retain Problem-classification record, threshold tests, context exceptions, rejected claims, dissent and unresolved-uncertainty register.

Decision or scoring rule All five tests must pass for an accepted problem claim, unless a named authority records a bounded exception. A failed material test produces validate, change, defer or stop, not an averaged pass.

Output and template Finding, classification, exception and uncertainty rows in T03.

Acceptance gate Pass when each claim has one human disposition, evidence basis, scope, limitation and expiry.

Leadership checkpoint The economic buyer accepts which claims may influence investment and which may not.

Human control point Only the named decision owner may accept a claim for decision use; specialists cannot self-approve it.

Failure modes and safeguards Composite scores and attractive narratives are controlled by non-compensating tests and retained rejected evidence.

Change, stop or escalation condition Stop the current product route when the core problem fails and no proportionate alternative problem remains.

Handoff to the next step Pass accepted and unresolved claims into the validation-option portfolio.

Step 10: Design the smallest decision-changing validation portfolio

Purpose and decision served Choose proportionate next evidence actions for the uncertainties that remain, including the option to stop research.

Accountable owner Product Sponsor.

Delegated lead and contributors Product Leader, researcher, commercial, operations, technology, finance and risk specialists.

Preconditions, inputs and access Classified claims, unresolved uncertainties, evidence costs and risks, decision event and adjacent-guide boundaries.

Actions

1. Rank uncertainties by their ability to reverse the decision, not by ease of testing.
2. Compare no further work, desk evidence, additional contextual research, behavioural observation, a commercial commitment test and an evidence-artefact handoff under the Evidence Artefact Decision.
3. Define the claim, method, population, authority, output, pass/change/stop rule and expiry for each candidate action.
4. Remove actions whose result would not change a decision or whose exposure exceeds the value of learning.
5. Assign the correct downstream owner without treating the validation portfolio as implementation authority.

Evidence to retain Uncertainty ranking rationale, candidate evidence actions, rejected tests, dependencies, exposures, owners and downstream guide mapping.

Decision or scoring rule Select only actions with a material decision use, valid method, human owner, acceptable exposure and explicit stop condition; otherwise decide with the stated uncertainty or stop.

Output and template Option, test, threshold, risk and handoff rows in T03.

Acceptance gate Pass when every authorised action resolves one named uncertainty and no action silently commissions a product.

Leadership checkpoint The sponsor accepts the resource and risk ceiling and which uncertainty will remain.

Human control point Applicable research, financial, technical and affected-person authorities approve their parts of each test.

Failure modes and safeguards Research backlog growth and prototype-first thinking are controlled by decision value, explicit rejections and The Evidence Artefact Decision: Prototype, Proof of Concept, Concierge Test or MVP separation.

Change, stop or escalation condition Stop evidence collection when the next activity cannot change the disposition or cannot be run safely and validly.

Handoff to the next step Translate accepted claims and tests into measures and expiry controls.

Step 11: Define measures, thresholds and expiry

Purpose and decision served Make evidence acceptance, later observation and claim retirement repeatable rather than dependent on enthusiasm.

Accountable owner Product Sponsor and named benefit or service owner.

Delegated lead and contributors Product Leader, research and analytics leads, finance, source-system owners and risk authorities.

Preconditions, inputs and access Accepted claim classifications, validation portfolio, source definitions, operating context and review events.

Actions

1. Define learning, leading, operating, commercial-outcome and guardrail measures separately.
2. For every measure record numerator, denominator, unit, population, period, exclusions, source, owner, cadence and attribution limits.
3. Set decision-specific thresholds before observing results; use “baseline required” where no accepted comparison exists.
4. Define claim expiry, refresh triggers and what material context change invalidates comparison.
5. Add guardrails for participant welfare, accessibility, privacy, service quality, financial exposure and false-positive commitment.

Evidence to retain Measurement contracts, source approvals, baseline decisions, threshold rationale, guardrail definitions and expiry schedule.

Decision or scoring rule A measure is accepted only when its definition can be reproduced and a named human response exists for pass, change, hold or stop.

Output and template T04 Executive Validation Decision and Review Register.

Acceptance gate Pass when all decision-critical measures have complete definitions, owners, sources and response rules.

Leadership checkpoint Finance and operating owners accept commercial and service definitions; the sponsor accepts the threshold consequences.

Human control point Metric and source owners approve computability; risk authorities approve guardrails.

Failure modes and safeguards Vanity metrics, retrospective thresholds and proxy drift are controlled by predefinition, versioning and source-owner acceptance.

Change, stop or escalation condition Do not use a measure when its source or population cannot support the decision; commission a baseline or narrow the claim.

Handoff to the next step Assemble the evidence, measures and alternatives for executive disposition.

Step 12: Make and record the executive disposition

Purpose and decision served Close the validation question with a bounded human decision and no implied implementation authority.

Accountable owner Economic Buyer or Product Sponsor named in the charter.

Delegated lead and contributors Product Leader presents; research, commercial, finance, operations, technology and risk owners challenge within their authority.

Preconditions, inputs and access Validation charter, accepted and rejected claims, contrary evidence, unresolved uncertainties, options, measures, exposures and recommendation.

Actions

1. Present the problem claim, current behaviour, alternatives, consequence, commitment evidence and limitations before the recommended route.
2. Present the strongest disconfirming evidence, excluded populations, unresolved uncertainties and conflicts of interest.
3. Compare validate, change, handoff, defer, stop and retain-as-context dispositions against the chartered rule.
4. Record selected disposition, reasons, rejected alternatives, dissent, accepted exposure, resource boundary, owner and next decision event.
5. State explicitly that The Product Problem and Market Validation Standard: Proving Need Before Solution does not authorise production build, procurement, launch or scale.

Evidence to retain Decision paper, presentation record, attendee authority, questions, dissent, signed disposition, resource approval and unauthorised-boundary statement.

Decision or scoring rule The named executive selects one disposition for each material claim and one bounded next route. Silence or meeting attendance is not approval.

Output and template Decision, dissent, resource, boundary and next-gate rows in T04.

Acceptance gate Pass when the decision, evidence basis, limitations, owner, next gate and stop conditions are all signed and traceable.

Leadership checkpoint The economic buyer states what has been authorised and what remains prohibited.

Human control point Only the authorised executive makes the disposition; no automated score or provider recommendation substitutes for it.

Failure modes and safeguards Conditional decisions disguised as approval are controlled by one explicit disposition, written conditions and no silent defaults.

Change, stop or escalation condition Defer when authority is absent; validate or change when reversible uncertainty is material; stop when the problem or next route fails.

Handoff to the next step Transfer only the authorised evidence package and preserve closure records for rejected routes.

Step 13: Transfer ownership, review and retire evidence

Purpose and decision served Keep validation evidence usable, bounded and current after the executive meeting.

Accountable owner Product Sponsor or receiving decision owner.

Delegated lead and contributors Product Leader, evidence custodian, research lead, source owners, records manager and receiving guide owner.

Preconditions, inputs and access Signed disposition, evidence inventory, measure definitions, retention decisions, participant obligations, next-gate charter and closure requirements.

Actions

1. Package stable IDs, source references, methods, populations, proof statuses, limitations, contradictions, measures, decisions and dissent.
2. Separate shareable findings from restricted participant data and enforce approved access, retention, withdrawal and deletion actions.
3. Brief the receiving owner on what is accepted, unresolved, expired, prohibited and capable of changing the next decision.
4. Schedule event-based reviews for material market, user, alternative, policy, service, pricing or operating change.
5. Renew, change, validate, retain as context, retire or close each active claim at review; record new questions under a new charter.

Evidence to retain Handover acceptance, controlled evidence index, access and deletion log, review record, claim lifecycle, change decisions and closure certificate.

Decision or scoring rule Handover passes only when the receiving owner can locate and interpret each decision-critical record and accepts the prohibited boundaries.

Output and template Handover, review, lifecycle, deletion, change, stop and closure rows in T04.

Acceptance gate Pass when ownership, access, expiry, review and closure are accepted; otherwise hold the next gate.

Leadership checkpoint The sponsor confirms benefit ownership or closes the opportunity and releases reserved resources.

Human control point The receiving owner accepts responsibility; qualified information authorities approve retention and deletion completion.

Failure modes and safeguards Orphaned repositories, stale claims and selective summaries are controlled by stable IDs, expiry, access review and signed receipt.

Change, stop or escalation condition Suspend downstream use when evidence expires, access is withdrawn, a material contradiction appears or ownership is lost.

Handoff to the next step Close The Product Problem and Market Validation Standard: Proving Need Before Solution or open a separately authorised The Build, Buy, Configure, Integrate or Stop Decision: An Executive Technology Investment Playbook, The Evidence Artefact Decision: Prototype, Proof of Concept, Concierge Test or MVP, The Software Investment Business Case: Scope, Total Cost, Risk and Operating Economics or The Product Opportunity Sprint: An Executive Standard for Build, Buy, Test or Stop Decisions decision using only the accepted package.

4. The Evidence & Measurement Checklist

Preflight and authority

• The validation decision names one bounded next action and can end in change or stop. Evidence: signed validation charter. Owner: Product Sponsor.
• The proposed solution is separate from the unproven problem claim. Evidence: proposal and problem records. Owner: Product Leader.
• Decision, method, evidence, participant-protection and stop rights are assigned. Evidence: authority matrix. Owner: Product Sponsor.
• Existing delivery, supplier and executive commitments are disclosed. Evidence: commitment and conflict register. Owner: Economic Buyer.
• Scope, exclusions, decision event and prohibited implementation boundary are accepted. Evidence: charter acceptance record. Owner: Product Sponsor.

Evidence access and quality

• Every material claim has a source, method, population, period, owner and limitation. Evidence: claim and evidence register. Owner: Research Lead.
• Existing behavioural and operating sources retain their native definitions. Evidence: source-definition records. Owner: Source Owners.
• Source dependence and duplicated evidence are explicitly recorded. Evidence: source relationship map. Owner: Evidence Analyst.
• Missing, contradictory and inaccessible evidence remains visible. Evidence: contradiction and gap ledger. Owner: Product Leader.
• Market-wide inference is withheld unless the research design supports it. Evidence: inference-limit approval. Owner: Research Authority.

Method execution

• Recruitment matches approved affected conditions and contexts. Evidence: recruitment reconciliation. Owner: Research Lead.
• Problem-centred research precedes exposure to the preferred solution. Evidence: session protocol and sequence log. Owner: Research Lead.
• Current behaviour, alternatives, assistance and non-action are recorded. Evidence: behaviour and alternative register. Owner: Service Owner.
• Statements, observations and researcher interpretations use separate record types. Evidence: coded evidence export. Owner: Research Lead.
• Commitment tests use a pre-approved action and decision rule. Evidence: commitment-test protocol. Owner: Product Sponsor.

Governance, privacy, security and risk

• Participant information and evidence use follow qualified organisational authority. Evidence: research data and ethics decision. Owner: Information Authority.
• Only data necessary for accepted research questions is collected. Evidence: data-minimisation review. Owner: Research Lead.
• Access, storage, supplier processing, retention and deletion are controlled. Evidence: data handling register. Owner: Information Authority.
• Accessibility and support needs are addressed in recruitment and sessions. Evidence: inclusion plan and session adjustments. Owner: Accessibility Authority.
• Withdrawal, distress, incident and test-exposure stop routes are operable. Evidence: rehearsed escalation record. Owner: Participant-Protection Authority.

Deliverables and acceptance

• The problem claim identifies person, context, behaviour, consequence and evidence boundary. Evidence: accepted problem claim. Owner: Product Sponsor.
• Every current alternative, including doing nothing, is considered. Evidence: alternative inventory. Owner: Product Leader.
• Every accepted finding links to evidence and contrary cases. Evidence: validation claim ledger. Owner: Evidence Analyst.
• Every rejected or retired claim retains a reason and source history. Evidence: claim lifecycle record. Owner: Product Leader.
• The validation portfolio addresses only decision-changing uncertainties. Evidence: approved validation portfolio. Owner: Product Sponsor.

Measurement

• Learning, leading, operating, commercial and guardrail measures are separated. Evidence: measurement contract set. Owner: Metric Owner.
• Each measure defines unit, population, period, exclusions and source. Evidence: measure-definition review. Owner: Analytics Lead.
• Baselines are accepted or explicitly marked baseline required. Evidence: baseline decision log. Owner: Finance or Service Owner.
• Thresholds and human responses were set before result review. Evidence: versioned threshold approval. Owner: Product Sponsor.
• Attribution limits and concurrent changes accompany outcome evidence. Evidence: outcome interpretation record. Owner: Benefit Owner.

Decision and handover

• The executive reviewed the strongest contrary evidence before deciding. Evidence: decision agenda and evidence pack. Owner: Product Sponsor.
• One disposition is recorded for every material claim. Evidence: signed executive validation decision. Owner: Economic Buyer.
• Rejected alternatives, dissent and accepted exposure are retained. Evidence: decision and dissent log. Owner: Governance Owner.
• The next owner accepted evidence, limitations and prohibited boundaries. Evidence: handover receipt. Owner: Receiving Owner.
• No The Product Problem and Market Validation Standard: Proving Need Before Solution record implies build, procurement, launch or scale authority. Evidence: boundary check. Owner: Product Sponsor.

Review, change and stop controls

• Every active claim has an expiry or material-change trigger. Evidence: claim lifecycle schedule. Owner: Product Leader.
• New populations, contexts or alternatives trigger an inference review. Evidence: change-control record. Owner: Research Authority.
• Withdrawal and retention obligations remain actionable after handover. Evidence: access and deletion audit. Owner: Information Authority.
• Evidence collection stops when another activity cannot change the decision. Evidence: stop decision. Owner: Product Sponsor.
• Closed or retired claims cannot silently re-enter a later business case. Evidence: closure and reuse-control record. Owner: Governance Owner.

Topic-specific measurement contract

Measure A: Decision-critical claim coverage

Measure B: Observed problem-condition evidence by context

Measure C: Credible commitment completion

Measure D: Current alternative displacement evidence

Measure E: Problem-to-valued-outcome transition

Measure F: Material participant or validation guardrail breaches

Evidence classifications used in this guide

Retain observed fact, participant statement, corroborated interpretation, assumption, evidence gap and constraint as separate engagement evidence types. Verification that words were spoken does not verify their explanation, prevalence or predictive value.

Sources and proof boundaries

• Abrasim validation sequence, problem-fitness tests and disposition model: PROPOSED Abrasim working methodology. It structures evidence and decisions; it is not proof of need, market size, willingness to pay, product-market fit, adoption or return.
• GOV.UK Service Manual: User research in discovery: VERIFIED official guidance at the 25 August 2026 source cut-off. It supports researching likely users, current behaviour, barriers, support and existing data before planning or building. Its public-service setting does not establish a private organisation's market conclusion.
• GOV.UK Service Manual: Plan user research for your service: VERIFIED official guidance at the source cut-off. It supports explicit research questions, participant groups, suitable methods, rounds and team involvement. Any example participant numbers are method- and context-dependent and are not imported as an Abrasim universal threshold.
• GOV.UK Service Manual: Finding participants for user research: VERIFIED official guidance at the source cut-off. It supports recruiting actual or likely users, inclusive coverage, explicit criteria and privacy care. It does not by itself make a sample statistically representative.
• GOV.UK Service Manual: Managing user research data and participant privacy: VERIFIED official guidance at the source cut-off. It supports purpose-specific information, minimisation, controlled access, consent records, retention and deletion. Organisation-specific lawful basis and compliance require its qualified authority.
• ICC/ESOMAR International Code on Market, Opinion and Social Research and Data Analytics 2025: VERIFIED international professional code at the source cut-off. It supports transparent, responsible research and confidence in collection and conclusions. Applicability and organisational implementation require qualified review.
• W3C WAI: Involving Users in Evaluating Web Accessibility: VERIFIED W3C guidance updated in 2024. It supports involving users with disabilities while warning against generalising from a few people and recommends combining user evaluation with standards review. It does not certify accessibility or replace WCAG conformance evaluation.
• Information Commissioner's Office: A guide to the data protection principles: VERIFIED official UK regulatory guidance at the source cut-off. Purpose limitation, data minimisation, storage limitation, security and accountability inform research controls; the guidance notes ongoing updates and does not constitute an Abrasim legal opinion.
• US Federal Trade Commission: Consumer Reviews and Testimonials Rule questions and answers: VERIFIED official US regulator guidance at the source cut-off. It illustrates why incentives tied to favourable sentiment and undisclosed incentives are unsafe evidence practices. Jurisdiction and applicability require qualified legal review.

Working files

• Validation Charter, Authority and Population Plan supports Steps 01–03.
• Problem, Behaviour and Alternative Evidence Register supports Steps 04–06.
• Validation Claim and Contradiction Ledger supports Steps 07–10.
• Executive Validation Decision and Review Register supports Steps 11–13.

The Leadership Audit Working Pack remains the shared governance layer. The Product Problem and Market Validation Standard: Proving Need Before Solution adds population, recruitment, participant, research-session, behaviour, alternative, problem-claim, contradiction, commitment-test, classification, validation-option and claim-lifecycle records. Keep one material evidence item per row, preserve stable IDs and separate claims, evidence, measures, decisions, gates and reviews.