The Meridian method
Principles for building products
Meridian is opinionated where it helps and flexible where it should be. These are the habits it is built around.
- 01
Write issues, not tickets
An issue is a short note about a problem worth solving. Keep it small enough to finish in a few days, and say why it matters.
- 02
Plan in cycles
Two weeks is long enough to ship and short enough to change course. What does not get done moves on, without ceremony.
- 03
Projects have a finish line
A project groups issues behind an outcome, a lead and a date. Its Gantt shows the plan; its updates tell the truth about it.
- 04
Say how it is going
A weekly update with a health — on track, at risk, off track — beats any status meeting.
- 05
Triage, then commit
Requests land in triage. Someone decides : accept, merge as a duplicate, or decline with a reason.
- 06
Speed is a feature
When every action is instant, people keep the tracker up to date. That is the whole game.