Cycle's help center
LegalCompany
  • 🚀Get started
    • 🤔What is Cycle? [Start here]
    • 📥Centralize feedback
    • 💡Extract insights from feedback
    • 🌱Document features in your roadmap
    • 📡Write your release notes and close the loop
  • 💪Core concepts
    • 🏡Home
    • 📥Feedback
    • 💡Insights
    • ⛰️Roadmap
    • 🔊Releases
    • 🤩Closing the loop
    • ⚡Cycle AI
    • 📊Customer voice dashboards
  • ⚙️Setup
    • 🔌Integrations
      • Slack
      • Linear
      • Intercom
      • Zendesk
      • Salesforce
      • Gong
      • HubSpot
      • Zapier
      • Chrome extension
      • Figma, Loom, Miro & Pitch
      • Email
      • Notion
      • GitHub
      • Modjo
    • Product areas
    • 📋Views
    • 🏷️Properties
    • 👱Customers
    • 🎭Manage workspace members
    • 🔔Notifications
    • 🔀Statuses
    • ✏️Collaborative, rich markdown and AI-powered editor
    • 🔓Security
  • 🚲Advanced
    • 🎉Public changelog
    • 🤖AI & automations
    • 📹Call recording
    • 📚Content templates
    • 🏔️Advanced Roadmaps and custom views
    • ⚒️Multiple doc types
    • 🔍Search
    • 🏆Pro Cycler tips shortlist
    • ⌨️Keyboard shortcuts
  • 🔐SAML/SSO
  • 👨‍🏫Cycle University
    • 👁️Best practices for views
    • 🏎️Fast-track your onboarding
    • 🐞Bug handling with Cycle
    • 💻API
      • ⚡Webhook event for all properties changes
      • 🔗How to integrate with Jira Product Discovery
    • ❓FAQ
  • 🤔Guides
    • ⬇️Migrate your data to Cycle
      • Canny migration
    • 📖Glossary
    • Synchronise your customer data
  • How to
    • Page 1
Powered by GitBook
On this page
  • Table of content
  • Cycle Collaborator 101 - Send feedback & collaborate better around product 🚀
  • Cycle Maker 101 - Understanding Cycle's logic 🚲
  • 🙌 Feedback collection
  • 🛠️ Feedback processing
  • 😎 Customize your workspace (with suggestions)
  • ✍️ Write your first PRD/spec
  • Search with "⌘+ k"

Was this helpful?

  1. Cycle University

Fast-track your onboarding

How to get value fast.

PreviousBest practices for viewsNextBug handling with Cycle

Last updated 8 months ago

Was this helpful?

We recommend starting small and then customizing the tool according to your needs.

Table of content

Cycle Collaborator 101 - Send feedback & collaborate better around product 🚀

Structure of this video

Part 1: Send feedback to Cycle with your existing toolset and get updates about your feedback

Part 2: What product teams do in Cycle (4:41)

Part 3: How you'll get updates on what you said (6:35)

Part 4: Get even more product information by going to Cycle (8:09)

Cycle Maker 101 - Understanding Cycle's logic 🚲

Structure of this video

Core concept: Feedback, Insight, Roadmaps and Releases

Feedback from Slack (02:26)

Create an insight & link it to a Feature (03:35)

Basic views walkthrough: Home, Feature Pipeline (07:25)

Collaboration (09:23)

Properties (09:35)

Creating & update views: Example with Customer voice (10:50)

Other Basic views- Insight view, Roadmap view, key customer view (12:46)

Search bar - Find Feature, and Feedback & Insights linked to a customer/company (15:15)

🙌 Feedback collection

  1. Going forward, write each user interview/interaction directly in Cycle. Simply click on "New Feedback" to get started. You can use our templates or create your own.

🛠️ Feedback processing

You can then process your inbox every day and get a feel for what customers are asking for. 10-30 minutes should be sufficient.

  1. Highlight the relevant piece of text in the feedback.

  2. Click on the 💡 icon (or hit ⌘1) to create an Insight.

  3. Link the Insight to the appropriate Feature (or create a new one).

  4. Mark the feedback as processed.

😎 Customize your workspace (with suggestions)

  1. Start with our three built-in doc types

    1. Feedback

    2. Insight

    3. Feature

One strength of Cycle lies in the flexibility of its data model. This allows you to create multiple doc types to suit your needs.

Another common doc type used is "Problem," which is useful when you do not have a clear idea about a "Feature". You need to have a Pro plan to have access to multiple doc types. Once you have gathered enough information, you can transfer insights to a child Feature of this "Problem" document type.

    1. Feedback

    2. Features

✍️ Write your first PRD/spec

Write your specs as you normally would, but in Cycle.

Search with "⌘+ k"

The best way to get started is to establish a routine of sending feedback through Slack into Cycle (e.g: from your Product Feedback Channel) through our.

Start with only one integration and We recommend starting with Slack, followed by Intercom, and then other sources. Chrome is a good workaround for any sources from Internet/ a SaaS.

To in your inbox, follow these steps:

In Cycle you can also choose among to fit your needs and way of doing Product.

Customize your Feature . Look at the to get inspired.

for Feedback, Insights, and Features. Look at the to get inspired.

Create your first in each section. Look at the to get inspired.

based on feedback properties.

Define your best for the following doc types

is similar to Notion, so writing your specs should be easy.

Hit "command + k" to open Cycle command panel. It lets you search through all your Cycle docs, navigate your Cycle workspace and perform quick actions. Learn more about the search .

👨‍🏫
🏎️
integration for Slack
then add more.
process feedback
Split your inbox
templates
Our editor
here
workflow
Customize the properties
views
Intro video for sending feedback & collaborating around product
Demo video to understand Cycle's logic
Feedback collection
Feedback processing
Customize your workspace (with suggestions)
Write your first PRD/spec
Search with "⌘+ k"
examples
docs templates
examples
examples