How would you measure the success of Cycles in Linear?

Introduction

Cycles are Linear's take on sprints: time-boxed periods (usually one or two weeks) that a team turns on in team settings. Cycles start and end automatically, unfinished issues roll over to the next cycle, and each cycle shows a burn-up style progress graph, scope changes and completion rate. Unlike Jira sprints, Cycles are deliberately lightweight. There is no sprint planning ceremony baked in, no story points required, and no manual "close sprint" step. That design choice shapes how I'd measure success: a good Cycle is not one that hits 100% completion, it is one that helps a team keep a steady, predictable rhythm without extra process.

Step 1

Product Context (3 minutes)

Cycles are one of Linear's oldest features and sit at the team level, below Projects and Initiatives in the planning hierarchy. A project can span several cycles, and an issue can belong to both a project and a cycle. The "Linear Method" encourages teams to work in cycles, keep them short, and let unfinished work roll over without guilt.

Key stakeholders:

• Engineers and designers: want a clear, small set of things to work on this week

• Engineering managers and team leads: want predictable throughput and an early warning when a cycle is overloaded

• PMs and leadership: want to see whether project milestones are on track, often through Insights and project updates

• Linear: wants Cycles to be the daily planning habit that keeps teams opening Linear and makes switching back to Jira costly

Typical user flow:

1. A team enables Cycles and sets length, start day and cooldown options
2. Before the cycle starts, the lead pulls issues from the backlog or Triage into the upcoming cycle
3. During the cycle, issues move through states; the GitHub integration moves issues to In Progress and Done as branches and PRs change
4. The cycle view shows progress, scope added mid-cycle, and at-risk work
5. At the end, Linear automatically rolls incomplete issues to the next cycle

Lifecycle stage: mature. Cycles are widely used by small and mid-size teams, but adoption is less certain in large Enterprise workspaces migrating from Jira, and agent-created issues (now around half of all new issues in Linear) are changing what goes into a cycle.