Linear Team Rituals
Tools work best when a team uses them in a steady rhythm. Rituals are short, regular routines that keep planning, progress, and learning visible. Linear supplies the data for each routine, so meetings stay brief and focused.
The Weekly Rhythm
MON TUE-THU FRI CYCLE END Planning Daily check-in Progress update Review + Retro │ │ │ │ Pick issues Update status Post summary Compare plan for cycle Flag blockers Clear triage with results
Everyday Comparison
A sports team follows a weekly pattern. Players review the game plan, practice daily, rest before the match, and study the replay afterward. The routine builds skill because it repeats. Software teams gain the same benefit from steady rituals.
Cycle Planning
Hold planning at the start of each cycle and limit it to 45 minutes.
- Open the backlog sorted by priority.
- Review the carry-over issues from the last cycle.
- Compare the planned estimate total with recent velocity.
- Pull in issues until the load matches capacity.
- Confirm that every issue has an assignee.
Daily Check-In
Many teams replace spoken stand-ups with a quick scan of the board. Each person updates statuses before the day starts. A short written message covers blockers. Teammates read the active cycle view and help where needed.
| Question | Where to Find the Answer in Linear |
|---|---|
| What am I working on? | My Issues view |
| What does the team finish this week? | Active cycle view |
| What blocks us? | A saved view filtered for blocked issues |
| What needs review? | The triage inbox and review statuses |
Friday Update
Project leads post a short update on each active project. Write three lines: progress, risks, and plans for the next week. Leaders read these updates in minutes and skip status meetings.
Cycle Review
Review the finished cycle with the cycle summary page. Look at four numbers: completion rate, scope added, velocity, and carry-over. Celebrate finished work and discuss the causes behind misses.
Retrospective
Hold a 30-minute retrospective after the review. Use three columns on a shared board.
KEEP DOING STOP DOING START DOING ─────────── ────────── ─────────── Small issues Late scope changes Estimate risky work early Friday updates Vague bug reports Use bug templates
Choose one or two actions and create issues for them. Assign owners so improvements actually happen.
Keep Rituals Healthy
Time-Box Every Meeting
Set a timer and end on time. Short meetings earn attendance.
Use Data Instead of Memory
Open Linear views during discussions. Facts end long debates.
Adjust Often
Drop rituals that no longer help. A routine should serve the team, and the team should not serve the routine.
Adapt Rituals for Remote Teams
Distributed teams span time zones. Replace live meetings with written updates where possible. Record planning sessions for people who cannot attend. Rotate meeting times so the same colleagues do not always join late at night.
Write Clear Notes
Capture decisions in issue comments or project updates. Written notes outlive meetings and help new members catch up quickly.
Measure Ritual Health
Ask the team every quarter whether each ritual still helps. A simple vote works: keep, change, or drop. Teams that review their routines avoid empty meetings.
Signs of a Healthy Rhythm
Meetings end on time, decisions become issues with owners, and people know their next task after every session. Carry-over rates fall, and surprises become rare.
Signs of Trouble
Attendance drops, updates arrive late, and the same problems appear in every retrospective. Treat these signs as feedback. Simplify the routine or change its format.