Skip to content

Step 3 - Assess the Problem (PAB)

Purpose

Summarise why the validated problem matters by capturing business impact, urgency, and strategic relevance.

This step exists to support a clear advance / defer / stop decision before any planning or design work begins.

When To Run This Step

This step is executed by a person after a problem has been:

  • Captured in a PPE
  • Validated with evidence in a PEV

Run this step when:

  • There is sufficient evidence that the problem exists
  • A prioritisation or advancement decision is required
  • The organisation needs clarity on impact and urgency

This step must not run if:

  • The PEV is incomplete or unvalidated
  • The team is attempting to define solutions, scope, or effort

Inputs (Required)

  • Approved Pain Point Entry (PPE)
  • Approved Problem Evidence Validation (PEV)

Prompt to Run

  • Prompt Name: Problem Assessment Brief (PAB)
  • Prompt Version: v1.0
  • Prompt Location: PAB Generator

Instruction: Run the PAB prompt using the approved PPE and PEV as inputs.

Follow the prompt instructions exactly. Do not introduce solutions, requirements, estimates, or interpretations beyond what the user provides.

Outputs (Produced)

The step produces a Problem Assessment Brief (PAB) containing:

  • Restated problem summary
  • Evidence summary
  • Business impact (financial, operational, customer)
  • Cost of inaction
  • Strategic importance
  • Urgency assessment
  • Overall recommendation

The output must strictly follow the PAB template.

Artifact Storage

Store the PAB 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 PAB is valid only if:

  • All content is factual and derived from user-provided information
  • Evidence aligns with the PEV
  • Impact and urgency are stated without solution bias
  • No effort estimates, requirements, or designs are introduced

The PAB is invalid if it:

  • Introduces solutions or preferred approaches
  • Reinterprets or expands the problem
  • Assigns effort, cost, or timelines

Invalid PABs must be revised before proceeding.

Decision Gate

Question: Is this problem sufficiently important and urgent to justify entering Project Planning?

Outcomes:

  • Yes: Proceed to Stage 2 — Project Planning (Step 4: POM)
  • No: Defer or close the problem

No other outcomes are allowed.

Failure Modes & Anti-Patterns

  • Treating this step as justification for a preferred solution
  • Inflating impact to force prioritisation
  • Mixing evidence with opinion
  • Skipping strategic alignment

If this step is rushed or politicised, downstream planning will be misaligned.

Traceability

  • Previous: Step 2 — Validate the Problem (PEV)
  • Next: Stage 2 — Project Planning (POM)
  • Consumes: PPE, PEV
  • Produces: Problem Assessment Brief (PAB)

Status

  • Maturity: Stable
  • Enforced by Tooling: Planned