The Mentor as Coach Smiles When the Team Wins
A love letter to the engineers who cheer loudest for the people they helped — and never needed a trophy to prove it.
INVENTOR'S MIND | Tuesday Deep-Content | Engineer Series
The Mentor as Coach Smiles When the Team Wins
A love letter to the engineers who cheer loudest for the people they helped — and never needed a trophy to prove it.
He Didn't Have to Post That
A high-temperature materials chemist posted a LinkedIn comment last week that stopped me cold.
He was responding to gratitude — someone thanking him for a lifetime of contributions to aviation propulsion. Work that people in this field understand quietly, even when they can't say it out loud.
He could have said thank you and moved on.
Instead, he started naming names.
Twenty-plus colleagues. Engineers and technicians. BS and MS contributors who never made a headline. He estimated roughly a hundred significant team members over the life of the program. He closed by crediting the founding vision that made it all possible.
He didn't list them for credit. He listed them because he still carries them. Decades later. Unprompted. On a Tuesday.
That is what a coach looks like.
The Coach Doesn't Need to Score the Goal
There is a specific kind of mentor that every serious engineer either had or needed and didn't get.
The coach who held the standard when it would have been easier to lower it. Who cleared the obstacle you didn't even know was in your path. Who watched you develop a capability over two years and never once made you feel like you owed him for it. Who asked the question in a hallway that reoriented your entire approach — and then walked away without noting the assist.
When the breakthrough finally happens — when the thing that others failed to do finally gets done — this person doesn't push to the front of the room.
He smiles. Quietly. Because he already knew you'd get there.
The coach's win is the team's win. He understood that before the season started.
What the chemist posted on LinkedIn was that smile. In text. Archived on a platform. Twenty names offered freely to anyone who might care — because he cared, and because every one of them counted when the work was hardest.
It All Counts When Others Have Failed
Breakthroughs don't happen because one person was brilliant enough.
They happen because a technician built the fixture that made the test possible. Because a materials specialist flagged the failure mode before it cost two years. Because a program engineer held schedule long enough for the team to iterate one more time. Because someone stayed late on a Saturday for reasons that never appeared in any report.
None of that is small. All of it is load-bearing.
The patent captures the invention. It doesn't capture the hundred decisions, recoveries, and quiet contributions that made the invention survivable. The named inventor gets the certificate. The invisible army gets the coach's memory.
And here is what I've learned in thirty-two years: the coach's memory is the more accurate document.
It all counts when you're trying to do what others failed to do. The coach knows that. He counted every contribution as it happened.
Only Certain People Can See the Invisible Army
This is where it gets interesting from an engineering standpoint.
Early in a career, the natural tendency is to overestimate individual contribution. You solved a hard problem. You filed a patent. You believe you understand how breakthroughs happen. The attribution feels clean: one person, one idea, one outcome.
But accumulate enough real experience — enough failed programs, enough recoveries that only worked because of someone you almost forgot to thank — and the model recalibrates. You start to see the network. You feel the weight of the people who cleared the path before you arrived at the solution.
This is the inverse of the Dunning-Kruger effect. The peak of the curve is the engineer who thinks he did it alone. The valley — the long, expert valley — is the one who knows exactly how many hands were on the rope.
The chemist is in the valley. He's been there long enough that listing twenty names isn't an act of generosity. It's just accuracy.
That calibration takes decades to earn. And it produces a very specific kind of mentor — the one who cheers without needing the spotlight, who advances innovation by investing in people years before those people will be needed, and who smiles quietly when the team wins something the world thought was impossible.
I Owe Some of Those Smiles
I'll say the part that's uncomfortable to write.
Early in my career I accepted recognition I should have distributed. Not dishonestly — I just didn't think to look back at the network that held me up. The system didn't ask me to. The patent form had lines for inventors, not for the people who made the inventors possible.
Thirty-two years and sixty-two patents later, I think about that differently.
I remember the mentors who coached me without calling it coaching. The ones who asked the question I wasn't smart enough to ask yet. The ones who kept me on the program when someone else might have moved me out. The ones who smiled when I got it right — genuinely, without reservation — because that was always the outcome they were working toward.
I owe them more than I ever said out loud.
The chemist's LinkedIn comment is one of the most technically honest things I've seen published in this industry in years. He's not being humble. He's being precise. He understands what the work actually cost, and who paid it.
That's the mentor as coach. And we don't have nearly enough of them.
Are You Building That Kind of Culture?
If you're leading an innovation team, managing a technical organization, or trying to understand why your breakthrough rate has stalled — the invisible army question is worth sitting with seriously.
Are you building the kind of environment where the coach can develop people years before they'll be needed? Where a contribution that doesn't appear in the patent still gets recognized as load-bearing? Where the team knows that it all counts?
Or are you running a system that only rewards the person who crosses the finish line?
Meanwhile…….
There is a high-temperature materials chemist somewhere in this industry who doesn’t know this post exists. He posted a comment on a Tuesday, listed his colleagues by name the way a good engineer documents what actually happened, and went on with his day. He wasn’t making a statement. He was just being accurate. But I read it, and I felt the weight of every mentor I’ve ever had — the ones who asked the right question, cleared the path, and smiled when I got there. So if you’re reading this, and you know who you are: thank you. Not for the comment. For the years before the comment. For the standard you held when it would have been easier to lower it. For the smile. I hope you know what it meant — and what it still means — to the people who were in the room.
Thank you.
If this post is describing someone in your life — a mentor who coached without calling it coaching, a colleague who cleared a path and never mentioned it — I’d love to hear about them in the comments. These people deserve to be named, even when we name them quietly.
And if you want more of this — the engineering life told honestly, without the resume polish — subscribe to Inventor’s Mind. It’s free. It shows up on Tuesdays and Wednesdays. And it’s written with exactly the kind of gratitude this post is about.
Herbert Roberts, P.E. | Inventor's Mind | inventorsmindblog.com
32 years aviation R&D • 62 U.S. patents • Forensic engineering • FEB methodology