In many organizations, judgment is discussed as a personal quality.
Someone is said to have “good judgment.”
Someone else is seen as lacking it.
When decisions don’t hold, the explanation often becomes individual.
But in practice, I’ve found that judgment behaves much more like a system-level outcome.
Across programs and portfolios, the same patterns show up regardless of who is leading:
signals are surfaced late or softened,
tradeoffs are acknowledged but not enforced,
decisions are approved without clear ownership of consequence.
Over time, those conditions shape what people are able to do. Even experienced PMs and delivery leaders struggle to exercise judgment when interpretation is fragmented and decisions don’t reliably close.
By the time the impact becomes visible, it rarely looks like a judgment issue. It shows up as missed milestones, delivery pressure, or execution churn.
From that perspective, judgment isn’t something individuals simply “apply.”
It’s something the organization either enables or erodes through structure, incentives, and decision design.
I’m curious how others here experience this.
When projects struggle, do you most often trace the root cause back to:
delivery discipline,
planning and prioritization,
or earlier strategic and governance decisions that never fully resolved?
Looking forward to learning how this shows up across different PMO and delivery contexts.
PMO Leader | Speaker & Mentor | Content Leader – PMOGA Latin America
Hub| Catholic University of UruguayMontevideo, Montevideo, Uruguay
I think this is a very accurate assessment. I agree that judgment rarely fails due to a lack of individual ability, but rather because of the conditions surrounding it. In my experience, projects are most affected by unresolved strategic and governance decisions that end up filtering through to execution. When the structure does not clarify responsibilities and incentives, even the most experienced leaders find their judgment limited. Delivery discipline and planning are essential, but if the strategic foundation is fragmented, these practices become palliatives rather than solutions. I believe that the challenge for PMOs is precisely to create environments where judgment can flourish as a collective outcome, rather than as an isolated attribute of a few.
...
1 reply by Imran Afzal
Feb 02, 2026 8:43 AM
Imran Afzal
...
Fabian — thank you for this perspective. I really agree with how you describe delivery discipline and planning as temporary fixes when the strategic foundation is fragmented.
In those environments, rigor downstream can help stabilize execution for a while, but it can’t make up for unresolved decisions upstream.
Your point about responsibilities and incentives is especially important. When those aren’t clear or aligned, judgment doesn’t disappear because leaders lack capability—it gets constrained by the system they’re operating in.
I also appreciate how you frame judgment as a collective outcome, not an individual attribute. That feels like the core challenge for PMOs—moving beyond supporting execution to shaping the conditions where interpretation, ownership, and consequence actually hold together.
Curious how you’ve seen PMOs most effectively influence that shift in practice—through governance design, decision forums, or something else?
I think this is a very accurate assessment. I agree that judgment rarely fails due to a lack of individual ability, but rather because of the conditions surrounding it. In my experience, projects are most affected by unresolved strategic and governance decisions that end up filtering through to execution. When the structure does not clarify responsibilities and incentives, even the most experienced leaders find their judgment limited. Delivery discipline and planning are essential, but if the strategic foundation is fragmented, these practices become palliatives rather than solutions. I believe that the challenge for PMOs is precisely to create environments where judgment can flourish as a collective outcome, rather than as an isolated attribute of a few.
Fabian — thank you for this perspective. I really agree with how you describe delivery discipline and planning as temporary fixes when the strategic foundation is fragmented.
In those environments, rigor downstream can help stabilize execution for a while, but it can’t make up for unresolved decisions upstream.
Your point about responsibilities and incentives is especially important. When those aren’t clear or aligned, judgment doesn’t disappear because leaders lack capability—it gets constrained by the system they’re operating in.
I also appreciate how you frame judgment as a collective outcome, not an individual attribute. That feels like the core challenge for PMOs—moving beyond supporting execution to shaping the conditions where interpretation, ownership, and consequence actually hold together.
Curious how you’ve seen PMOs most effectively influence that shift in practice—through governance design, decision forums, or something else? Saving Changes...
Luis BrancoCEO| Business Insight, Consultores de Gestão, LdªCarcavelos, Lisboa, Portugal
Excellent reflection. I fully agree with the core premise.
In practice, judgment rarely breaks down because of individual capability. It breaks down when the system no longer allows judgment to be exercised with clarity and consequence.
I consistently see three forms of organizational erosion.
First, decisions without a real owner. When approvals are not paired with explicit accountability for consequences, judgment turns into opinion. The decision exists on paper, but it never truly closes in the system.
Second, trade-offs that are acknowledged but not owned. Saying “we know this increases risk” without adjusting scope, timeline, or priorities is not judgment. It is deferred tension. The cost simply reappears later, during execution.
Third, governance that arrives after the fact. When strategic intent, capacity constraints, or risk appetite are not resolved upstream, projects inherit ambiguities that no level of delivery discipline can compensate for.
This is why, when projects come under stress, I rarely start by questioning delivery discipline or planning. More often, the root cause lies in early decisions that were incomplete, softened, or left intentionally unresolved, pushing complexity downstream.
One practice I have seen make a real difference is treating decisions as deliverables. A clear decision record, an explicit owner, the trade-off being accepted, and the conditions under which the decision will be revisited. Without this, systems implicitly reward “approve and move on,” and judgment steadily erodes.
So the most useful question is not “who made a bad decision,” but rather “at what point did the system stop allowing good decisions to be made.”
Curious to hear from others. What decision mechanisms have you seen work best across PMOs and delivery environments?
...
1 reply by Imran Afzal
Feb 02, 2026 1:16 PM
Imran Afzal
...
Luis — this is a terrific articulation, and I think your three forms of erosion are exactly where judgment most often breaks down in practice.
Your point about decisions without a real owner resonates strongly. When approvals aren’t paired with accountability for consequence, what looks like judgment quickly degrades into opinion — and, as you put it, the decision never truly “closes” in the system.
I also really like how you frame acknowledged-but-unowned tradeoffs as deferred tension. That’s such an accurate description. The organization feels momentary relief upstream, but the cost simply reappears later — usually in the form of delivery pressure that teams are then asked to absorb.
And governance arriving after the fact is a pattern I see constantly. When intent, capacity, and risk appetite aren’t resolved early, projects inherit ambiguity that no amount of downstream discipline can compensate for.
Treating decisions as deliverables is a powerful practice. Explicit ownership, recorded tradeoffs, and clear revisit conditions create the obligation loop that allows judgment to actually hold over time. Without that, “approve and move on” becomes the default behavior the system rewards.
Your closing question really gets to the heart of it — not who made a bad decision, but when the system stopped allowing good ones to be made. That feels like the right diagnostic lens.
Curious to hear more about where you’ve seen decision-as-deliverable practices stick long term — especially in portfolio or PMO contexts.
Judgment can break down at any time, including before a project begins and after it closes. We're dealing with people who, by nature, can have misaligned objectives and priorities. I think that some, not all, breakdowns during projects are really symptoms of larger, organizational problems.
How have I seen this show up? I think the most common way I've seen this show up is never-ending firefighting mode, chasing after quick wins and thinking that eventually you'll find the right one and turn things around. This spawns projects that probably never should have been considered, creating the situation that, even if judgment during the project is perfect, you're still doing the wrong thing (or at least not the best thing for your circumstances).
...
1 reply by Imran Afzal
Feb 02, 2026 1:21 PM
Imran Afzal
...
Aaron — this is a great example of how judgment can fail before delivery ever really begins.
Your description of perpetual firefighting and chasing quick wins resonates. That pattern often signals that the organization is optimizing for motion rather than choice. Even strong judgment within a project can’t compensate for starting the wrong work in the first place.
I also appreciate your distinction that not every breakdown is systemic—but many are symptoms of larger organizational misalignment. When objectives and priorities are unstable, judgment gets exercised locally while direction remains incoherent globally.
What you describe—projects that never should have been considered—feels like a failure of entry judgment, not execution judgment. Once work is underway, teams are often left trying to make the best of a decision that was never fully resolved upstream.
That’s where I’ve seen PMOs add the most value: not by improving delivery once the train has left the station, but by slowing things down just enough at the front door to force clarity about intent, tradeoffs, and opportunity cost.
Thanks for grounding this in lived experience—it adds an important dimension to the conversation.
Excellent reflection. I fully agree with the core premise.
In practice, judgment rarely breaks down because of individual capability. It breaks down when the system no longer allows judgment to be exercised with clarity and consequence.
I consistently see three forms of organizational erosion.
First, decisions without a real owner. When approvals are not paired with explicit accountability for consequences, judgment turns into opinion. The decision exists on paper, but it never truly closes in the system.
Second, trade-offs that are acknowledged but not owned. Saying “we know this increases risk” without adjusting scope, timeline, or priorities is not judgment. It is deferred tension. The cost simply reappears later, during execution.
Third, governance that arrives after the fact. When strategic intent, capacity constraints, or risk appetite are not resolved upstream, projects inherit ambiguities that no level of delivery discipline can compensate for.
This is why, when projects come under stress, I rarely start by questioning delivery discipline or planning. More often, the root cause lies in early decisions that were incomplete, softened, or left intentionally unresolved, pushing complexity downstream.
One practice I have seen make a real difference is treating decisions as deliverables. A clear decision record, an explicit owner, the trade-off being accepted, and the conditions under which the decision will be revisited. Without this, systems implicitly reward “approve and move on,” and judgment steadily erodes.
So the most useful question is not “who made a bad decision,” but rather “at what point did the system stop allowing good decisions to be made.”
Curious to hear from others. What decision mechanisms have you seen work best across PMOs and delivery environments?
Luis — this is a terrific articulation, and I think your three forms of erosion are exactly where judgment most often breaks down in practice.
Your point about decisions without a real owner resonates strongly. When approvals aren’t paired with accountability for consequence, what looks like judgment quickly degrades into opinion — and, as you put it, the decision never truly “closes” in the system.
I also really like how you frame acknowledged-but-unowned tradeoffs as deferred tension. That’s such an accurate description. The organization feels momentary relief upstream, but the cost simply reappears later — usually in the form of delivery pressure that teams are then asked to absorb.
And governance arriving after the fact is a pattern I see constantly. When intent, capacity, and risk appetite aren’t resolved early, projects inherit ambiguity that no amount of downstream discipline can compensate for.
Treating decisions as deliverables is a powerful practice. Explicit ownership, recorded tradeoffs, and clear revisit conditions create the obligation loop that allows judgment to actually hold over time. Without that, “approve and move on” becomes the default behavior the system rewards.
Your closing question really gets to the heart of it — not who made a bad decision, but when the system stopped allowing good ones to be made. That feels like the right diagnostic lens.
Curious to hear more about where you’ve seen decision-as-deliverable practices stick long term — especially in portfolio or PMO contexts. Saving Changes...
Judgment can break down at any time, including before a project begins and after it closes. We're dealing with people who, by nature, can have misaligned objectives and priorities. I think that some, not all, breakdowns during projects are really symptoms of larger, organizational problems.
How have I seen this show up? I think the most common way I've seen this show up is never-ending firefighting mode, chasing after quick wins and thinking that eventually you'll find the right one and turn things around. This spawns projects that probably never should have been considered, creating the situation that, even if judgment during the project is perfect, you're still doing the wrong thing (or at least not the best thing for your circumstances).
Aaron — this is a great example of how judgment can fail before delivery ever really begins.
Your description of perpetual firefighting and chasing quick wins resonates. That pattern often signals that the organization is optimizing for motion rather than choice. Even strong judgment within a project can’t compensate for starting the wrong work in the first place.
I also appreciate your distinction that not every breakdown is systemic—but many are symptoms of larger organizational misalignment. When objectives and priorities are unstable, judgment gets exercised locally while direction remains incoherent globally.
What you describe—projects that never should have been considered—feels like a failure of entry judgment, not execution judgment. Once work is underway, teams are often left trying to make the best of a decision that was never fully resolved upstream.
That’s where I’ve seen PMOs add the most value: not by improving delivery once the train has left the station, but by slowing things down just enough at the front door to force clarity about intent, tradeoffs, and opportunity cost.
Thanks for grounding this in lived experience—it adds an important dimension to the conversation. Saving Changes...
Program Manager| HARPER SRLSanto Domingo / Distrito Nacional, Dominican Republic
I see judgment breaking down when decisions don’t truly close. When ownership is vague, trade-offs are acknowledged but not enforced, or governance arrives after execution starts, even strong leaders lose room to exercise judgment. At that point, delivery problems are just symptoms of unresolved decisions upstream. Saving Changes...
In my experience, judgment breaks down long before delivery. Weak governance signals, unclear priority tradeoffs, and decisions approved without real ownership shape the conditions PMs work in. By the time delays appear, the root cause is usually unresolved strategy or fragmented decision paths rather than execution alone. Strong judgment needs strong decision design. Saving Changes...
Community Champion
