executive vs senior-consultant

Topic: Writing to thank a mentor who shaped your career
Axis varied: voice
A: Executive B: Senior Consultant

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: senior-consultant

Dear Dana,

I am writing for a specific reason. Last month, I put a member of my team forward to lead a project she had not yet run at that scale. She was visibly uncertain; her technical preparation was sound, but the stakeholder complexity was new territory. I stayed close but did not steer. The project closed well, and she is clearly a different practitioner. In the debrief, I found myself describing exactly what I was doing and recognizing where I had learned it.

Looking back, the pattern is clearer now than it was then. Viewed through a development lens, you had two viable paths. You could have waited until my preparation was more visible - the lower-risk option, with lower upside for me and lower cost to you in patience and oversight. Or you could place me in a role that exceeded my current capability and stay close enough to catch structural failures without absorbing the day-to-day friction. You chose the second path. The assumptions that choice required - that the gap between my readiness and the role’s demands was traversable, and that I would respond to pressure by building rather than retreating - were not obvious at the time. You made them anyway.

What that cost you was real. You carried the ambient risk while appearing to carry none of it. You held your counsel when the easier move was to redirect. The patience that requires is not passive; it is a discipline that most senior practitioners I have observed do not sustain under pressure.

What it made possible is harder to name precisely, but the strongest read is this: you did not teach me to lead a difficult project. You showed me what it feels like to be trusted before the evidence fully warrants it - which turns out to be the only thing that teaches you to extend the same to others.

Thank you for that first call.