Project Management

Home / Discussions / Project Management Central /

Leadership Style vs. Leadership Confidence in Program Environments

Consulting Ethics Leadership

Omar Jabbar Project Management and Digital Transformation Consultant| OGreen IT Service Inc. Ontario, Canada

I recently experienced a situation within one of the local government entities that made me reflect on leadership maturity and confidence.

When a major program supported by an executive began facing challenges, instead of addressing the root causes transparently, the division leadership chose to delay other unrelated programs. The narrative presented at the board level became: “all programs are delayed” masking the actual performance issue.

Early in my career, I received advice from an experienced Program Manager that has stayed with me:

“Never assume you are the smartest person in the room, others are just as capable, and they will see through it.”

This decision came with real consequences:

Strong program leads were removed from well-performing initiatives
Consultant contracts were terminated and replaced with junior PMs, with no knowledge transfer plan in place
Momentum, accountability, and delivery confidence were disrupted across the portfolio

This raises an important question for our community:

Is leadership about protecting optics or enabling truth and recovery?

From over 24 years of experience, more than half spent in consulting, I’ve found that confident leadership:

Owns challenges openly
Protects high-performing teams
Focuses on targeted recovery rather than broad disruption
Builds trust with stakeholders, even in difficult moments

whereas less confident leadership often:

Dilutes accountability across the portfolio
Prioritizes perception over performance
Creates wider delivery risk to shield isolated failure
Focuses on self-preservation and personal agendas, rather than transparency and organizational outcomes

In complex enterprise environments, especially within large transformation programs, how we respond to failure defines leadership more than success ever will.

Curious to hear from others:

Have you seen similar patterns in program environments?
How do you balance executive optics vs. delivery transparency?

Posted: Mar 17, 2026 9:53 AM

Sort By:

Md. Golam Rob Talukdar

Community Champion

Project Manager| AWR Development (BD) Ltd. Cox's Bazer , Bangladesh

This is a very real situation, and I’ve seen similar patterns in complex programs. When pressure increases, some leaders try to protect the narrative rather than address the root issue—but that often creates wider disruption than the original problem.
In my experience, transparency builds more long-term trust than perfect optics. Stakeholders can accept challenges if they see clear ownership and a focused recovery plan.
The real balance, I think, is not choosing between optics and truth—but framing the truth with a recovery path.
When leaders acknowledge issues early, protect strong teams, and act precisely rather than broadly, projects tend to stabilize faster and with less collateral impact.

Posted: Mar 17, 2026 6:33 PM

Lissette Indhira Pimentel Sosa

Community Champion

Program Manager| HARPER SRL Santo Domingo / Distrito Nacional, Dominican Republic

There are situations, especially in complex programs under pressure. When leaders try to protect the narrative, it usually creates more disruption than the original issue.

I think this is not about choosing between optics and transparency, but about how you communicate the truth. When challenges are acknowledged with a clear recovery path, stakeholders tend to trust the process more, even if the message isn’t perfect.

Posted: Mar 23, 2026 8:38 PM

Imran Afzal Cary, NC, United States

Omar:

This is a very real dynamic — and one that shows up most clearly in complex programs under pressure.
What’s interesting is that it’s rarely framed internally as “protecting optics.”

It usually shows up as protecting confidence.

The moment a program becomes visible at the executive level, the pressure shifts:

from understanding reality
to maintaining alignment around a narrative

And that’s where things start to drift.

Delaying unrelated programs to normalize the signal is a good example — it doesn’t solve the problem, but it stabilizes the appearance of the system.

I’ve found the more useful question isn’t:

“optics vs transparency?”

It’s:

“What does the system reward under pressure?”

Because behavior follows that very quickly.

If leaders are rewarded for:

predictability → issues get smoothed
confidence → risk gets reframed
consistency → variability gets hidden

But if leaders are rewarded for:

surfacing risk early
making tradeoffs explicit
protecting delivery capacity where it matters

Then transparency becomes a byproduct, not a choice.

The strongest environments I’ve seen don’t rely on individual courage to “tell the truth.”

They design mechanisms where:

tradeoffs are visible
assumptions are challenged
and recovery paths are expected, not exceptional

So the conversation shifts from:

“How do we explain this?”

to:

“What needs to change?”

And to your point — how leadership responds in those moments becomes the signal everyone else calibrates to.

Not what’s said.
What’s reinforced.

Most organizations don’t lose transparency because people hide the truth.
They lose it because the system quietly teaches them not to surface it.

Posted: Mar 24, 2026 12:27 AM

Please login or join to reply

Leadership Style vs. Leadership Confidence in Program Environments

Sponsors

Vendor Events

Guessing is not a strategy: How to build decision velocity with AI and real-time data

Newsletters