Skip to content
The Owner's Friday Review Routine: What to Look at for 20 Minutes

The Owner's Friday Review Routine: What to Look at for 20 Minutes

Yaroslav Maxymovych· with AI assistance11/9/202683 views6 min read

TL;DR

  • •Spend 20 minutes on Friday reviewing Plan vs Fact vs Gap across your key workflows.
  • •Look for three signals: stalled decisions, recurring blockers, and work that vanished between handoffs.
  • •Use the review to decide what needs your attention next week — and what does not.

If your Friday afternoon feels like a blur of open tabs and half-remembered conversations, you are not seeing the week clearly. You are feeling it.

What to Look at in Your Friday Review

1. Which commitments from Monday actually closed?

Start with the plan you set at the beginning of the week. Not the aspirational version — the real one. Look at the top three to five operational commitments your team made. Did they ship? If not, why?

This is not about blame. It is about seeing whether your team’s word on Monday means anything by Friday. If commitments keep rolling over without explanation, you have a visibility problem, not a motivation problem.

2. Where did work get stuck between people?

Handoffs are where most operational friction lives. Sales to delivery. Product to engineering. Support to product. Look at the things that were “almost done” on Monday and are still “almost done” on Friday.

A task that sits in limbo for five days usually means someone is waiting on someone else, and nobody owns the follow-up. That is your gap.

3. What blockers appeared more than once?

One-off blockers are noise. Repeated blockers are systemic. If the same approval, the same tool, or the same person shows up as a blocker two weeks in a row, that is the thing to fix next week — not the individual task.

4. What did your team figure out without you?

This is the positive signal. Look for decisions your team made and executed without escalating to you. If that list is empty, you are the bottleneck. If it is growing, your team is operating.

Manager Scan (2-Minute Digest Example)

Here is what a Friday review output looks like when you run it through Plan → Fact → Gap:

  • Sales: Plan — 8 discovery calls booked. Fact — 5 booked, 3 rescheduled by prospects. Gap — outreach list was stale; need updated ICP criteria before next week.
  • Product: Plan — ship onboarding checklist v1. Fact — shipped, but only after two days of QA rework. Gap — QA criteria were undefined at kickoff.
  • Support: Plan — reduce average first response to under 4 hours. Fact — average was 5.2 hours. Gap — weekend coverage gap; no owner assigned for Saturday tickets.
  • Ops: Plan — vendor contract signed by Thursday. Fact — still in legal review. Gap — no internal owner drove the signature.

Each line takes ten seconds to read. The whole scan takes two minutes. The decisions it triggers take the remaining eighteen.

Copy/Paste: Friday Review Template

# Friday Review — [Date]

## Week commitments vs reality
| Commitment | Owner | Status | Gap note |
|------------|-------|--------|----------|
|            |       |        |          |

## Blockers that appeared more than once
- 

## Handoffs that stalled
- 

## Decisions the team made without me
- 

## Next week: one thing I need to unblock personally
- 

Micro-Case (What Changes After 7–14 Days)

A founder of a 40-person services company started running this Friday review instead of his usual end-of-day scroll through Slack. Within two weeks, he noticed that his operations manager was repeatedly waiting on the same client approvals before projects could move to delivery. The gap was visible every Friday. He assigned one person to own client follow-ups, and the approval lag dropped by roughly half. The change did not come from a new tool or a meeting. It came from looking at the same data on a fixed schedule.

Note on this case: This example is illustrative — based on typical patterns we observe with companies of 30–500 employees, not a single named client. Specific numbers are rounded approximations of common ranges, not guarantees.

Tool tip (AiAdvisoryBoard.me): The Friday review works best when it is grounded in what your team actually reported during the week, not in what you assume happened. Our Plan → Fact → Gap operating layer surfaces those reports automatically, so your 20-minute review starts with real data instead of memory. See how the 7-day diagnostic works.

FAQ

Do I need a dashboard for this? No. A shared document, a few exported reports, or even a well-kept email thread is enough for the first month. The discipline matters more than the tool.

Who should attend the review? Just you, ideally. If you involve the whole team, it becomes a status meeting. If you do it alone, it becomes a decision session. Share the output, not the process.

What if nothing changed this week? That is the finding. A week with no movement on core commitments is a signal that something is stuck — usually before anyone feels comfortable saying it out loud.

How is this different from a weekly team meeting? Team meetings are for alignment. This review is for your own calibration as the owner. You are checking whether the business is doing what you think it is doing.

Conclusion

Twenty minutes on Friday is enough to see whether your company is moving in the direction you set on Monday. The goal is not to catch people falling behind. It is to catch the business drifting before the drift becomes expensive.

Pick one operational area, run the review this Friday, and note the gap that surprises you most.

If you want a system that surfaces the Plan → Fact → Gap automatically — every day, across the company — see how the 7-day diagnostic works. https://aiadvisoryboard.me/?lang=en

Frequently Asked Questions

Read with AI

Open this article in your assistant — it will summarize it and help apply it to your company.

Show the prompt

Read the article https://aiadvisoryboard.me/blog/owner-friday-review-routine-20-minutes-weekly-check.md and summarize the key points. Then ask me about my company (industry, team size, what takes the most time) and explain which ideas from the article apply to us and where to start.

More on this topic
Owner Visibility Before AI: Why You Need a Baseline First →

The pillar guide for "Owner Visibility Before AI" linking every article in this cluster.

Yaroslav Maxymovych
Author
Yaroslav Maxymovych
Founder & CEO, AI Advisory Board

Implements AI agents in companies and teaches founders and their teams to work with them — through courses and corporate programs.

This article was prepared with AI assistance, based on Yaroslav Maxymovych's methodology and materials. Spotted an inaccuracy — let us know via the form below.

For companies

Your company's first 3 AI automations — in 2 weeks

A corporate AI-transition program: 4 live sessions with your team plus a video course for every employee. Up to 20 people for one fixed price. If it doesn't work — money back.

Working automations in 2 weeks
Up to 20 employees, one price
Money-back guarantee
See the program & priceIt's the program page, not a checkout — a 2-minute read
Newsletter

AI adoption resources — one email

Leave your email to receive a welcome email with blog resources. There is no regular newsletter at present

No spam. Unsubscribe anytime.