direct-communicator vs operator

Topic: A personal year-end reckoning with a difficult year
Axis varied: voice
A: Direct Communicator B: Operator

What to notice

A is domain-neutral. Its precision is about the writer’s own state and the plain sequence of events.

B is operational and self-auditing. Numbers first, then accountability in the same register: “By August, scope had drifted by 60 percent and I had let it drift. I approved extensions I should have flagged.”

The tell: B reads like an incident review of a year. The percentage and the “I approved” belong to a mode of accounting that the direct communicator never invokes.

A: direct-communicator

This year broke me in a few specific ways, and I am still accounting for them.

The project - eighteen months of work, a team I trusted, a problem I believed in - ended in April without the outcome we needed. The product shipped. Nobody used it. I spent the summer parsing what went wrong and landed on this: I protected the vision too long. Evidence was arriving that the core assumption was off, and I kept reframing it as a validation problem. It was not a validation problem.

The relationship ended in a quieter way, which made it harder to name. Mara and I did not fight. We stopped being the same people who had started the thing. I do not have a clean read on whose fault that is, or whether fault is even the right frame. What I know is that I handled the last six months of it poorly. I was not present in the ways that mattered. I noticed this mostly after.

What the year asked of me was more honesty than I managed to give it. Not the dramatic honesty of hard conversations - though I owed some of those - but the quieter kind: looking at what I was actually seeing instead of what I wanted to see.

I am not going to call any of this a gift. It was expensive and I would not choose it. What I am choosing to carry forward is simpler: I want to be faster to name what I am actually observing. The gap between what I saw and what I acknowledged cost me this year. I would like it to cost less next time.

B: operator

The year broke in two places. I need to name them.

The project: I spent 14 months building Cascade, a content workflow tool, for a client named Mira. She signed off on the spec in March. By August, scope had drifted by 60 percent and I had let it drift. I approved extensions I should have flagged. I did not run the retrospectives we had scheduled. When Mira cancelled in October, she was not wrong to. The tool did not deliver what we scoped. I did not hold the line.

The relationship: Clara and I had been close for six years. The distance opened in February. I did not name it until June. By the time I named it, she had already made her decision. I waited too long to surface the condition. I thought naming it would make it worse. It did not get worse because of the naming; it got worse because I delayed.

What the year asked: precision I was not giving it. In both cases, I saw the signal early. February 14th: Clara said she felt like she was maintaining the friendship alone. March 8th: Mira flagged the first scope creep. I logged both. I did not act on either.

What I got wrong: I treated ambiguity as a hold state. That is the operator’s error. Ambiguity is not a hold state. It is a signal that someone needs to name the condition and make a call. I did not make the calls.

What I am carrying forward.

Rule 1: Name the condition when you see it. The latency between signal and response cost me both of these.

Rule 2: A decision deferred is not a decision avoided. Both resolved, but not the way I would have chosen. They resolved the way things resolve when no one makes an explicit call.

The year was hard. It did not resolve neatly. That is not a gift I am reframing. It is the actual outcome of specific calls I made and did not make. That is the record.