When Conflicting Choices Are Both Valid

We often face choices where both options seem reasonable but lead in different directions.
– Trust the experts or question their decisions?
– Act quickly or take time to plan for the future?
– Let technical leads decide or intervene?
These decisions are not one-time events; they occur frequently and are rarely straightforward.
These conflicting choices are trade-offs that program managers deal with daily, often with limited information and imperfect timing.

A Story That Still Stays With Me

In a large systems renewal program, I was told that the functional and technical leads would make most decisions because they knew the system better. I trusted their experience. However, as the program progressed, I heard phrases like: “It’s complex to change that part,” and, “Let’s leave it alone.” I mostly agreed with them, though I felt uneasy, sensing that some untouched areas could cause problems later, but I lacked the data to argue. When we began the next renewal, the product vendor reviewed the system and noted that those areas should have been addressed earlier, which had now made changes more costly and complicated. They weren’t blaming anyone, but I felt the impact. Looking back, I realized I chose to trust the experts without fully considering the broader consequences of my decisions.

What I Took From That Experience

It wasn’t that I made the wrong choice; I just didn’t fully see the balance between trusting the leads and considering what the program might achieve or overlook. Both aspects were important. The result could have been the same even with more discussion, but I would have had a better understanding of the situation. These decisions often determine if a program meets its goals or falls short.

What I Try to Do Now

In similar situations since, I’ve changed how I approach decisions.
Instead of just deferring, I pause and ask:
• “How will this affect us later—technically, financially, or operationally?”
• “Are we shying away from the effort, or it really shouldn’t be changed right now?”
• “Should we consult the product vendor for their input—especially if this area might be revisited later?”

It’s not about questioning someone’s expertise, but about clarifying the consequences of our decisions—so we can be intentional instead of just cautious. Sometimes the decision remains the same, but the conversation is more thorough—and the risks are better understood.

Next Post:
In the next post, I’ll discuss a common paradox in transformation programs:
Business staff play a key role in driving change, yet many are reluctant to leave their daily tasks for fear of career impacts.

This creates a real dilemma:
Should you focus on transformation or protect your job?
I’ll explain how this issue arises, its implications for programs, and potential alternatives.

The Program Paradox