Feature Launch Workflow

How to get there: Manage post statuses from All Posts in the sidebar. Add changelog entries by opening a post and tagging comments for changelog.

The complete lifecycle of a feature in ProductLift, from customer idea to shipped product with documentation, showing how every piece of ProductLift works together seamlessly.

What is the Feature Launch Lifecycle?

This workflow demonstrates how ProductLift integrates feedback collection, prioritization, roadmap planning, development tracking, release announcements, and documentation into a single connected system. Rather than managing these processes in separate tools, ProductLift guides a feature through its entire journey while keeping customers informed at every step.

This is ProductLift's most powerful capability: closing the complete feedback loop from "customer has idea" to "customer uses shipped feature and reads documentation."

The Complete Feature Journey

Customer Idea → Feedback Post → Validation → Prioritization → Roadmap → Development → Testing → Release → Changelog → Knowledge Base → Customer Notification

Step 1: Customer Submits an Idea

The Journey Begins:

A customer has a need and submits feedback through your ProductLift widget or portal.

Example Scenario:
Sarah, a user of your project management SaaS, notices that she spends significant time switching between light and dark modes on different devices. She submits a feature request through your feedback widget.

Submission Details:

• Title: "Add Dark Mode Support"
• Description: "I work late hours and find the bright interface straining on my eyes. A dark mode option would be incredibly helpful for night work sessions. I've seen this in Notion and Linear and it's a game-changer."
• Category: UI/UX
• Attachments: Screenshot showing mockup of dark mode interface

[Screenshot: Feedback widget submission form filled out with "Dark Mode Support" title, detailed description, UI/UX category selected]

The post is submitted and enters your moderation queue.

Step 2: Moderation and Approval

Review the Submission:

Your team reviews the incoming feedback in the moderation queue.

• Navigate to Moderation → Pending Posts
• Review Sarah's "Dark Mode Support" post
• Check if it's a duplicate (search existing posts)
• Assess quality and clarity

Moderation Decision:

Option 1 - AI Auto-Approval:
If you have AI moderation enabled, the post is automatically approved based on:

• Clear, well-written description
• Specific use case provided
• Relevant category selected
• No spam or inappropriate content detected

Option 2 - Manual Approval:
Team member reviews and approves:

• Click "Approve"
• Assign to "New" or "Under Review" status
• Add tags: "ui", "accessibility", "high-demand"
• Optionally assign category if not already set

