Why Monday, Wednesday, Friday — and not daily or weekly
A short argument for the Mon/Wed/Fri cadence as the minimum viable rhythm for small teams. Fewer touchpoints lose signal; more cost focus.
There is a defensible case for running a daily standup. There is a defensible case for running a single weekly one. We pick a different fight: three touchpoints a week, on Monday, Wednesday, and Friday.
The argument is simple. Mon/Wed/Fri is the lightest cadence that still catches problems while they are cheap to fix.
The cost of daily
Daily standups trade a small recurring cost (fifteen minutes a day, per person) for fast detection. If your team ships multiple times a day, to production, with real blast radius, this trade often makes sense. Most small teams do not work like that.
For a team of 3 to 20 shipping on a normal weekly rhythm, a daily meeting is theater. The signal to noise is bad. People say "yesterday I did X, today I will do Y, no blockers," which is a status update that nobody needed to write down out loud. The blockers that matter do not surface in thirty seconds of speaking time, and the ones that do can wait until Wednesday.
Daily also costs more focus than it advertises. It is not the fifteen minutes; it is the fragmented morning around it.
The cost of weekly
Running a single weekly touchpoint — usually a Friday recap or a Monday plan — is the opposite failure. The signal is there, but it arrives too late.
Monday plans without a mid-week check catch problems on Friday, four days after they happened. Friday reviews without a Monday plan are reports, not rhythm. Both shapes let small problems run for most of the week before anyone notices.
A week is a long time when something is quietly off.
Why Mon/Wed/Fri
Two days between touchpoints is the sweet spot. Short enough that a stuck person cannot hide for long, long enough that the team is not performing standup for its own sake.
- Monday sets intent. Focus, goals, owners.
- Wednesday checks reality against intent. What moved, what changed, what stuck.
- Friday closes the loop. What shipped, what didn't, what rolls over.
Nothing happens on the other days except the work. Saturday and Sunday, ideally, nothing at all.
Why exactly those days
The days are not magic. Some teams run Tue/Thu or Mon/Wed/Thu. The three things that matter are:
- Monday (or the team's first working day) has to be a plan. You cannot optimize a week that has no shape.
- A mid-week checkpoint has to sit far enough from Monday to show progress and far enough from Friday to act on what is stuck.
- The last working day has to be a review. Without it, Monday starts from a cold context.
Public holidays, four-day weeks, async teams across timezones — all fine. Move the touchpoints. The cadence is a rhythm, not a law.
The signal this catches
The specific thing Mon/Wed/Fri catches, that daily and weekly both miss, is the slow-go-sideways. A project that was fine on Monday, felt fine on Tuesday, and then around Wednesday morning someone quietly realised the approach is wrong but has not said it yet. Wednesday check-in gives that realisation a forum. By Thursday it is a solved problem. By Friday it is a wrap-up line in the review.
Without the mid-week check, that same realisation hits at Friday review. Now it is a lost week.
If you try this
Run it for three weeks before judging. The first week will feel like ceremony. The second week will feel like process. By the third week most teams stop scheduling it and it just happens.
If it doesn't, the rhythm is not the problem. Usually the weekly focus is too vague, or Wednesday check-ins are long-form status reports instead of three-line updates. Shrink those, and the rhythm takes over.