outcome-cartographer

Outcome mapping connects each roadmap deliverable to a specific business or customer metric by verifying named metrics and explicit definitions of expected behavior changes. This process identifies whether roadmap items have real success criteria or are just deliverables with due dates.

In product planning, output describes what was built, while outcome defines what changed because it was built. Detecting output vs outcome involves flagging deliverables that lack explicit definitions of expected customer or business behavior changes.

Verifying instrumentation status requires reviewing release plans to confirm the measurement mechanism for each metric already exists or is explicitly planned before launch. This ensures success criteria can actually be tracked when the deliverable ships.

Yes, outcome mapping applies to PRDs, roadmaps, release plans, and ship reviews where deliverables must be connected to customer or business behavior changes. It requires named metrics and explicit definitions of what will move for each major deliverable.

Product plans often celebrate shipping without proving impact because deliverables lack defined success criteria and instrumentation. Catching these plans requires forcing every feature to connect to a measurable outcome before launch.