candid vs matter-of-fact

Topic: A personal year-end reckoning with a difficult year
Axis varied: tone
A: Candid B: Matter of Fact

What to notice

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

The honest picture: this year broke things I did not expect to lose.

The project - I’ll call it Vantage, the platform I spent eighteen months building with a team of four - ended in April without the outcome any of us wanted. The funding did not come through. We had to wind it down. I want to be direct about what that cost me: not just the work, but the story I had told myself about what the work meant. I believed we were building something necessary. I still think we were. That does not change the outcome, and I made it worse by waiting too long to say what I was seeing in the numbers. That is something I got wrong. I named it internally and then softened it for everyone else, and that softening cost us time we did not have.

The relationship piece I will not detail here - some things belong to the people in them. What I will say is that it changed on a trajectory I did not choose, and I spent the better part of six months waiting for it to reverse. It did not. That kind of waiting is its own kind of work, and I am not sure I did it well.

I am not writing this to find the silver lining. The hard parts were not secretly gifts. What I am choosing to carry forward is narrower than what I used to carry: a preference for naming things when I see them, before there is no room left to move. That is not a resolution. It is a small recalibration, and I am holding it loosely.

B: matter-of-fact

The year started with two things I believed in. By December, both had changed in ways I hadn’t planned for.

The project - three years of work building a data infrastructure platform for a mid-sized logistics company - ended when the client shifted priorities and chose a vendor solution instead. The decision made sense from their side. The code was solid. The team did the work we said we would do. The outcome we wanted, which was a long-term engagement and a product in production, did not happen.

The relationship with my collaborator Marcus changed more slowly. We had worked together for five years. Somewhere in the second quarter, the dynamic shifted. He took another position. The friendship adjusted to something more distant. That was his choice to make.

Both losses landed at the same time, which made the year harder than either would have been alone.

I did not handle the project ending well. I held on to the engagement longer than was warranted, and I absorbed the client’s ambivalence as feedback about the work instead of feedback about their internal situation. These were errors in judgment. I recognized them late.

What I am carrying forward: a clearer sense of when to escalate versus absorb, and a better read on the difference between a client who is uncertain and one who has already decided. The relationship loss I am still sitting with. There is no tidy lesson to extract from it.

The year was what it was. The next one starts from here.