-by Jaya Pathak
Technology is advancing at great speed. Innovation is not about keeping up with the latest news articles but understanding which sectors to focus on. Between back to back meetings, podcasts and conferences, it can be difficult to know which areas to focus on. The key is to eliminate the noise and pick up the key areas that will provide the most return.
How Technology Leaders Keep Up With the Latest Innovations
Information
The technology landscape is constantly changing. Every week there are hundreds of white papers, analyst reports, podcasts and executive briefings. There is so much information coming through, from AI, Quantum Computing, Edge Processing, Spatial Computing, Blockchain Infrastructure, Synthetic Biology and so many other mega trends that will be introduced each year.
Filtering
It can be a long process to keep up with everything. At the end of the day, those making the decisions on where to invest will only be focusing on a few specific areas. They will usually have a tight focus on what they are looking to invest in (4-6 areas). With a quick review each quarter on the remainder of their area.
Intelligence From The Kitchen Table
Some of the best insights you will get on technology are not from research papers or industry reports but from talking to people in similar roles. The main source of intelligence will come from people in similar roles.
These are usually found from industry groups, executive education seminars and exclusive events with venture firms. The biggest benefit though is understanding the context. If someone has deployed a particular machine learning platform you know exactly what issues they had, how much it cost and how long it took. Nothing beats experience. Although often you will hear the failures more than the successes.
Sensor Network Of Engineers
If you have a strong engineering team in your technology leadership then don’t bother with reading any research papers. They will become a sensor network. Any architect attending a niche conference on distributed systems will have a technical note. Any engineers playing around with a new model architecture will have a prototype in their usual lunchtime hack sessions.
The CTO’s role is not to provide signals but to provide the correct tools. They will have a Tech Radar every quarter to understand what tools, platforms and methodologies they want to invest in, experiment, review and retire. Technologies that consistently show up on their radars will generally be funded with a POC. If it only shows up once then it will go in the digital bin.
Proof of Concept (POC)
No real platform tech leader will invest in a platform that has been pitched by a vendor. You will need a POC. A good POC will have clear deliverables, scope and will take between 4-8 weeks. Success criteria will be clear. The engineering team will aim to use real data and connect to legacy systems.
Sometimes the results will not be immediately clear. Perhaps it solves the issue but causes lots of overhead. Or maybe it does not solve the original issue. As a tech leader you should look at the results from a business perspective. Does it make sense to have the overhead, cost and training?
Vendor Management
Enterprise tech sales can be a complicated and long process. You could be getting hundreds of vendor introductions each month. You could ignore them completely but someone will have solved a real issue with their infrastructure.
Assign a person to review the vendors (likely to be a senior architect or platform lead). They will do an initial review of the pitch and provide a one page summary. The CTO will not attend the initial meeting. The summary will be reviewed and if there was a genuine issue identified then a deeper technical discussion will be scheduled. If not then they will be politely declined.
Be Deliberately Ignorant
Not all innovations are relevant. Maybe the tech exec at a regional insurer isn’t interested in new consumer AR hardware. Maybe the CTO at a manufacturing company doesn’t need to attend a fintech blockchain summit. However, the temptation to know everything can mean you have a lot of shallow knowledge.
If you have a couple of areas you are deliberately ignorant about then less is more. You are not lazy, you are looking at the bigger picture. The time you would have spent on these areas will now be spent focusing on the pain points of integrating, the exact latency requirements of your production system and the skills gaps in your team. Quality over quantity each quarter.
Business Focus
Only what impacts your business metric matters. If a technology improves speed but doesn’t impact infrastructure costs or customer experience then it doesn’t matter. If a programming language doesn’t assist with recruitment or creating better products then it doesn’t matter. If a new database architecture does not allow the organisation to deliver features competitors can’t then it doesn’t matter.
If you are only focussed on the quality of engineering then you will have some great tools that do not impact revenue. If you are only focussed on cutting costs then you will miss out on any architectural changes that could revolutionise our industry in 3 years. This should be a strategic decision and should be discussed with peers, tested and held accountable to the board.
Make It Routine
Tracking innovation should be made a routine task. It can help keep CTOs up to date with the latest developments. Each task has a purpose and will provide some insight into the development area. Finding a solution is worth looking into. Although this may not seem very exciting, the effectiveness comes from being consistent. It is more about finding the right information to the right people consistently to build a system.
Add Business Connect magazine to your Google News feed
