Features & Roadmap
Your roadmap is the heart of Release Cadence. Learn how to plan features, track progress, and share your vision with users.
Creating Features
Features represent the work you're planning or building. To create a feature:
- Open your project
- Click "New Feature"
- Fill in the details
- Click "Create Feature"
Feature Fields
Title
A clear, concise name for the feature. Keep it user-focused.
- ✅ Good: "Dark Mode Support"
- ❌ Bad: "Implement CSS theme switcher"
Description
Explain what the feature does and why it matters. Include:
- What problem it solves
- Who it benefits
- How it works (high-level)
Status
Track where the feature is in your workflow:
- Draft: Initial idea, not yet committed
- Prospective: Under consideration
- Backlog: Approved but not scheduled
- Development: Actively being built
- Testing: In QA or beta testing
- Ready for Release: Complete, awaiting deployment
- Releasing: Currently deploying
- Post-Release Feedback: Gathering user feedback
- Done: Complete and stable
- Archived: Removed from active roadmap
Visibility
Control who can see the feature:
- Public: Shown on public roadmap
- Private: Only visible to team members
Priority
Indicate importance (optional):
- Critical
- High
- Medium
- Low
Feature Details
Attachments
Add mockups, designs, or documentation to features. Supported formats:
- Images (PNG, JPG, GIF)
- Documents (PDF)
- Design files (Figma links)
Work Items
Break features into smaller tasks:
- Create work items for each component
- Assign to team members
- Track progress independently
Linked Surveys
Connect surveys to features to:
- Collect targeted feedback
- Validate assumptions
- Measure interest
Public Roadmaps
Share your roadmap publicly to build trust and gather feedback.
Making a Roadmap Public
- Open project settings
- Enable "Public Roadmap"
- Copy the public URL
- Share with your users
What Users See
On public roadmaps, users can:
- View features marked as public
- See feature status and descriptions
- Click on features to get more information
What Users Don't See
- Private features
- Internal notes or work items
- Team member assignments
- Technical implementation details
Best Practices
Keep It Current
Update feature statuses regularly. Stale roadmaps lose credibility.
Be Realistic
Don't overpromise. It's better to under-promise and over-deliver.
Explain Why
Help users understand the value of each feature and why it matters.
Communicate Changes
If you cancel or delay a feature, explain why. Transparency builds trust.
Roadmap Communication
Announcing Features
When you move a feature to "Development" or "Released":
- Update your public roadmap
- Share progress in your community
Handling Feedback
When users vote on features:
- Acknowledge their input
- Explain your decisions
- Thank them for participating
Tips for Success
- Start Small: Don't plan too far ahead. Focus on the next 3-6 months.
- Get Feedback Early: Share feature ideas before building them.
- Iterate: Your roadmap should evolve based on user feedback.
- Be Transparent: Share both successes and setbacks.
- Celebrate Wins: Announce completed features and thank contributors.