Engineer Your Freedom

How Do I Know If My Engineering Firm Needs Another Hire or a Better Process?

Before you add another engineer, run a lean experiment. Ask what the last how much for how little test was and what it produced.

A person in a work shirt stands by a large tree beside a leaning chain-link fence overgrown with brush, with a shallow rocky creek beyond.
A person in a work shirt stands by a large tree beside a leaning chain-link fence overgrown with brush, with a shallow rocky creek beyond.

Run a lean experiment before you post the job. If you cannot name the last time you tested a cheaper way to get the same output, the next hire will not break your throughput ceiling. It will raise it. The ceiling is not a headcount problem first. It is a design problem first, and the hire is what you do after the design test tells you the constraint is real.

What is a lean experiment in an engineering firm?

A lean experiment is not a budget cut. It is a design test. You pick one bottleneck, change one constraint, and measure what comes out. The question is not how little can we spend. The question is how much output can we get for the same money, or how much less money for the same output.

Take submittal review. If it takes ten days and you are about to hire a reviewer, test a checklist and a first-pass rule first. If the checklist cuts two days, you learned something. If it changes nothing, you learned the constraint is somewhere else. Either result is worth more than a job posting.

Lean is not another word for cheap. Cutting costs removes capacity. Lean redesigns the work so the same capacity produces more. A firm that cuts a reviewer and lets submittals rot is not lean. A firm that removes a review pass because the checklist catches the errors is lean. The test is output, not spend.

Why does adding people first scale the ceiling?

Every gap closed with money or bodies teaches the firm that growth is a purchase. The work design stays the same. You add a person, output rises, coordination rises, and the same bottleneck comes back. The ceiling moves up. It does not go away.

The ceiling is not a fixed number. It is the point where the current design runs out of room. If you add people without changing the design, you move the point. You do not remove it.

A CEO who has only ever closed gaps by adding money or bodies will scale the throughput ceiling, not break it. That is true whether the firm has five engineers or fifty. The habit is the problem, not the size.

Grandfather Engineering answers every capacity question with a hire. Modern delivery answers it with a design test, then a hire if the test says the constraint is real. The difference is not the number of people. The difference is whether the firm knows why it is adding them.

A hire also feels like action. An experiment feels like a delay. But a hire based on an undefined problem takes longer to fix than a two-week test. You pay the salary while you learn what you should have learned before the offer.

What question should I ask before the next hire?

Ask what the last 'how much for how little' experiment was, and what it produced. If the answer is blank, the hire is a guess. If the answer is a test that failed for a specific reason, you have a real constraint and a real case for the hire.

Ask it of yourself first. Then ask it of the people who lead delivery, drafting, and project controls. If none of them can name a test from the last quarter, the firm is buying its way out of problems it has not defined.

If you own the firm, you are the CEO. The question is not for someone else. It is for you. If you sit above operating leaders, ask them the same question. The answer tells you whether the next dollar buys capacity or buys time.

This is not a reason to avoid hiring. It is a reason to hire second, after the design test, not first. The question is not meant to shame anyone. It is meant to separate a capacity gap from a design gap. They look the same on a timesheet and they need different answers.

How do I run one this month?

Pick one bottleneck. Not the whole firm. One bottleneck that costs a week or more on a regular project.

  1. Write down the current design. Who touches the work, how many handoffs, where it waits, what gets reworked.
  2. Change one constraint. A checklist, a template, a decision rule, a different sequence, a drafting standard.
  3. Set a measure. Cycle time, rework rate, number of returns, hours per deliverable. Not a feeling.
  4. Run it on one project or one client for two weeks.
  5. Keep it if it works. Kill it if it does not. Either way, write down what you learned.

A lean experiment does not need a consultant or a new software platform. It needs a stopwatch and a willingness to be wrong about where the problem is. If drafting turnaround is the bottleneck, test a standard layer set and a single point of review. Measure the number of returns. If it does not move, the bottleneck is not the drafting standard.

If proposal production is the bottleneck, test a standard scope template and a single review. Measure the hours from kickoff to signature. The experiment is small on purpose. You are not trying to prove a theory. You are trying to find the constraint.

What do I do when the experiment works?

Write it down as a standard. Train one person to own it. Then the next hire operates a better system instead of patching a bad one. That is how a firm breaks the ceiling instead of raising it.

If the experiment fails, you now know the constraint is capacity, skill, or a decision you are holding. Hire with a reason. That is a different hire from the one you would have made on instinct, and it is more likely to stick.

A failed experiment is not wasted. It is the cheapest way to find out that the constraint is real before you pay a salary for the answer.

The lean advantage is a design mentality, not a budget line. A firm that runs one experiment a quarter will know more about its own ceiling than a firm that runs five hires a year and never asks why the work still piles up.

What should I do next week?

Pick the hire you are about to make. Write the two-week experiment that would make that hire smaller or later. Run it before you post the job. Ask what the last 'how much for how little' test was, and what it produced. If you cannot answer, you have your next experiment.

The hire you make after that test will count more. The one you make before it is a guess with a salary attached.

From the book Engineer Your Freedom

Michael Groselle, P.E., is the founder of Modern Engineering Solutions, a multi-state water and wastewater engineering firm. He left salaried engineering in 2017 and built the firm from one resignation letter and zero clients to more than $2M in annual revenue, with a team of 37 and 525+ completed projects.

Sold on Amazon. Prefer the Kindle edition? Buy it on Amazon ($9.99).