3
4 Comments

Public Roadmaps - How do you do them?

Hey folks,

as I’m getting closer and closer to version 1.0 of my newsletter tool Keila, I’m also finding myself more confident with the exact roadmap I want to follow for the next couple of versions.

But I’m still unsure how – if at all– to make this roadmap (which currently lives on a piece of scrap paper on my desk) public.

Currently I have the usual list of "features and coming-soon features" on the landing page and a roadmap board on GitHub.

What are your experiences with public roadmaps when building in public?
Do you keep them minimal and abstract or do you make concrete promises like "feature X will be in version Y"?
Have you found them to be effective marketing tools - or do you know any best practices from other startups?

on January 10, 2023
  1. 2

    You could use a tool like Canny to create a public roadmap and list features only "Under Review" or something like this, so that you don't experience the problem of promising too much and then underdelivering.

    It's useful because users will automatically get notified when a feature is released. Also, in my experience users want to see progress and that a tool (especially maintained by a small team) is actively being developed.

    1. 2

      Thanks for the suggestion! Have you had positive experiences with roadmaps like this in your own projects that you’d like to share?

      1. 2

        Yeah totally! We moved from tracking feature requests on our Discord server to a Canny powered feature request site - https://sagahq.canny.io/

        It's easy to maintain, discuss, and inform users.

        1. 1

          Cool, thanks for sharing!