Five-Step Get Out of the Weeds Hiring System
Document, hire, train, and validate someone before handing off recurring work
- Difficulty
- Moderate
- Time to result
- ~months to results
- Steps
- 5
- Confidence
- 98%
This framework turns delegation into a documented hiring and validation process rather than an abrupt handoff. The founder first creates an SOP that records how the work is performed, including preferences, decision rules, exceptions, and escalation paths. That SOP becomes the basis for an accurate job description. Interview and training blocks are then protected on the calendar so the hiring effort does not compete with routine work. Candidates can complete a relevant paid test to demonstrate how they think and execute. Training follows a staged transfer: the founder demonstrates, observes, remains available for questions, and finally releases ownership. Reviews at 30, 60, and 90 days compare performance with the SOP, identify corrections, and determine whether the relationship should continue.
Origin
Jasmine Star shared this process to help listeners escape ground-level work after explaining that telling a founder to stay out of the weeds was insufficient. Extracted from The Jasmine Star Show.
Core principles
- 01Document the work before recruiting for it.
- 02Hire against actual responsibilities rather than a generic title.
- 03Reserve calendar capacity for interviewing and training.
- 04Validate capability with a relevant paid test.
- 05Transfer work through progressively reduced supervision.
- 06Treat the first 90 days as a structured validation period.
How to run it
- 1
Create the SOP
Document how the selected responsibility should be performed, including preferences, decision criteria, exceptions, filing rules, and escalation paths. Make the document usable by someone who lacks the founder's unstated context.
Pro tip Start with a recurring task that consumes meaningful time but follows recognizable rules.
Watch out A new hire cannot infer personal preferences or undocumented operating conventions.
- 2
Build the Job Description
Translate the SOP's actual activities and standards into a job description. Recruit for the work the person will perform rather than relying on a broad title.
Pro tip Use the SOP to distinguish essential capabilities from skills that are merely helpful.
Watch out A generic description can attract candidates who fit the title but not the real responsibilities.
- 3
Protect Interview and Test Time
Block interview periods on the calendar before recruiting begins and include time for a relevant paid work test. Evaluate both the candidate's result and the way they approach the task.
Pro tip Design a test that resembles the role without using unpaid candidate work in the business.
Watch out Do not begin recruiting if normal calendar pressure will prevent timely interviews and evaluation.
- 4
Train Through Progressive Release
Schedule training and walk the hire through the SOP. Demonstrate the task, watch them perform it, remain available while they work independently, and then release the responsibility.
Pro tip Use the progression: show them, watch them, support questions, then let them own it.
Watch out Giving someone an SOP without guided application is not adequate onboarding.
- 5
Run 30-, 60-, and 90-Day Reviews
At each checkpoint, assess performance against the SOP and its metrics, communicate specific corrections, and set expectations for the next period. Use the 60- and 90-day reviews to decide whether the person can meet the team's required pace and quality.
Pro tip Anchor feedback in observable SOP requirements rather than personal impressions.
Watch out Do not assume that a hire is a permanent fit before enough evidence has accumulated.
In the wild
A founder documents which emails require a personal response, which can be archived, how messages should be escalated, what meetings can be accepted, and when meetings may occur. The SOP informs the assistant's job description, work test, and training. During the first 90 days, response quality and scheduling accuracy are reviewed against those written rules.
→ The founder transfers routine communication and scheduling without forcing the hire to guess at personal preferences.
A founder with established launch SOPs hires a project manager to coordinate repeatable delivery. After a paid test and staged training, the project manager takes over task tracking and dependencies while the founder shifts attention to a new revenue initiative.
→ A proven operational process is delegated with limited training risk, freeing founder capacity for higher-value work.
Common mistakes
Hiring Before Documenting
Recruiting first forces the new employee to extract every preference through repeated questions, increasing frustration for both parties.
Skipping Training Because an SOP Exists
Written instructions still require demonstration, observation, and opportunities for clarification before ownership is released.
Assuming Immediate Fit
A promising interview does not prove that someone can meet the team's pace and standards; structured checkpoints are needed.
Is it for you?
Best for
It is best for founders who perform repeatable tasks that can be documented and transferred to a capable hire.
Not ideal for
It is not ideal for singular responsibilities that depend entirely on the founder's identity, authority, or irreplaceable judgment.
From the transcript
“Step number one is to create an SOP. This is a standard operating procedure. Basically this is a work manual for what needs to get…”
“Let me show you. Let me watch you. Let me be here if you have any questions. And then I'm going to let you do…”
“Lastly, you want to plan a 30, 60 and 90 day check in.”
From the episode
The CEO’s Guide to Working ON Your Business (Not Just In It)