Back to the radar Projects, PMO and Risk

Seu Projeto Tem Pressa Demais para Pensar?

Projects, PMO and Risk

Neste episódio, Ricardo reflete sobre a pressa de iniciar ações em projetos sem compreender o problema. Ele explica que agir transmite sensação de progresso, enquanto pensar pode parecer perda de tempo, embora decisões precipitadas gerem reuniões, retrabalho, atrasos e desperdício.

Neste episódio, Ricardo reflete sobre a pressa de iniciar ações em projetos sem compreender o problema. Ele explica que agir transmite sensação de progresso, enquanto pensar pode parecer perda de tempo, embora decisões precipitadas gerem reuniões, retrabalho, atrasos e desperdício.

Em contexto

  • Tema: Proyectos, PMO y Riesgos — Gestión de proyectos, oficinas de proyecto y riesgo del portafolio.
  • Fonte: Ricardo Vargas
  • Publicado: 16/08/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

Projects rarely fail on the day they are declared failed. They fail months earlier, in a meeting where somebody saw the problem coming and calculated it was not in their interest to say so. Everything else — the slipping schedule, the stretching budget — is the visible consequence of that silence.

I read these things looking for where the risk sat before it became an incident. It was almost always already written in some register nobody reviewed, with an assigned owner who never found out they were one. A risk identified and not managed is worse than one never identified: it creates the false sense that there is control.

What usually goes wrong

What I see fail most is the absent sponsor. They sign the kick-off, appear in the photo, and do not come back until there is a problem. Without somebody with real authority clearing obstacles every fortnight, the project manager ends up negotiating as an equal with areas that do not report to them, and loses.

What to watch

  • Which risks are identified, who owns each one, and when they were last reviewed.
  • 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.

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

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.

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.