Your team is divided on innovation versus code quality. How do you find the right balance?

Setting goals is crucial, but it is also essential to measure and track progress against these objectives with key performance indicators (KPIs). Additionally, maintain ongoing communication with all stakeholders to ensure goals remain aligned throughout the project. Incorporating periodic reviews and feedback can help adjust strategies and maintain the balance between innovation and code quality.

It is important for the whole team to understand and agree on the project’s objectives and goals. This will set the compass for the team to naturally understand the best balance between quality and innovation. It is important that everyone in the team feels heard and that their opinion matter, so they speak up when they feel the need, have healthy discussions with the team members and, ultimately, embrace the project’s goals as a team.

Define the project objectives in advance and try to explain the project's priorities, this way it will be clearer to everyone what needs to be done at each moment, but be sure to bring both innovation and quality to the code, as these are two things that will help with the project.

La calidad del software es un atributo no negociable, ya que, si esto no se asegura de la mejor manera, repercute al usuario final y de retorno al mismo dueño del producto, lo que traducirá en si el usuario final puede o no confiar en lo que se le ofrece como producto o activo digital. Por tanto, es importante que desde los equipos de trabajo se mantenga mucho el trabajo colaborativo de la mano de las metodologías agiles nos aportan mucho valor al ser aplicados a los desarrollos, pues nos ayuda a lograr incrementos alcanzables en el tiempo y verificables rápidamente logrando así, observar cómo se genera valor e impacta de cara al cliente o al dueño de producto de manera positiva.

Finding the right balance between innovation and code quality involves setting clear priorities and maintaining open communication. Encourage your team to innovate within defined guidelines that uphold code quality standards. Implement robust review processes to ensure new ideas are thoroughly vetted and aligned with best practices. Promote a culture of continuous improvement where both innovation and quality are valued. Regularly reassess priorities based on project needs and feedback to adapt and maintain balance.

La evaluación de riesgos permite permear las necesidades y establecer un enfoque claro para minimizar el impacto que puedan llegar a tener en el desarrollo de nuevas características de un producto. La esencia de la calidad no reposa únicamente en ubicar soluciones rápidas, sino en velar porque el trabajo realizado no se caracterice por la ineficiencia. En otras palabras, elegir soluciones efectivas en lugar de rápidas, minimizando la deuda técnica y optimizando el desarrollo.

I think the idea that a heavy emphasis on code quality might “stifle creativity and slow down progress” feels more like a bogeyman than a practical concern. If anything, a lack of sufficient emphasis on code quality bogs down development even in the medium-term. Any innovation activity undertaken without a solid foundation is sure to suffer.

Both are important to survive in competitive era but we have to keep balance. Some measures, strategies for Quality should be in place and strictly followed. Innovation should be made incrementally and pass through quality standards.

Innovation doesn’t mean compromising quality. Code quality should never be compromised since it can result out adverse results

As a DevOps engineer, I believe that code quality and innovation are not mutually exclusive but are, in fact, complementary. High code quality is the foundation that allows innovation to thrive. When we prioritize code quality, we create a stable, reliable, and maintainable codebase that enables rapid experimentation and iteration. This stability is crucial for implementing new ideas and adapting to changing requirements without incurring technical debt that could stifle future innovation. In essence, innovation is a mindset rather than an approach to code quality.

Begin by explaining to your team that both innovation and code quality are crucial. Innovation drives the creation of new features and improvements, while code quality ensures the software is maintainable, scalable, and less prone to bugs. Encourage a culture that values quality from the start. This includes good coding practices, code reviews, and automated testing. High-quality code is easier to innovate with because it's easier to understand and modify. Dedicate specific time for innovation and for maintaining code quality. For example, some companies use a "20% time" policy, where developers spend 80% of their time on their regular tasks and 20% on innovative projects or ideas. Use agile or iterative development methodologies.