Throughout the year, tech executives will be able to compare notes across the most pressing IT trends, from AI cost management to cyber resilience.
Throughout the year, tech executives will be able to compare notes across the most pressing IT trends, from AI cost management to cyber resilience.
In context
- Topic: Estrategia y Gobierno de TI — Decisiones de portafolio, costo total, gobierno y marcos de referencia.
- Source: CIO Dive
- Published: 08/10/2026
Continue reading at the original source →
Excerpt published automatically by the site radar. The full text belongs to its publisher and is linked above.
Why it matters
There is a wide gap between a company that has technology projects and one that has a technology strategy. The first accumulates initiatives; the second decides what it will not do. Moves like this are usually the moment somebody at the top finally wrote down the list of what gets left out.
I read it looking for coordination cost. Every technology decision splits work across areas that do not report to each other, and that is where the return leaks out. If nobody defined who resolves it when two areas disagree, the project already has its grounding date set.
What usually goes wrong
Where I see this fail most is in the second half of the year. The announcement is made with energy, the team gets assembled, and eight months later the person driving it changed role or company. Without an institutional owner, not just a personal one, the programme fades without anybody formally cancelling it.
What to watch
- Whether business metrics appear or only delivery metrics — cost per transaction beats percentage complete.
- The real calendar of contracts and renewals: that is where you see whether the move was strategic or was an expiry date.
- What gets switched off to fund the new thing; if nothing does, the budget will hurt in six months.
How I read this entry
The way I would bring this down to earth is in three moves: name an owner with their own budget, define two metrics reviewed in committee every month, and set a date on which somebody decides to continue or stop. It is unglamorous, and it is what separates programmes that land from programmes that get discussed.
This entry is an excerpt from the original source, selected by the site radar. The commentary above is the site's own and does not belong to the cited publisher.
Comments
No comments yet. Yours can be the first.
Living through this in your own team?
Open the chat and tell me how you're handling it. I'm interested in comparing notes.
