The first month decides whether an operations hire takes work off your plate or becomes one more person asking you questions. I have started operations roles in a startup academy, a remote conference team working between Nairobi and Tallinn and a tech hub. The ones that went well followed the same pattern.
This playbook is for both sides: the new operations person and the founder or programme lead who hired them.
Week 1: listen and map
Resist the urge to fix things in week one. The goal is to understand how work moves today.
- Sit in every standing meeting and read the last month of the main channels: the team WhatsApp group, the shared inbox and whatever chat tool the team uses.
- List every recurring job you see: weekly reports, partner follow-ups, onboarding steps, payments, event logistics.
- For each one, write down who does it, how often, which tools it touches and what happens when it slips.
- Meet each team member for 20 minutes and ask one question: what do you do every week that feels like a waste of time?
For the founder: give full access on day one. An operations person who has to ask permission for every tool loses a week.
Week 2: pick the biggest leak
By now you will have a list of 15 to 30 recurring jobs. Pick the one that costs the most when it fails. It is usually one of these:
- A pipeline nobody owns, so leads and partners go cold.
- A weekly or monthly report built by hand.
- Onboarding that depends on one person remembering the steps.
Agree with the founder on what fixed looks like, in one sentence. For example: every partner in the pipeline has an owner and a next step with a date.
Week 3: fix one thing properly
Build the smallest system that solves that one leak. A clean tracker, a checklist, a template or a simple automation. Then run it yourself for the rest of the week.
When I joined the Startup Garage Academy for its first cohort, the leak was follow-up. More than 70 founders, weekly sessions and trainers who needed their materials ready. One tracker and one weekly follow-up routine made the rest of the programme manageable.
Week 4: document and hand back
- Write the process on one page: the steps, the owner and what to do when something goes wrong.
- Put that page where the work happens, linked from the tracker or pinned in the channel, so nobody has to hunt for it.
- Show the founder the result with numbers: hours saved, follow-ups sent, items that no longer slip.
- Agree on the next leak for month two.
What the founder should do
- Hand over decisions with the work. If every change still needs your approval, you have hired an assistant.
- Protect a weekly 30 minutes. One short check-in beats ten interruptions.
- Judge the month on one result. One leak fixed properly is a strong first month.
Mistakes I see often
- Buying a new tool in week one. Learn the process before you choose software for it.
- Fixing five things at once. Nothing gets finished and the team loses trust in the changes.
- Documenting without running. A process you have not run yourself will have gaps.
- Staying invisible. Share small wins in the team channel so people know what changed and why.
After day 30
Month two repeats the cycle with the next leak. By month three the founder should notice they spend less time on status questions and more time on the work only they can do.
Questions I get about the first month
How do I know the hire is working?
By the end of month one, one recurring process should run without you. Ask yourself one question: which job did I stop doing this month? If the answer is none, sit down together and pick a smaller first target.
What if the company has no processes to map yet?
Every company has processes. They just live in people's heads and WhatsApp chats. Week one becomes a listening week: follow the work, write down what happens and turn the most common job into the first written process.
Should the operations person also handle admin?
Some admin always comes with the role. Keep it under a third of their week, or the systems work never gets done.
If you are about to bring in your first operations person, or you want a fractional one to run this playbook with you, get in touch. You can also read why founders need an operations person in the first place.
