Do you need a full-time CIO?

The question tends to arrive after something went wrong: a system selection nobody felt qualified to run, a vendor relationship that drifted, a project that should have been stopped six months earlier. Underneath it is usually the same observation — the decisions have outgrown whoever has been making them alongside another job.

What the trigger actually is

Not headcount, and not revenue. Three things:

Decisions are being deferred. Nobody has the standing or the time to make a call, so it waits, and waiting has a cost.

Nobody is accountable for the estate as a whole. There are people running parts of it well, and nothing joining them up.

The organization is being sold to rather than buying. Vendor relationships are setting direction because no internal view exists to set it instead.

When a full-time hire is right

The work has to be continuous and large enough to hold a senior person’s attention. That usually means a technology function of meaningful size, a business where technology is core to how revenue is earned, or a multi-year program that genuinely requires daily leadership.

It also requires the organization to be able to attract someone good. A senior technology leader in a business with no budget, no mandate and no seat at the table will not stay, and the failed hire costs more than the vacancy did.

When part-time fits better

Part-time leadership works when what you need is judgment, direction and accountability rather than daily operational presence. The specific situations:

• A capable team that needs direction and someone to hold the vendor relationships.
• A defined period — a transformation, a system selection, a post-acquisition integration — with a natural end.
• A business where the technology decisions are consequential but not continuous.
• A bridge while a permanent search runs, so the decisions do not wait for the hire.

What it is not

It is not a cheaper way to get a delivery team. A part-time technology leader can set direction, make decisions, hold suppliers to account and build the plan. They cannot also be the architect, the project manager and the support function — and an arrangement that quietly expects that will disappoint everyone.

The cost of deferring

The decisions still get made. They get made by vendors, by whoever is most confident, or by default through inaction. A system gets selected because a demonstration went well. A contract renews because nobody diarized the notice period. A project continues because stopping it requires someone to decide.

That is the real comparison. Not the cost of leadership against zero, but against the cost of the decisions that happen without it.