Operations
Why Hiring a Project Manager Does Not Hand Off the Delivery Hat
A project manager gets the plan and the tracker, but the founder keeps the judgement calls. Delivery comes off the founder when decisions, approvals and escalations are written down.
•

A founder hires a project manager and expects delivery to take care of itself. It rarely does. The PM gets the plan, the tracker and the status meetings. The founder still answers the client escalations, still makes the scope calls, and still steps in when a deadline slips.
Six months later, the project manager is reporting problems, and the founder is still solving them.
Why the hire does not take the hat
Delivery is mostly judgement, and judgement has not been handed over. The PM does not know what the founder would accept as done, who can approve a change, or when a problem is theirs to fix versus the founder's to hear about. So they ask, and the founder answers.
Each answer feels quick and helpful. Together, they keep the hat on the founder.
Write down what done looks like
Start with the standard. For each type of work, put in writing what a finished piece looks like, what the client has agreed to, and what is out of scope. It does not need to be long. It needs to be specific enough that someone else can check the work against it without calling you.
Decide who can approve a change
Scope changes are where founders get pulled back in. Agree who can say yes to a small change, who must approve a bigger one, and how the cost or timing impact gets recorded. Once the PM can say yes or no within clear limits, most of the escalations disappear.
Agree what gets escalated, and when
Not everything needs the founder. Set a short list of triggers: a deadline at risk, a client unhappy, a change beyond the agreed limit. Everything else is the PM's to handle and report on weekly. This is the same operating rhythm we covered in Rhythm Over Heroics, applied to delivery.
Review delivery in the same weekly slot
A weekly look at what is late, what is at risk and what was decided keeps the hand-off honest. It also shows you early whether the PM needs more authority or more support.
The client-change test
Ask three questions. If a client asked for a change today, would your team know who decides? Could the PM explain what done looks like for each live piece of work? Does anyone other than you know which jobs are at risk this week?
Three yes answers mean the hat is largely off. Any no shows you what to write down next.
Where to start
Pick one type of work and write down its definition of done, its approval limits and its escalation triggers. Then review it weekly. That is the core of a Management Rhythm Reset. The wider version of this problem, hiring a senior operator and still holding every decision, is in The Real Cost of Not Having a COO. And the order to hand hats off in is in Which Hats a Founder Should Hand Off First.
If you want to see where your own rhythm stands, start with the free five-question Management Rhythm Check, or book a 20-minute Review and we can look at which part of delivery to hand off first.