CIOs do setor financeiro aceleram IA mas carecem de governança
Nove em cada dez diretores de tecnologia da informação (CIO) do setor financeiro aceleraram a adoção de inteligência artificial (IA) no último ano, mas a maioria ainda carece de governança e capacidade para escalar as iniciativas.
Nove em cada dez diretores de tecnologia da informação (CIO) do setor financeiro aceleraram a adoção de inteligência artificial (IA) no último ano, mas a maioria ainda carece de governança e capacidade para escalar as iniciativas.
Em contexto
- Tema: Estrategia y Gobierno de TI — Decisiones de portafolio, costo total, gobierno y marcos de referencia.
- Fonte: IT Forum
- Publicado: 09/09/2026
Continuar lendo na fonte original →
Trecho publicado automaticamente pelo radar do site. O texto completo pertence ao veículo e está vinculado acima.
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.
When I look at a move like this, the question is not which tool they bought but which capability was left installed: an architecture function that holds the line on criteria, a prioritised portfolio with real business owners, and metrics somebody actually reviews every week. Without that, any announcement dissolves within twelve months.
What usually goes wrong
What usually goes wrong is the part never discussed with the areas that will carry the work. It gets decided at the top, communicated downward, and the resistance shows up not as opposition but as slowness. Nobody says no; everything simply takes twice as long and nobody can explain why.
What to watch
- 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 the relationship with current vendors is left, which is usually where the dependency nobody measured is sitting.
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.
The original story is published in another language; the excerpt is quoted as the publisher delivers it and the commentary is written in English.
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.
