Before/after journey mapper

What CLARA will ask you for

• Programme name — your programme's name (e.g. SKYPROTECT).
• Track — the slice of the programme this artefact belongs to (workstream, capability area, feature line, etc.), or Programme-wide if it spans tracks.
• Journey scope — the journey being compared (e.g. "ICT cycle", "Handling a contradiction-class alert").
• PRD to compare against — which PRD's solution defines the AFTER column. Its Scope-module table is the AFTER vocabulary.
• Inputs — CLARA will search the programme's Confluence space for current-state journey (the before); the prd whose solution defines the after; problem-impact analysis (for the phase tags); persona (optional). You can also paste fresh material if it's not in Confluence yet.

Where the output lands

Knowledge Base/{{track}}/Before-after-journeys/{{journey-scope}} inside your programme's Confluence space.

Tips

• This artefact earns its keep two ways: as a stakeholder-facing picture of what changes, and as a coverage check. If a high-ranked problem has no "after", you've found a gap in the PRD, not a gap in this page.
• Keep the sourcing strict — BEFORE from the journey, AFTER from the PRD. The moment you write an AFTER step the PRD doesn't scope, you've started designing outside the PRD, which is the PRD generator's job.
• Step counts are a mechanism signal (handoffs removed, rebuilds avoided), not a time measurement. Cite the PRD's success metrics for the real reduction, and say so explicitly so no one reads the step delta as a benchmark.
• This is the most downstream artefact in the chain (journey → ranking → PRD → here). If the before/after won't line up, resist fixing it here — correct the upstream artefact and regenerate.