CIO magazine's Beverly Head asked Coles CEO John Fletcher and CIO Peter Mahler about the company's IT and the controversy that arose during the takeover. Here are their answers:
How would you describe your information systems at present?
Coles CEO John Fletcher: When I came to Coles we were dealing with a maze of disparate systems, which was mostly a legacy of the way the company had grown over time through mergers and acquisitions. Since then we've massively re-engineered our IT platforms and are ready to reap substantial business benefits as a result.
I took this role for the challenge, and was not disappointed
Coles CIO Peter Mahler: I took this role for the challenge, and was not disappointed. As John has said, the systems were a legacy of the company's growth via acquisition. Most of the technology was developed in-house too, which created a lot of problems for the business when it needed new functionality to compete successfully.
The systems today are significantly different; we don't develop in-house any more, we buy best practice and refine to suit out needs. We have a strong focus on strategic architecture, so our systems are largely integrated. Systems are modular, [which means] we are flexible in responding to market needs and we don't have to spend a month trawling through indecipherable code that was written by 50 different people over decades. Less focus on the minutiae of the code means we can focus on engagement with the business.
To what extent does IT influence Coles' business strategy — to what extent is IT an enabler of change?
Fletcher: IT enables the business strategy. We are fortunate to have a team that is focused on how to support the business in achieving the strategy. This is possible because IT has a seat at the table — Peter is on the executive team and reports directly to me.
Mahler: I believe that IT should be intimately involved in the business; we need to understand the business, otherwise how can we ensure that our work enables the business to meet its objectives? The days of getting isolated requests for programming then throwing the code back over the fence for the business to deal with are long gone.
The relationship is much more sophisticated these days, throughout the corporate world. In Coles, technology requirements are defined by the business and IT working together, based on the business's strategic objectives. On major technology changes, IT is in a unique position to use our inherent process and analysis skills to guide the business in their thinking about managing change. We can help them understand the implications of changes because our experience reaches into all parts of the business. We can see the interactions between elements of the business because we have to understand them in order to implement systems.
How does a fast-moving enterprise cope with the nexus that exists between developing new applications for current strategy, while maintaining sufficient agility to be able to cope with any changes that are required by rapidly shifting business conditions?
Fletcher: There's no denying that we embarked on a massive transformation program, and I think such programs are always tweaked and refined as the business requires. Over the course of our transformation program, we have brought some initiatives forward, and pushed other initiatives back where it made business sense to do so. This does require a degree of flexible thinking by a management team, and I think it's been a feature of our team that we've been able to focus on what's best for the business when these sort of calls are made.
Mahler: I anticipated in 2002 that things would change over the course of the five-year strategy. It would have been foolish to think otherwise. So we designed the IT strategy very consciously to cover both the long-term strategic requirements and the shorter-term operational requirements. As well as some flex for any surprises, which did come — retailing is a very dynamic environment. And we did all of this within a pressured cost environment.