Everyone Agrees the Problem Is a Person
You have had the meeting. Everyone looked at the status board, saw the same name in the approval column for the fourth week running, and nodded in unison. Marcus is the problem. You sent the reminder. You CCd his manager. You put his name in the weekly update in a color that is not quite red but is not quite not-red. The whole team knows who the bottleneck is. And here is the part nobody says out loud in that meeting. You are pointing at a person because pointing at a person is easier than admitting the process has no rule. A person who takes four days to approve a two-thousand-dollar purchase and four days to approve a two-hundred-thousand-dollar purchase is not doing two different jobs. They are doing the same job in a gap where nobody wrote down where the line is.
The Rule Is Missing, Not the Speed
A bottleneck is a place where work accumulates because the next step has no clear trigger. Think about the last time you approved something in under an hour. The request was specific, the amount was obvious, and the criteria were already in your head. You did not need to think. You just said yes. Now think about the request that sits in Marcus's inbox for four days. It is not that he is slow. It is that the request is asking him to make a judgment call that nobody defined for him. Is this a standard expense or a capital decision? Does this need a second sign-off? What is the threshold where his approval alone is enough? He does not know, and he is not going to guess wrong in front of his manager. So it sits. The person is not the bottleneck. The absence of a written decision rule is the bottleneck. The person is just the most visible object sitting in that gap. And the reason the same person answers in an hour once the rule is written down is not that they suddenly care more. It is that the question they were avoiding has been answered for them.
Why You Keep Pointing at the Person
Because blaming a person gets you a meeting. Blaming a process gets you a conversation about what you actually agreed to, and most leaders do not want that conversation. You can put Marcus on a performance review. You can put his name in a one-on-one. You can escalate to his director. All of those actions have a clear doer and a clear next step. You cannot put no one defined the approval threshold on a performance review. You cannot assign an action item to a missing document. The person is a target. The process is a mirror. And the uncomfortable part is that if you admit the rule is missing, you have to say who was supposed to write it. Usually that is you, or the person one level above you, or the founder who said we will formalize it next quarter. That is three quarters ago. So the person-blame survives because it is the only version of the problem that has a clear owner.
The Part That Does Not Resolve
Here is where it gets messy, and I will not pretend the distinction above is the whole story. Sometimes the person is the problem. Sometimes Marcus is disengaged, or he does not understand the work, or he is using the approval queue as a place to hide from something else. If you only fix the rule, you still have a person who cannot or will not execute. If you only swap the person, the next hire hits the same wall in week three. You need both. The rule and the person. But you cannot see which one is actually missing until you separate them, and most teams never do. They just add another reminder email, another escalation path, another status check, and call it process improvement. The real question was never how do I make Marcus faster. It is who wrote down what good enough looks like, and if the answer is nobody, you have a different problem than the one you walked into that meeting to fix.
