Cycle is built around a No Code paradigm, which means you can set up your workspace to exactly match the way you organize and run your product discovery currently. No need to adapt your processes to the rigidity of a tool.

There are as many product processes as there are product teams, right?

Cycle is built on top of the Doc object. Each doc is a collaborative editing space, where product teams can build and organize their product information.

There are different types of Docs — called Doc types — to account for specific product logics (feedback, initiative, OKR, etc)

Doc types are organized through specific hierarchy rules (children/parent relations). This makes the Hierarchy diagram, bridging the power of a product management-specific tool with the flexibility of a No Code paradigm.

Each doc type has specific properties linked, that will enable custom views along with sorting and filtering options.

You can create as many doc types as you want. To start with, 3 doc types exist in Cycle:

Built-in ones (cannot be deleted):

Custom ones:

To create a new doc type, head to the Settings > Doc types and click on the “+” button.

Doc types are related to one another through hierarchy relations. Those relations are either Parent or Children to another doc type.

Note that one doc type can be parent to multiple children, but a doc type can only be child to one parent doc type.

Head over to your Hierarchy diagram in the settings to visualize it!

Each doc type can have a set of dedicated properties, that can be of different types:

Depending on the property type, property values can be defined here (note: property values can only be defined from the settings page).

Any property can be linked to multiple doc types — this will allow for visualizing multiple doc types in a single view (= board).