Even on the basic level, they provide valuable ideas on what should be considered, and what is very often ignored:
- A lot of enterprises try to move very quickly without giving employees time to get a feel of technology.
- They don't support implementation and don't cover employees' needs who are performing an adoption.
- Don't build practices that support the adoption inside the organization.
- Don't treat variability in performance on the chaos phase (Satir Change Model) with the right attitude. An example is not acknowledging new overhead that is required on this stage e.g. performing PoC, prototypes, because it contradicts their overall understanding of what should be the delivery speed.
- Technology change pains are not discussed and treated with the required level of importance.
Also, there are other things that we think are contributing to the failed initiatives that underperform.
From the management perspective:
- Very often leadership sticks to the old-school management approach where decisions are made on the top without giving employees a chance to contribute to the best of their ability.
- Sometimes, it is hard to think beyond the project scope and how different tech concepts/processes depend on and influence each other.
- The same about lack of technology leadership capability to assess strategies and understand how to bridge business with a correct technology solution.
- Struggles of organizations to manage resistance, plan and implement sustainable change
What could be done about it?
- Blindly adopting technology trends. The vivid case is with microservices architecture that is not required by most of the enterprises, but a lot are trying to build it.
- Limiting employee's tech view to the scope of one organization and its technology base. They should have channels to observe what is happening outside, gain experience from industry leaders.
- Technology people should have passion and companies should strive to stimulate that passion and promote an always-learn, continuous growth mindset. Stimulate knowledge sharing, conference visits, companies' RSS technology feeds and case studies.
Skills, capabilities and processes outlined above require specialized training and experience that most of the companies simply don't have. It is not their specialization and this is perfectly normal.
It is always a good idea to partner with technology companies and individual technologists whose main business is about understanding how to embrace the latest technology and test/learn how to apply it to solving real-world problems.
Software engineering is a comprehensive discipline on the intersection of UX/UI, business analysis, architecture etc. If UX/UI is done correctly, but the software architecture perspective is lacking behind, the company's ability to test hypotheses and deliver quickly falls to a minimum.
That is why in TageSpot we think more in coarse-grained services proposition rather than fine-grained e.g cyber-security assessment. It doesn't mean that we start doing everything together, but we always maintain a parallel view, showing our clients how important are all other aspects and what should be done about them.Contact us
to get to know about our value proposition and how we could help you to accelerate your growth.