CIO Insights: How to approach innovation

CIO Insights: How to approach innovation

Three Australian CIOs share their advice

CIOs face a multitude of challenges in their daily roles. In the first installment of our new CIO Insights series, we talk to three leading Australian technologists about their approaches to encouraging innovation in their organisations and engaging other c-level executives in the process.

Scenario: The CIO is trying to encourage innovation and has an informal approach to people submitting their ideas to the IT department. However, the CEO or another business head wants to take a different approach and review each single idea – big and small – making the approval process time consuming. The CIO’s concern is that this might stifle creativity.

What would you do in this situation? CIO Australia talks to three CIOs who share their advice.

Ajay Bhatia, CIO at

We are surrounded by uncertain times and this is making many CEOs and execs very wary of risk so doing something small is going to be more palatable than doing something big. Conservative organisations are risk averse and starting small reduces risk. But it’s about building that small innovation into your technology process.

For example, developers could be encouraged to come up with innovative ideas through the project life cycle. Agile is very helpful here as it discourages you to define everything upfront and leaves scope for you to ‘innovate as you go’. When we define a project we don’t define all of the requirements of the project upfront; we leave a lot of room for discovery, for incidental and accidentals ideas.

These wins could then be celebrated within the organisation through peer recognition and sold tactfully to the other c-level execs, including the CEO. Once the CEO starts to see value in these small ideas, she or he should be more receptive to bigger ones. The bigger ones may still require a level of approval but that is not all a bad thing.

It’s also not a bad thing in some cases for you to make the CEO believe an idea is his or hers. Innovation for most people is about what they do, not what someone else does. If someone else is creating a really interesting idea or project, then that is not necessarily always going to be seen as innovation to another person unless they have been involved at some stage during the project lifecycle.

Organisations are either culturally innovative or they are not. I’ve seen organisations where they have tried to create an innovation department or a process around innovation and it almost inadvertently fails because the organisation and the c-level suite as a whole don’t accept innovation.

So they will always focus on the short-term priorities, “let’s do this to get short-term money”. If the CIO alone is trying to fight this battle with the CEO, there is less chance of being on the winning side so you need to be on board with all the executives when it comes to them channelling ideas.

A recent example of innovation at Carsales is we recently built our own search engine, RyvusIQ. Carsales used to be previously powered by a search engine called Endeca which is now owned by Oracle. It cost us hundreds of thousands of dollars, if not a seven-figure amount of money to implement.

One of the developers came to me and the CEO and said, “You are asking me to do all these innovative things, but I cannot do them with this search engine.” And from customer feedback, they were also asking for all these new search innovations. But we were really limited with what we could do with that search engine.

The developer, along with another team leader, offered to develop a new, better search engine so we commissioned six weeks of research for them to work only on the project and prove to us what they could do and build a prototype.

Already in six weeks, there were aspects of the prototype that were better than our search engine so that gave us the confidence to continue to commission that project. We estimated the project would take a year, but it took us two years.

The organisation that built the previous search engine that Carsales used was worth $1 billion. Therefore, at first we were scared about developing a new search engine as there are billion dollar organisations out there that build search engines and here are two developers coming to me and saying they can build one that’s better.

Carsales-owned Quicksales website is also powered by that search engine, our own proprietary search engine, and we now are starting to sell that to other organisations.

Innovation is no more something nice to have for organisations. Some organisations will spend 50 per cent of their time innovating, others 1 per cent of their time. The question is not whether you should innovate or not, it is how much time you allocate for innovation.

The best thing is to work on an acceptable level of risk taking within the organisation while educating the other executives on the value of innovation. This is why I define innovation as new thinking that creates value because all of the execs love value. At the end of the day, there is value, but there is also some risk that comes with it. It’s just balancing the two.

Alex Jones, CIO at Synergy

From a stakeholder management perspective, it’s important that the beneficiaries of any innovation (generally not the CIO) are actually involved in supporting the concept. So if you are going to run an innovation process that’s designed to benefit a certain part of the business then you really want to get that part of the business involved before you get started.

When it comes to deciding on the process you could say, “I know we haven’t done this before in this organisation but I have done some research and have sought opinions from experts and it seems that this particular process would be effective in bringing the benefits of innovation to you. What do you think?” Then you can have that conversation about who has what role in driving an innovation process.

Once having agreed on that, then you start soliciting ideas from the employees or customers or whoever you are going to get your ideas from. You have to get an agreement on what you are going to do in terms of the innovation process before you go out there asking people for ideas.

In regards to the CEO or the other business executive wanting to review and approve each single idea, if you ask yourself the question “why do people micro manage?” it’s because they don’t have confidence that the process as it stands is going to deliver the right result. Maybe they are concerned that it’s a waste of time and the team doesn’t have capacity to do all of this.

Join the CIO Australia group on LinkedIn. The group is open to CIOs, IT Directors, COOs, CTOs and senior IT managers.

Join the newsletter!


Sign up to gain exclusive access to email subscriptions, event invitations, competitions, giveaways, and much more.

Membership is free, and your security and privacy remain protected. View our privacy policy before signing up.

Error: Please check your email address.

Tags stakeholder engagementtechnology innovationCIO Ajay BhatiaCIO Alex JonesCIO Christopher Topp

More about AgileFacebookOracleSynergy

Show Comments