Ship every week. Meet less. Write it down once.
Keel is built around a rhythm we have watched work in 1,900 teams: small issues, two-week cycles, one triage shift a day and a Friday update nobody has to write. Take the parts you like.
Six principles
- METHOD-1 Adopted
Small issues ship. Big issues wait.
If an issue will take more than three days, it is a project with sub-issues. Two-day issues finish inside a cycle; two-week issues roll over until somebody splits them.
- METHOD-2 Adopted
Plan from capacity, not from hope.
A cycle holds what the team finished in its last three cycles, give or take 10%. Keel fills it by priority and stops. The rest waits, visibly.
- METHOD-3 Adopted
Every report gets an owner the same day.
One person per team takes the triage shift each morning. Reports are accepted, merged or declined before lunch. Nothing sits in a shared inbox.
- METHOD-4 Adopted
Status comes from the work.
Branches move issues, merges close them, projects measure themselves. If you are asking someone for a status, a tool is not doing its job.
- METHOD-5 Adopted
Write it down once, where the work is.
Decisions go in the issue, not a chat thread. The Friday update is drafted from the week’s issues, so the history is already written.
- METHOD-6 Adopted
Rest on purpose.
After six cycles, a cooldown week with nothing planned. Fix the papercuts, explore, delete the backlog you will never do.
Fifty minutes of meetings. The rest is work.
Click through a real week of the Halyard team. What the team does is short; what Keel does without being asked is the long list.
Monday · Cycle 25, week 1
The cycle opens itself
Leads glance at the plan over coffee and swap an issue or two. That is the planning.
before Keel: 4 h 15 min a week, per lead
Filed, done, not missed.
What teams tell us they stopped doing in their first two months, and what replaced each one.
of meetings back every week, per lead
- AM
Monday planning
MTG-1 · was 90 min, whole team
replaced by Capacity-based cycles that fill themselves
- SP
Mid-cycle check-in
MTG-2 · was 45 min, leads
replaced by The burn-up and its projection
- RD
Thursday status sync
MTG-3 · was 60 min, 12 leads
replaced by Health measured from the work
- JK
Bug triage meeting
MTG-4 · was 30 min, twice a week
replaced by A 20-minute triage shift, one person
The numbers we would start with.
Defaults, not law. Every one is a setting in Keel, per team.
- cycle length
- 2 weeks
- Long enough to finish something real, short enough that a bad plan costs little.
- per issue
- ≤ 3 days
- Anything bigger becomes a project with sub-issues.
- issues in progress per person
- 2
- Finishing beats starting. Keel shows a soft warning at three.
- from report to owner
- 1 day
- The triage shift rotates daily; nothing waits for a meeting.
- cycles is a cooldown
- 1 in 7
- Planned rest, so the other six can run at full speed.
Start with one team and one cycle.
Two weeks is enough to know. If the Monday meeting comes back, nothing is lost: it is all still in the issues.