A business that has outgrown its systems needs to know why before it briefs a CIO

Jake Rose
Jake Rose Technology Executive Search Partner
October 2026
6 min read

“We’ve outgrown our systems” opens a lot of CIO searches, and it tells me the symptom without telling me the mandate. Why the systems fell behind has more than one answer, and the answers don’t produce the same role. A function that was seen as a cost centre and never funded to keep pace needs a different CIO from a business where the market moved faster than anyone could have kept up with, and both are different again from a merger or a technology leadership build-out. Which of those applies, and in what proportion, is what I’m trying to find out before the search goes anywhere, and the answer usually puts the CFO and the rest of the leadership team in the picture alongside whoever last held the role.

What the brief over-indexes on

The pattern is easy to recognise. The platforms are unsupported, and the business has already decided what the previous CIO’s weaknesses were. So the brief lists the systems, asks for someone who has fixed those systems before, and the search goes to market for a platform person.

What that misses is the capability that would have stopped it happening. Of the CTOs and CIOs I’ve placed in Australia, I’ve never placed one based on how capable they are technically. There are a lot of brilliant technologists who can explain the platform, the architecture and the team and can’t tell you what any of it did to margin, growth or business value, and a CIO who could make that case to the CFO as the business grew would usually have got the funding to keep the systems in step with it. Someone who has made that case to a CFO before is the harder person to find, and a search that goes to market off the systems list won’t surface them.

Why the systems fell behind has more than one answer

Bear in mind it might not have been the CIO’s fault. Technology may have been seen as a cost centre and never funded to keep the systems in line with where the business had grown to, and businesses that have only ever seen IT as a cost centre tend to get the cost centre they budgeted for, which is usually a self fulfilling prophecy. The business might be under new ownership, with a recognition that the previous CIO wasn’t fit for purpose. Or maybe it was their fault, maybe it was poor leadership above them, maybe it was a lack of investment. There are so many variables it could be, and a brief that settles on one of them early tends to settle on the one that fits the systems list.

The CFO belongs in the frame as well. Systems pain can reflect a lack of forward thinking, systems thinking and commercial acumen in the previous leadership team, and that doesn’t just fall at the feet of the CIO, it’s the CFO as well. There needs to be coherence within a leadership team for systems pain not to be there, and it’s always there to some degree. So “we’ve outgrown our systems” is the start of a diagnosis. Every growing business has some of this pain, and the useful questions are how much of it was avoidable, who had the levers to avoid it, and whether those people are still on the leadership team when the new CIO arrives.

The business that hasn’t noticed

There’s an opposite version as well, and I’d put it in front of any board that is briefing for AI transformation. The business is focused on what’s new, what’s shiny and how it can transform with AI, and it doesn’t know that the systems underneath have already been outgrown by the business. Nobody has written “outgrown our systems” on the brief because nobody has looked. The mandate in that business is the same diagnosis in reverse: before the CIO can do anything the board will recognise as transformation, they have to find out how far behind the base is and get the leadership team to fund closing that gap, which is a harder commercial sell than the AI roadmap ever was.

The same title, three different jobs

Across my career before Innova I’ve placed CIOs into PE-backed and ASX-listed businesses, and the role has meant something different each time because what “outgrown” meant was different.

One was a group formed by merging two businesses under one owner. The CIO was appointed for the new group, so the job was defined by the merger itself before any systems list came into it. That person has to be credible with two leadership cultures at once, and a systems list says nothing about that.

Another was a PE-backed business where the CIO appointment sat inside a complete technology leadership build-out. Outgrown there meant the function had never been built for the size the business had reached, and the first hire’s job was to build the team beneath them, which is a different person again from someone who inherits an established function and a neglected estate.

The third version I see more as a pattern than from any one appointment, where technology was seen as a cost centre and never funded to keep the systems in line with where the business had grown to, so the CIO walks into a leadership team that still has to be sold on funding it. That person needs the commercial case first and the platform plan second, and the test for it is whether they can back up what they’ve delivered before with real, measurable dollar values the CFO and the board will accept. The title is the same on all three and the brief is different each time, which is why the systems list on its own tells me very little about who to go and find.

The question I put to a client before the brief is set

So before I accept the stated problem, what I want to know is what the actual pain is. What’s broken, and what is actually good and working? Have you got unsupported platforms that you’ve just neglected, or is this a case of the world and the market moving faster than you ever could have? Most of the briefs I take now are over Teams, and that is the question I put to whoever is on the call, because there are so many variables it could be and which of them apply is what sets the mandate.

If the answer is neglect, the role is a recovery and the person needs to have rebuilt a function’s credibility with a CFO before, with the numbers to show for it. If the answer is the market, nobody needs blaming, the role is a catch-up and the brief can look forward from day one. Systems pain is always there to some degree, so the answer can carry some of both, and a brief that settles on one of them early tends to go to market for the systems rather than the commercial acumen that should have kept them scaling with the business.

Frequently asked questions

Only once you’ve worked out how much of the pain was theirs to prevent. Technology may have been seen as a cost centre and never funded to keep pace with growth, and the coherence a leadership team needs to keep systems pain down is the CFO’s responsibility as much as the CIO’s. A brief that starts from the last person’s gaps tends to describe the systems, and the capability that keeps systems scaling with a business is commercial.
The technical fix is the baseline. What I test for in every search is whether someone can simplify technical complexity, translate it into outcomes the CEO, CFO and board understand, and back those outcomes up with real, measurable dollar values. Someone who has done that inside a business that treated IT as a cost centre is more use than someone who has run the same platform somewhere it was properly funded.
Something different from a repair in both cases. In a merger the CIO is appointed for a group that didn’t exist before the deal, so the brief has to describe what the combined business needs and the two leadership cultures the person has to carry with them, and the state of either side’s platforms is a smaller part of it than it looks. In a PE-backed build-out the function is being put together around the appointment, so the brief has to describe someone who can lead and structure a team so it can move the needle, as well as run what they inherit. Neither is a platform fix, and briefing either as one narrows the search to the wrong people.

What this means for a CEO, a CFO or an operating partner about to brief the role is that the previous CIO is rarely the whole explanation, and a brief written against their perceived weaknesses hires for the systems. Work out why the systems fell behind, be straight about where the leadership team sat in that, and the mandate follows from the answer. I’ve written before about the questions a brief usually doesn’t answer, and in the outgrown-systems case this is the one to start with. If you’re about to open a CIO role on that basis, start with me.

Jake Rose
Jake Rose
Co-Founder & Technology Executive Search Partner, Innova Search
Jake partners with investors, boards and CEOs on critical technology leadership hires across private equity, ASX-listed and high-growth businesses.

Starting a technology leadership search?

The brief is where it begins. Let's get it right.

Start a conversation