The Art of Elephant Management

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.

The first elephant: methodology bias

When my company got bought out, one of the phrases I heard repeated was "you cannot teach an old dog new tricks." I suspect I was one of those dogs.

The assumption ran ahead of the conversation. I held formal project management credentials, which some people read as: rigid, process-heavy, top-down. When I moved toward agile practices, someone told me I was being dictatorial. That stopped me cold.

I was not dictatorial. I had never been dictatorial. The thing is, before anyone handed those practices a label, I was already running projects that way. People-first. Collaborative. Iterative where it made sense. The methodology framework showed up years later and put a name on what I had already been doing.

The assumption that my credentials defined my style was the elephant. Nobody named it. So it sat in every conversation we had about how to run the work, invisible and load-bearing.

Labels are not strategies. When teams get stuck debating which framework they are in, they stop focusing on what needs to move next.

Name the methodology assumption early. It is not about attacking anyone’s preference. It is about clearing the air so the work can actually start.

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 is not 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:

1. Time
2. Cost
3. Scope
4. Resources
5. Risk
6. 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.

The biggest elephant I ever named

It was the timeline.

Not a missed milestone. Not a slipped sprint. The timeline itself. It was unrealistic, and everyone in the room already knew it. Nobody said it.

I called it out. The conversation was uncomfortable. Some people were relieved. A few were frustrated. But once we named it, we could actually decide what to do about it.

I believe in pushing people. In my experience, people are almost always more capable than they think they are. The right pressure, at the right time, draws out work that would not have happened otherwise.

But that only works when the timeline is honest.

An unrealistic timeline does not motivate people. It defeats them. The project fails because it misses the date, and the people fail because they were set up to miss it. They cannot succeed, no matter how hard they work. The elephant was there from the beginning, and no one said anything.

Naming an unrealistic timeline feels like bad news. It is not. It is the only way to give a team a real chance.