How Do You Stop a Six-Hour Job From Turning Into 22?
Work runs over budget when nobody owns the number. Name one person to watch hours every morning, set an alert at 80% of budget, and require approval before anyone goes over. Expect 60 to 90 days of repeating it before the team treats it as normal.
Two email campaigns came back at 22 hours against a six-hour budget, and nobody said a word until the numbers stopped adding up. An agency owner told me that on our call Tuesday morning. She had the data the whole time. A report every morning landed in her inbox with every task and every hour logged. Nobody acted on it.
Nobody owned the report, so it read like wallpaper. Most owners I talk to have a version of this.
Why does work run over budget when everyone can see the hours?
Seeing a number and owning a number are two different jobs. Her report listed hours for the whole design team, 40 or 50 lines a day, and it flagged nothing. She scans it at 7 a.m., sees a wall of text, and moves on to whatever client fire started overnight.
The designer on those campaigns didn't understand the four-hour goal the system attached to new tasks. The software assigned that number on its own. She never asked what it meant, and nobody asked her. By the time 22 hours had piled up, everyone had a theory. Unclear expectations, too much polish on small details, a handoff that stalled. The owner couldn't say which one it was, and I gave her credit for admitting that.
Who should watch the budget?
One person, by name. In this agency it's the project manager, and her job is simple to describe. She spends the first 30 to 45 minutes of every workday on the hours report, unless a client emergency pulls her away. She finds the jobs closest to their limit, writes a short morning plan, and sends it to the owner. The owner approves it or changes it.
I pushed for the morning plan because it forces a decision every day. You can ignore a report. You can't ignore a plan sitting in your inbox waiting for a yes.
The owner will meet with her every day for the first 30 days, and move to a lighter schedule. Before any of that starts, I'm going to talk to the project manager myself. She watched these hours pile up and didn't raise a hand, and I want to know whether she saw the problem and stayed quiet, or never thought the call was hers to make. If she doesn't want the job, better to learn that in week one than week six.
What should the alert rules look like?
Three rules cover most of it, and each one fits in a Slack message. Warn at 80% of budget. Escalate before the work crosses 100%, not after. Require the owner's written approval for anything that goes over.
On a six-hour job, the warning fires at 4.8 hours. That's about the point where the designer knows whether the work will finish in the time left. Someone can ask a question while the answer costs little, and the owner can decide to spend more hours on purpose instead of finding out on the invoice. A designer who hears about the overage at hour five can say the brief was vague or the client sent three rounds of changes. A designer who hears about it at hour 22 has nothing to offer but an apology.
The agency had a second problem sitting under the first one. The owner covers every gap herself, which is how she ended up at her laptop at 10 p.m. most nights. A budget rule with no one to enforce it gives her one more thing to check after dinner. She has six or seven strong applicants for an open social media role, and I told her to make the hire so the process has more than one pair of hands.
How long until the team follows the rules?
Longer than she wants. I told her to plan on 60 to 90 days of repeating the same explanation, in meetings, in Slack, and in one-on-one check-ins. Most teams hear a new rule once, nod, and go back to what they did last month. Nobody is being difficult. A habit that took two years to form doesn't swap out after one meeting. The ones that change are the ones where the owner says it again on day 40 as if it were the first time.
She needs to treat the overruns as information. If the designer gets scolded for a 22-hour job, the next overrun stays hidden until it's 30. If she gets asked what happened, the next one gets flagged at hour five.
To find the cause, the owner will have her operations lead sit with the designer for a few days and watch where the hours go. Nobody has to guess between perfectionism and a stalled handoff if someone can see it happen.
The first thing the owner is going to ask the designer is what she thought the four-hour number on that task meant.
This is the kind of work I do inside Scalable Systems — naming an owner for every number, building rules that fire before the damage, and designing the founder out of the after-dinner checks.
