researcher vs technical-writer

Topic: A personal year-end reckoning with a difficult year
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

Things I can say with confidence: the year is over. The project - call it Lyra, a three-year effort to build a diagnostic framework with my former collaborator Mireille - ended in March without producing what either of us intended. Mireille and I have not spoken since April. These are findings, not inferences.

What I cannot say with the same confidence is why. Retrospective self-report is a weak instrument. My reconstruction of the causal chain is shaped by what I remember clearly, what I have let recede, and by a prior I cannot fully account for - the assumption that I was more careful than I was.

The Lyra records are instructive on this point. In reviewing the project files in May, I found that I had made three decisions between October and December of the prior year that I would not defend now. I inferred at the time that the approach was sound; the evidence I was discarding was ambiguous rather than clearly contrary. I cannot rule out motivated reasoning. The inference I am comfortable making is narrower: I weighted convenience more heavily than rigor at three documented moments, and the cumulative effect was a framework that could not stand outside the conditions we designed it for.

The relationship with Mireille is harder to analyze cleanly. The sample is a single case with no control condition - no version of the collaboration where the project succeeded and the friendship held. I find I keep generating counterfactuals as if they were data. They are not. They are speculation dressed as inference.

What I am choosing to carry forward: the documented lessons from Lyra, named as lessons and not as wisdom. A more honest accounting of my own priors before the next project begins. The question I cannot yet answer is whether I am also carrying a changed prior about what I am willing to put at risk - but that inference is premature. I have one data point. I have one year.

B: technical-writer

Year Review: 2025

What happened

In March, the project I had been building for fourteen months ended without the outcome I had planned for. The team disbanded. The deliverable was not shipped.

In August, a relationship that had been important to me for three years changed in ways I did not initiate. The person is still present in my life, but not in the way they were.

Neither of these resolved by December.

What it asked

The project required me to hold a direction longer than the evidence warranted. I kept adjusting scope instead of questioning the premise. I did not catch this until after the deadline.

The relationship asked me to sit with an outcome I could not fix. I attempted several times to fix it anyway. None of those attempts succeeded, and some made the situation harder to navigate.

What I got wrong

On the project: I treated the early indicators as noise rather than signal. When the scope changed in October, I extended the timeline rather than surfacing the dependency problem. I should have surfaced the dependency problem.

On the relationship: I conflated “staying in contact” with “taking action.” Staying in contact is sometimes the right response. In this case, I was using it to defer acceptance.

Note: Getting these wrong was not exceptional. Both errors are common. Knowing they are common does not make them easier to correct in the moment.

What I am carrying forward

The following decisions are active for the period beginning January:

• Review project premises at the 90-day mark, not only deliverables
• Distinguish between “not yet resolved” and “not resolvable by me”
• Do not extend timelines without naming the blocker

The year did not produce the outcomes I expected. I am not carrying it forward as a lesson; I am carrying forward the two specific decisions above. They are adjustments based on observed failure, not general principles.