What is Cycle about?
Welcome to Cycle! 🚲
Wondering what Cycle is about, and what you can expect from using the tool? Here is a quick overview of where to start.
Why we built Cycle
As Product Managers ourselves, we’ve been trying to find ways to build products that matter and have an impact on our users. And for us, that meant putting the customers at the center of product discovery. Not just building a roadmap out of customer requests, but infusing the entire organization with customer insights, to be mixed with our product vision to build up on our product sense and draft our product strategy.
Concretely, making sure our processes for building impactful products would evolve continuously around what we would learn from our customers while scaling the organization that would work it out.
But doing so appeared to be a complex task, essentially because we didn’t have the right tools. We had to choose to either use feedback-capturing tools (that would help in automating the centralization and processing of inbound/direct customer feedback and prioritizing it), but those would come with their existing rigid process and frameworks — or generic NoCode tools that would allow for flexibility around our product processes but would not be scalable with us evolving onwards.
What you can expect to do with Cycle
Cycle is a hub that centralizes all product information (customer feedback, user interviews, product specs) in a neat, flexible, and collaborative space. Cycle is built on a NoCode paradigm to enable every product team to craft their own process within their product management platform (and not the other way around).
Here are a few things you’ll be able to do:
capture and centralize customer feedback in one place
connect relevant insights to your product roadmap
write your product spec (PRD) in the context of customer insights
close the loop with customers and maximize the impact of what you ship
For more details about those use cases, feel free to head to our extensive documentation!
--