What Should I Do in the First Hour of the Week?

None of that email work was wrong. All of it would've happened anyway, because the week supplies that work whether you start early or not.

So what should the first hour actually be? Read three things and decide one. Last week's exceptions, four numbers, and the one commitment you made last week, then pick a single change and write it down where the team can see it.

The hour disappears because starting work is comfortable and reading isn't, and an inbox always has something to start.

Nothing gets started in the first hour

That's the rule, and it's the only thing that makes this work. No replies, no fixes, no calls, no starting anything.

Read-only sounds precious until you try it. The first two weeks feel like a waste, because reading produces nothing you can point at by 9am.

What it does produce is a decision made from evidence instead of from whatever landed most recently. Start inside the inbox and you spend the week on whoever emailed hardest.

High-reliability operations run a version of this. Their weekly read is a divergence scan against plan, not a status meeting: nobody's reporting, everybody's comparing.

Three reads, about six minutes each

Time-box them or the first one eats the hour. Whatever's left after is thinking time.

Then the rest of the hour takes no input at all. That's where the decision comes from, and it won't show up while you're still reading.

Owners cut the thinking time first. It's also the part that carries the hour, since twenty minutes of no new information is the only unscheduled thinking most operators get all week.

Of the three, the exception read is worth the most. A rule broken twice by different people in one week is a rule that doesn't match the work anymore, and that decay has a mechanism worth understanding before you rewrite anything.

Pick your four numbers once and keep them. The case for a short list is the five numbers rather than twenty, and it holds at four. (If your numbers live in three systems and a shoebox, sort out the dashboard question before you start this habit, because six minutes won't cover it.)

One decision, one sentence

At the end of the hour you write one sentence. It's the week's change, and it names a thing, a person, and a date.

Just one. Three decisions on one Monday turns into zero by Friday, because none of them gets the follow-through that makes a change stick.

Say the first decision is that route-swap requests under two hours don't come to you anymore. One sentence on the whiteboard, and it removes about nine interruptions a week.

Put it where the team can see it, because a decision nobody can point at quietly expires.

What it catches

It catches divergance early, and early is the only cheap time to catch anything. A rule broken twice in a week costs a sentence to fix. The same rule broken for two months costs a retraining.

It also catches the commitment that quietly died. Most owners can't tell you, without looking, what they decided to change three Mondays ago, and the third read makes that visible.

Be honest about what it won't do, though. It doesn't replace a monthly review, it doesn't manage anybody, and it won't fix a business where the owner's the only person allowed to decide anything.

And there's an exit-value side. A business where the owner is the early-warning system runs on a person, and buyers discount a business that runs on a person.

The weekly hour and the monthly review do different jobs: weekly catches divergence, monthly catches drift. Run only one and you're missing half the picture.

A buyer runs their own version of this scan, and it's not comfortable. What buyers ask your employees is the diligence form of the same question, pointed at whether the business matches its own description.

Next Monday, block 60 minutes before anybody else is working. Read three things, touch nothing, and write one sentence on the board.

If you want that sentence aimed at whatever's really dragging the business, the Keystone diagnostic is meant for that, though Keystone is closed for now while we finish building it. Join the waitlist at https://app.trykeystone.io.

Once it's open, the diagnostic is 18 questions and about four minutes. It returns three scores and your value range with the most likely figure locked, calibrated against 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records.

You can start the weekly hour on Monday. Building what it reads from (the exception log, the four numbers in one place, the standing cadence underneath) is months of work, and a Full Operations Modernization installs that layer in a live system your team runs. Scoping starts on the Full Operations Modernization page.

FAQ

What should a business owner do in the first hour of the week?

Read three things and decide one: last week's exceptions, four numbers, and the single commitment you made last Monday. Keep the hour read-only, then write one sentence naming the week's change, its owner, and its date.

What numbers should I check every week?

Four is enough: cash position, work booked ahead, jobs closed out and invoiced, and one number specific to your trade. A longer list turns a six-minute read into a report nobody finishes.

Why should the first hour be read-only?

Because starting work is comfortable and reading is not, so an unprotected hour always fills with whatever arrived most recently. A read-only hour produces a decision made from evidence rather than from the loudest inbox.

How is this different from a weekly team meeting?

A team meeting is people reporting to each other, while this is one person comparing what happened against what was supposed to happen. The hour has no attendees and its output is a single written decision.