One hour a day. That's what it took to write down what the other seven had been spent on.

Before I ran my own companies, I worked for other people's. Almost every manager I had wanted the same thing: a daily report. What did you do today, how long did it take, what's left, what's blocking you. Every evening, before anyone went home, the whole office sat down and wrote it.

Do the arithmetic. One hour out of eight is an eighth of every salary. Over a working year it's more than two hundred hours per person, over a month of full-time work. Paid at exactly the same rate as the hours that actually produced something.

And the daily report is only the bottom of the pile. On Friday the days get rolled up into a weekly summary. At the end of the month, the weeks become a monthly report. Every quarter there's a review with slides, and every year an appraisal where people spend days writing about the twelve months they could have spent working. Each one retells the same work again, for a different reader, at a different length.

Put fairly ordinary numbers on it: an hour a day, two hours on Friday, half a day at the end of the month, a day each quarter, a few days for the annual review. Added together, that's around four hundred hours per person per year. Nearly a quarter of the working year spent describing the other three quarters. In a team of ten, that's two people or more, paid full time to produce nothing but the story of what the others did.

Nearly a quarter of the working year, spent describing the other three quarters.

Then ask who reads them. The manager, maybe, for the first week. After that they pile up, and the monthly one is a copy of the weekly ones, which were copies of the daily ones. Nobody runs a business on fifty reports a week. The report was never information. It was reassurance.

Let me say it plainly. A manager who needs his people to write down what they did isn't managing the company. He's babysitting the staff. And if you're paying someone to ask the people who work to tell him what they worked on, the problem isn't your people. It's that you don't know the business you're running. If you knew it, you'd know what a good day, a good month or a good year looks like without reading about it. You'd see it in what got finished, what got delivered, what got paid.

A manager who needs his people to write down what they did isn't managing the company. He's babysitting the staff.

And it isn't harmless. The report doesn't just cost the time it takes to write. It changes the rest of the time too. The moment people know they'll be judged on what they write, they start working for the report. They pick the tasks that sound good in one line over the ones that matter. They stretch the visible jobs and rush the invisible ones. The best people, the ones who'd rather do the work than describe it, get tired of proving themselves every evening, every Friday, every quarter, and they're the first to leave.

You end up paying twice for every day: once for the work, and once for the story about the work. And the story is the part you're reading.

So when I started running things myself, I kept one rule. I don't ask for activity reports, not daily, not weekly, not any of them. If the work is done at a computer, the log can keep itself while the work happens: which project, which page, how long. Nobody stops to write anything. Nobody polishes it. It's just there, for the day someone genuinely needs to know where the week went. Most weeks, nobody looks, and that costs nothing.

Judge people by what they finish, not by how well they describe it. If you can't tell a good week from a bad one without a report, the report isn't the thing that's missing.