Linear Cycles for solo engineers: how to use them without the team you don’t have

Linear is the project management tool that designed itself for teams of 5–50 engineers. The Cycles feature — Linear’s name for time-boxed iterations — is built around that team-scale workflow. For solo engineers and tiny teams (1-2 people), the docs aren’t really written for you.

This guide is from running Linear Cycles both solo and on a 2-person team across 18 months, and the resulting workflow that makes Cycles work at solo scale.

Why bother with Cycles solo

The honest answer: most solo engineers don’t. They use Linear as a fancy issue tracker, ignore Cycles entirely, and that’s fine.

The reason to use Cycles solo: forced scoping. A cycle has a fixed time-box. You commit to a set of issues for that cycle. Anything that doesn’t fit gets explicitly bumped. This discipline is rare in solo work where you can always justify “just one more thing” and never finish a release.

If you have ever:

• Started a feature and not shipped it for three weeks
• Looked at your backlog and felt overwhelmed
• Forgotten what you were working on after a vacation
• Said “I’ll get to it” about something for two months

Then Cycles can help. They give you a regular ritual of “what did I commit to, what did I do, what carries over.”

The solo cycle workflow that works

After iterating, the workflow that has stuck for me:

One-week cycles, not two

Default Linear cycles are 2 weeks. For solo work, 2 weeks is too long — by the time you’re reviewing your cycle, the world has moved past most of what you committed to.

One-week cycles force tighter scoping. You commit on Monday, ship through the week, retrospect on Friday. The cadence matches a solo engineer’s natural attention span.

Plan on Monday morning, retrospect on Friday afternoon

The Monday plan:

• Open the backlog
• Pick 5-8 issues that fit one week
• Move them into the current cycle
• Estimate roughly (don’t spend more than 5 minutes total on estimation)
• Close Linear and start working

The Friday retrospect:

• What shipped? Move to done.
• What didn’t ship? Decide: bump to next cycle, or move back to backlog?
• Did anything block that you didn’t see coming?
• Anything you want to remember? Put it in a project note or doc.

These two rituals take 30 minutes total per week. The discipline pays off in shipping rhythm.

Don’t fake-estimate

Linear has estimates (XS, S, M, L, XL or numeric points). For solo work, estimates are noise. You’re estimating yourself; you’ll be wrong; nobody else needs the data.

Either skip estimates entirely or use a binary “this fits in a week” check. That’s the only signal worth tracking.

Use cycle goals, not just issues

Linear lets you set a cycle goal — a one-line description of what you’re trying to accomplish. Use it. “Ship the search feature” or “Get the migration unblocked” or “Investigate the performance complaint.”

The goal is more useful than the issue list because it tells future-you what cycle this was. Six months later, the goal is the searchable artefact.

Treat cycles as autobiography, not commitment

The mental model that breaks for solo cyclists: treating the cycle as a contract. You’ll over-commit, miss things, feel bad. Stop.

Instead, treat the cycle as a record. “This week I worked on these things.” Some shipped, some didn’t. The point isn’t hitting the commitment exactly; it’s having a regular checkpoint for honest self-assessment.

What to skip

Linear has a lot of features designed for team workflows. Solo, you can skip:

• Triage — you’re the only one assigning, so just assign
• Statuses beyond Todo / In Progress / Done — solo flows don’t need In Review or Blocked
• Projects (the M-level grouping) unless you have a genuine multi-cycle initiative
• Roadmap for a solo engineer is a backlog, not a roadmap
• Automations — most solo workflows are simpler than the automation pays back
• Cycle estimates and burn-down charts — noise at solo scale

The most common mistake solo Linear users make is configuring it like a team. The opposite is right: strip configuration down until it matches what you’re actually doing.

The Linear features that genuinely earn their keep solo

A few features that solo work actually benefits from:

• The keyboard-first UX — you can run Linear without a mouse, and that compounds over a year
• The single-issue view for deep work — Linear stays out of your way once you’re on an issue
• The mobile app for capturing ideas without context-switching to laptop
• GitHub PR integration — link issues to PRs, see status, close issues on merge
• Sub-issues for breaking down medium tasks into half-day chunks

What r/Linearapp tells you

The community signal on solo Linear use:

• Most solo subscribers admit they “don’t really use Cycles”
• A minority swear by them with workflows similar to the one above
• The recurring complaint is the team-scale feature load (statuses, projects, triage) feels heavy at solo scale
• Pricing concerns occasionally surface — Linear Pro at $8/month per user feels steep for a single-person backlog tracker

The community pattern: Linear users who came from team contexts retain their habits. Linear users who started solo often switch to lighter tools (Things, TickTick, Apple Reminders) within a year.

When to drop Linear entirely

A non-judgmental observation: not every solo engineer needs Linear. If you find yourself opening it once a week and ignoring it the rest of the time, you have evidence that simpler is better. Things, Bear, Apple Notes, or a plain text file all work for solo issue tracking.

Linear earns its keep at solo scale only if you’re using Cycles or the GitHub-integration features actively. Otherwise, the $8/month is buying you nothing.

My personal setup

For TopInsight’s solo development:

• One-week cycles starting Monday
• 5-8 issues per cycle, no estimates
• Single cycle goal in plain English
• GitHub PRs linked to Linear issues, auto-close on merge
• Friday afternoon 15-minute retrospect ritual
• Annual “is this still worth $8/month?” check (so far, yes — but it’s close)

The honest test: Linear feels worth it because the Friday retrospect ritual genuinely makes me a more honest about what I’m shipping. If I lost that ritual, I’d drop Linear.

For broader productivity tooling, see our Raycast Pro review. For the team-scale alternative to Linear, Notion / Linear comparisons cover the broader picks (forthcoming).