executive vs product-thinker

Topic: Writing to thank a mentor who shaped your career
Axis varied: voice
A: Executive 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: executive

Dana,

The reason I’m writing is this: last month I put one of my direct reports forward for a scope she did not feel ready for, and within two weeks I recognized that I had borrowed the playbook from you.

You made that call on me about ten years ago. The project was a cross-functional launch - more visibility, more stakeholders, more exposed surface area than anything I had carried before. I told you I wasn’t sure I was the right bet. You disagreed, and you put me in. What I did not fully reckon with at the time was the cost on your end. You stayed close enough that I was never actually alone in that first hard stretch, but you did not step in. That is a harder line to hold than it sounds. Taking over is faster, lower-risk, and easier to justify. You chose the slower path, and that patience had a price.

The outcome it made possible is not separable from that tradeoff. I learned something you cannot teach in a debrief: what it feels like to carry weight that is actually yours, without a safety net that makes it notional. That lesson transferred. When I made the call on my direct report last month, I knew exactly what I was asking her to hold, and I knew what staying close without taking over actually requires.

I don’t know what I cost you in re-work or anxiety during those months. I probably still underestimate it. What I can say clearly is that the bet compounded. It is paying out now in someone else’s growth, which means you are further downstream in this outcome than you could have planned for, but you are in it.

That felt worth naming explicitly.

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.