Building and Sharing a Roadmap Workflow

How to get there: Set up a roadmap board in Settings → Boards (separate page). View your roadmap by clicking it under Boards in the sidebar.

Learn how to transform customer feedback into a public roadmap that keeps your customers informed about what you're building and shows your product direction transparently.

What is a Roadmap in ProductLift?

A roadmap in ProductLift is a public-facing view of your product plans, showing customers what features you're planning, building, and have recently completed. Unlike traditional product roadmaps locked in spreadsheets, ProductLift roadmaps are dynamic, transparent, and directly connected to customer feedback.

This guide walks you through the complete journey from prioritizing feedback to sharing a beautiful public roadmap that builds customer trust and reduces support inquiries.

The Complete Roadmap Journey

Feedback Prioritization → Roadmap Planning → Status Tracking → Public Sharing → Customer Updates

Step 1: Review and Prioritize Collected Feedback

Before building a roadmap, you need to decide which feedback to commit to building.

Access Your Feedback Board:

  • Navigate to your main Feedback Board
  • Review all submitted and approved posts
  • Look for patterns in votes, comments, and customer segments

[Screenshot: Feedback board showing list of posts sorted by votes with vote counts, status badges, and category labels]

Use Prioritization Frameworks:

ProductLift offers multiple ways to prioritize feedback:

RICE Scoring (Reach, Impact, Confidence, Effort):

  • Navigate to Prioritization → RICE
  • Score each post on four factors:
    • Reach: How many customers will this affect? (1-10)
    • Impact: How much will it improve their experience? (0.25-3)
    • Confidence: How sure are you about reach/impact? (0-100%)
    • Effort: How many person-months to build? (0.5-20)
  • ProductLift calculates RICE score automatically
  • Sort by RICE score to see highest-priority items

[Screenshot: RICE prioritization interface showing posts with reach, impact, confidence, effort inputs and calculated scores]

ICE Scoring (Impact, Confidence, Ease):

  • Navigate to Prioritization → ICE
  • Score on three factors (1-10 scale each)
  • Faster than RICE for quick prioritization
  • Sort by ICE score

Impact/Effort Matrix:

  • Navigate to Prioritization → Matrix
  • Visual quadrant view:
    • Quick Wins (High Impact, Low Effort) - Build these first
    • Major Projects (High Impact, High Effort) - Plan carefully
    • Fill-Ins (Low Impact, Low Effort) - Nice-to-haves
    • Time Sinks (Low Impact, High Effort) - Avoid these
  • Drag posts to position them on the matrix
  • Export matrix as image for stakeholder presentations

[Screenshot: Impact/Effort matrix with posts distributed across four quadrants, color-coded by priority]

AI Prioritization:

  • Navigate to Prioritization → AI Prioritization
  • ProductLift AI analyzes posts based on your Product Vision
  • AI considers: votes, comments, voter segments, strategic fit, urgency signals
  • Winners podium displays top 3 AI-recommended priorities
  • Review AI reasoning and adjust as needed

See Using Prioritization Methods and AI Prioritization for detailed guides.

Analyze by Customer Segments:

Weight priorities by customer value:

  • Filter by high-MRR voters (use the MRR filter in the post list filter sidebar)
  • Sort by "Total Voter MRR" to see revenue impact
  • Review enterprise customer requests separately
  • Balance broad appeal (vote count) with customer value (MRR)

[Screenshot: Feedback board with segment filters showing MRR range and plan type filters applied]

Select Features for Roadmap:

After prioritization, select 10-20 posts to commit to:

  • Top-voted features with broad customer demand
  • High-value customer requests (enterprise, strategic accounts)
  • Quick wins from Impact/Effort matrix
  • Strategic features aligned with product vision
  • Bug fixes or technical debt customers are tracking

Step 2: Create or Configure Your Roadmap Board

Set Up Roadmap Board:

If you haven't already created a roadmap board during onboarding:

  • Navigate to Settings → Boards
  • Click "Create Board"
  • Configure:
    • Name: "Roadmap" (or "What We're Building", "Product Plans")
    • Type: Roadmap
    • Icon: Calendar or map icon
    • Visibility: Public (so customers can view) or Members Only

