🌱
Document features in your roadmap
Getting stuff done.
Okay, you got some feedback, extracted the relevant insights, and tied them to features. Time to prioritize what you'll ship, document what to build, and get stuff done.
Feedback-Insight-Feature is the default configuration. In a Pro plan, you can customize your hierarchy with additional layers like epic, bug, feature, user story, etc.
You can always rename these to fit your own taxonomy.
A view is a filtered and structured way to visualize your Cycle Features. They can take a kanban or list shape and be filtered on or grouped by properties.
Product teams use views to prioritize features, build custom roadmaps, track progress on discovery and delivery, focus on specific tasks, and more.
Here's an example of a view with all "Small" Features grouped by "Status".
Only "Makers" can create views. If you are the first to join yourn workspace, you're a "Maker" by default. If not, ask a Maker to change your role.
Producing actionable and contextual documents is the core of every PM's job. We made it delightful to write and structure PRDs using a "/" command.
Plenty of choice to format documents in no time.
Bring your users' voices into your PRDs. Spread it into your organization.
Embed media, files, and other content types to include everyone's work in one structured document.
.gif?alt=media&token=f56c3495-a8c8-4a95-ab9c-6b7567e8ac84)
Embed files from Figma, Miro, Loom, Pitch
.gif?alt=media&token=53130643-f7a4-437e-ae84-0a38e4d742ee)
Mention Linear issues in your Cycle docs
Once you ship something, it's time to communicate about it and close the loop. You can do it manually or use our Release feature.