Information technology covers so many purposes: from classical computing , data handling, system integration to support of human communication and interaction, and articifical intelligence. Building working solutions are based on many types of technology: hardware, software, infrastrucure and network components with many choices about usage in the form of architecture , code logic and configurations.

Getting overview of the technology stack is a vital  task – What systems are involved with what underlying technolgoes. Is technology fit for use, shall new technology be implemented or is existing and propriotary technolgy being challenged to do new tricks?

Project are easiest if they can be based on fit modern technology that is already in use in the organization , with all needed support processes in place, and with teams having experince with development, operations and knows the way around.

Pay attention if the project is introducing new technology –  It can be exiting but also time consuming to introduce new tecnology. Remember that it can take time before new technology becomes mature and keep in mind the many extra tasks there can be involved. Especially when whole new systems are built (with a patchwork of involved technologies)  many  extra taks can be encountered incl.

• Selection and approval processes
• Contract and licensing
• Hardware and infrastructure
• Establishment of test and prod environments
• Establish build and deploy procesures.
• Ensure GDPR compliance
• Security setup
• Training
• Build competences
• Proof of concept and pilot activities
• Hand-over to operations

Pay attention when the old horse is forced to do new tricks – If existing technology is being challenged to do new things it has not done before, or is forced to adapt new patterns e.g new integration methods you should be alert. It may be a huge challenge to open the box and interfere with things and principles that have been untouched for long time.

Pay attention if the project involve system integration – All experience shows that complexity is increasing  when multiple systems with different technologies and logics must play together, but also different teams that must syncronize plans and coordinate efforts. Adding middleware to facilitate integration may be a prerequisite but is also another layer of technolgy (and organization)  to be managed.

It is people that make technology work – No matter what kind of technology, the succesful exploration will be dependent on having the right people involved that can manuveuer the technology. This include:

• Ability to transform business needs to solutions
• Knowledge about functional options and limitations
• Knowledge about how long time it takes to develop features
• Knowledge about operational facts (like performance and stability)
• Motivation to work with the technology
• Have implemented the technology in the organization before
• Overview how the technology is playing together with other technology

Technology does not work from day one: It is easy to forget, but as complexity is increasing the more time it takes to make technology work smoothly. The smooth operation include

• Having all technologies in the stacks implemented and connected
• Making sure the technology  serves the business needs
• Eliminating bugs
• Reaching stable operations also perfornance wise
• Having processes in place to develop and deploy improvements

Technology in corporate perspective: Corporate IT strategy and -standards can have huge impact on what technology to use, the freedom to introduce new technology and agility during implementation. It makes perfect sence to have a corporate strategy that defines how to use technology and to select certain tecnologies rather than having an cluster or patchwork of technologies serving the same purposes. The backbone can be limitations for a project to choose best-fit technology, the allowed technology may be old and not upgraded, there can be ressource limitations or other bottlenecks. No matter what it is important to understand and navigate within the options and limitations in the organization.