Roadmap

Roadmap turns approved feedback into a public view of planned, active, and shipped work.

Organize the Board

Create named lists for the workflow your team uses. Lists have a color, position, and sort order. Available sorting includes votes, comments, newest, oldest, recently updated, and title.

Move feedback into a list and set its lane to Now, Next, Later, or Released. A feedback item remains the source record, so votes, comments, customer context, status, and release links stay connected.

Add Customer Votes

When you create a roadmap item, choose a submitter and select existing customers in Upvoters. Search by name, email, or customer ID. Each customer gets one vote, even if selected more than once or also chosen as the submitter. Selected upvoters are subscribed to updates.

To add a vote later, open the card, select a customer under Upvote on behalf, and click Add vote. The voter list and card count update without closing the dialog or reloading the board. If another vote arrives while yours is saving, the dialog retrieves the current voter list. The picker clears after success. If the request fails, an error appears and your selection stays available to retry.

Publish the Roadmap

Approved public items appear in the site's public portal and widget. Private, pending, or rejected feedback does not become public merely because it was added to a roadmap list.

Use the short /r portal URL when sharing a roadmap. Managani redirects it to the canonical /roadmap page and preserves query parameters.

When a roadmap item ships, link it to a Changelog entry so customers can move from the request to the release notes.

Keep the Board Useful to Customers

Choose list names that explain your team's process without implying a delivery date you have not agreed to. The Now, Next, Later, and Released lanes communicate relative timing. Use the feedback description to explain the customer problem and expected outcome, especially when an internal project name would be unclear to visitors.

Review the board regularly with the people responsible for product delivery. Check whether active items still belong in their current lane, whether their status matches the work, and whether newly approved requests should be included. Votes and comments provide demand signals, but they do not replace a review of effort, dependencies, and product direction.

Before sharing the board, inspect it through the public portal. Confirm that the intended cards appear and that private or pending requests remain excluded. When work ships, update the source feedback and connect a changelog entry that explains what customers can now do. This keeps the roadmap useful after the initial announcement.