Skip to content
Keel
Customers · Brightloom

Brightloom cancelled its Monday planning meeting. Cycle time halved.

Four squads, one Monday meeting that ate 90 minutes of 26 people, and a cycle time stuck at five days. Ten months on Keel later, the cycle plans itself and nobody has asked for the meeting back.

Median cycle time, days2.4 days

Oct

JanOct
median cycle time
0.0 days
Before: 5.1 days before Keel
in planning meetings each week
0 min
Before: 90 min × 26 people
Friday updates in a row, drafted by Keel
0
Before: a slide, when someone remembered
“We cancelled our Monday planning meeting in March and nobody has asked for it back. The cycle plans itself, the roadmap updates itself, and our median cycle time went from 5.1 days to 2.4.”
Mara LindqvistHead of Product, Brightloom

A meeting that planned last week

Brightloom builds the course platform that 300 vocational schools teach on: timetables, coursework, grades and the parent app. Twenty-six people work on it in four squads, and until January every one of them spent Monday morning in the same room, planning the week.

“The meeting was 90 minutes on a good day,” says Mara Lindqvist, who runs product. “Half of it was reading tickets aloud to find out what had happened since Friday. By the time we agreed on a plan, it was already describing last week.”

Their old tracker held 3,400 issues across three projects nobody trusted, and a spreadsheet held the real plan. Median cycle time, from started to shipped, sat at 5.1 days.

Moving in a Thursday afternoon

The importer brought over all 3,412 issues, comments and attachments in 11 minutes. The team spent the rest of the afternoon archiving: 1,180 issues nobody had touched in a year went to the archive in one bulk edit (select with X, then ⌘⌫).

  • Week 1: issues only, no cycles. Everyone learns C, S, P, A.
  • Week 3: two-week cycles for all four squads, starting Mondays at 09:00, capacity from the last three cycles.
  • Week 5: Burrow connected. Branches move their issues; nobody drags cards to Done any more.
  • Week 8: the Monday meeting is cut to 30 minutes, then, in March, cancelled.

What replaced the meeting

Nothing, mostly. Keel fills each cycle by priority up to the squad’s capacity on Friday evening, and carries over what is left. Squad leads glance at the plan on Monday morning and swap an issue or two in the cycle view. Questions go to the issue, not to a room.

“The first Monday without the meeting, three people asked if it had been moved. The second Monday, nobody asked.”

Mara Lindqvist, Head of Product

On Fridays Keel drafts each project’s update from what merged that week, and Mara posts it to the leadership channel in Parley. Thirty-eight weeks in a row, she has edited an average of one line.

The numbers, ten months in

Before KeelOctober 2026
Median cycle time5.1 days2.4 days
Planning meetings90 min a weeknone
Issues carried over per cycle143
Open issues3,412612

Smaller issues explain most of the cycle-time drop. With sub-issues and a two-week horizon, squads stopped filing “Rebuild the timetable” and started filing the eight pieces it is made of.

More stories

Plan like Brightloom, starting Monday.

Import your issues in minutes. Turn on cycles when the team is ready, not before.