Newsletter
Thirty minutes later the drawing was fixed. The designer learned nothing
The most expensive mistake a team leader makes has nothing to do with technical work. What it costs, where I could be wrong, and a count to run this week.
For engineering firm owners
The most expensive mistake a team leader makes has nothing to do with technical work. Here is what it costs, where I could be wrong, and a count you can run this week.
Updated November 2026 from my June letter. What changed: the cost example is now labeled as an illustration, our own review times are measured, and I added the study that cuts against me.

You have a senior engineer running a project. The designer sends back a site plan and it is not right. Maybe the grading is off, maybe the layout does not match the markup. The engineer looks at it, sighs, and starts fixing it. Thirty minutes later the drawing is corrected. The engineer feels good. The project moved. The designer learned nothing.
My business coach calls this heroic engineering. I call it expensive. I still catch myself doing it.
The pull is real. When you do the work yourself, you can feel the project move. If you got to team leader by being the best technical person in the room, that reward is familiar. You have been earning it your whole career. But you are now paid to produce work through other people, and every fix you make yourself spends your most expensive hours on your lowest-value work.
A team leader who keeps doing the work is a high-priced individual contributor with people around them.
The firm pays a premium for a team's output. If the team doesn't produce it, the premium buys nothing.
Here is the arithmetic, with round numbers. It is an illustration, not our rates. A lump sum job carries $80,000 of budget. The team leader costs $150 an hour fully loaded, the designer $50. Over a month the leader spends 40 hours on corrections the designer should have made. That is $6,000 of work that would have cost $2,000. The $4,000 difference is 5 percent of the budget, gone on one habit, and the designer missed 40 hours of practice.
There is a cousin of this habit. Some engineers hold knowledge on purpose. Not out of malice: being the only one who can run the model feels like job security. I once worked with someone exceptional at a specialized kind of modeling, and the only one who could do it, one project at a time. I kept picturing five people under him with 85 percent of his skill, running the repeatable parts while he made the judgment calls. My guess is four times the volume at the same quality. That is a guess, not a measurement. What I know is that the firm's capacity stopped at one person, and nobody behind him was growing.
Redirect. Don't resolve.
A precise comment, sent back fast, is the whole job.
When a drawing comes back wrong, write the comment that tells the designer exactly what to fix and why, send it back fast, and move to the next thing. The designer gets the rep. The project keeps moving.
My rule of thumb is two days. It is my rule, not a study, so I checked how close we come. Our app records each review round from the dated folders on a project. This year, across 44 projects on three repeat programs, comments went back a median of half a day after a set came in, 30 of 36 times within two days. The designer sent the next set a median of about a day later, 35 of 51 times within two days.

Here is what I did not expect. Our own turn is not where the long waits are. On finished jobs for our repeat clients, more than half of a typical job's calendar days sat in gaps of two weeks or more with no hours logged at all. Some of that is an agency, some a client, some us. Our records can't tell them apart. Fast comments still matter. They won't fix your schedule alone.
The study that cuts against me
A boss who can do the work is worth something. Keep that, and still put down the pen.
Artz, Goodall and Oswald studied surveys of American and British workers. The strongest single predictor of a worker's job satisfaction was the boss's technical competence, such as whether the supervisor could do the worker's job. It is an association, not proof. But it is the best evidence I found against this letter. A leader who stops touching the work loses what made people want to work for them.
So I'm not telling you to stay out of the drawings. Read them closely. Write the comment a great engineer would write. Just don't redraw the sheet.
There is a second cost that never shows up in a billing report. Every fix a leader makes is a rep a junior engineer didn't get. Six months later you are asking why you can't promote from within. Same problem.
Here is the exercise. In June I told you to pull your team leaders' timesheets. We tried it on ourselves and it doesn't work. On our biggest repeat program, 53 percent of all hours land under one code for agency reviews and plan revisions, including about a quarter of the hours in a job's first two weeks. A timesheet can't tell reviewing from redrawing. So count instead. Pick ten review rounds from last month. For each one, who made the fix: the designer, after a comment, or the reviewer, at the desk? And how many days did the comment sit?

Tell me your count out of ten through our contact page. I read every one.
Michael Groselle, PE
Founder and CEO
Modern Engineering Solutions
mod-eng.com
Keep reading
More to read
- Your project manager inherits the files. Everything that actually matters stays with whoever sold the work
- 192 hours worked. $50,000 short on billing. The problem was not effort
- I spent eight rounds making a blind tool smarter. A plain chat beat it, so I closed it
- I told you to audit the setting. I didn't audit mine
What we do
Planning a project?
Talk to an engineerTalk to an engineer
Tell us about your project
An engineer reads it
Not a salesperson. Someone who can tell you whether the pathway is real.
You get a first answer
Your options, the agencies involved and the questions that decide cost and schedule.
You decide
No commitment to have the first call.
Prefer the phone? (214) 833-6748