Do you need more people or less duplicated work?

Before you hire, look at where work gets stuck, repeated or lost. EWOR’s scale model can help you decide whether you need more people, better coordination or more automation.

Lead & Operate
Founder judgmentAI & Automation

Adapted by the EWOR Team from Daniel Dippold’s article (opens in a new tab)2 min read

Find the constraint before adding capacity

When demand outgrows your team, hiring another person can feel like the obvious next step. But Daniel Dippold, EWOR’s CEO and co-founder, suggests looking at three things first: how many people you have, how well they work together and how much useful output each person can deliver. His Models of Scale framework offers a way to think through these factors before adding headcount.

His model combines people, alignment and efficiency, with efficiency further divided into individual quality and automation. Think of it as a way to diagnose what's holding your team back, not a formula that predicts productivity. Before adding headcount, ask yourself: will another person have clear ownership? Can the team coordinate with them? Or is the real problem the way the work gets done?

See how the work actually gets done before expanding

Pick a recurring bottleneck and follow the work from the initial request to the final result. Where does it slow down or get repeated? Look for duplicated tasks, work nobody uses, decisions that keep coming back to the founder and mistakes that need fixing. Talk to the people doing the work, too. A process diagram rarely captures every workaround or judgement call.

Once you understand the problem, compare three options: clarify ownership, hire someone with a defined remit or automate a specific step. Each comes with trade-offs. A new hire might bring expertise a tool can't replace. Automation might reduce repetitive work but introduce setup, monitoring, security checks and exceptions to manage. Consider not just the time saved, but also the extra work each option creates for the rest of the team. Whatever you choose, someone still needs to be accountable for the result.

Test one reversible change

You don't need to redesign the whole organisation at once. Choose a task where you can safely test a reversible change, and establish a baseline for cycle time, errors, rework and the experience of customers or colleagues. Give someone responsibility for the trial and the authority to stop it if quality suffers.

Afterwards, look beyond the immediate time saved. Has the change improved the whole workflow? What does it take to maintain, monitor and oversee? How has it affected the people doing the work? If you don't yet understand a process, or a failure could cause serious harm, get the process clear before automating it.

Be careful with the dramatic automation multipliers and staffing predictions in scale models. Don't treat them as expected returns or use them to plan headcount without evidence from your own operations.

Choose what improves the work and check its effect on people

The answer might be another hire, clearer ownership, a new tool or a combination of all three. Use what you've learned from the test to make that choice, document the result and revisit it as the company grows.

Source: EWOR article by Daniel Dippold (opens in a new tab)

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter