When the roadmap outruns the leadership under it

A new CEO, CFO or transformation lead sets the agenda in the first quarter, resets the operating model, and then finds that the technology leadership was built for the plan before theirs. Nobody did anything wrong. The team delivered what the last plan asked of it. The new plan asks for something else: a platform modernised, a data layer that can carry AI into production, a delivery function that moves at the pace the board was promised.

That is the moment a CIO or CTO search starts, and it is the moment most of them go wrong, because the brief describes the old seat with a bigger title.

Why first shortlists miss

We see the same five causes, in roughly this order.

The brief is a skills list. Twelve technologies, three certifications and “proven leadership”. A skills list describes a hundred people and none of them in particular. The people who can actually do this job will not read it, and the ones who do will not be the ones you want.

The title has outrun the remit. A role called Chief Technology Officer that reports to the COO, owns no budget and inherits a run function will attract CTOs for exactly one conversation. Candour about what the seat really is, early, saves the search from a shortlist that walks.

The comp was set to the last role. The last CIO was hired three or four years ago, into a smaller mandate, in a different market. If the number has not moved with the remit, the market will say no and it will say it late, after you have invested in the process.

The process assumes availability. The right people for this seat are in jobs they are good at. A process designed for active candidates, a long form and a portal, screens out the people you most want before anyone has spoken to them.

Nobody has written down what success is. “Transform the function” is not a measure. Without three plain statements of what must be true in eighteen months, every interviewer assesses against a different picture and the panel cannot agree.

What a brief that lands actually contains

The briefs that produce the right shortlist first time have six things in them, and almost none of them are about technology.

1. The plan, and what it needs from this seat in eighteen months. Not the strategy document. The two or three outcomes the CEO will be judged on, and which of them depend on this hire.
2. The team as it really is. Who is strong, who is tired, who will leave when a new leader arrives, and what the new leader is expected to do about it. Candidates ask this in the first conversation. If the answer is honest, it becomes a reason to take the role.
3. The board’s expectation and its tolerance. How much change the board will fund, how fast it expects to see it, and what it will not forgive. A first-time CIO and a sitting CIO read this very differently, and it tells you which of them you need.
4. Three things that must be true in year one. Written as outcomes a referee could confirm. These become the assessment framework, so the panel scores the same thing.
5. The why-now you will say out loud. The story a candidate hears about why this role exists and why it is worth leaving a good job for. If that story is not ready, the search is not ready.
6. The money, and the market’s view of it. We tell you in the first week whether the package will reach the people you have described. If it will not, you decide early whether to move the number or move the brief.

Where these people are

Almost none of them are on the market. The leaders who have modernised a stack and held a board’s confidence while they did it are mostly still in the seat where they did it. They take a call because of the relationship behind it and because the story is specific, not because a role was advertised.

Three pools produce most of the strong shortlists for this seat. Sitting CIOs and CTOs in organisations one size down, who have done the hard version of your program and are ready for a bigger stage. Transformation and program directors who have landed the platform your plan depends on and are ready to own the function rather than the program. And technology leaders from consulting and systems integrators who have run the delivery for clients like you and want the line role, which is a strong source when the brief is honest about operating rhythm.

Each pool comes with a different conversation about readiness, comp and timing. The brief decides which pools are worth working.

Assessing for the seat, not the CV

The CVs in this market look alike. Everyone has led a transformation. The assessment has to get underneath that to what the person actually did, decided and carried.

We assess against the brief, not against a skills list. For each of the three year-one outcomes, we want evidence of a comparable thing done: the platform decision they made and defended, the team they rebuilt and how they handled the people who did not come with them, the board paper that changed a decision, the vendor they held to account. We want to know what they got wrong and what it cost. Referees are taken from above and beside the candidate, not only below.

That is slower than a keyword match and it is why the shortlist holds when the panel meets it.

What the process looks like with us

A retained search for a CIO or CTO runs three to six weeks from brief to accepted offer. The brief is written as the story a candidate will hear and tested on the first calls. Steering is weekly, with the market map on the table: who has been approached, who has said what, and what the market is telling us about the role. The assessed shortlist arrives in weeks three to four, scored against the brief with the reasoning shown. If the role is mispriced or the process is costing you candidates, you hear it in week one, not week five.

The seat you are filling decides whether a plan lands. It is worth briefing properly.

Questions clients ask