Spotters Save More Than Reps

Spotters look like the quiet people standing behind the bench or beside the squat rack, waiting for something to go wrong, but there is a lot more to the job than that. A good spotter is a safety net if a lift fails in a way that could hurt you. They are a second set of eyes on your form as it starts to break down. They are the source of the small cues, right when you need them: “tighten up,” “drive through.” But the heart of the job is restraint. A spotter gives you just enough help, and often none at all, so you can push yourself safely and build strength that is actually yours.

“A spotter’s purpose is to help you lift, not to lift for you.”

The best peer reviews work on the same principle. When a teammate reviews your code, your design, or your plan, they are not there to rewrite it. They are there to catch what you missed, point at the risks, and offer an angle you had not considered. A good review leaves the author better equipped to own the work and improve it, not dependent on the reviewer to fix it. The best reviewers, like the best spotters, pay close attention the whole time and keep their hands off until they are needed.

User feedback should act like a spotter’s cues too. Engaged users tell you what is confusing, what they love, and what is missing, and that tells you where to focus. What they do not do is dictate the solution. They guide the decision with their lived experience, and the decision is still yours. Lean on user feedback as a script and you lose your strategic intent. You become the lifter who expects the spotter to lift every rep, and you stop growing.

The same goes for the boardroom. I do not go into a major strategy session or an executive presentation cold. I run the documents past colleagues I trust, and I dry-run the meeting to find the hard questions before someone senior asks them. That is spotting too. The spotter’s goal is the safety and growth of the lifter, not their own performance, and the same is true of the colleagues who review your work. Skip the spotters and rush in unprepared, and you have dropped the weight in front of your peers. You overlook a key stakeholder’s concern, fumble a critical metric, or never get everyone aligned on the goal.

The risks are real in both places. A near-max squat without a spotter or safety pins is how people get seriously hurt. Shipping straight to production without a second set of eyes is how bugs, security flaws, and things you simply did not think of slip through. Even alone, you can set up spotter arms or safety straps in the gym, and linters and automated security scans in software, to catch a failure before it does damage. Those tools do not replace human judgment, they add a layer of resilience underneath it.

In security this watchful role gets active, even adversarial, in red, blue, and purple team exercises. The spotter there is not standing quietly by the rack. Red teams attack assumptions and infrastructure to expose weaknesses. Blue teams defend and shore up what gets found. Purple teams combine both so the learning happens faster. Spotting becomes deliberate stress, so the team gets stronger and smarter before a real adversary shows up to do it for them.

So how do you become a better spotter, in the gym, on your team, or in the boardroom? Stay attentive, give clear feedback at the moment it is useful, and resist the urge to take over. You are not there to lift the weight, give the presentation, or write the feature. You are there to assist, to protect, and to create the conditions for someone else to succeed. Great spotters know when to speak up, when to stay silent, and how to encourage without undermining. It is the same discipline I described earlier in product management: define the why, not the how, and let engineering find solutions you never would have instead of trying to do the lift alone. Above all, great spotters listen, because knowing what someone needs in the moment is the difference between helping them grow and accidentally holding them back. Listening, as a skill and as a form of strength, is what the next chapter is about.