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

Your week starts at a keyboard and it is already gone

A 9-person pest-control company at about $1.6M in revenue has an owner who sits down at 7:30 on Monday. By 8:40 he has answered 14 emails, rescheduled two routes, and approved a parts order.

None of that was wrong. All of it would have happened anyway, because the week supplies that work whether or not he starts early.

What a business owner should do in the first hour of the week is read three things and decide one. Read last week's exceptions, read four numbers, read the one commitment you made last week, then pick a single change and write it down where the team can see it.

The reason the hour disappears is not discipline. Starting work is comfortable and reading is not, and an inbox always offers something to start.

The first hour is read-only

The rule is absolute and it is the only thing that makes the hour work. No replies, no fixes, no calls, no starting anything.

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

What it produces is a decision made from evidence rather than from whatever arrived most recently. An owner who starts inside the inbox spends the week on whoever emailed hardest.

There is a version of this in high-reliability operations. The weekly read there is a divergence scan against plan, not a status meeting, and the difference is that nobody is reporting and everybody is comparing.

An owner who starts inside the inbox spends the week on whoever emailed hardest.

The three things you read, and the time each gets

Time-box these three or the first read will eat the hour. What is left after them is thinking time.

Then the rest of the hour takes no input at all. This is where the decision comes from, and it does not arrive while you are still reading.

The thinking time is the part owners cut first and the part that carries the hour. Twenty minutes of no new information is not idleness, it is the only unscheduled thinking most operators get in a week.

The exception read is the highest-value of the three. A rule broken twice by different people in one week is a rule that no longer matches the work, and that decay has a mechanism worth understanding before you rewrite anything.

Which four numbers to use is a decision worth making once and keeping. The case for a short list over a long one is the five numbers rather than twenty, and the argument holds at four.

One decision at the end, and only one

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

One is the number. Three decisions in one Monday produces zero by Friday, because none of them gets the follow-through that makes a change stick.

The pest-control owner's first decision was that route-swap requests under two hours no longer came to him. It took one sentence, it went on the whiteboard, and it removed about nine interruptions a week.

Write it where the team can see it, not in your notes. A decision the team cannot point at is a decision that quietly expires.

Three decisions on one Monday produces zero by Friday.

Reading four numbers weekly only works if those numbers are somewhere you can see them in six minutes. If yours live in three systems and a shoebox, the dashboard question comes before this habit does.

What the hour catches that the rest of the week does not

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

It also catches the commitment that quietly died. Most owners cannot say, without looking, what they decided to change three Mondays ago, and the third read is what makes that visible.

Be honest about what it does not do. It does not replace a monthly review, it does not manage anyone, and it will not fix a business whose problem is that the owner is the only person allowed to decide anything.

There is an exit-value side, and it is the same one as always. A business where the owner is the early-warning system is a business that runs on a person, and on a $300,000-SDE business the gap between that and an owner-light operation is $555,000 on identical earnings.

The weekly hour and the monthly review do different jobs. Weekly catches divergence, monthly catches drift, and running only one of them leaves half the picture.

A buyer runs a version of this scan too, and theirs is uncomfortable. What buyers ask your employees is the diligence form of the same divergence question, aimed at whether the business matches its own description.

Block 60 minutes before anybody else is working, and read three things without touching anything. Then write one sentence on the board.

The free Keystone diagnostic is 18 questions and about four minutes. It returns three scores and an estimated sale price, calibrated against 10 years of BizBuySell Insight Reports and 1.6M+ SBA 7(a) loan records, so the decision you write on Monday is aimed at the thing actually dragging.

Get your three scores and an estimated sale price, free, at https://app.trykeystone.io.

A weekly hour is something you can start next Monday. Building what it reads from, the exception log, the four numbers in one place, the standing cadence underneath it, is months of work.

A Full Operations Modernization installs that layer in a live system your team runs. The Full Operations Modernization page is where scoping begins.

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.