Do I have a rep-performance problem or a system constraint?

Low meetings, low connects, thin qualified pipeline. Those are symptoms. They are visible, they are ranked weekly, and they invite an obvious explanation: this rep is not performing. Sometimes that is true. Often the rep is executing reasonably inside a system that cannot produce a different result.

The cost of getting this backwards is high in both directions. Coach a system constraint and you burn credibility. Excuse genuinely weak execution as a system problem and you teach the team that output is optional.

Six areas around the rep. Each one can cap output regardless of effort.

The binding constraint is the one that, until it moves, prevents anything else from mattering. There is usually only one at a time, and it is usually knowable within a week of looking properly.

Work in evidence order rather than opinion order. Observe the work before interviewing people about the work, because self-report and reality diverge in predictable directions.

FusionAuth is a useful example because the early picture looked like execution inconsistency. What the engagement surfaced was broader: targeting was wide, tooling and tracking were fragmented, and visibility into the actual conversations was limited. Once those tightened, the work became measurable and coachable in a way it had not been before.

That is the honest claim: the system became more inspectable. Read the Field Report for what the evidence supports rather than treating it as a causal outcome.

Coaching works when the rep has the right accounts, the time to work them, a clear owner, and a manager who can see the calls. In that setting, behaviour change is the constraint and coaching moves it.

Coaching does not work as a substitute for territory design, headcount, tooling that functions, or a partner AE who engages. Applying it there produces motion and resentment.