Mapping priorities to capabilities

A priority only becomes measurable once it is connected to the capabilities it depends on. That connection is what lets Pytheus answer whether you are ready.

Proposed and confirmed

Pytheus proposes mappings for you, based on the template you started from and the shape of the outcome. Proposed mappings are a suggestion and are labeled as such.

Confirming a mapping is a person saying yes, this capability genuinely matters to this outcome. Until someone confirms it, it stays a suggestion, and the readiness picture makes that distinction visible rather than presenting a guess as a fact.

This matters more than it sounds. A readiness number built on unreviewed guesses is worse than no number, because it looks authoritative. Confirming is quick, and it is the step that makes the rest trustworthy.

Setting the required level

A mapping also carries the maturity level that outcome requires. Not every priority needs every capability at the top of the scale: shipping a product to a regulated market demands more of your evidence capabilities than an internal efficiency goal does. Setting the required level honestly is what keeps the gap analysis meaningful.

Removing a mapping

If a proposed mapping is wrong, remove it. A priority connected to capabilities it does not actually depend on will report gaps that are not real, and people stop trusting the surface quickly after that.

Next: What it takes to close the gap.