Linear earned its reputation by being faster than Jira. But the moment teams grow past ~30 engineers, the same teams that picked Linear for its simplicity start asking for roadmaps, planning, and quarterly views. Linear’s answer: Initiatives and Roadmaps.
Done right, they keep planning lightweight. Done wrong, they recreate Jira inside Linear. This guide is how to do them right.
The Three-Layer Hierarchy
Linear’s planning model has three layers. Knowing what goes at which layer is the entire game.
- Initiative — A multi-quarter strategic theme. “Make onboarding self-serve.” 1-5 active per company.
- Project — A bounded scope of work. “Launch self-serve signup flow.” Has a target date. Has a single PM/EM owner.
- Issue — Day-to-day work. Bugs, tasks, sub-tasks. Lives in a Cycle.
If you only use Issues and Cycles, you have a great execution tool but no strategy view. If you create 50 Initiatives, you have Jira with a black UI.
Right ratios for a 50-person product org:
- 3-5 Initiatives
- 15-30 active Projects
- Thousands of Issues across all time
How Roadmaps Actually Render
The Linear Roadmap view shows Initiatives and Projects on a timeline. You can:
- Group by Initiative, Team, or Lead.
- Filter by status, target quarter, or label.
- Color by health, priority, or milestone progress.
- Embed the roadmap in a Linear Doc or share a read-only public URL with stakeholders.
The public-URL share is the killer feature. Send the URL to your CEO/CFO/board once and never explain “what’s shipping next quarter” again.
Setting Up Roadmaps in 4 Steps
Step 1: Define Initiatives first
Pick 3-5 strategic themes for the next 2 quarters. Each Initiative should be:
- Owned by an exec (VP Product, VP Eng, or CTO).
- Broad enough to span multiple teams.
- Narrow enough to fail or succeed on a yes/no basis.
Bad Initiative: “Improve the product.” Good Initiative: “Reach 60% activation rate for new signups.”
Step 2: Pull Projects under Initiatives
For each Initiative, list the Projects that contribute to it. A Project can roll up to one Initiative (Linear enforces 1:1 today). If a Project genuinely contributes to two Initiatives, pick the dominant one and label the other.
Each Project gets:
- A clear deliverable
- A single owner (one name, not “the team”)
- A target date (not “next quarter”)
- A status: Planned → Started → In Progress → Completed (or Cancelled)
Step 3: Wire Issues to Projects
Every Issue that’s part of a Project should have the Project assigned. Issues without a Project are fine — that’s how bug fixes and small ad-hoc work get tracked — but the Roadmap only shows Project-scoped progress.
A good rule: if it takes more than 5 cycles of work, it needs a Project. If it fits in 1 cycle, just a Cycle assignment is fine.
Step 4: Set Project Health weekly
Project Health (On Track / At Risk / Off Track) is updated manually by the Project lead, ideally on Friday. Linear nudges you if it’s stale. The Roadmap colors Projects by Health, so stakeholders see what’s slipping without opening anything.
This is the entire ritual. Five minutes per Project per week.
Initiatives vs Projects vs Cycles
The three concepts confuse everyone at first. The clarifier:
| Initiative | Project | Cycle | |
|---|---|---|---|
| Time horizon | 2-4 quarters | 4-12 weeks | 1-2 weeks |
| Owner | Executive | PM or EM | Engineer or team |
| Scope | Strategic theme | Deliverable | Throughput unit |
| Visible to | Whole company | Whole product org | One team |
| Created by | Leadership | PM/EM | Auto (recurring) |
If you find yourself making Projects that are 1 week long, those are Cycles. If you find yourself making Initiatives that are 6 weeks long, those are Projects.
Stakeholder Communication Patterns
Three patterns that work:
1. Public roadmap URL in Slack channel topic. Pin a Linear Roadmap share link in #company-product or similar. Stakeholders bookmark it. Status meetings get shorter.
2. Quarterly snapshot in Notion/Coda. Embed the Linear Roadmap into your strategy doc. Add narrative around what changed since last quarter. This is the artifact for board updates.
3. Project updates auto-posted to Slack. Linear’s Slack integration can post Project Health changes to a channel. Engineers don’t have to write status updates — the roadmap is the status update.
Anti-Patterns That Recreate Jira
Watch for these. They all start innocent.
❌ Custom workflows per Project. Linear lets you create custom statuses. Don’t, unless one team genuinely needs them. Consistency across teams is the speed unlock.
❌ Sub-projects. Linear doesn’t have these natively. Resist requests to “just nest one more layer.” Use Milestones inside a Project instead.
❌ Tracking every meeting as a Project. Projects are deliverables, not activities. “Run weekly engineering sync” is not a Project.
❌ Permanent Initiatives. An Initiative that’s been open for 4 quarters is a category, not a strategic theme. Close it or split it.
❌ Mirroring sales/CS workflows. Linear is for product/engineering. Don’t try to track sales pipelines or support tickets here. Use HubSpot / Zendesk and integrate.
When You’ve Outgrown Linear’s Roadmap
Honest signal: when you have 100+ active Projects, 10+ Initiatives, and stakeholders want OKR scoring on top, Linear Roadmaps starts to strain. At that point, you have two options:
- Stay in Linear and accept that Roadmaps is a viewer, not a planning tool. Plan in Coda or Notion, execute in Linear.
- Move planning to a dedicated tool like Productboard or Aha! and treat Linear as execution-only.
Most 100+ person orgs land on option 1. It keeps Linear fast and lets strategy live where strategy belongs — in writing.
Bottom Line
Linear Roadmaps work when you respect the hierarchy: a few Initiatives, focused Projects, weekly Health updates. They fail when teams try to make Linear do everything. Use it for product execution. Plan elsewhere.
See Linear in our directory → Linear on AIToolPick | Linear pricing breakdown → /blog/linear-pricing-2026/