Don't Just Deliver the Project—Ask Why It Matters
Earlier in my career, I believed a good project manager should always have answers: milestone dates, mitigation plans, status updates and decision points.
One conversation changed that perspective.
My team and I were presenting a business case for a standardized observability platform to our CIO. We explained the technical benefits: centralized visibility, utilization data, better reporting and operational improvements.
Then our CIO asked a simple question:
“How does this project translate into dollar value for the business?”
At first, I thought he wanted another financial calculation. But as we discussed it, I realized we had explained what the platform would do—not clearly enough why the investment mattered.
The value was not simply better infrastructure visibility. Better visibility could help leaders make better capacity-planning decisions: Where were resources constrained? Were we using existing capacity effectively? Where was additional investment justified?
The technology had not changed. The way we articulated its value had.
That conversation changed the questions I ask when evaluating and leading projects. I want to understand not only what we will deliver, but how it connects to an organizational outcome.
1. What problem are we actually trying to solve?
Project requests often begin with a solution: “We need a new
Please log in or sign up below to read the rest of the article.
|
Love can sweep you off your feet and carry you along in a way you've never known before. But the ride always ends, and you end up feeling lonely and bitter. Wait. It's not love I'm describing. I'm thinking of a monorail. - Jack Handey |




