A Delivery Leader’s Take on Measuring Real Impact
Beyond Metrics: The iron triangle manages delivery constraints, but lasting impact determines whether a project truly succeeded.
Measure Outcomes: Separate measurable KPIs from broader objectives, then validate difficult goals through user testing and stakeholder evidence.
Align Early: Project and team charters expose stakeholder priorities, personal motivations, and success conditions before delivery work begins.
Plan Longevity: Define post-launch benchmarks to assess whether products remain useful, understandable, and valuable months or years later.
Communicate Tradeoffs: Flexible scope, schedules, and budgets can support success when leaders disclose changes and explain their reasoning.
*This article is adapted from the DPM Podcast episode "How To Measure The True Impact Of Your Projects," hosted by Galen Low.
Every project leader knows the iron triangle: scope, schedule and budget. It's the default scorecard taught to project managers from day one. But hitting all three doesn't guarantee a project actually mattered, and missing one doesn't necessarily mean it failed.
Pam Butkowski, SVP of Horizontal Digital, has spent her career managing delivery for enterprise clients, including a 20-month website redesign for the LPGA that involved 74 people and nearly 25,000 hours of work. Her take: the iron triangle is a tool for managing risk and expectations, not a definition of success.
Continue Reading for Free
Create a free account to finish this article, plus get ongoing access to timely insights and practical resources.
Have an account? Log In
The Iron Triangle Isn't the Whole Story
Butkowski has seen projects hit every constraint on paper and still fail the people delivering them. Technical success on time and on budget means little if the team is burned out or the client relationship doesn't survive the project.
She also pushes back on the idea that risk can be fully engineered away. "Things are going to go wrong on every project, right? You can't mitigate every risk," she said. What separates a successful project from a failed one, in her view, isn't the absence of problems — it's the response to them. "What you do when something does go wrong also contributes to whether something was successful or not," she said.
Things are going to go wrong on every project, right? You can’t mitigate every risk.
For Butkowski, one of the clearest signals of success is whether the relationship with the client outlasts the original scope of work. "We don't want one-and-done work," she said. "If we launch a site, if that relationship with the client continues beyond that, it was successful."
KPIs Are Measurable. Objectives Aren't.
Delivery leaders often conflate business goals with KPIs, and Butkowski draws a hard line between the two. Objectives can be aspirational; KPIs cannot. "We can't just say, we're going to increase your ROI," she said. "No, it needs to be measurable. Your traffic will increase by this much. Your ad clicks will increase by this much. Very clear, again measurable, yes we hit it or no we didn't KPIs."
That distinction matters most when the underlying goal is difficult to quantify directly. On the LPGA project, the team's main objective was increasing fan engagement — a goal that resists a single clean metric. "That's really hard to measure," Butkowski said. "So, we came up with quite a few pieces of functionality that we believed would drive fan engagement, and then proved it through user testing. Proved it through stakeholder interviews." The team couldn't attach a hard KPI to fan engagement directly, but validated the hypothesis another way. "We proved our hypothesis, and then we put it into action, and sometimes that's good enough."
Start With Why the Role Exists
Rather than jumping to tactics, Butkowski recommends delivery leaders start by defining the purpose behind the function itself. She ran this exercise with her own team, pushing past the reflexive answer of risk mitigation. "I literally pushed back and said to my team, why do we exist? Why do project managers exist in this organization?" she said. The team distilled its purpose down to five things: "We exist to quarterback and lead the team, provide value to our clients and help them achieve their goals, be the source of truth, eliminate swirl and protect the agency."
From there, each of those five pillars ladders down into concrete practices. Under "leading the team," for example, one expectation is to "call the plays" — which in practice means running "a clear project plan," maintaining "staffing and resourcing plans clear what's on deck for each week," and "running really clear and succinct stand ups."
Charters Force the Right Conversations Early
Butkowski relies on two kinds of charters to surface what matters to a project's stakeholders before work begins. The first is a project charter with the client. "I find project charters invaluable," she said, "because just the act of making a charter with your client forces you to talk about what you care about." Clients reveal priorities they might not otherwise state outright — wanting to impress a boss, save money or protect their team's reputation. "I really care about saving the company money," is a typical answer, she said. "I really care about taking care of my team and making sure they look good."
I really care about taking care of my team and making sure they look good.
The second is a team charter, built with the people delivering the work. "Let's find out for each of the team members that you're working with who are actually delivering the product," Butkowski said. "What is this going to benefit them? What are they trying to get out of it?" That input then shapes how the plan is built, so the project delivers value for the team as well as the client.
Measuring Impact That Outlasts the Project
Some of the most meaningful impact doesn't show up until long after a project wraps, long after the delivery lead has moved on. Butkowski's team plans for that by defining what success should look like well beyond launch. "We want to make sure that we understand where the product can go long term," she said. "What does this thing look like in six months, a year, two years, five years from now?"
That long view becomes a benchmark she can return to later, even without hard traffic numbers in hand. "If I go back and look at a marketing site that was created with that goal in mind, if I look at it a year later and the content is still easy to understand, we did it," she said. "It is still paying off."
We want to make sure that we understand where the product can go long term. What does this thing look like in six months, a year, two years, five years from now?
The Triangle Can Flex — If You Say So Out Loud
Butkowski doesn't dismiss the iron triangle; she treats it as adjustable rather than fixed. "Nobody says that the sides of the triangle all have to be the same length," she said. "And nobody said that the sides of the triangle can't change length while you are delivering." A budget can expand. A timeline can shift. Scope can contract. What can't happen, in her view, is any of that occurring without the client's knowledge.
"I do think that there is a world where you can break the triangle and still call the project successful," she said, "as long as people know you're doing it." Leadership has to be looped in before a constraint breaks, not after. "The reasoning behind why you are breaking the triangle is more important than the fact that you're breaking it in the first place."
That principle shows up directly in how she runs kickoffs. "Whenever we kick off a project, I make the client prioritize the iron triangle," she said. "I make them say, this is the most important side to me, this is the second most important, and this is the least important." From there, she takes ownership of the third: "I own number three. You don't have control over number three. I do. I'll tell you what I'm doing with it, but in order to deliver one and two for you, I have to own the third side so that I can flex like this." The trade-off is transparent from day one: "I can give you two, I promise."
Growth Is Part of the Job, Not an Extra
For Butkowski, developing the team isn't separate from delivery; it's built into the role. "We have the word manager in our title for a reason," she said. "You are leaders by nature." She encourages delivery leads to actively create stretch opportunities within the plan itself: "If you've got a content author who's really passionate about getting into QA, let them. Build them in the plan. Have them shadow your QA team." The one caveat is coordination — those opportunities still need to connect back to each person's broader goals: making sure the work "fit[s] into their overall goals and where they want to go in their career at the organization."
The Bottom Line
For Butkowski, the iron triangle still has a role to play: it manages risk and sets expectations — but it was never designed to measure whether a project actually mattered. Real impact shows up in what a client keeps returning for, what a team learns to do better, and what a product is still doing a year after launch. Measuring that takes more than tracking scope, schedule and budget. It takes asking why the work exists in the first place.
Want more insights like these? Sign up for a free DPM account to hear from more experts like these.
