Linear Core Concepts
Linear organizes software work with a small set of objects. Each object answers one question: who does the work, what the work is, when it happens, and why it matters. Learning these objects early makes every later feature easy to follow.
The Big Picture
Every object sits inside a larger one. The workspace holds everything, and the issue is the smallest unit of work.
WORKSPACE (your company) │ ├── TEAM: Engineering │ ├── Cycle: Week 1 - Week 2 │ ├── Issue ENG-101: Fix login error │ └── Issue ENG-102: Add dark mode │ ├── TEAM: Design │ └── Issue DES-14: New icon set │ ├── PROJECT: Mobile App Launch (uses issues from many teams) │ └── INITIATIVE: Grow Mobile Users (groups several projects)
Workspace
The workspace represents your whole organization. It stores teams, members, projects, and company-wide settings. Most companies run one workspace. Your workspace name forms the web address, such as linear.app/your-company.
Team
A team is a group of people who ship work together. Each team owns its issues, workflow statuses, labels, and cycles. Linear gives every team a short key, and that key prefixes each issue number. The key ENG creates issues named ENG-1, ENG-2, and so on.
Issue
An issue is a single piece of work. A bug report, a feature request, and a small chore all become issues. Each issue carries a title, a description, a status, an assignee, and a priority.
Project
A project collects issues that deliver one outcome with an end date. Projects can include issues from several teams. A launch of a mobile app fits a project well.
Cycle
A cycle is a fixed time block, usually one or two weeks. A team picks issues for the block and works through them. Cycles give the team a steady planning rhythm.
Initiative
An initiative sits above projects. It tracks a large company goal, such as growing the mobile audience. Several projects can feed one initiative.
Everyday Comparison
Think of a school. The comparison below maps each Linear object to a school activity.
| Linear Object | School Comparison | Question It Answers |
|---|---|---|
| Workspace | The whole school | Where does everything live? |
| Team | One class | Who works together? |
| Issue | One homework task | What needs doing? |
| Cycle | The weekly timetable | When does it happen? |
| Project | The science fair | Which result are we building? |
| Initiative | The school-wide goal of better results | Why does it matter? |
How the Objects Work Together
Follow one real scenario. A company wants a faster checkout page, so a leader creates the initiative "Increase Sales". The product manager adds the project "Checkout Redesign" under that initiative. Engineers and designers write issues for each task. Each team pulls those issues into its next cycle.
Initiative: Increase Sales
│
▼
Project: Checkout Redesign
│
├──► Issue DES-21 (Design team) ──► Cycle 12
└──► Issue ENG-88 (Engineering) ──► Cycle 12
Work flows from the top goal down to daily tasks. Progress flows back up. When engineers close issues, the project bar fills, and the initiative bar follows.
Common Beginner Mistakes
- Creating a new workspace for each team. One workspace lets teams share projects and see each other's work.
- Using projects as folders. A project needs an outcome and an end date.
- Skipping cycles. Without a time block, work drifts and plans lose shape.
- Writing giant issues. Smaller issues move faster and show progress sooner.
Quick Check
Pick any task from your own work and label it with these objects. Decide which team owns it, which project it supports, and which cycle fits it. This small exercise builds the habit of thinking in Linear's structure.
Naming Tips for New Workspaces
Choose clear names from the start. Use a short team key of two to four letters that people recognize at a glance. Name projects after outcomes, such as "Checkout Redesign", and avoid vague words like "Improvements". Descriptive names help new teammates navigate without a guide.