Sua equipe está dividida em novos recursos do projeto. Como você vai uni-los para avançar efetivamente?

Actively listening is crucial when the team is divided and we aim to unite them. We can start by fostering open communication where everyone feels heard and can share their viewpoints and opinions. As a team leader, it is important to ensure that everyone feels comfortable and to avoid interrupting while they are expressing their thoughts. Maintain full attention during the discussion and, once it concludes, ask clarifying questions. Summarize the points discussed to ensure everyone is on the same page. Avoid interrupting or arguing before the speaker has finished. By implementing these practices, we can unite the team despite differing opinions on project features, allowing us to move forward effectively with the project.

Decide on measures to compute short and long term values of the features suggested amongst team members, and assign priorities accordingly.

Every single decision must ultimately be guided by objective data and must have the goal of solving a problem users have. It's not about personal preferences, it's about what moves the needle for the users, and that can almost always be measured objectively.

Ideally, during the active listenning stage you took some notes on key points. These will be crucial to objectvely analyzing and further down the line in making a decision and presenting it to the team. Find good, relevant criteria to analyze the points to ensure the final path will be a good one.

Inclusivity and diversity are cornerstone in collaborations, every member of the team needs to feel that's a good, safe place to work and collaborate together. The only way we can distinguish good and bad opinions is if we hear them. Unfortunally humans can't read each others mind yet so make sure the team feel safe to speak up their ideias and truly appreciate the value it might have.

Many times, what you initially think needs to be built is actually a huge superset of what you can get away with. Try to think critically around which bits of your solution are actually necessary to solve your users' problem, you might be able to deliver 80% of the value with only 20% of the effort, in which case, you might not need to prioritise as aggressively as you thought you would.

I always encourage my teams to embrace Lean Software Development techniques and build any feature iteratively. By launching a very basic V1 as quickly as possible, you shorten the feedback loop and can get invaluable feedback from your users at a relatively early stage, before you spend loads more effort in building what you initially thought was the "perfect" solution. You might just find out that users actually want something different than what you thought they did, and it won't be too late in the process to pivot your solution to accommodate that.