[Screenshot: Moderation queue showing Sarah's post with Approve button highlighted, tags being added, and status dropdown showing "Under Review"]

The post is now live on your feedback board and Sarah receives a confirmation email.

See Post Moderation for detailed moderation workflow.

Step 3: Validation Through Community Engagement

Customers Vote and Comment:

Once published, other customers discover the post and engage:

Week 1-4:

• 47 customers vote for dark mode
• 12 customers leave comments with use cases:
  • "Yes! I need this for accessibility reasons"
  • "Dark mode is essential for developer tools"
  • "Would reduce eye strain significantly"
• 3 customers provide design mockups in comments
• Post shows strong validation signals

[Screenshot: Post detail view showing 47 votes, 12 comments with user avatars, and status badge "Under Review"]

You Add Clarifying Questions:

As product team, you ask questions to understand requirements:

• Comment: "Thanks for the feedback! Quick questions: Should dark mode be automatic (based on system settings) or manual toggle? Any specific areas of the UI that are most important?"
• Customers respond with preferences and context
• Discussion helps refine requirements

Segment Analysis:

Review who's voting to understand customer value:

• Filter voters by segment: 18 are Enterprise customers ($5k+ MRR)
• 6 are trial users considering conversion
• Top voters include strategic accounts
• High revenue impact potential

[Screenshot: Voter list showing user avatars with MRR badges: "$12,000/mo", "$8,500/mo", "$5,000/mo" next to Enterprise customer names]

This validation data helps prioritization.

See User Segments for segment analysis.

Step 4: Prioritization and Planning

Prioritize Using Framework:

After 1-2 months of feedback collection, you run quarterly prioritization.

RICE Scoring:
Navigate to Prioritization → RICE and score "Dark Mode Support":

• Reach: 8/10 (affects many users, accessibility need)
• Impact: 2.5/3 (significantly improves user experience)
• Confidence: 90% (clear demand, well-understood feature)
• Effort: 3 person-months (UI overhaul, CSS variables, testing)

RICE Score: (8 × 2.5 × 0.9) / 3 = 6.0 (High Priority)

[Screenshot: RICE scoring interface showing Dark Mode post with reach, impact, confidence, effort inputs and calculated score of 6.0]

Compare with Other Requests:

• Dark Mode: RICE 6.0, 47 votes, $287k total voter MRR
• Slack Integration: RICE 5.2, 63 votes, $156k total voter MRR
• Mobile App: RICE 4.1, 89 votes, $312k total voter MRR

Decision: Dark Mode ranks high on RICE and has strong enterprise customer demand. Add to Q2 roadmap.

See Using Prioritization Methods for detailed prioritization.

Step 5: Add to Roadmap

Promote to Roadmap:

Commit to building the feature by changing status.

• Open "Dark Mode Support" post
• Click "Change Status"
• Select "Planned"
• Add comment: "Great news! We're adding dark mode to our Q2 roadmap. We'll be implementing system-aware automatic switching plus a manual toggle. Thanks for the detailed feedback!"
• Check "Notify followers" to send email update

[Screenshot: Status change interface showing dropdown selecting "Planned" status, comment field filled, and "Notify followers" checkbox checked]

Automatic Notifications Sent:

All 47 voters receive email:

Subject: "We're building Dark Mode Support!"

Body:

Good news! The feature you voted for is now on our roadmap.

Dark Mode Support has moved to Planned

"Great news! We're adding dark mode to our Q2 roadmap. We'll be implementing system-aware automatic switching plus a manual toggle. Thanks for the detailed feedback!"

We'll keep you updated as we make progress. [View Roadmap →]

[Screenshot: Email notification showing "We're building this!" header, post title, status change, team comment, and link to roadmap]

Post Appears on Roadmap:

The post automatically appears on your Roadmap board because it has a roadmap status ("Planned").

• Customers can view roadmap at yourcompany.productlift.com/roadmap
• Post shows in "Planned" column on Kanban board
• Target date shows "Q2 2026"

See Building and Sharing a Roadmap for complete roadmap workflow.

Step 6: Development and Progress Tracking

Start Development:

When your team begins work, update the status.

Week 1 - Sprint Planning:

• Team commits to dark mode in sprint planning
• Change status from "Planned" to "In Progress"
• Add comment: "We've started development! Our designer is finalizing the color palette this week, and engineering will begin implementation next week."
• Followers receive "Development started!" notification

[Screenshot: Kanban board with Dark Mode post being dragged from "Planned" column to "In Progress" column]

Week 2-6 - Development Updates:

Provide regular progress updates through comments:

Week 2:

• Comment: "Design complete! We've finalized the dark mode color palette and created UI mockups. Here's a preview: [link to Figma]"

Week 4:

• Comment: "Backend work done. We've implemented CSS variable system for theme switching. Now working on UI components."

Week 6:

• Comment: "Almost there! All UI components support dark mode. Now in internal testing to catch edge cases."

Each comment notifies followers and shows transparent progress.

[Screenshot: Post comments section showing chronological progress updates from team with timestamps and avatar]

Move to Testing:

When ready for testing:

• Change status to "Testing" or "In Beta"
• Add comment: "Dark mode is now in beta testing! If you'd like early access to test it out, reply to this post or email beta@yourcompany.com"
• Optional: Invite high-engagement followers to beta test

Step 7: Release Preparation

Final Testing and QA:

Before releasing:

• Internal QA testing on all browsers and devices
• Beta tester feedback collected and bugs fixed
• Documentation prepared (help articles, changelog entry)
• Marketing materials ready (screenshots, demo video)

Prepare Changelog Entry:

While feature is in testing, draft changelog entry:

• Navigate to Changelog → Create Entry
• Title: "Dark Mode Support"
• Description: "We've added dark mode to the entire application! Dark mode automatically detects your system preferences, or you can manually toggle it in Settings → Branding. Perfect for late-night work sessions and easier on your eyes."
• Release Date: June 15, 2026
• Category: UI/UX Enhancement
• Link to Post: Link to original feedback post
• Screenshots: Before/after dark mode screenshots

[Screenshot: Changelog entry draft showing title, rich text description with images, release date picker, and linked post]

Prepare Knowledge Base Article:

Create help documentation:

• Navigate to Knowledge Base → Create Article
• Title: "How to Enable Dark Mode"
• Content:
  • What is dark mode
  • How to enable (Settings → Branding → Dark Mode toggle)
  • Automatic vs manual mode
  • Troubleshooting
  • Screenshots showing toggle location
• Category: Getting Started
• Related Articles: Link to other UI customization articles

[Screenshot: Knowledge base article editor showing "How to Enable Dark Mode" article with step-by-step instructions and screenshots]

See Knowledge Base for documentation best practices.

Step 8: Release and Announcement

Ship the Feature:

Deploy dark mode to production.

Change Status to Released:

• Open "Dark Mode Support" post
• Change status from "Testing" to "Released"
• Add comment: "🎉 Dark mode is now live! Check it out in Settings → Branding. Thanks to everyone who voted and provided feedback - your input helped shape this feature."
• Post automatically moves from Roadmap board to Changelog board

[Screenshot: Status change to "Released" with celebratory comment and automatic board migration indicator]

Publish Changelog Entry:

• Navigate to your draft changelog entry
• Click "Publish"
• Changelog entry appears on Changelog board at yourcompany.productlift.com/changelog
• Customers can see all recent releases

[Screenshot: Published changelog entry showing dark mode feature with screenshots, description, and release date]

Automatic Release Notifications:

All 47 voters automatically receive "Feature Shipped!" email:

Subject: "We shipped Dark Mode Support!"

Body:

🎉 Great news! The feature you requested is now live.

Dark Mode Support has been released!

"Dark mode is now live! Check it out in Settings → Branding. Thanks to everyone who voted and provided feedback - your input helped shape this feature."

[Try it now →] [View Changelog →] [Read Documentation →]

[Screenshot: Release notification email with celebration emoji, post title, description, and three call-to-action buttons]

See Follower Notifications for email customization.

Announce to All Customers:

Beyond automatic notifications to voters, announce broadly:

• In-App Notification: Show tooltip highlighting Settings → Branding
• Blog Post: Write announcement blog post with details and screenshots
• Social Media: Tweet about the release, thank customers who requested it
• Newsletter: Include in monthly product newsletter
• Help Widget: Show "What's New" message in app with dark mode demo

Step 9: Documentation and Support

Make Documentation Accessible:

Ensure customers can find help:

Publish Knowledge Base Article:

• Knowledge Base article "How to Enable Dark Mode" is published
• Appears in Knowledge Base search results
• Linked from changelog entry
• Linked from Settings → Branding (help icon)

Update Related Documentation:

• Update "Customizing Your Workspace" article to include dark mode
• Add dark mode to "Accessibility Features" article
• Include in onboarding guides for new users

Link Everything Together:

Create interconnected documentation:

• Feedback Post → Links to Changelog and Knowledge Base
• Changelog Entry → Links to Feedback Post and Knowledge Base
• Knowledge Base Article → Links to Changelog and related articles

This creates a complete paper trail from idea to shipped feature to documentation.

[Screenshot: Post sidebar showing linked items: "📋 Changelog: Dark Mode Support Released" and "📖 Knowledge Base: How to Enable Dark Mode"]

See Post Linking and Relationships.

Step 10: Measure Impact and Follow-Up

Track Adoption:

Monitor how customers use the new feature:

Analytics:

• Track dark mode toggle usage (% of users enabling it)
• Monitor time spent in dark mode vs light mode
• Analyze user segments: who adopts dark mode most?

Gather Feedback:

Create follow-up feedback mechanism:

• Add poll to changelog: "How do you use dark mode?" (Auto/Manual/Not using)
• Monitor comments on changelog and original post
• Watch for bug reports or refinement requests
• Create "Dark Mode Improvements" follow-up post for iteration ideas

[Screenshot: Poll on changelog entry asking "How do you use dark mode?" with options: Automatic, Manual toggle, Haven't tried it yet]

See Polls and Voting.

Thank Contributors:

Recognize customers who helped:

• Reply to Sarah (original requester): "Sarah, thanks for suggesting this! Your mockup was really helpful in shaping the design."
• Highlight power users who beta tested
• Feature customer quotes in blog post: "Dark mode has been a game-changer for my late-night work sessions" - Sarah, PM at Acme Corp

Iterate Based on Feedback:

As customers use the feature:

• Collect refinement requests ("Can you add scheduled dark mode?")
• Fix edge case bugs discovered in production
• Create new posts for enhancements
• Repeat the cycle for continuous improvement

Complete Lifecycle Timeline Example

Real-World Timeline: Dark Mode Feature

Total Time: Idea to Shipped Feature = 5 months

Customer Touch Points: 8 emails (confirmation, approval, planned, dev started, 3 progress updates, released, changelog)

Real-World Example: Feature Launch Success Story

Scenario: A B2B SaaS company uses ProductLift to manage the complete lifecycle of a customer-requested integration feature.

The Feature: Slack integration for notification delivery.

Month 1 - Idea Phase:

• 12 customers submit "Slack integration" requests
• Posts merged into single post with 73 total votes
• Comments reveal specific use cases: status updates, daily digests, mention notifications
• Segment analysis shows 34 Enterprise customers voted ($428k total MRR)

Month 2 - Prioritization:

• Quarterly roadmap planning session
• RICE score: 7.2 (high reach, high impact, moderate effort)
• Compared to other requests, ranks #2 priority
• Decision: Add to Q3 roadmap

Month 3 - Roadmap Communication:

• Status changed to "Planned"
• 73 voters receive notification
• Roadmap shows "Q3 2026" target
• Support ticket volume asking "When will you add Slack?" drops by 60%

Month 4-6 - Development:

• Status → In Progress (Week 1)
• Progress updates every 2 weeks (6 updates total)
• Beta testing with 8 high-engagement customers (Week 10)
• Bugs fixed based on beta feedback

Month 7 - Launch:

• Feature shipped to production
• Status → Released
• Changelog entry published with setup guide
• Knowledge Base article: "How to Connect Slack"
• 73 "We shipped it!" emails sent
• Blog post announcement
• Demo video created

Results:

• 68% of voters (50 customers) connected Slack within first week
• NPS score increased +12 points among voters
• 3 trial users converted to paid (cited Slack integration as key factor)
• Feature generated $47k ARR from conversions and upsells
• Support tickets reduced (customers get notifications in Slack)
• Community trust increased (customers see you deliver on promises)

Ongoing Iteration:

• Collected 23 refinement ideas in first month
• Created follow-up posts: "Slack Digest Frequency Options", "Slack Thread Notifications"
• Continuous improvement based on usage patterns

Tips and Best Practices

Validation Phase:

• Let ideas collect votes for at least 2-4 weeks before prioritizing
• Ask clarifying questions in comments to refine requirements
• Look for quality of comments, not just vote quantity
• Analyze voter segments to understand revenue impact

Prioritization:

• Use multiple signals: RICE + votes + MRR + strategic fit
• Don't just build most-voted features (balance with strategy)
• Consider "quick wins" to build momentum
• Re-prioritize quarterly as market evolves

Roadmap Communication:

• Be transparent about what you're building and why
• Set realistic expectations (quarters, not specific dates)
• Update status regularly to show progress
• Explain delays honestly when they happen

Development:

• Update status at key milestones (started, in testing, released)
• Add progress comments every 1-2 weeks
• Invite engaged customers to beta test
• Link to design mockups or preview videos in comments

Release:

• Prepare documentation before shipping
• Coordinate changelog, knowledge base, and emails
• Announce broadly (not just to voters)
• Include clear "how to use" instructions in announcement

Post-Launch:

• Monitor adoption and gather feedback
• Thank customers who contributed ideas and feedback
• Create follow-up posts for iterations
• Measure impact on key metrics (adoption, NPS, revenue)

Common Challenges and Solutions

Challenge: Feature Takes Longer Than Expected

• Solution: Update followers regularly with progress. Transparency builds trust even when timelines slip.

Challenge: Requirements Change During Development

• Solution: Add comment explaining the change and why. Involve voters in decisions when possible.

Challenge: Feature Ships But Voters Don't Adopt It

• Solution: Follow up with targeted emails, create tutorial content, add in-app prompts, gather feedback on adoption barriers.

Challenge: Voters Want Different Things

• Solution: Build MVP with core functionality first. Create follow-up posts for variations. Explain decisions in comments.

Challenge: Managing Expectations for Timeline

• Solution: Use quarter-based targets (Q3 2026) not dates. Update roadmap if priorities shift. Communicate changes proactively.

Challenge: Feature Launches with Bugs

• Solution: Update status to "Testing" if severe, add comment acknowledging issues, communicate fix timeline, ship fix quickly.

Related Articles

Use Case Workflows:

• Complete Feedback Workflow - Collecting and validating customer ideas
• Building and Sharing a Roadmap - Planning and communicating what you're building

Feature-Specific Guides:

• Post Moderation - Reviewing and approving feedback
• Using Prioritization Methods - RICE, ICE, and other frameworks
• Kanban Board Management - Tracking development progress
• Post Linking and Relationships - Connecting posts, changelogs, and docs
• Follower Notifications - Customizing update emails
• Knowledge Base - Creating help documentation
• Changelog - Publishing release announcements