TLDR
- A tech debate can turn into “my idea versus your idea.” That is when the project stalls.
- The PM does not have to choose the stack.
- Ask clear project questions. Find the missing facts. Decide on the work, not on ego.
On one project, two team members had a hard fight about the system setup.
One said: keep it on-premise.
The other said: move to cloud.
At first, it looked normal. Both had reasons. Both could explain their side.
Then the same meeting kept coming back. Same arguments. Same pushback. The talk stopped sounding like design review. It started sounding like each person defending themselves.
The decision slipped. Other work waited. The rest of the team could not move with confidence.
How I saw it change
On-prem and cloud are real options. One can feel safer and more familiar. The other can feel faster to change and easier to grow.
The problem was not the options. The problem was the shift:
- From “what does the project need?”
- To “why my option is right”
After that, new facts did not help much. Each fact got used as proof for one side. Gaps stayed open because asking for more detail felt like losing.
What I did not do
I did not walk in and say, “We go with cloud” or “We stay on-prem.”
That can look strong in the moment. It also teaches the wrong lesson: escalate, and the PM will pick a winner.
I wanted something else. First, hear why each person cared. Then move the talk off people and back onto the project.
The questions we used
We put both options next to the same list:
- What does this project actually need?
- Which option fits those needs better right now?
- What does each option cost in money and time?
- What can go wrong with each option?
- What will maintenance and growth look like later?
- What do we still not know?
We did not start with a final vote. We started with the missing information. Where numbers or constraints were unclear, we stopped the debate and went to get them.
Only after that did we look at both options again, side by side, against the project needs.
What I own as PM
I do not need to win the architecture argument.
In that room, my job was to set the frame:
- Shared questions
- Visible gaps
- A talk that stays about the work
When people feel heard on the “why,” they can live with a decision that is not their first choice. When a leader only announces the answer, the fight often continues later in smaller ways: slow replies, quiet pushback, half support.
Conflict is not the enemy
I do not try to remove every conflict.
I try to keep the conflict useful. Keep it about the project. Stop it from turning personal.
On-prem versus cloud was the topic. The real test was whether we could decide with facts, not with pride.
If your team is stuck in the same loop, start with missing facts and shared questions before you ask someone senior to pick a winner. More on hard team phases: Tuckman’s Ladder. More on how a team agrees to work: rules of engagement.