Most learning rhythms are designed during a good month. Someone is enthusiastic, the calendar has room, and the first session goes well. The design question that actually matters is different: what happens to this in the month when a legislative deadline lands, two people are out, and a complaint needs a response by Friday.
A ninety-minute quarterly session does not survive that month. It gets moved, then moved again, and the second move is usually the end. Twenty-five minutes attached to a meeting that already exists often does survive, because it is small enough to keep and it does not require anyone to find a new hour.
The second design question is who it belongs to. A rhythm carried by one enthusiastic person is a personal practice that other people attend. It ends when that person moves, goes on leave, or gets tired — and the team learns, incorrectly, that this kind of thing does not last here. Rotating the host, with a short outline anyone can follow, is the difference between a practice and a person.
The third question is who the schedule was built around. A single slot that suits full-time day staff reads as neutral and is not. Part-time colleagues, people on early or late hours, staff with caregiving at midday, staff in the field, and anyone who needs time to process before speaking are all filtered out by a choice nobody made deliberately. Offering one way to take part and calling it fair because it is the same for everybody is the Minimization pattern in its most ordinary form.
