Template
Public product roadmap template
A public product roadmap template: Planned, In progress and Shipped columns fed by your voted feature requests, with setup steps for Looph.
Any team that wants to publicly show what's coming next and reduce 'is this being worked on?' questions.
- Statuses
- 4
- Tags
- 4
- Things to ask for
- 3
- Setup steps
- 6
Use this template
Copy the setup, import the starter posts
Two ways to start from this template today: copy the checklist below into your setup notes, and import the starter CSV into a new board from the Posts page of your team area. The file holds this page's example posts, with each status mapped to Looph's built-in name so the importer accepts it; delete them before you share the board.
Columns: title, details, status. 3 example posts.
Setup checklist
Public product roadmap template (looph.ing/templates/public-roadmap) Statuses (the Statuses page in the team area): - Rename "Under review" to "Exploring" - Keep "Planned" - Keep "In progress" - Rename "Complete" to "Shipped" The public roadmap's columns are Planned, In progress and Complete, under whatever names you give them. Statuses are shared by every board in a workspace, so a rename or a hidden status shows on all of them. Tags: - Core product - Integrations - Enterprise - Mobile Board description: What should be possible that isn't today, and who is it for? Ask for in the details: - The outcome as a title - The problem and who has it - Timing, if you must Setup steps: 1. Start from a board that collects requests, such as the feature request setup. The roadmap is a view over your boards' statuses, not a separate list to keep in sync. 2. Rename Under review to Exploring and Complete to Shipped. The roadmap's columns follow your status names, and you can drag cards to order them within a column. 3. Seed it from the top of the board. Sort the inbox by Top, and move a dozen posts you are confident about into Planned, or into Exploring if you are still looking. 4. Keep sensitive work on a private board rather than a public one, so only people with access to that board can see it. 5. Optionally serve your Looph site, roadmap included, on a subdomain of your own with your logo and colour. 6. As items ship, publish changelog entries that link them, and choose to mark them Shipped and tell their voters.
Templates aren't applied automatically yet: you set the board up yourself by following the steps on this page. One-click templates are coming soon.
Fit
When to use this template
A good fit when
Customers, prospects and your own sales team keep asking whether something is being worked on. A public roadmap answers that on a page they can bookmark. Because its columns are statuses on your feedback board, it stays current as you move posts rather than on a quarterly update ritual.
It fits teams that already collect requests on a board. Every card on the roadmap is a post carrying its voters, so shipping a card closes the loop with the people who asked.
Pick something else when
It is not a delivery plan for engineers. Sprint dates, dependencies and estimates belong in your project management tool; publishing them turns every slip into a broken promise.
If competitive or contractual reasons mean you can say little about upcoming work, keep the roadmap internal rather than publishing a thin one. Three vague items read worse than no roadmap at all.
What's inside
Statuses, tags and what to ask for, and why each one is there
Looph has a fixed set of statuses that you can rename, recolour, reorder and hide, but not add to; each status below says which built-in one to use. Posts are a title plus details, so the last list is what to ask for in the details.
Statuses
- ExploringRename Under review
- Being researched, with no commitment. It stays off the public roadmap, which shows only the three columns below. Items leave Exploring for Planned or, just as often, for Not planned with a stated reason.
- PlannedBuilt-in status
- Committed but not started. Customers read this column most closely, so only put things here you intend to build.
- In progressBuilt-in status
- Being built now. Keep it short: a column of twenty in-progress items reads as nothing ever finishing.
- ShippedRename Complete
- Released. Items stay visible as evidence that the roadmap turns into releases, and a linked changelog entry can tell everyone who voted.
The public roadmap's columns are Planned, In progress and Complete, under whatever names you give them. Statuses are shared by every board in a workspace, so a rename or a hidden status shows on all of them.
What to ask for in the details
- The outcome as a title
- Write it as the outcome for the customer, such as "Bulk edit tasks", rather than the internal project name nobody outside the team recognises.
- The problem and who has it
- A sentence or two on the problem it solves and who it is for. A prospect reads this to judge whether their need is covered.
- Timing, if you must
- Now, Next and Later communicate order without dates and age better. If your customers insist on dates, write the quarter into the details and update it every time something moves. A dedicated field is coming soon with custom fields.
Custom fields and file attachments are coming soon. Until then, a post is a title plus up to 5,000 characters of details.
Suggested board description
Put a line like this in the board description, so people know what to include: “What should be possible that isn't today, and who is it for?”
Tags
- Core product
- Integrations
- Enterprise
- Mobile
Tags are workspace-wide and applied by your team. Visitors can filter the board by tag to find the part of the product they care about; the roadmap itself filters by board. Enterprise earns its own tag because buyers evaluating you often look only for SSO, permissions and audit work.
Setup
Set it up in Looph
Each step in order, with the guide that covers it.
- 01
Start from a board that collects requests, such as the feature request setup. The roadmap is a view over your boards' statuses, not a separate list to keep in sync.
- 02
Rename Under review to Exploring and Complete to Shipped. The roadmap's columns follow your status names, and you can drag cards to order them within a column.
- 03
Seed it from the top of the board. Sort the inbox by Top, and move a dozen posts you are confident about into Planned, or into Exploring if you are still looking.
- 04
Keep sensitive work on a private board rather than a public one, so only people with access to that board can see it.
- 05
Optionally serve your Looph site, roadmap included, on a subdomain of your own with your logo and colour.
- 06
As items ship, publish changelog entries that link them, and choose to mark them Shipped and tell their voters.
Illustrative examples
Example posts
Made-up posts that show what a useful entry on this board looks like. They are not from real customers.
Example · Core product
Bulk edit tasks
Select several tasks and change assignee, due date or label in one action. The most-voted request tagged Core product.
Planned
Example · Enterprise
SAML single sign-on
Working out which identity providers to support first. If you need this, comment with the provider your company uses.
Exploring
Example · Mobile
Offline access in the Android app
Read-only access to recently opened projects without a connection. Editing offline is a separate item for later.
In progress
Plan
Which plan it needs
Works on Free. The public roadmap is included on every plan, Free among them, together with the changelog and one public board to feed it. Keeping sensitive work on a private board needs Starter, and serving the roadmap on your own domain or removing Looph branding needs Growth. Compare plans.
How the pieces work: Public roadmap. Teams running this workflow: Customer feedback management for SaaS product teams and A feedback board and roadmap for solo founders.
More templates
Other starting points
Customer feedback portal template
B2B teams and agencies that want a single branded destination per account instead of scattered email threads.Changelog page template
Teams that want shipped work to automatically close the loop with the customers who asked for it.Beta feedback board template
Teams running a private or invite-only beta that need structured, votable feedback before a general release.Internal IT request board template
Internal IT and operations teams that need a searchable, votable alternative to a ticketing spreadsheet.
Related
The features and reading behind this template
Start collecting feedback in five minutes
Free forever on one board, with unlimited members and a 14-day Business trial. No credit card, no sales call.
Unlimited members · Published prices · Cancel anytime