Skip to content

Step 6 - Project Initiative Package (PIP)

Purpose

Bundle all approved Stage 2 planning artifacts into a single, authoritative package that defines the approved initiative scope for Strategic Domain Design.

This step exists to record what has been approved, what has been deferred, and whether the initiative is authorised to proceed.

When To Run This Step

This step is executed by a person after:

  • A valid Process Outcome Map (POM) has been completed
  • Outcome Estimates (OE) have been produced for each outcome
  • Prioritisation and funding discussions have occurred

Run this step when:

  • Leadership approval is required to proceed into Stage 3
  • Scope must be formally locked
  • Deferred outcomes must be explicitly recorded

This step must not run if:

  • Stage 2 artifacts are incomplete or inconsistent
  • Outcomes or estimates are still under debate

Inputs (Required)

  • Approved Process Outcome Map (POM)
  • Approved Outcome Estimates (OE)
  • Leadership or sponsor input for approval decision

Prompt to Run

  • Prompt Name: Project Initiative Package (PIP)
  • Prompt Version: v1.0
  • Prompt Location: PIP Generator

Instruction: Run the PIP prompt using the approved POM and OE as inputs.

Follow the prompt instructions exactly. Do not alter, reinterpret, or extend the content of POM or OE.

Outputs (Produced)

The step produces a Project Initiative Package (PIP) containing:

  • Initiative name and summary
  • Included Stage 2 artifacts
  • Approved outcomes for Phase 1
  • Deferred outcomes
  • Estimated delivery window
  • Key risks and dependencies
  • Formal Go / No-Go decision

The output must strictly follow the PIP template.

Artifact Storage

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

  • All content is derived directly from POM, OE, and user-provided approval details
  • Approved and deferred outcomes are explicitly listed
  • No new outcomes, risks, or dependencies are introduced
  • The approval decision is clearly recorded

The PIP is invalid if it:

  • Reinterprets planning artifacts
  • Introduces solutions, requirements, or designs
  • Omits the approval decision

Invalid PIPs must be corrected before proceeding.

Decision Gate

Question: Is the initiative formally approved to proceed into Strategic Domain Design?

Outcomes:

  • Approved: Proceed to Stage 3 — Strategic Domain Design
  • Deferred: Pause or revisit Stage 2
  • Rejected: Close the initiative

No other outcomes are allowed.

Failure Modes & Anti-Patterns

  • Treating the PIP as a restatement instead of a commitment record
  • Allowing scope creep at the point of approval
  • Failing to document deferred outcomes
  • Proceeding without explicit authorisation

If this step is rushed or politicised, downstream design will be built on unstable ground.

Traceability

  • Previous: Step 5 — Estimate the Effort (OE)
  • Next: Stage 3 — Strategic Domain Design
  • Consumes: POM, OE
  • Produces: Project Initiative Package (PIP)

Status

  • Maturity: Stable
  • Enforced by Tooling: Planned