Use this skill when the user needs to plan roadmaps or initiatives around outcomes instead of features. Apply it for customer journey mapping, booster and blocker analysis, hypothesis-driven roadmaps, or converting fixed-scope planning into outcome-centered planning, even if the user does not explicitly say "journey map" or "outcomes-based planning." For defining outcomes and leading indicators themselves, prefer `outcome-thinking`. For org structure, backlog reset, and trust rebuilding, prefer `organizing-for-outcomes`. For internal transformation programs, prefer `outcomes-driven-transformation`.
