Back to the radar Projects, PMO and Risk

Cuando el software funciona, pero el proyecto no

Hablar hoy de transformación digital supone hablar, casi inevitablemente, de velocidad y no solo de software o hardware. Las organizaciones necesitan automatizar, mejorar su eficiencia, digitalizar procesos y responder a

Hablar hoy de transformación digital supone hablar, casi inevitablemente, de velocidad y no solo de software o hardware. Las organizaciones necesitan automatizar, mejorar su eficiencia, digitalizar procesos y responder a

En contexto

  • Tema: Proyectos, PMO y Riesgos — Gestión de proyectos, oficinas de proyecto y riesgo del portafolio.
  • Fuente: Revista Byte TI
  • Publicado: 14/09/2026

Seguir leyendo en la fuente original →

Extracto publicado automáticamente por el radar del sitio. El texto completo pertenece a su medio y se enlaza arriba.

Why it matters

A project management office is worth the decisions it makes possible, not the reports it produces. Once the PMO becomes the function chasing status updates, it has already lost: the team learns to fill in the template and the real information goes back to travelling through the corridors.

My filter is the quality of the status report. If every project is green, the reporting system is not working: in any real portfolio some initiatives are in trouble, and a healthy organisation surfaces them in time rather than discovering them at the closure committee.

What usually goes wrong

The classic mistake is treating risk management as a deliverable of the planning phase. The matrix gets built, approved, filed. Nobody opens it again until closure, when it serves to document that the risk was foreseen — which is exactly the opposite of managing it.

What to watch

  • The size of the first useful delivery: the further out it is, the more it resembles a bet.
  • How it was estimated and how close the same organisation's previous estimates turned out to be.
  • Who the sponsor is and how often they actually show up — not on the org chart, in the calendar.

How I read this entry

I would use it to review how the organisation estimates. If historical estimates were systematically out by half and nobody adjusted the method, no project will land well: you are planning with a ruler that measures short and blaming the team for not reaching the mark.

The original story is published in another language; the excerpt is quoted as the publisher delivers it and the commentary is written in English.
Share

Comments

No comments yet. Yours can be the first.

Plain text only, no links. No email is requested. Comments are reviewed before they are published.

Living through this in your own team?

Open the chat and tell me how you're handling it. I'm interested in comparing notes.

Keep reading

More entries from the radar

See all
Darinel Ortega Online · I reply during the day
Today
Hello. I'm not selling anything here: this is for exchanging knowledge about technology.
Write whatever you like — you can send text, images or documents. Messages reach my console and I reply from there.
You are writing outside working hours. I will read you as soon as the day starts.

An open conversation to share knowledge. Messages reach my console and I reply from there.

Let us book a conversation

Pick the day and time that work for you. Thirty minutes, no sales pitch.

Video call

For a video call, just ask for one here and I'll send you the session link.