outcome-roadmap

oleh phuryn

Ubah roadmap yang berfokus pada keluaran menjadi roadmap yang berfokus pada hasil untuk mengomunikasikan maksud strategis. Tulis ulang inisiatif sebagai pernyataan hasil yang mencerminkan dampak bagi pengguna dan bisnis. Gunakan saat beralih ke roadmap hasil, membuat roadmap lebih strategis, atau menulis ulang daftar fitur sebagai hasil.

npx skills add https://github.com/phuryn/pm-skills --skill outcome-roadmap
Unduh ZIPGitHub
25.7k
Coba skill iniDisponsori

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

Lebih banyak skill dari phuryn

create-prd
phuryn
Buat Dokumen Requirements Produk menggunakan template komprehensif 8 bagian yang mencakup masalah, tujuan, segmen, proposisi nilai, solusi, dan perencanaan rilis. Gunakan saat menulis PRD, mendokumentasikan requirements produk, menyiapkan spesifikasi fitur, atau meninjau PRD yang sudah ada.
prioritization-frameworks
phuryn
Panduan referensi untuk 9 kerangka kerja prioritas dengan rumus, panduan kapan digunakan, dan templat — RICE, ICE, Kano, MoSCoW, Opportunity Score, dan lainnya. Gunakan saat memilih metode prioritas, membandingkan kerangka kerja seperti RICE vs ICE, atau mempelajari cara kerja berbagai pendekatan prioritas.
strategy-red-team
phuryn
Lakukan red-team terhadap PRD, roadmap, atau strategi dengan menyerang asumsi penopangnya sebelum realitas melakukannya. Steelman setiap klaim lalu serang, rangking mode kegagalan berdasarkan dampak × kemungkinan × murahnya pengujian, dan kembalikan tes termurah serta kriteria penghentian untuk masing-masing. Gunakan saat menguji ketahanan sebuah rencana, menguji tekanan sebuah strategi, menantang asumsi, atau menyiapkan dokumen untuk tinjauan eksekutif.
pre-mortem
phuryn
Jalankan analisis risiko pre-mortem pada PRD atau rencana peluncuran. Mengategorikan risiko sebagai Tigers (masalah nyata), Paper Tigers (kekhawatiran berlebihan), dan Elephants (kekhawatiran yang tidak diungkapkan), lalu mengklasifikasikan sebagai launch-blocking, fast-follow, atau track. Gunakan saat mempersiapkan peluncuran, menguji ketahanan rencana produk, atau mengidentifikasi hal-hal yang bisa salah.