A public roadmap
built from customer feedback

Turn collected requests and backlog priorities into a plan customers can follow. Keep each idea connected to delivery progress, then tell the people who asked when it ships.

Create your public roadmap

See a request become a shipped update →

// decide what to build

Give requests a place in your product plan.

Review customer context, compare backlog priorities and choose the ideas your team is ready to share.

// keep customers informed

Show progress on the requests they care about.

Publish clear statuses and connect shipped work to release announcements and subscriber updates.

// illustrative workflow

From a customer request to a public plan

A customer asks for Custom roles. Your team organizes the feedback, links it to backlog issue ENG-142 and compares it with other work before adding it to the public plan.

  1. Collect and organize: review requests, group related ideas and keep their customer context.
  2. Prioritize: evaluate the linked backlog work using the criteria that matter to your team.
  3. Share your plan: choose customer-facing ideas and the statuses your audience can see.
  4. Show progress: configured rules keep linked ideas aligned with tracker statuses.
  5. Close the loop: review the release announcement, publish it and send updates to subscribers according to your delivery settings.

The team makes the product decision. The public roadmap gives customers a clear place to see the result and follow what happens next.

Review suggestions

Edit boards offline

Team-selected idea → Planned, related requests linked

ENG-142linked backlog issue

Custom roles

Done

Configured status rule → Done on the roadmap

Public Roadmap PublicSelected customersTeam only
Roadmap25Bugs10Enterprise6

Planned

  1. ▲ 4 Offline editing Mobile +3 similar requests Shipped

In progress

  1. ▲ 19 Dark mode UI Shipped
  2. ▲ 31 SSO login Security Shipped

Done

  1. ▲ 40 Custom roles Permissions Shipped
  2. ▲ 42 CSV export Reporting Shipped
Illustrative ideas, vote counts and issue IDs. The demo shows review, a linked Linear issue and configurable audiences; it repeats while visible.

Start with the feedback you have already collected

Bring requests into one place, review their meaning and connect them to work your team can evaluate.

Organize customer requests

Add labels, keep useful customer context and review related requests before merging duplicates.

Collect and organize feature requests →

Capture requests from conversations

Save selected Slack and Discord messages as drafts, then review them before publishing to a board.

Feedback from Slack →
Feedback from Discord →

Link the request to backlog work

Add the idea to your internal backlog or link it to an existing issue. Keep the customer request connected to the work being planned.

Connect ideas and backlog issues →
// customer evidence · team priorities

Let backlog priorities inform what you share

Compare requests with bugs and planned improvements. Use impact, effort, confidence, votes and customer context in the scoring approach your team chooses.

In the sample, Custom roles competes with an export fix, SSO and other work. Changing the criteria changes the order; your team reviews the trade-offs and chooses what belongs on the roadmap.

Turn selected backlog issues into clear public ideas, with an AI draft if helpful. Review the customer-facing summary and visibility before sharing it. Keep internal implementation details in your backlog.

Publish the plan you are ready to communicate, with statuses that explain progress. Add dates when your team has chosen to commit to them.

  1. SSO request
    R250 I2 C80% E4
    100
  2. Fix export crash
    R400 I1 C80% E4
    80
  3. Custom roles
    R150 I2 C80% E4
    60
  4. API refactor
    R200 I1 C80% E4
    40
Scoring values and revenue in the demo are illustrative. A priority score supports the team’s decision; it does not publish a plan or promise a delivery date.

Give users a clear status for their requests

Customers see the ideas available to them on the roadmap. Authors and voters can receive email updates when those ideas change status, with controls over their notification preferences.

// progress

Use stages that match your workflow

For example: Planned → In progress → Done. Customize statuses and the columns you display so customers can understand what the team is considering, building and releasing.

Configure idea statuses →
// sync

Keep linked work and roadmap aligned

Map Jira, Linear or another connected tracker’s statuses to idea statuses. If Done precedes production release, use the documented release-webhook condition.

Set up status rules →
// notifications

Let requesters follow progress

Authors and voters can receive status-change emails for their ideas. They can manage or disable notifications in their profile. Release-note subscriptions and delivery are configured separately.

See how voter updates work →
// request → shipped → announced

Tell the people who asked when the work ships

Custom roles reaches Done after the linked work is released. AI prepares an announcement, your team checks the benefit and availability, then approves the customer-facing text.

The approved announcement appears in the changelog and its in-product widget. Subscribers can receive release notes through your configured schedule, manual send or release webhook.

Customers can follow their original request’s status and read what changed, where to use it and why it matters.

Explore release-note automation → · See the full feedback-to-release workflow →

app.acme.com
Illustrative release · sample issue IDs.

Choose the audience and where your roadmap lives

Share the right ideas

Make a board public, limit access to invited voters or restrict it to email domains. Check the public view before sharing the link.

Configure board access →

Make it part of your product

Match your brand and embed the roadmap in your website or web product so customers can follow progress where they work.

Configure the roadmap widget →

Show a plan customers can understand

Choose which ideas and columns to display. Keep public summaries useful and review internal details before publishing.

Explore the Ducalis roadmap →

Keep users informed about the plan

Explore the process around a public roadmap: collect requests, connect them to work and communicate progress.

Give every request a path to progress.

Start with one customer request. Link it to backlog work, choose its public status and check the roadmap your customers will see.

Create your public roadmap

Follow the roadmap setup →