friendly-mentor vs product-thinker

Topic: Writing to thank a mentor who shaped your career
Axis varied: voice
A: Friendly Mentor B: Product Thinker

What to notice

Both examples address the same topic and (by default) share every axis other than voice. The only deliberate variable is which voice the writing was rendered through. Read both and ask: where does the framing change? Where does the vocabulary change? What does the reader take away from A that they would not take away from B, and vice versa? The voice swap is the entire cause of those differences.

A: friendly-mentor

Dear Dana,

I owe you a long-overdue explanation. You might think I am writing to say thank you - and I am - but first I need to walk you through what actually happened, because I do not think you saw all of it from where you were standing.

Last month I put a junior analyst named Priya forward to lead the Northbrook account review, a project she was not ready for on paper. The moment I did it, I recognized the move. I remembered 2015, when you nominated me to lead the Harmon infrastructure rollout before I had any business running it.

Here is the part that took me years to understand: you were not gambling on me. You had already run the calculation. The project could absorb the cost of my mistakes; the stakes were real but survivable. You picked the container before you picked me for it. I could not see that at the time, which is probably why it worked.

So why am I writing now? Because staying close without taking over - which is exactly what you did - turns out to be a skill, and I did not know I had learned it until I watched myself use it. You showed up, asked questions instead of giving answers, and then stepped back and let me climb. I did not feel the safety net. That was the design.

Watching Priya struggle through week two, and making myself stay quiet when I could have fixed it in ten minutes, I finally felt what that cost you. It is not patience in the abstract. It is the active, uncomfortable work of trusting someone when you could just handle it yourself. You did that for me for months.

You gave me something I have been using for a decade without knowing its name. Now I do.

Thank you.

B: product-thinker

Dana,

I have been trying to figure out why this is the right time to write this letter. The honest answer is that I recently did something you did for me, and doing it made me understand what it cost you.

A decade ago, I was not the person who should have led the Meridian redesign. I knew it. You almost certainly knew it. The project had a real deadline, a skeptical stakeholder who had already flagged concerns to your director, and a team that was watching to see if the new PM could hold the room. The job to be done was not “give the project to someone ready.” The job was “give the project to someone who would become ready by doing it.” You made that distinction when I could not even articulate the difference.

What I could not see then was the second part of what you did. You stayed. Not in a way that let me off the hook - you never ran the meetings or rewrote my decks. But you were reachable. Every Thursday at noon, you asked questions that were actually corrections phrased as curiosity. “What is the stakeholder’s job here? What outcome does she need to see before she trusts the timeline?” I thought I was getting coached. I was being given the framing I was missing.

The measure of what you built is that I recently asked myself those same questions automatically, about a person I manage, before deciding she was not yet ready. She led the project. She found her footing without me interfering. And I recognized the whole shape of it because I had been inside it before.

What you gave me was not confidence. You gave me a repeatable way of seeing a problem clearly enough to act on it. I am grateful, and I wanted you to know it has compounded.