researcher vs technical-writer

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

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

B: technical-writer

Dana,

You taught me something over four months in 2016 without naming it as a lesson. I want to name it now, because I just used it.

You put my name forward for the Harlow platform documentation project in the spring of that year. I had eight months in the role. The project required coordination across four engineering teams, sign-off from a release manager who was already skeptical of the docs function, and a scope I had not fully mapped when you submitted my name. I told you I was not ready. You disagreed and submitted it anyway.

What followed matters. You checked in every Friday for the four months the project ran. You asked about specific blockers, not general progress. When I came to you stuck on the architecture section, you did not solve it. You asked what I had already tried. You waited while I listed the options I had considered, then asked one question. The answer came from me. You repeated that pattern across three similar moments.

I did not have a name for what you were doing while it was happening.

Last month, I put Marcus forward to lead the onboarding guide redesign. He has fourteen months in his current role. He told me he was not ready. I ran the process you ran: submitted his name, scheduled Friday check-ins, and when he brought me a blocked decision, I asked what he had tried before I offered anything. The project shipped last week.

When Marcus thanked me, I told him the method was not mine.

You gave me four months of weekly attention when I was not operating cleanly. That was a cost you did not account for in any project tracker I could see. This letter accounts for it.

Thank you.