跳到正文
cccskills
免费在 GitHub 公开

outcome-roadmap

Rewrite a feature-based roadmap around the changes customers and the business should experience. The result pairs each initiative with an outcome statement, success metrics, sequencing notes, and context connecting the plan to company strategy.

中文简介正在准备中。当前显示英语简介。

原文查看原文说明

Transform an output-focused roadmap into an outcome-focused one that communicates strategic intent. Rewrites initiatives as outcome statements reflecting user and business impacts. Use when shifting to outcome roadmaps, making a roadmap more strategic, or rewriting feature lists as outcomes.

查看安装方法

适用场景

  • Turning a feature list into measurable outcomes
  • Connecting roadmap initiatives to company strategy
  • Defining success metrics for planned work
  • Reviewing quarterly priorities and dependencies

包含的文件(1)

  • SKILL.md3.5 KB

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Transform Roadmap to Outcome-Focused Format

Purpose

You are an experienced product manager helping $ARGUMENTS shift from output-focused roadmaps (which emphasize features) to outcome-focused roadmaps (which emphasize customer and business impact). This skill rewrites initiatives as outcome statements that inspire and measure what matters.

Context

Output-focused roadmaps create false precision and misalign teams around features rather than results. Outcome-focused roadmaps clarify the customer problems being solved and the business value expected, enabling flexible execution and strategic thinking.

Instructions

  1. Gather Information: If the user provides a current roadmap, read it carefully. If they mention strategy documents or company objectives, use web search to understand how the roadmap should align with broader goals.

  2. Think Step by Step:

    • For each initiative, ask: "What outcome are we trying to achieve?"
    • What customer problem are we solving?
    • What business metric will improve?
    • How will this impact the customer experience or business?
    • Is there a better, different way to achieve the same outcome?
  3. Transformation Process: For each initiative on the roadmap:

    • Identify the Output: What feature or project is planned?
    • Uncover the Outcome: Why are we building it? What changes for customers or business?
    • Rewrite as Outcome Statement: Use this format:
      Enable [customer segment] to [desired customer outcome] so that [business impact]
      
  4. Example Transformation:

    • Output (Old): Q2: Build advanced search filters, implement AI recommendations, redesign dashboard
    • Outcome (New):
      • Q2: Enable customers to find products 50% faster through intuitive discovery
      • Q2: Increase average order value by 20% through personalized AI recommendations
      • Q2: Help operators monitor all systems with 80% reduction in dashboard load time
  5. Structure Output: Present the transformed roadmap with:

    • Original initiatives listed by quarter/phase
    • Outcome statements for each initiative
    • Key metrics that will indicate success
    • Dependencies or sequencing notes
  6. Include Strategic Context: For the overall roadmap, add:

    • How outcomes align with company strategy
    • Key assumptions about customer needs
    • Flexible release windows (quarters, not specific dates)
  7. Save the Output: If substantial, save as a markdown document: Outcome-Roadmap-[year].md

Notes

  • An outcome should be testable and measurable
  • Multiple outputs may achieve one outcome; focus on the outcome, not the feature list
  • Outcome roadmaps are more resilient to change—embrace flexibility
  • If unsure what outcome a feature drives, ask: "So what?" until you reach real customer/business value

Further Reading

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

Analyze A/B test results to decide whether to launch a change, extend testing, stop, or investigate further. Check sample size, statistical significance, uncertainty ranges, and effects on other important metrics, then summarize the recommendation and next steps.

中文简介正在准备中。当前显示英语简介。

  • Checking whether an A/B test shows a meaningful difference
  • Reviewing sample size and test duration
  • Deciding whether to launch a tested change
phuryn/pm-skills2.7万2026年10月16日 更新

Organize customer feature requests into themes and rank the top three against product goals, customer value, effort, and risk. For each recommendation, explain the underlying need, possible alternatives, uncertain assumptions, and simple ways to test them.

中文简介正在准备中。当前显示英语简介。

  • Grouping customer requests into themes
  • Selecting the top three requests for product goals
  • Considering alternatives to requested features
phuryn/pm-skills2.7万2026年10月16日 更新

Compare growth options across existing and new products and markets using the Ansoff Matrix, a four-part planning framework. Assess opportunities, resources, competition, and risks, then develop market launch plans and a phased roadmap for priority options.

中文简介正在准备中。当前显示英语简介。

  • Comparing growth options for an existing business
  • Planning expansion into new regions or customer groups
  • Evaluating new products for current customers
phuryn/pm-skills2.7万2026年10月16日 更新

Choose the first customer segment for a product launch by comparing urgent needs, willingness to pay, achievable market share, and referral potential. Get scored recommendations, a priority segment, a 90-day acquisition plan, and expansion options.

中文简介正在准备中。当前显示英语简介。

  • Choosing the first customer segment for a new product
  • Focusing limited resources on a launch market
  • Comparing segments using interviews and customer feedback
phuryn/pm-skills2.7万2026年10月16日 更新

Plan low-effort experiments to check assumptions about an existing product before building a feature. Compare prototypes, A/B tests, and other methods, with a clear assumption, procedure, metric, and success threshold for each experiment.

中文简介正在准备中。当前显示英语简介。

  • Checking feature assumptions before implementation
  • Planning prototype usability tests
  • Defining metrics and success thresholds for A/B tests
phuryn/pm-skills2.7万2026年10月16日 更新

Turn a new product idea into a testable hypothesis and two or three simple experiments. Define target customers, expected actions, measurement methods, and success thresholds to assess demand through behavior such as sign-ups, pre-orders, or paid commitments.

中文简介正在准备中。当前显示英语简介。

  • Testing demand before building a new product
  • Planning landing page or waitlist experiments
  • Checking willingness to pay through pre-orders
phuryn/pm-skills2.7万2026年10月16日 更新

查看 phuryn 的全部技能

报告此技能的问题