HIVE80lab — Ops notes

Weekly Review Checklist: 30 Minutes to Close the Week Properly

The weekly review is the highest-leverage 30 minutes in a solo or small-team operation, and the most commonly skipped. Not because it's hard — because it's unstructured. "Look at the week" is a task that dies; "check these five things and write three lines" survives. Here's the checklist structure that holds up, and how to keep the ritual alive past week three.

The 30-minute structure

Minutes 0–10: metrics. Look at the numbers that define health — revenue, pipeline, output shipped, support load. The rule: two numbers you can influence this week, not twenty you can't. Write both down with last week's value next to them; the delta is the review.

Minutes 10–20: loose ends. Sweep for three specific kinds of debris: promises made but untracked (reply-due emails, "I'll send that Monday"), stalled items (anything untouched for 7+ days — decide: do it, schedule it, or kill it), and repeat friction (anything that annoyed you twice this week gets either a fix or an SOP note).

Minutes 20–30: next week. Pick the three outcomes that would make next week a success — not ten tasks, three outcomes. Block time for them immediately. Anything not chosen goes to a someday list, explicitly, so it stops leaking attention.

Why weekly and not daily or monthly

Daily reviews blur together — there's rarely enough signal per day for a small operation, and the ritual cost is too high for the value. Monthly is too slow: a problem found at month-end cost you four weeks. Weekly sits at the point where noise averages out but course-correction is still cheap. If your operation runs on fast cycles (e-commerce, launch weeks), a daily five-minute metrics glance plus this weekly review covers both speeds.

Keeping the ritual alive

Attach it to a hard anchor. Friday 4pm or Sunday evening, same trigger every week — reviews scheduled "when there's time" happen twice, total. Cap it at 30 minutes by default; a review that can sprawl becomes a chore you resent. Write something permanent — three lines in a running doc: what worked, what didn't, next week's three. In week 12, that doc is the most honest picture of your operation you'll own. Skip-week rule: miss a week, do a ten-minute version rather than a guilt-driven double session; the goal is cadence, not thoroughness.

Honest limits

A review is a feedback loop, not a plan — if your three outcomes for next week never change, the ritual has become theater; ask what would actually move those numbers. And metrics without baseline data don't mean much: the first month of reviews mostly builds the baseline, so don't panic at week two's numbers. Finally, reviews can drift into anxiety sessions; if a metric can't be influenced this week, it belongs in a monthly look, not a weekly one.

Toolkit to run alongside