There's no need to focus on 'winning over' the team when it comes to coding styles. At the end of the day, what truly matters is that the code is properly formatted, consistently structured, and well-documented. While coding styles may vary between teams or individuals, enforcing rigid preferences can often lead to unnecessary friction. Instead, the focus should be on using tools like linters and formatters to automate consistency and ensuring that the codebase remains easy to understand and maintain.

First, I will outline the advantages of the new coding style compared to the current regarding such aspects as readability, maintainability, and efficiency. The detailed comparisons of new and old conventions with views to show improvement would be given next. Findings are shared with the senior members to seek their view and further validation of the benefit. Then, I would inform the junior members of the team and explain to them the benefits of the new coding style. I would invite open feedback for any apprehensions, allowing sufficient time to get comfortable with the new approach. By effective collaboration and transparency, I hope to make this transition smooth and acceptable for the new coding conventions by the team.

Explaining the benefits of learning a new coding convention can really help with insights into improvements in code contributions and product deployment. However, seeking input and feedback from the team really plays a big part of their involvement in improvement. These steps are all crucial before even thinking of providing resources or trainings.

I would promote dialogue tables (face-to-face or virtual) to listen to workers' opinions. By compiling the opinions, I would guide the change based on the most accurate comments and clear up any doubts they may have, showing the benefits that the improvement will bring. I would admit that it might produce some extra effort or discomfort, but I would encourage them through recognition, awards and, over time, an analysis would be made of how much the condition of the work has improved thanks to the implementation of the coding.

To win over the team on new coding style conventions, I'd emphasize the benefits: improved readability, maintainability, and consistency. I'd present the conventions clearly, explaining the rationale behind each rule. Instead of imposing them top-down, I'd encourage discussion and feedback, addressing concerns and incorporating reasonable suggestions. A gradual rollout with automated linting tools can ease the transition. Highlighting how these conventions prevent future bugs and simplify collaboration can help gain buy-in.