journalist vs researcher

Topic: Writing to thank a mentor who shaped your career
Axis varied: voice
A: Journalist B: Researcher

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: journalist

Dana Reeves, who ran the client analytics group in the spring of 2015, gave me my first real assignment with a sentence I wrote down afterward: “You’re not ready, and that’s exactly why.”

The project was a full practice-wide reporting overhaul - six workstreams, forty-odd stakeholders, a go-live date that predated any reasonable preparation. I had been with the team eight months. Two colleagues with more experience were available and, by most measures, better positioned for the role. You put me forward anyway. Three people I later interviewed independently confirmed they were surprised by the choice.

What those accounts do not fully capture is what you did next. You did not take over. The project logs show seventeen steering meetings across four months; you attended nine. You asked questions in the ones you attended and stayed quiet in ways that forced me to be the person in the room with answers. Jamila Torres, who served as project coordinator at the time, recalled last year that she never once saw you redirect the room to yourself when I got something wrong. “She just let you figure out you were wrong,” Jamila told me. That may be the plainest description of mentorship I have encountered.

The reason I am writing now is not sentiment, or not only sentiment. Three weeks ago I put Marcus Webb, who joined my team fourteen months ago, in charge of a restructuring project he was not ready for. I stayed close. I did not take over. I watched him find the question he should have been asking two days after he stopped asking the wrong one. Somewhere during that stretch I recognized what I was doing and where I had learned it.

The record, as I can reconstruct it, shows you exercised considerable patience at a moment when taking the project yourself would have been faster and, in the short term, cleaner. What that patience made possible is the part I wanted you to hear from me directly.

B: researcher

Dear Dana,

I am writing because I recently ran an experiment I did not know I was running, and the results pointed back to you.

Three months ago, I nominated a junior analyst on my team to lead our departmental process review - a project she had not requested and, by her own account at the time, did not feel equipped to carry. I held the brief, checked in twice a week, and made clear I would catch anything structural before it fell. I did not take the work back. She found her footing in approximately six weeks; the review shipped on schedule and exceeded its initial scope.

I cannot claim I designed this deliberately. The cleaner inference is that I reproduced a pattern I had observed at sufficient resolution to replicate without consciously recognizing it as a technique. The prior was you.

Specifically: the project you assigned me in my second year, the one I said I was not ready for and you said “noted” and assigned anyway. I have one data point, so I am careful not to generalize beyond it. What I can say is that I observed you do three things with consistency across the six months that followed. You stayed present without substituting your judgment for mine. You named the risks I had not yet found before I compounded them. You held a patience that, I now understand, required you to suppress instincts I can estimate were strong, because I have those same instincts now.

The limitation of this account is that I cannot observe what it cost you. I can only infer from my own current experience as a proxy, and that inference is weak. What I can say without hedging is that the pattern transferred. Ten years later, it replicated in a different person, a different project, and a different organization. That is not nothing, and it is traceable to you.

I thought you should know.