The conflict started as a process mismatch.

I thought I was following the working norm. I saw work that needed to be captured, so I added stories. From my perspective, I was helping clarify the work and move the project forward.

From their side, I understand how it may have landed differently.

Maybe the other senior engineer felt bypassed. Maybe the manager thought ownership needed to be clarified. Maybe leadership saw the back-and-forth as a distraction and wanted to restore order.

That part is not hard for me to understand.

I also do not tell this story as if I had no accountability.

I was part of the conflict. I am direct. I am skeptical. I am persistent when something does not make sense. Those traits can be useful, but they can also raise the temperature. Directness can land as pressure. Skepticism can land as distrust. Persistence can land as refusal to move on.

I understand that.

I believe I acted in good faith. I was not trying to bypass anyone, undermine anyone, or win some hidden power struggle. But good faith does not mean perfect execution.

Still, understanding what they may have been trying to do does not make what happened okay.

They had the authority to change the process. They had the authority to say, “Going forward, this needs to go through the lead.” They had the authority to tighten expectations.

That was never the issue.

The issue was how they got there.

They interpreted what happened, changed the process, and treated the conclusion as settled without giving me a meaningful chance to explain what I understood, what I intended, or what concerns I had.

The process and resolution conversation happened without me in the room.

I was not there to explain what I thought the process was. I was not there to ask what expectation had changed. I was not there to raise concerns about the new process. I was not there to help clarify the misunderstanding.

I was brought in afterward and expected to accept the conclusion.

That is a very different thing.

At the time, I did not have clean language for this. I did not think, “My agency is being removed.” That came later.

At the time, I thought it was a communication problem. So I kept trying to communicate.

But management was not talking to me about it.

That was the stressful part. Conversations were happening about me, but not with me. I was asking to understand the situation, and they were refusing to engage.

That is where the process started to feel demeaning.

Not because every conflict deserves endless discussion. It does not.

But if leadership is going to resolve a situation involving me, change the process because of it, and expect me to accept the conclusion, then I should have a meaningful opportunity to understand and respond.

That is basic fairness.

My concern with the new process was not simply that I disliked it.

The process may have been intended to clarify ownership. But it also created a bottleneck.

If every meaningful decision had to clear the lead first, then every other engineer’s ability to move forward became tied to that lead’s availability, judgment, and bandwidth.

That is risky.

It slows the team down. It limits parallel work. It concentrates decision-making in one person. Over time, it can burn that person out.

I had seen versions of that pattern before. I believed that kind of concentration had contributed to burnout for a previous lead. So my concern was not only personal. I believed the team was recreating a real failure mode.

It also affected my own role.

As a senior engineer, part of my growth was learning how to see gaps, clarify work, make judgment calls, and help the team move without routing every decision through one person.

If the new rule was, “Everything goes through the lead,” then that did not just change a ticket workflow.

It changed how I was expected to participate.

That should have been a conversation.

Instead, the conversation happened without me.

That is where inclusion broke down.

Not inclusion as a corporate slogan. Real inclusion. The kind where the person directly affected by a decision is part of the discussion before the conclusion is finalized.

That is also where psychological safety broke down.

Psychological safety does not mean everyone is comfortable. It does not mean hard conversations are avoided. It means people can clarify intent, challenge assumptions, surface misunderstandings, and say what they actually think without being treated as a problem to manage.

That did not happen.

I was handled.

Not heard.

And my intent was not only ignored. It was reframed back to me.

I had stated what I was trying to do. But instead of engaging with that, the meaning of my actions was effectively handed back to me as something else: resistance, argument, trying to win, or refusing to move on.

That is the part that felt similar to gaslighting.

I stated my reality, and the response treated a different version of my reality as the one I needed to accept.

That is what made the process feel demeaning.

I know “abusive” and “discriminatory” are loaded words, so I want to be clear about what I mean.

I do not mean discriminatory as a legal argument.

I mean discriminatory in the plain human sense: being treated like a lesser participant in a process that directly affected me.

Like a second-class teammate.

Like a child.

And I do not mean abusive only in the obvious sense of yelling, insults, or cruelty.

Sometimes the abusive part is the process. Sometimes it sounds professional. Sometimes it uses words like “alignment,” “clarity,” and “moving forward.”

But underneath, the message is: your perspective is not needed here.

That was the part that broke trust.

They seemed to believe the issue was order.

I believed the issue was truth.

They seemed to think the new process solved the problem.

I thought the way the new process was imposed revealed the deeper problem.

That deeper problem was agency.

Agency is not getting your way. Agency is not being in charge. Agency is not winning the argument.

Agency is being treated as a meaningful participant in decisions and processes that affect you.

I was not asking for control.

I was asking not to be managed around.

There is a big difference between:

“We heard your perspective and made a different decision.”

And:

“We decided what happened, changed the process around you, and now expect you to accept the conclusion.”

The first one is leadership.

The second one is containment.

For me, clarity and truth are not decorative values. They are how I operate.

I am direct because I want the real issue named. I am skeptical because vague explanations usually hide important assumptions. I am disagreeable when something does not make sense because pretending it makes sense does not help anyone.

That can be inconvenient.

But inconvenience is not the same as bad faith.

The lesson for me is that I reacted too slowly to being handled.

At the time, I thought I was dealing with a communication problem, so I tried to communicate better. I tried to explain. I tried to understand. I tried to get the conversation that would make the situation make sense.

But the real issue was not that I had failed to explain myself clearly enough.

The real issue was that management did not want to have the conversation with me.

That is what I should have named earlier.

Not perfectly. Not with the agency language I have now. But plainly.

Something like:

“I am asking to discuss a situation that directly involves me, and management is refusing to engage. The process is being changed without giving me a meaningful chance to explain what I understood, what I intended, or what concerns I have. That is not okay.”

Then I should have documented it factually.

What happened. What I understood the process to be. What changed. Who was included in the resolution conversation. Who was not. What I asked to discuss. What management refused to discuss. Why the new process created a bottleneck. How it affected the team. How it constrained my growth as a senior engineer. Where my voice had been removed.

Then I should have raised it with HR as a process concern.

“Please review why management resolved a situation involving me without including me, why they refused to hear what I had to say, and whether that process met the company’s standards for inclusion, psychological safety, and fair treatment.”

Would the outcome have changed?

Probably not.

But I would have protected my agency sooner.

I would have named the demeaning part out loud instead of trying to reason my way through silence. I would have documented the refusal to engage instead of trying to interpret it. I would have treated the lack of communication as the signal, not as a problem I could solve by communicating better.

That is the lesson.

A fair process does not mean I get my way.

It means I get heard before the decision is treated as settled.

It means hidden expectations are not enforced retroactively as if they were obvious.

It means leadership does not confuse discomfort with danger.

It means directness is not automatically treated as disrespect.

Most of all, it means that if a process changes because of something I was directly involved in, I should have a meaningful voice before that change is finalized.

That should not be controversial.

That is basic respect.

I can accept being corrected.

I can accept someone saying, “I understand your point, and we are still doing it this way.”

What I cannot accept is being managed around and then asked to call that alignment.

That is not alignment.

That is compliance dressed up as resolution.

And once I understood that, the outcome was inevitable.

Not because the original conflict was too big to repair.

But because the process used to resolve it destroyed the trust required for repair.

That is the part that broke trust, and essentially determined that I could no longer be part of that team.