Skip to content

celebratory vs encouraging

Topic: A personal year-end reckoning with a difficult year
Axis varied: tone
A: Celebratory B: Encouraging

Both examples address the same topic and (by default) share every axis other than tone. The only deliberate variable is which tone 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 tone swap is the entire cause of those differences.

A: celebratory

The project ended in April. I had been building it for two years - a content infrastructure tool I called Verdant, for a market I thought was ready. It was not. The wind-down was quiet, which was its own difficulty. No postmortem, no closing ceremony, just the tool sitting in a private repo while the team I had assembled moved on to other things.

Elena and I had already been changing. That process did not stop or start in any single month. It was slower, and I did not choose the direction of it, and I did not handle all of it well.

What I want to name - because it deserves to be named - is the one thing I did not do. I did not make these two things into one. I did not use the project to explain the relationship, or use the relationship to explain why the project failed. They were distinct. The failure of Verdant was a real loss, and the reasons for it were technical and market-shaped and mine to understand. What changed with Elena was something else entirely, with its own causes and its own weight.

Keeping those separate, honestly, when the year was asking me to collapse everything into a single story - that was the work. I am not carrying both things forward. I am carrying what I actually learned from each, without adding meaning that was not there.

That is what I am acknowledging. Not that the year was secretly good. But that I stayed accurate in it, and that accuracy costs something.

B: encouraging

The project was called Meridian, and it failed. Not in a way I could blame entirely on bad luck or misaligned stakeholders - though both were present. It failed in part because I held the original vision too long when the evidence said revise, and by the time I revised, we had run out of runway. Liora, my co-lead, saw it coming six weeks before I did. I was not willing to hear it. That is not a comfortable thing to write.

The relationship - I will not name it, because some things lose something when they get named - changed because I could not be present in the way the other person needed. I was pouring everything into Meridian and calling it unavoidable. It probably was not unavoidable. That is also not comfortable to write.

Here is what I can actually say, though - and I am saying it as carefully as I said the harder things above: I stayed. I did not disappear into distraction or exit early. When Meridian wound down, I sat with the team through the close. When the relationship shifted, I showed up to those conversations even when they were painful. I did not do everything right, but I stayed present.

That matters because staying when you want to leave is the thing you build on. I am not further along than I think I am - I think the year cost what it cost. But I have handled things I did not know I could handle. I have a clearer account of where I misread the signals than I did a year ago. That clarity is not free, and it is not nothing. I am going into next year carrying different questions than the ones I started with. That is what I am choosing to take forward.