Skip to content
Roadmaps live preview
All projects

Roadmaps

Show what's being built next instead of fielding the same feature request twice.

Users had no visibility into what was coming, which led to duplicate feature requests and missed input on priorities.

Tech Domain · Book Dev|Published|Evidence: Live|Next.js, TypeScript

A public deployment is available to try.

Case Study

Before

Portfolio users and potential collaborators had no visibility into what was being built next. This led to duplicate feature requests and missed opportunities for community input on priorities.

After

Created transparency that built trust with the audience. Feature voting revealed user priorities that differed from assumptions, and the public roadmap cuts down on duplicate feature requests since users can see what's already planned.

How it's solved

Built a public roadmap system with status columns (planned, in progress, completed, shipped), voting on features, and changelog integration. Each project has its own roadmap with cross-links to related items.

Trade-offs

Voting has no anti-abuse measures — a determined user could vote more than once from different sessions.

Related Articles

Further reading on related topics from the blog

Related Projects

More in Tech Domain · Book Dev

Roadmaps - Chaowalit Greepoke Portfolio