Skip to content
Keel
Blog

Notes from a team that ships every week.

How we plan, triage and build Keel, written by the people doing it. One post a month, roughly, when there is something worth saying.

LatestProduct

Triage is a habit, not a meeting

Keel Assist now suggests a label, a priority and an owner for every new report. Here is why it never changes anything on its own, and what 212 teams taught us while we built it.

Priya RamanKeel Assist · 7 min read
  1. NOTE-30Engineering38 milliseconds: where the time goes in a Keel actionChanging a status in Keel takes 38 ms at the median, on every client. A walk through the local store, the render and the sync queue that make that number hold.Malik Osei · 9 min read
  2. NOTE-29MethodWe cancelled the planning meeting. The cycle plans itself.Two-week cycles, automatic rollover and a capacity number everyone trusts. How Keel plans Cycle 24 without anyone in a room, and what we do on Monday morning instead.Noor Visser · 8 min read
  3. NOTE-28ProductEvery shortcut is a promiseKeel answers to 64 shortcuts. We removed 19 to get there. On choosing keys people can guess, the G-then pattern, and why a shortcut that sometimes fails is worse than none.Ines Bakker · 6 min read
  4. NOTE-27MethodWrite the Friday update from the workStatus updates rot because they are written from memory. Since 4.10, Keel drafts each project's update from what moved that week. What goes in, what we leave out, and how leads edit it.Camille Roy · 5 min read
  5. NOTE-26CompanyTwo harbours, one trackerKeel is eleven people in Rotterdam and Montréal, six hours apart. How we use three shared hours a day, why we write everything down, and the one ritual we kept.Théo Gagnon · 6 min read

New posts and releases, by email.

Every other Tuesday, with the changelog. Unsubscribe with one click.

Read less about it. Try it.

Import your issues in minutes and plan your first cycle before lunch.