What do you do if your software engineering ideas are constantly dismissed in the workplace?

Understand that your ideas will not be accepted instantly, no matter how useful they are. Here are some of the impediments to your idea acceptance: 1. Lack of research: Maybe the idea hasn't been properly analyzed and the impact not ascertained. It is important to note how your idea will impact the current working state before implementing it. 2. It has already been tried before: As mentioned, do your due diligence to check if the idea you've suggested has been implemented before, and what were the outcomes. 3. Maybe the management is hostile to change: In which case, don't ruffle feathers. Use gentle persuasion skills to show how your idea can help to improve things. 4. Keep trying: Don't get discouraged by early setbacks.

The right context is essential. No matter how brilliant your idea is or how well you work out the other 5 points, if the idea does not solve a problem of the person you're talking to, it will get rejected or ignored. Therefore, it's crucial to understand the troubles of each individual and stakeholder. If things don't fit, you might adjust the idea, or find another addressee, or make your counterpart aware of the problem. If none of the above fits, you won't convince anyone.

In such a case, I will begin to propose the opposite of what I want. When the opposite of what I want gets dismissed, then what I do want is what remains. /s

Para lidar com o descarte constante de ideias de engenharia de software, é essencial compreender o contexto do projeto, identificar problemas e oportunidades, alinhar propostas com objetivos e metodologias, apresentar uma abordagem baseada em dados, solicitar feedback e persistir com resiliência. Essa abordagem estratégica aumenta as chances de influenciar positivamente mudan?as no local de trabalho.

The adage "understand before being understood" highlights the importance of context comprehension. It's crucial for several reasons: 1) Building rapport is key; without connection, ideas are dismissed, and we have local champions to backup for change. 2) Addressing specific pain points requires contextual understanding for effective solutions. 3) Recognising potential obstacles ensures plans are adaptable and successful. 4) Overcoming "know-it-all" attitudes fosters lasting systemic change. To enact change effectively, it's vital to understand past experiments and current situations thoroughly.

Quando ideias de engenharia de software s?o constantemente descartadas, é crucial considerar tempo e formato ao compartilhá-las. Evitar interromper colegas ocupados e optar por momentos adequados, como reuni?es ou sess?es de brainstorming é fundamental. Comunicar de forma clara e concisa, usando exemplos e convide feedback ativo para aumentar a receptividade às propostas é consideravelmente aceitável.

IMHO, the primary factor which decides adoption of new ideas is the cost:benefit ratio and its value addition to the business both for short as well as long term goals. It may happen that the proposed idea is the most brilliant one (in time space), yet it might fail in adoption because of the factors mentioned above. So, best would be to research about the C:B ratio along with the rigorous research about thd topic / idea. Just think, many products are still running on top of JDK 1.8, whereas the latest stable version is JDK 17. The product could easily migrate to JDK 17, yet due to C:B ratio, the idea is rejected. Instead if the individual could propose the extra benefits that the customer would experience with JDK 17, it will get adopted.

I would be accepting the negative feedback and wait for perfect moment to show them what vision will be brought my ideas and how things will be easier

Se as ideias de engenharia de software s?o constantemente descartadas, é necessário manter-se aberto e flexível. Evitar conflitos para n?o levar a rejei??o para o lado pessoal, reconhecer diferentes perspectivas, s?o boas práticas dentro de um ambiente de trabalho saudável. Estar disposto a compreender o feedback e adaptar as ideias para atender às necessidades da equipe e da organiza??o, também.

If no-one will consider your idea at work, maybe it's just a terrible idea. In this case, write it in a LinkedIn 'advice' section which is unmoderated and full of inexperienced wafflers trying to market themselves. That way it makes your LinkedIn profile more marketable and you are more likely to secure your next role - assuming they don't actually read your contributions, of course!

Think about the ideas that are being implemented. Take some time think about what makes them acceptable. If possible, set aside the people who are promoting the ideas, and think objectively just about the ideas and their goals and even more about the actual outcomes. Try to align your ideas to the outcomes the other ideas address (or discuss why those outcomes are problematic and need to be addressed), and consider the outcomes your ideas may or may not address. Then try to reframe your argument for the idea to align with desired outcomes and overcome the objections by showing what additional benefits your ideas offer.

If everything else fails, you can still write the idea down, put it into your (virtual) drawer, and let it wait for the right moment to be pulled out. Just make sure you get it out of your mind before it starts fermenting.

Think about the ideas that are being implemented. Take some time think about what makes them acceptable. If possible, set aside the people who are promoting the ideas, and think objectively about them. Try to align your ideas to the outcomes the other ideas address, and consider the outcomes your ideas may or may not address. Then try to reframe your argument for the idea to align with the ideas that are being accepted.

You may have all the best ideas and solutions but working in autonomy with decision influencers in your organisation downplays the chances of having your ideas go through. Know when and who to go to.