At some point, I stopped wondering if people understood the problems. They did. I had explained them clearly enough.
I wasn't vague about it, and I didn't keep it to myself. I wrote things out. Long messages, structured explanations, step by step breakdowns of what was happening, why it was happening, and what needed to change. I treated it like part of the job, because it was. If you are leading something, you do not just build. You communicate. You document. You make sure the people around you understand the system well enough to make good decisions. That was the standard I held myself to, so I made the effort to meet it.
I explained why the conversion effort needed dedicated focus. Why splitting work across legacy and new systems would slow everything down. How the release process worked, why it worked, and what would happen if we ignored it. I explained things before they became problems, and then I explained them again after they did.
There were times where I would write out full breakdowns just to make sure nothing was misunderstood. Not emotional, not reactive, just clear. This is how the system works. This is what will break. This is what we should do instead. And for a moment, it would feel like it landed. Someone would acknowledge it. There would be a response. Maybe even agreement.
Processes that had been working were replaced without discussion. Working implementations in the new system were questioned or ignored in favor of older ones. Decisions were made without input from the people closest to the system, and most of the time I found out after the fact.
The same patterns kept repeating. Processes that were already working would be replaced without discussion. Working implementations in the new system would be questioned or ignored in favor of older ones. Decisions would be made at a high level that didn't match how the system actually worked, and most of the time I would find out after the fact.
Image by OpenIcons (https://pixabay.com/users/28911)Sometimes it showed up in smaller ways. A ticket with no real scope turning into a disagreement after the work was already done. A request to split apart something that had been intentionally designed as one connected system.
And sometimes it showed up in ways that were harder to ignore. I was asked to break apart tightly integrated authentication work into separate deliveries, even though doing that would have meant disabling core functionality just to fit the request. I explained why that didn't make sense, clearly and directly. It was acknowledged, and then partially walked back, but only after being pushed publicly first.
None of it was hidden, and that was the part that made it hard to ignore. I had already said it. Not once, but over and over again. And not in a way that could be misunderstood. It was written down, documented, explained in plain terms, with context, with reasoning, with alternatives.
There's a point where you stop thinking maybe I need to explain this better, and you start realizing that is not the problem. The problem is not that people don't understand. The problem is that understanding is not changing behavior.
That was the shift.
Before that, I was still trying to fix things. Still trying to align people. Still thinking that if I could just get the right explanation in front of the right person, things would start moving in the right direction. After that, it felt different. I was still doing the work, still building the new system, still maintaining the standards I had set, but I was no longer under the illusion that the system around me was going to meet me there.
Because it hadn't. Not after all of that.
And that's when it really became clear. This wasn't a communication problem. It was a decision problem. And it wasn't going to fix itself.