You're caught in a debate with developers on a technical issue. How do you steer towards a resolution?

Listening, and encouraging others to listen, mostly works. Sometimes, the obvious needs to be pointed out, and people need to be told to list in order to understand, instead of listening to answer, as the scope of the conversation is not to create a debate, but to find a solution.

Ouvir é priomordial para entender o motivo do debate, fazer com que os outros ou?am também se faz necessário para ambas as partes entendam cada ponto de vista antes de iniciar o debate.

In these situations, I ask: how is one's argument bringing us closer to finding a solution? The goal of the conversation is to find a solution, and not a mere exchange of arguments. So, the conversation needs to be around possible solutions and how to choose one.

While many arguments might have equal weight, their applicability/ scope/ impact/ feasibility will differ, so while two or more alternatives might seem to have equal value, they might not have the same business value/ time value/ maintainability value etc. Therefore, alternatives need to properly be explored, and not dismissed, because one of these is the solution that should go forward.

There are always going to be conversations around short term loss versus long term gain, or around pragmatism versus purity and whatnot, and every decision has a cascading effect, and even the best decisions could be wrong, in some other context. Therefore, if a decision is to be made, the team should first clarify what sort of impact/ change they are after, and then see what solutions/ alternatives the team has to deliver on that very specific goal and then evaluate what impact the solutions/ alternatives for this goal have on the immediate goals. This will make the decision more obvious.

é necessário sempre vermos qual dor será resolvida e qual dor será criada, olhar apenas o agora levando em considera??o o curto prazo, talvez seja o pior cenário para quando for mais a frente a longo prazo tudo volte a contecer porque os impactos n?o foram mensurados corretamente, pois, no calor do momento foi levado em considera??o apenas a dor atual. A decis?o ela deve ocorrer em castaca, levando em condidera??o todos os seus efeitos de curto, médio e longo prazo, sua curva de aprendizado, implementa??o, manuten??o e custos.

Depending on the size of the team, consensus might not be attainable, but a consensual majority can be found in teams with an off number of members (5,7) as opposed to even ones (4,6). Therefore, when a decision is made by the members of the team, for the team, all members of the team should work to achieve it, even though they might not believe in it. It's a team decision, so it's a team (shared) effort.

Avaliar como os membros do time se sentem / o que pensam sobre um problema é muito importante, pois, com base na perspectiva dos membros, pode-se construir uma ideia solida de como superar os obstaculos relacionados de forma a alcan?ar o objetivo final de forma mais eficiente.

It can be difficult to navigate a technical dispute with developers. Encourage an open discussion where all points of view are taken into account to start. Promote data-driven conversations to unbiasedly weigh the advantages and disadvantages. After an agreement is established, make sure to express the choice clearly. Everyone should be aware of the solution that has been decided upon and their part in putting it into practice. For instance, our team argued over the optimal database solution in a recent project. After careful consideration, we settled on PostgreSQL. A seamless transition and effective deployment were made possible by clear communication, which made sure everyone understood the plan and how to carry it out.