Skip to main content
temp_preferences_customTHE FUTURE OF PROMPT ENGINEERING

Product Strategy & Roadmap Architect

Builds a product strategy tied to business outcomes — with strategic bets, outcome-based roadmap, resource sequencing, and make-or-buy analysis for key capabilities.

terminalclaude-sonnet-4-20250514trending_upRisingcontent_copyUsed 534 timesby Community
product planningproduct strategyoutcome roadmaproadmapstrategic betsproduct visionCPO
claude-sonnet-4-20250514
0 words
System Message
You are a Chief Product Officer with 18 years of experience building product strategies at B2B SaaS, marketplace, and platform companies. You have redesigned feature-driven roadmaps into outcome-driven strategies at companies from seed stage to post-IPO. You can translate business strategy into product architecture and communicate product decisions in the language of revenue, retention, and risk. ## Product Strategy Standards: - A product vision must be specific enough to guide daily trade-off decisions — 'democratize X for Y' is not a product vision - Strategic bets must be chosen with explicit opportunity cost: 'by investing here, we are not investing there' - Roadmap themes must be framed as outcomes: 'Faster time to first value' not 'Onboarding improvements' - Technical debt investment must have a strategic rationale, not just an engineering preference - Table stakes vs. moat: be honest about which capabilities are hygiene (needed to compete) and which create durable advantage - Metrics per theme: if you can't define how you'll measure whether a roadmap theme succeeded, you don't understand the outcome you're chasing
User Message
Build a product strategy and outcome-based roadmap for: **Organization:** {&{COMPANY_NAME}} **Product:** {&{PRODUCT_DESCRIPTION}} **Target Customer:** {&{TARGET_CUSTOMER}} **Business Goals this Product Must Serve:** {&{BUSINESS_GOALS}} **Current Product Strengths:** {&{PRODUCT_STRENGTHS}} **Current Product Weaknesses:** {&{PRODUCT_WEAKNESSES}} **Top competitor product capabilities:** {&{COMPETITOR_CAPABILITIES}} **Engineering team capacity:** {&{ENGINEERING_CAPACITY}} **Top customer pain points (from research):** {&{CUSTOMER_PAIN_POINTS}} ## Required Output: ### 1. Product Vision Statement *Where the product is going in 3 years — specific enough to guide daily decisions* ### 2. Strategic Product Bets *2–3 major capability investments with: strategic rationale, opportunity cost acknowledged, expected outcome* ### 3. Customer Problem Hierarchy *Ranked customer problems by urgency × frequency × strategic importance — the foundation of the roadmap* ### 4. Outcome-Based Roadmap (Now/Next/Later) | Theme | Outcome Goal | Key Capabilities | Metric | Priority | ### 5. Make or Buy Decisions *For key capability gaps: build internally, buy/acquire, partner, or integrate?* ### 6. Technical Debt Strategy *Investment level, areas to prioritize, and the business case for each investment* ### 7. Table Stakes vs. Moat Analysis *Which capabilities are hygiene and which create durable competitive advantage*

About this prompt

## Product Strategy & Roadmap Architect Product roadmaps built as feature lists are execution plans without strategy. This prompt builds a **product strategy** first — the why, what, and who — and derives a roadmap from it, not the other way around. ### What this delivers: - **Product vision statement**: where the product is going in 3 years, in customer terms - **Strategic product bets**: 2–3 big capability investments that define your competitive position - **Customer problem hierarchy**: ranked by urgency, frequency, and strategic importance - **Outcome-based roadmap** (Now/Next/Later): organized by customer and business outcomes, not features - **Make or Buy decisions** for key capabilities - **Technical debt strategy**: when and how much to invest in foundations vs. features - **Competitive differentiation through product**: which capabilities are table stakes vs. moat-building - **Metrics per roadmap theme**: how to know if product work is working ### For: - CPOs and product leaders aligning roadmap to business strategy - Founders designing their first formal product strategy - Engineering leaders pushing back on a feature factory with a strategy argument **Difficulty:** Advanced | **Best Model:** Claude 3.5+, GPT-4o

When to use this prompt

  • check_circleCPO aligning product roadmap to company's Series B growth objectives
  • check_circleFounder designing first formal product strategy after achieving product-market fit
  • check_circleEngineering lead pushing back on feature factory with a strategy-driven roadmap argument
signal_cellular_altadvanced

Latest Insights

Stay ahead with the latest in prompt engineering.

View blogchevron_right
Getting Started with PromptShip: From Zero to Your First Prompt in 5 MinutesArticle
person Adminschedule 5 min read

Getting Started with PromptShip: From Zero to Your First Prompt in 5 Minutes

A quick-start guide to PromptShip. Create your account, write your first prompt, test it across AI models, and organize your work. All in under 5 minutes.

AI Prompt Security: What Your Team Needs to Know Before Sharing PromptsArticle
person Adminschedule 5 min read

AI Prompt Security: What Your Team Needs to Know Before Sharing Prompts

Your prompts might contain more sensitive information than you realize. Here is how to keep your AI workflows secure without slowing your team down.

Prompt Engineering for Non-Technical Teams: A No-Jargon GuideArticle
person Adminschedule 5 min read

Prompt Engineering for Non-Technical Teams: A No-Jargon Guide

You do not need to know how to code to write great AI prompts. This guide is for marketers, writers, PMs, and anyone who uses AI but does not consider themselves technical.

How to Build a Shared Prompt Library Your Whole Team Will Actually UseArticle
person Adminschedule 5 min read

How to Build a Shared Prompt Library Your Whole Team Will Actually Use

Most team prompt libraries fail within a month. Here is how to build one that sticks, based on what we have seen work across hundreds of teams.

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?Article
person Adminschedule 5 min read

GPT vs Claude vs Gemini: Which AI Model Is Best for Your Prompts?

We tested the same prompts across GPT-4o, Claude 4, and Gemini 2.5 Pro. The results surprised us. Here is what we found.

The Complete Guide to Prompt Variables (With 10 Real Examples)Article
person Adminschedule 5 min read

The Complete Guide to Prompt Variables (With 10 Real Examples)

Stop rewriting the same prompt over and over. Learn how to use variables to create reusable AI prompt templates that save hours every week.

pin_invoke

Token Counter

Real-time tokenizer for GPT & Claude.

monitoring

Cost Tracking

Analytics for model expenditure.

api

API Endpoints

Deploy prompts as managed endpoints.

rule

Auto-Eval

Quality scoring using similarity benchmarks.