Continuity at Technology Validation
Daniel Delfino
Chief Executive Officer - CEO at AOL Precision and Chief Operating Officer - COO LATAM | Technology Leadership | Digital Transformation | AI Solutions | IoT Innovations | AI-based Customer Support | Oracle and SAP
The common sense is "The Importance of listening Customers" but the article below bring something which I believe is the key for (good) product development (Hardware & Software): Continuity!
https://dzone.com/articles/the-importance-of-listening-to-developers
When we listen engaged developers (the real ones) we can get informations over the development, such as: ups&downs, pro&con, customers feedback, reliability and weakness.
I see this important not only for software DevOpers, to whom the article was wrote, but to all sort of technology developers where 1 year or even 1 month of experience may make diference to the result of a new project.
People who work for us, remotely or at the office, know the intensity and the energy needed to create, innovate and deliver technology. It is not to everybody, we know. The experience shows us how to manage the stress and turn it productivity and a source of inspiration, building a self regulated community focused at the same target.
For me the DevOper, who crossed the line of the first product delivery and still want this life, must be the main source of information for a new development.
What do you think? How do you manage this with unstable markets/customers? How do you keep good engineers at the technical path?
www.r-dtechnologies.com