Skip to content

Step 4 - Process Outcome Map (POM)

Purpose

Define the high-level business process and identify the business outcomes that make up the initiative.

This step exists to ensure the initiative is framed around outcomes and workflow, not solutions or requirements.

When To Run This Step

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

  • Captured (PPE)
  • Validated with evidence (PEV)
  • Assessed and approved to advance (PAB)

Run this step when:

  • The problem has been approved to move into Project Planning
  • The team needs a shared understanding of the business process involved
  • Outcomes must be defined before estimating effort or scope

This step must not run if:

  • Stage 1 artifacts are incomplete or unapproved
  • The team is attempting to define solutions, requirements, or technical designs

Inputs (Required)

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

Prompt to Run

  • Prompt Name: Process Outcome Map (POM) Generator
  • Prompt Version: v1.0
  • Prompt Location: POM Generator

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

Follow the prompt instructions exactly. Do not introduce solutions, requirements, or technical detail.

Outputs (Produced)

The step produces a single Process Outcome Map (POM) that describes the end-to-end business process and identifies multiple outcomes as logical milestones along that process.

  • Linked summaries of PPE, PEV, and PAB
  • High-level workflow steps covering the full process (30,000 ft view)
  • Distinct outcomes representing meaningful business milestones
  • Mapping of workflow steps to outcomes
  • A scope decision (GO / NO-GO / REVISE)

A single POM may contain multiple workflows as long as they are part of the same end-to-end business process and contribute toward the same overall objective.

The output must strictly follow the POM template.

Artifact Storage

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

  • Workflow steps describe business actions, not technical implementation
  • Outcomes represent meaningful business milestones, not steps
  • Each outcome groups one or more workflow steps
  • No solutions, requirements, or designs are included
  • A clear scope decision is recorded

The POM is invalid if it:

  • Collapses steps and outcomes into the same concept
  • Introduces features, tools, or systems
  • Reads like a requirements document

Invalid POMs must be revised before proceeding.

Decision Gate

Question: Is the business process and set of outcomes sufficiently defined to estimate effort and scope?

Outcomes:

  • Yes: Proceed to Step 5 — Estimate the Effort (Outcome Estimates)
  • No: Revise the POM or stop

No other outcomes are allowed.

Failure Modes & Anti-Patterns

  • Treating outcomes as steps
  • Defining too many micro-steps
  • Using technical or solution-oriented language
  • Skipping the scope decision

If this step is rushed or polluted with solutioning, all downstream planning will be compromised.

Traceability

  • Previous: Stage 1 — Problem Management (PAB)
  • Next: Step 5 — Estimate the Effort (Outcome Estimates)
  • Consumes: PPE, PEV, PAB
  • Produces: Process Outcome Map (POM)

Status

  • Maturity: Stable
  • Enforced by Tooling: Planned