Que faire si vous n’êtes pas sûr de la technologie à choisir pour l’innovation produit ?

By outlining your product goals and requirements, you'll be better equipped to decide which technologies and development approaches best meet your needs. You'll also ensure that your product meets the needs of your target audience, aligns with your business objectives, and can adapt to changing market conditions over time. Defining your product goals and considering factors that can impact its success is especially critical before starting a new product development project. These factors might include your target audience, the desired functionality of your product, how scalable it needs to be to meet future demand, performance requirements, and any budget constraints you may have.

When choosing technology for product innovation, start with understanding user needs through market research. Consult industry experts and leverage trend reports for insights. Prototype and test in small environments to gauge impact and integration with existing systems. Embrace agile development for rapid iteration based on feedback and performance. Prioritize technologies that offer flexibility and can adapt to future market changes. This approach ensures an informed, user-centered decision, paving the way for sustainable innovation and competitive advantage.

It's important to monitor market trends to take advantage of new technologies. Consider whether any recent developments or innovations could make this technology more useful or widely adopted in your industry. Also, explore whether implementing this technology could open new markets, improve customer satisfaction, or provide a competitive edge. When considering potential risks, you should consider external factors like emerging technologies, regulatory changes, or security vulnerabilities. You should also consider whether the technology provider is stable and whether there's a risk of vendor lock-in.

SWOT et PESTEL c'est un peu bizarre pour évaluer des technologies. Les niveaux de maturité (TRL) s'est très bien mais attention à deux choses : 1/ si la technologie est immature c'est que les risques ne sont pas identifiés, 2/une technologie mature pour une une application ne l'est pas forcément pour celle en question donc il faut faire l'analyse. Donc j'encourage vraiment à faire une analyse de risque au moins préliminaire. De plus dans ma thèse de doctorat j'ai expliqué les limites des TRL pour l'innovation de rupture : les critères sont trop figés. Il faut avoir une approche plus euristique. Enfin il faut comparer l'ACV ou aux moins quelques impacts environnementaux de base, c'est la modernité !

When you set out to test different technologies, make sure you do not forget what you are actually out to test. This goes back to the way you define the problem or opportunity. Too often I see companies (startups and enterprises alike) that define the wrong experiment because they want to "prove" that the technology they already selected, and the product they already had in mind, is a good choice. Be prepared to discover that the technology, or the way that you have chosen to deploy it, is not producing the expected outcomes. A product innovator should not fall in love with the technology. They should fall in love with the problem and be passionate about solving it.

Keep in mind that choosing innovative technologies will attract new talents, and this is a good thing, but you also need to retain your current talents. Avoid choosing a technologies without considering the learning curve and the "coolness" for your current team: you don't want to have a great and shiny technology, without anyone being able to work on it except your R&D team...

Le sous-entendu dans ce paragraphe c'est qu'on expérimente plusieurs technologies en parallèle. Attention ce n'est pas du tout une évidence dans la réalité, mais effectivement pour l'innovation de rupture, c'est vraiment recommandable d'expérimenter plusieurs alternatives en parallèle !

Sometimes you are not selecting a technology on its own but in conjunction with what is used by a company or individual you outsource to. We are presently developing several apps and webapps, the technology selection we have to evaluate is very much skewed by what they are using, and is probably secondary to the end product and their cost. As long as they can hit the design spec, the technology uncertainty is there but is offset. If you are unsure of the technology to use it may be worth considering outsourcing or subcontracting the work to others who have done all the hard work of tech evaluation for you. Just a thought.

I recommend prototyping each shortlisted technology and seeing how it performs in real-world scenarios before making a purchase decision. Prototyping is a valuable step in the development process because it allows you to test how well each technology will work with your product concept. Prototyping can help identify potential issues early on, saving time and resources in the long run. By creating prototypes, you can better understand how each technology will function within your product and make informed decisions about which to pursue.