It’s Monday morning and a client onboarding that “always worked” just failed. A new client didn’t get welcome materials, the team scrambled, and you’re on reactive mode for the week. That breakdown didn’t happen overnight - it crept in. I learned in demolition that regular inspections catch the tiny failures before they accumulate into catastrophe. The same habit saves most businesses from painful, expensive surprises. (More on the routine in The 15‑minute Friday.)
Do one short ritual every Friday to keep your systems healthy. The Weekly Review is a maintenance habit that surfaces slow decay, reveals small leverage changes, and prevents emergencies. Here are the five questions I use (copy this script and paste into a note for Friday):
The 5‑Question Weekly Review
1) What’s working better than expected?
Which systems saved time or created fewer errors this week?
2) What’s breaking down or slowing down?
Where did tasks get stuck, slow, or need intervention?
3) What’s missing or unclear?
Where did teammates ask “how do I…?” or need guidance?
4) What’s changed in our environment?
New tools, roles, customer expectations, or market shifts?
5) What’s one small improvement you can make next week?
The smallest, highest‑leverage change you can implement Monday.
(These are the exact review prompts and rationale I use with clients - pulled from The 15‑minute Friday.)
Implementation protocol — how to make it stick
Block 15 minutes on Friday (e.g., 3:00 PM). Put it on your calendar now.
Open a simple doc and run the five questions, top to bottom.
Pick one improvement and schedule a 10‑minute slot on Monday to implement it.
Track the outcome next Friday: Did the tweak move the needle?
Pro tips (from practice)
Don’t overthink - go with first instincts. Small changes compound.
Focus on patterns, not isolated incidents. One late ticket is noise; consistent slippage is a signal.
If nothing stands out, the improvement might be documentation: write a 2‑sentence SOP for the friction point.
Make the review collaborative once a month: gather a quick team input round to catch blind spots faster.
Quick example (what this saves)
A client noticed their calls were running 15 minutes long during a weekly review. That looked small - until they realized it cost 5 hours per week. One small change (add a 5‑minute agenda and buffer) fixed it, saving the team hours and preventing downstream delays. (Example from The 15‑minute Friday.)
One‑page copy you can paste into a planner
Friday Weekly Review (15 min)
Q1: Wins? — __
Q2: Breakdowns? — __
Q3: Missing/Unclear? — ___
Q4: Changes this week? —
Q5: One small improvement (schedule on Monday) — __
Why this matters
Systems don’t die suddenly - they decay. A brief weekly inspection is your early‑warning system. It’s maintenance, not more work. Over months, those 15‑minute reviews compound into predictable delivery, fewer surprises, and a business that scales without constant firefighting. This approach pairs perfectly with the continuous improvement ideas in the RAIL loop and the SCALE framework you’ve used with clients. See the RAIL concept for maintaining systems in the previous newsletter “The System Behind Every Successful System” and the SCALE program where I walk clients through this work in “The Chaos Ceiling.”
Try the Weekly Review for four Fridays. If your review surfaces a bottleneck that’s costing time, money, or sleep, I’ll help you turn that bottleneck into a reliable system. Apply to the 1:1 program here and we’ll see if we’re a fit to fix it together.
Fifteen minutes a week beats fifteen crises a quarter. Block the time, run the five questions, and tell me what you find.