01 / Hiring signal
How do you tell a hiring need from a broken process?
A full founder calendar is weak evidence for an operations hire. Record two weeks of interruptions: what triggered each request, who could have answered it, how long the work waited, and whether the same question had already been settled. If most interruptions involve missing instructions, fix the process first. If the work requires judgement across suppliers, customers, people and cash every day, there may be a durable operating role.
Look for a stable outcome the person can own. 'Help with everything' leaves the candidate unable to prioritise and the founder unable to evaluate. 'Own the order-to-delivery process, its exception queue and its weekly service review' describes a job. Demand matters too. A permanent role should be supported by work that is recurring enough to warrant its cost, not merely a stressful launch week.
| Observed problem | Try before hiring | Hire when |
|---|---|---|
| The same approval interrupts each day | Set decision thresholds and an owner | A person must manage varied exceptions within those limits |
| Tasks are missed | Create one queue and a weekly review | The queue requires sustained cross-team ownership |
| Founder has too many meetings | Remove meetings without decisions | Customer, supplier and team coordination still dominates |
02 / Role charter
What must be decided before writing the job advert?
Write the role charter in four parts: outcomes, decision rights, interfaces and first ninety days. Outcomes might include reliable fulfilment, predictable reporting and fewer unresolved exceptions. Decision rights state what the operator may spend, change or escalate. Interfaces name the founder, finance, customer and supplier contacts the role must coordinate. The ninety-day plan describes what must be learned and improved, without pretending the new hire can repair every inherited problem immediately.
Include the information the candidate will need to succeed. Can they see unit economics? Can they renegotiate a routine supplier term? Can they change a process that the founder designed? If the answer is no, define a narrower role. A senior title with junior authority is a poor bargain for both sides.
- One operating outcome and its current baseline
- Daily choices within the role
- Reserved decisions and response times
- Systems, people and information available
- Thirty, sixty and ninety-day evidence of progress
03 / Assessment
How can a founder assess operating judgement?
Use a short, paid work sample based on a sanitised operating problem. Give the candidate a late supplier delivery, three customer commitments and a fixed cash limit. Ask for the first-day response, the decision log and the question they would escalate. Judge how they separate facts from assumptions and protect the customer while keeping the business solvent. Do not ask for unpaid consulting on a live company problem.
Reference checks should ask about a decision the candidate owned, an exception they mishandled, and how they made a team less dependent on them. A strong operator can explain trade-offs and follow through. Familiar logos or polished process vocabulary do not establish that they can own the actual workload in your company.
04 / Onboarding
What should the first ninety days prove?
In the first month, map the work and make failure visible. In the second, let the operator own one bounded process and its exceptions. In the third, review whether decisions are timely, customers receive the promised service, and the founder's interventions are limited to reserved matters. Set the baseline before the hire so that a change can be judged honestly.
Give feedback on the quality of decisions, not only whether the founder would have chosen the same option. If every different choice is reversed, the operator will stop deciding. If important risk is repeatedly hidden, widen the reporting requirement or narrow authority. The goal is a reliable operating system with a capable owner, not a founder's clone.