[Screenshot: Board creation form with Roadmap type selected, name input, icon picker, and visibility options]

Configure Roadmap Statuses:

Map statuses to your roadmap workflow:

  • Navigate to Settings → Statuses
  • Ensure you have roadmap-appropriate statuses:
    • Planned - Committed features we're going to build
    • In Progress - Currently in development
    • Testing - In QA or beta testing
    • Ready to Ship - Done, awaiting release
    • Released - Shipped (usually moves to Changelog)
  • Assign these statuses to your Roadmap board

[Screenshot: Status management showing statuses with "Roadmap" board checkboxes checked for Planned, In Progress, Testing, Released]

Roadmap Visibility Settings:

Control who can see your roadmap:

  • Public - Anyone can view (recommended for transparency)
  • Members Only - Logged-in users only
  • Group-Restricted - Specific user groups (e.g., beta testers, enterprise customers)
  • Admin Only - Internal roadmap for team planning

Step 3: Promote Posts from Feedback Board to Roadmap

Move Features to Roadmap:

Once you've prioritized features, move them to your roadmap by changing their status.

Single Post Method:

  • Open a post from your Feedback Board
  • Click "Change Status"
  • Select "Planned" (or your chosen roadmap status)
  • Optionally add a comment: "Great idea! We're adding this to our roadmap for Q2."
  • Save changes

[Screenshot: Post detail view with status dropdown open, showing "Planned" being selected, and comment field below]

Bulk Operation Method:

  • On Feedback Board, select multiple posts (checkboxes)
  • Click "Bulk Actions" → "Change Status"
  • Choose "Planned" status
  • Optionally enable "Notify followers" to send update emails
  • Apply to all selected posts

[Screenshot: Bulk actions panel showing 8 posts selected, status dropdown with "Planned" selected, and "Notify followers" checkbox]

See Bulk Post Operations for advanced bulk management.

Automatic Notifications:

When you move posts to roadmap:

  • All voters and followers receive email notification
  • Email says "Good news! We're building this feature"
  • Customizable email template with your branding
  • Followers automatically subscribe to future status updates

[Screenshot: Email notification example showing "We're building your requested feature" with post details and roadmap link]

Step 4: Organize Roadmap by Status and Timeline

Kanban Board View:

Organize your roadmap visually using Kanban board:

  • Navigate to your Roadmap board
  • Click "Board View" or "Kanban View"
  • See columns for each status: Planned | In Progress | Testing | Ready | Released
  • Drag and drop posts between columns to update status

[Screenshot: Kanban board showing five columns with posts as cards, drag-and-drop in action from "Planned" to "In Progress"]

Kanban Workflow:

As you work on features:

  1. Planned column: Features committed for upcoming quarters
  2. In Progress column: Currently in active development
  3. Testing column: In QA, beta testing, or staging
  4. Ready to Ship column: Complete, awaiting deployment
  5. Released column: Shipped (then moves to Changelog)

Drag posts between columns as progress happens. Each move triggers notifications to followers.

See Kanban Board Management for detailed board features.

Timeline View:

Organize roadmap by quarters or months:

  • Switch to "Timeline View"
  • Assign target dates or quarters to posts
  • View roadmap as Gantt-style timeline
  • Helpful for communicating "when" not just "what"

[Screenshot: Timeline view showing posts organized by Q1 2026, Q2 2026, Q3 2026 with horizontal bars indicating duration]

Add Roadmap Context:

Enhance posts with roadmap-specific information:

  • Target Date: Set expected release quarter/month
  • Progress Updates: Add comments with development progress
  • Internal Notes: Use internal comments for team coordination
  • Linked Posts: Link related features being built together

Step 5: Track Development Progress

Update Status Regularly:

Keep customers informed by updating status as you make progress:

Weekly or Bi-Weekly Updates:

  • Review roadmap in team meeting
  • Move posts to next status when progress happens
  • Add comment with progress update: "We've completed the backend API and are now working on the UI"
  • Followers receive update notifications

Progress Transparency:

Customers appreciate knowing:

  • When you start work (Planned → In Progress)
  • When features are in testing (In Progress → Testing)
  • When features are ready (Testing → Ready to Ship)
  • When features ship (Ready → Released)

Internal Team Coordination:

Use internal comments for team-only notes:

  • Technical blockers or dependencies
  • Resource allocation discussions
  • Architecture decisions
  • Risk assessment

Internal comments don't appear on public roadmap but help team collaborate.

[Screenshot: Post with both public comment "We're working on the mobile version first" and internal comment (lock icon) "Need to refactor auth system first - 2 week delay"]

Step 6: Share Roadmap Publicly with Customers

Make Roadmap Public:

Share your roadmap so customers know what's coming:

Direct Portal Link:

  • Share your roadmap URL: https://yourcompany.productlift.com/roadmap
  • Add link to your app's navigation or footer
  • Include in onboarding emails for new customers
  • Link from support documentation

Embedded Roadmap Widget:

Embed roadmap directly on your website:

  • Navigate to Settings → Widgets → Roadmap Widget
  • Customize widget appearance (colors, layout)
  • Copy embed code:

<div id="productlift-roadmap"></div>
<script>
  window.ProductLiftRoadmap = {
    workspace: 'yourcompany',
    board: 'roadmap',
    view: 'kanban',  // or 'timeline', 'list'
    statuses: ['planned', 'in-progress', 'testing']  // which statuses to show
  };
</script>
<script src="https://app.productlift.com/roadmap-widget.js" async></script>

[Screenshot: Embedded roadmap widget showing Kanban board with three columns on a company website]

See Roadmap Widgets for widget customization options.

Email Announcements:

Announce roadmap updates via email:

  • Send quarterly roadmap newsletter
  • Highlight newly planned features
  • Celebrate shipped features
  • Link to public roadmap for full details

Roadmap Visibility Best Practices:

  • Be transparent: Show both plans and progress
  • Set expectations: Use "Planned" not "Committed" for tentative items
  • Explain delays: Update followers if timelines shift
  • Show progress: Regular updates build trust even if shipping takes time
  • Balance detail: Share enough to inform, not so much to overwhelm

Step 7: Keep Customers Updated on Progress

Automatic Status Change Notifications:

ProductLift automatically notifies followers when status changes:

Planned → In Progress:

  • Email: "We've started working on [Feature Name]"
  • Builds excitement and shows you're delivering

In Progress → Testing:

  • Email: "We're testing [Feature Name] - almost ready!"
  • Optional: Invite followers to beta test

Testing → Released:

  • Email: "We shipped [Feature Name]!"
  • Link to changelog for details

[Screenshot: Email template for status change notification with feature details, new status, and link to post]

Customize Notification Emails:

  • Navigate to Settings → Email Templates
  • Edit status change notification template
  • Add your branding, tone, and custom messaging
  • Include links to help docs or demo videos

See Follower Notifications for email customization.

Manual Progress Updates:

Add comments to posts for detailed updates:

  • "We've completed the API integration and are now building the UI"
  • "Testing revealed a performance issue - we're optimizing before release"
  • "Shipped to 10% of users for beta testing - release to all users next week"

Comments notify all followers and appear on public post.

Roadmap Changelog Integration:

When you ship features:

  • Change status to "Released"
  • Post automatically appears on Changelog board
  • Write changelog entry highlighting what shipped
  • Link changelog in "We shipped it!" email to followers

This closes the feedback loop completely.

Step 8: Manage Roadmap Over Time

Regular Roadmap Reviews:

Schedule recurring roadmap planning sessions:

Monthly:

  • Review progress on In Progress items
  • Move completed items to Released → Changelog
  • Add newly prioritized items to Planned
  • Adjust timeline expectations

Quarterly:

  • Major roadmap refresh
  • Re-prioritize based on new feedback and business goals
  • Communicate roadmap updates to customers
  • Archive old released items from roadmap view

Handle Roadmap Changes:

Be transparent when plans change:

Delayed Features:

  • Update post with comment explaining delay
  • Adjust expected timeline
  • Followers receive notification of update
  • Honest communication builds trust

