Turning customer feedback into a product roadmap in 6 prompts

Someone on r/PromptEngineering shared a full prompt chain that takes raw customer feedback and spits out a prioritized sprint roadmap plus a stakeholder email. I tested it. It actually works.

The original poster, u/Prestigious-Tea-6699, built a 6-step chain where each prompt hands off to the next. No jumping around. No manual copy-paste between sessions.

How the chain works

You define three variables upfront: your feedback data, sprint length, and max initiatives. Then the chain runs six sequential roles:

• Senior product analyst , cleans the data, clusters themes, scores sentiment (-1 to +1), outputs a frequency table
• Experienced product manager , picks the top 8-12 themes and proposes one initiative each with a success metric
• Cross-functional estimation panel , scores each initiative on impact and effort (1-5), calculates priority as Impact minus Effort
• Delivery lead , assigns initiatives to sprints (max 2 major per sprint), builds a Gantt view
• 🗣️ Communications specialist , writes a polished executive update under 250 words
• Reviewer , audits the full output, flags gaps, and signs off with “Roadmap package ready”

Each step ends with a confirmation question before proceeding. That pause-and-confirm pattern is actually what makes this useful. You stay in control at every handoff.

Here’s the prompt

Variable definitions:

• [FEEDBACK_DATA] = Full set of qualitative inputs including customer feedback, NPS comments, and support tickets
• [SPRINT_LENGTH] = Number of weeks per sprint (e.g., 2)
• [MAX_INITIATIVES] = Maximum initiatives to include in the roadmap (e.g., 10)

Step 1: Senior product analyst

Your task is to clean, cluster, and quantify qualitative data.

1. Parse [FEEDBACK_DATA] and remove duplicate or near-duplicate entries.
2. Tag each unique comment with: a) product area, b) theme, c) emotional tone (positive, neutral, negative).
3. Count frequency of each theme and calculate average sentiment score per theme (-1 to +1 scale).

Output a table with columns: Theme | Product Area | Frequency | Avg Sentiment. Ask “Ready for initiative ideation?” when finished.

Step 2: Experienced product manager

Generate initiatives from themes.

1. For the top 8-12 themes by Frequency and negative sentiment, propose one initiative each. If fewer than 8 themes, include all.
2. Describe each initiative in one sentence.
3. List assumed success metric(s) for each.

Output a table: ID | Initiative | Target Theme | Success Metric. Ask “Proceed to impact/effort scoring?”

Step 3: Cross-functional estimation panel

1. Assign an Impact score (1-5) based on ability to improve NPS or reduce ticket volume.
2. Assign an Effort score (1-5) where 1=very low engineering work and 5=very high.
3. Add a Priority column calculated as Impact minus Effort.

Output a table sorted by Priority DESC. Ask “Generate prioritized roadmap?”

Step 4: Delivery lead

Build a sprint roadmap.

1. Allocate initiatives into sequential [SPRINT_LENGTH]-week sprints, max 2 major initiatives per sprint; minor items (less than 3 total story-points) can be bundled.
2. For each sprint, define: Sprint Goal, Included Initiatives (IDs), Key Deliverables, Risks/Mitigations.
3. Render a simple textual Gantt where rows=sprints and columns=weeks, marking initiative IDs.

Output sections: A) Sprint Plan Table, B) Gantt View. Ask “Prepare stakeholder update copy?”

Step 5: Communications specialist

Craft an executive update.

1. Summarize overall objective in 1 sentence.
2. Highlight top 3 high-impact initiatives with expected customer outcome.
3. Call out timeline overview (number of sprints × [SPRINT_LENGTH] weeks).
4. List next steps and any asks from stakeholders.

Deliver polished prose (≤250 words) suitable for email.

Step 6: Reviewer

Review and refine. Compare all outputs against initial requirements: data cleansing, initiative list, scoring, roadmap, stakeholder copy. Confirm each section exists, follows structure, and no critical gaps remain. If gaps found, request clarification; otherwise reply “Roadmap package ready.”

Before running it, fill in your three variables:

• [FEEDBACK_DATA] , paste in your survey results, NPS comments, or support tickets
• [SPRINT_LENGTH] , 2 weeks is the standard starting point
• [MAX_INITIATIVES] , 10 keeps the roadmap tight and actionable

Why this approach actually holds up

Most people dump feedback into AI and ask “what should we build next?” That gets you a vague list with no prioritization logic behind it.

This chain does it differently. The Impact minus Effort scoring gives you a defensible priority score. When someone asks why Sprint 1 looks the way it does, you have a number to point to. That changes the conversation in planning meetings.

The sentiment analysis step is also underrated. High-frequency feedback with neutral sentiment is different from low-frequency feedback with deeply negative sentiment. Both matter, but for different reasons. The chain handles that distinction automatically.

Where to use this

• 📋 Quarterly product planning with 50+ survey responses piling up
• Post-launch feedback analysis when you need a roadmap draft fast
• Pre-investor prep when you want data-backed prioritization, not gut feel
• Customer success handoffs to product , turn ticket patterns into sprint items

One variation worth trying

Add a step zero before the chain: “You are a data quality auditor. Review [FEEDBACK_DATA] for missing context, ambiguous entries, or noise. Flag anything that would skew theme analysis. Output a clean version of the data with a brief audit summary.”

That way the analyst prompt in step one starts from cleaner inputs. Small addition, noticeably better outputs.

The full Reddit thread has more details and a few community reactions worth reading. Grab the prompt above, swap in your variables, and see what it spits out.

Transform customer feedback into actionable roadmaps. Prompt included.
by u/Prestigious-Tea-6699 in PromptEngineering