The “don’t mention it” trap
I once bought an elephant for a friend to put in his living room.
When he tried to thank me, I smiled and said, “Don’t mention it.”
It is a classic dad joke. In program leadership, it is a failure pattern.
In complex initiatives, the problem is often obvious long before it is discussed. The risk is visible. The tension is real. The misalignment is shared by everyone in the room.
And yet no one names it.
Teams stay polite. Leaders protect reporting lines. Conversations avoid friction. What follows is not alignment. It is drift.
Delivery rarely fails because people did not see the issue. It fails because no one took responsibility for saying it out loud.
That silence is the trap.
In one line
Naming the elephant doesn’t create risk. It reveals the risk that already exists.
The first elephant: methodology bias
One of the most common elephants in delivery is the assumption that credentials define behavior.
Because I hold formal project management training, people sometimes assume I’m a rigid “waterfall” leader. That assumption is incorrect and often harmful.
Over time, I have led agile, hybrid, and traditional initiatives using Scrum, Extreme Programming, Behavior Driven Development, and other approaches. The objective was never methodological purity. The objective was delivery.
Deliver usable value as quickly as possible, at the lowest responsible cost, without skipping the hard parts.
Methods are tools. Labels are not strategies. When teams stop debating which framework they are in and start focusing on what must move next, delivery accelerates.
Bad elephants and useful elephants
Not every elephant is a problem, but every elephant matters.
- Bad elephants: unspoken risks, technical debt, misaligned goals, unrealistic assumptions.
- Useful elephants: strengths or opportunities that accelerate delivery once named.
Leadership isn’t about eliminating elephants. It is deciding which ones require attention now, before delay turns them into damage.
Ignoring an elephant does not neutralize it. It gives it time.
The elephant pack: balancing the six constraints
Every transformation, whether a billion-dollar enterprise modernization or a home repair, operates under the same six constraints:
- Time
- Cost
- Scope
- Resources
- Risk
- Quality
These constraints do not move independently. When one shifts, the others respond, whether anyone acknowledges it or not.
Time compresses quietly. A date turns into a commitment, then an assumption, while the work remains unchanged.
Cost rarely explodes all at once. It creeps forward through small approvals and temporary decisions that quietly become permanent.
Scope is the stabilizer that keeps the rest of the pack in formation. When scope expands without being named, every other constraint absorbs the impact.
Resources stretch before they break. Teams compensate until fatigue becomes normalized and warning signals are missed.
Risk does not disappear when ignored. It accumulates silently and surfaces when options are limited and pressure is highest.
Quality erodes last and loudest. By the time customers feel it, trust has already been spent.
When leaders fail to name movement in the constraints, they are not avoiding disruption. They are postponing it.
That is the elephant pack.
Leading under pressure
When a program is under pressure, the temptation to “not mention it” is at its highest.
This is when I return to root cause thinking, asking Why? and How? until the problem stops being abstract and becomes concrete.
Naming the elephant creates shared reality. Shared reality enables deliberate action.
Without it, teams are left improvising in midair.