Cancelled Features:

  • Change status to "Won't Build" or "On Hold"
  • Explain reasoning in comment (strategic shift, technical constraints, deprioritized)
  • Notify followers with explanation
  • Be open to reconsidering in the future

Added Features:

  • As new priorities emerge, add to Planned
  • Explain why new feature was prioritized
  • Balance responding to urgent needs with roadmap consistency

Real-World Example: Building a Public Roadmap

Scenario: You want to show your SaaS customers what you're building next to reduce churn and build trust.

Month 1 - Prioritization:

  • Review 156 feedback posts collected over 3 months
  • Run RICE scoring on top 30 posts
  • Analyze by customer segment (Enterprise vs. SMB requests)
  • Select 12 features for Q2 roadmap

Week 1 - Roadmap Setup:

  • Create Roadmap board (public visibility)
  • Configure statuses: Planned, In Progress, Testing, Released
  • Move 12 prioritized posts to "Planned" status
  • 1,247 voters receive "We're building this!" emails

Month 2-4 - Development:

  • Update Kanban board weekly in team standup
  • Move features: Planned → In Progress (4 features start development)
  • Add progress comments: "Backend complete, working on UI"
  • Followers receive updates, engagement stays high

Month 3 - First Shipment:

  • Complete "Dark Mode" feature
  • Move status: Testing → Released
  • 156 voters receive "We shipped it!" email
  • Create changelog entry and help doc
  • Move to next feature

Month 5 - Roadmap Refresh:

  • Review completed items (5 features shipped)
  • Move completed items to Changelog board
  • Add 6 new prioritized features to Planned
  • Send quarterly roadmap newsletter to all customers

Results:

  • Churn decreased 15% (customers see you're building what they want)
  • Support tickets asking "When will you add X?" decreased 40%
  • Customer trust and engagement increased
  • Product team has clear priorities aligned with customer needs

Tips and Best Practices

Prioritization:

  • Use multiple frameworks (RICE + customer value analysis)
  • Don't just build most-voted features - consider strategic fit
  • Balance "quick wins" with "major projects"
  • Review priorities quarterly as market changes

Roadmap Structure:

  • Keep "Planned" to 10-20 items (don't overcommit)
  • Show 3-6 items "In Progress" at a time (shows focus)
  • Use clear status names customers understand
  • Avoid date-specific promises unless confident

Communication:

  • Update status weekly to show progress
  • Add comments with context, not just status changes
  • Be honest about delays and challenges
  • Celebrate shipped features to close the loop

Visibility:

  • Make roadmap public to build trust (unless competitive reasons prevent)
  • Embed roadmap widget on your website
  • Link roadmap from in-app navigation
  • Include roadmap link in onboarding emails

Maintenance:

  • Review roadmap weekly in team meetings
  • Archive shipped features quarterly
  • Re-prioritize quarterly based on feedback
  • Keep roadmap fresh and realistic

Common Challenges and Solutions

Challenge: Too Many Features to Commit To

  • Solution: Be selective - roadmap shows focus, not wishlist. Use "Under Review" status for feedback not yet committed.

Challenge: Customers Expect Dates, Not Just Statuses

  • Solution: Use quarters (Q2 2026) rather than specific dates. Add "Target: Q2" in post description.

Challenge: Features Taking Longer Than Expected

  • Solution: Update timeline transparently with comment. Customers appreciate honesty over silence.

Challenge: Stakeholders Want Private Roadmap

  • Solution: Create two roadmaps - public (high-level, sanitized) and internal (detailed, with sensitive features). Use board visibility settings.

Challenge: Customers Asking "When Will You Build [Not On Roadmap Feature]?"

  • Solution: Keep feature on Feedback Board with "Under Review" status. Comment explaining prioritization and that you're monitoring votes.

Challenge: Roadmap Becomes Stale

  • Solution: Set recurring calendar reminder for weekly roadmap review. Make status updates part of sprint ceremonies.

Use Case Workflows:

Detailed Roadmap Features:

Prioritization:

Customer Communication: