Skip to content

Step 2 - Validate the Problem (PEV)

Purpose

Gather factual evidence to confirm whether the problem described in the PPE is real, repeatable, and observable.

This step exists to separate assumption from evidence before any assessment or prioritisation occurs.

When To Run This Step

This step is executed by a person after a valid PPE has been completed and stored in the system of record.

Run this step when:

  • A problem has been captured in a PPE
  • There is uncertainty about whether the problem actually exists or how widespread it is
  • Evidence is required before deciding whether the problem is worth solving

This step must not run if:

  • A PPE does not exist
  • The team is attempting to assess impact, priority, or solutions

Inputs (Required)

  • An approved Pain Point Entry (PPE)
  • Access to people, data, or records that can confirm or refute the problem

Prompt to Run

  • Prompt Name: Problem Evidence Validation (PEV)
  • Prompt Version: v1.0
  • Prompt Location: PEV Generator

Instruction: Run the PEV prompt using the approved PPE as the primary input.

Do not analyze causes, suggest solutions, or reinterpret the problem.

Outputs (Produced)

The step produces a Problem Evidence Validation (PEV) artifact containing:

  • A factual restatement of the problem
  • Evidence collected
  • Observations gathered
  • Affected roles or departments
  • Validation sources
  • Confidence level

The output must strictly follow the PEV template.

Artifact Storage

Store the PEV in the predefined system of record selected during setup.

  • One primary location only
  • The artifact must be referenceable
  • Ownership must be clear

Validation Rules

The PEV is valid only if:

  • All statements are factual and observable
  • No causes, solutions, or recommendations are included
  • The problem is restated without reinterpretation
  • Missing information is explicitly marked as TBD

The PEV is invalid if it:

  • Introduces analysis or opinion
  • Suggests fixes or next steps
  • Reframes the problem beyond the PPE

Invalid PEVs must be corrected before proceeding.

Decision Gate

Question: Is there sufficient factual evidence to confirm the problem exists and warrants assessment?

Outcomes:

  • Yes: Proceed to Step 3 — Assess the Problem (PAB)
  • No: Collect additional evidence or stop

No other outcomes are allowed.

Failure Modes & Anti-Patterns

  • Treating this step as analysis or root-cause investigation
  • Filling gaps with assumptions instead of marking TBD
  • Allowing opinions to be recorded as evidence
  • Skipping validation sources

If this step is rushed or polluted with interpretation, downstream assessment becomes unreliable.

Traceability

  • Previous: Step 1 — Capture the Problem (PPE)
  • Next: Step 3 — Assess the Problem (PAB)
  • Consumes: Pain Point Entry (PPE)
  • Produces: Problem Evidence Validation (PEV)

Status

  • Maturity: Stable
  • Enforced by Tooling: Planned