Deciding Which Work Is Actually Worth Doing

Organizations invest time, money, and people into projects for different reasons. Some initiatives promise immediate financial returns, while others improve operations, strengthen customer relationships, support long-term business goals, or meet regulatory requirements. But while these are all legitimate reasons to consider an initiative, they do not automatically make it worth pursuing. The challenge is determining whether the expected benefits justify the investment and whether those resources could be put to better use elsewhere.

That distinction matters because simply approving a project does not guarantee that it will deliver sufficient value. A project can be funded, staffed, and completed successfully without delivering enough business value to justify the investment. Work that exceeds its original budget, on the other hand, may still be worth continuing if its expected benefits remain strong. Because costs, risks, and business priorities change, organizations need to evaluate their decisions both before committing resources and throughout delivery. The question is whether the work remains a better use of those resources than the available alternatives.

When the Original Commitment No Longer Makes Sense

At a digital agency where I worked, I managed a website and branding project for a professional services client that had been sold with too little time and budget for the expected work. As delivery progressed, repeated client approval cycles consumed more time than planned, and development requirements increasingly exceeded what the remaining resources could support. The project exposed a problem that should have been addressed before the agreement was signed, which was whether the expected work could realistically be delivered within the proposed investment.

Before approving a project, an organization needs a sound business case explaining why the work deserves funding and whether its expected benefits justify the costs and risks. A delivery plan addresses a different question, which is how the work will be completed. Both matter, but a realistic plan does not make an unjustified project worthwhile, and a promising business case does not make an unrealistic delivery commitment achievable.

But even when both the business case and delivery plan appear sound, circumstances can change once work begins. The question then becomes whether the benefits still expected are worth the money, time, and resources needed to finish. Previous spending helps explain how the project reached its current position, but spending more will not recover that money. When assumptions change, management should compare the available alternatives instead of automatically defending the original plan. Project Managers can provide evidence and recommend a direction, while clients, sponsors, or authorized leaders decide whether commitments should change.

How to Determine Which Projects Deserve Investment

Deciding whether a project is worth doing starts with understanding the business need. The organization should identify what problem the project will solve, what opportunity it will create, or what obligation it must satisfy, along with the expected benefits and how they will be measured. Financial returns matter, but operational stability, customer experience, regulatory requirements, and future capabilities can also justify investment when immediate returns are limited or difficult to measure.

But identifying a worthwhile objective is only part of the decision. Leadership must also consider the full cost, required skills and resources, delivery risks, timing, and whether the work supports broader priorities. These decisions involve opportunity cost: committing resources to one initiative makes them unavailable for another. Even worthwhile projects may need to wait if more urgent obligations take priority or the organization lacks the capacity to deliver them effectively. Rather than approving initiatives individually, leadership should compare their relative benefits, risks, urgency, and strategic importance.

“Stopping work because its remaining benefits no longer justify its costs and risks can also represent effective management.”

And that evaluation shouldn’t end once a project is approved. Expected benefits may decline, costs may rise, assumptions may prove incorrect, or another initiative may become a better use of resources. These changes should prompt reassessment, but not necessarily cancellation. Depending on the remaining investment and expected value, leadership may decide to continue, increase funding, reduce scope, delay, change direction, or stop the work. The decision should reflect future benefits and costs rather than money already spent.

These decisions also become more complicated when organizations must balance immediate obligations with longer-term investments. Regulatory deadlines, contractual commitments, and essential operations may need priority, but focusing exclusively on urgent work or quick returns can leave too little capacity for modernization and future improvements. The appropriate balance depends on the organization’s circumstances and should be reconsidered as priorities change.

That balancing act can become even harder when different parties have competing financial interests. While managing a major utility client’s digital platform at the same agency where I managed the professional services website project, I encountered recurring tension between the client’s preference for controlled monthly spending and the agency’s desire to increase billable hours. Production support, enhancements, and modernization competed for Engineering capacity, and additional billing did not necessarily provide equivalent value to the client.

And the tension extended beyond that particular account. At the agency, annual revenue goals were translated into monthly billing targets, and meeting those targets often took priority over project health, delivery quality, and client needs. Leadership pressured teams to generate enough billable hours to meet those targets, even when the available work did not justify that pace. This sometimes meant pulling tasks forward or starting development before designs were finalized, increasing the risk of rework, inefficiency, and quality problems. The focus on meeting immediate financial targets could therefore come at the expense of sustainable delivery, client relationships, and longer-term business value.

Of course, agencies have legitimate financial needs, but those interests do not always align with their clients’ priorities. Investment decisions should account for whose objectives are being served and whether the proposed work delivers sufficient value. Project Managers can challenge assumptions and recommend alternatives, while sponsors and authorized leaders decide how resources are committed.

Why Financial Pressure Can Lead to Different Decisions

Earlier, I described a website and branding project for a professional services client that had been sold with insufficient time and budget. That engagement demonstrated the need to reassess planned work when the original commitment no longer supports it. At one point, less than half the work was complete even though nearly the entire planned schedule had elapsed, and additional development effort was still expected. Rather than preserve every deliverable, I worked with the project team to identify ways to simplify development, reuse components, and reduce scope. One recommendation was to remove a planned design deliverable that was not essential to the finished website. These adjustments helped address the gap between the remaining work and available resources, although their exact savings and the project’s final financial outcome are unknown.

At another agency, however, I encountered a different approach to managing an investment that exceeded budget expectations. I managed a branding and ecommerce transformation for a luxury ecommerce client that included migrating its website to Shopify Plus. As ambitious design requirements increased delivery estimates, I presented opportunities to simplify certain features. However, leadership chose to preserve the intended experience to maintain the agency’s reputation for high-quality design and development, while also considering the client’s importance and the project’s potential portfolio value. The website launched successfully, the client was pleased, and the project remained profitable despite exceeding its original budget expectations.

The difference between these decisions illustrates why financial pressure does not always justify the same response. The professional services engagement required reconsidering planned work because the original commitment had not provided sufficient resources. The luxury ecommerce engagement involved leadership’s willingness to support additional effort for broader commercial and strategic reasons. Neither decision can be judged solely by whether the original budget was exceeded. The appropriate response depends on the remaining investment, the expected value, existing obligations, and whether those resources could be used more effectively elsewhere.

How to Challenge Work Without Controlling the Decision

Making those investment judgments also means being willing to question work that no longer appears worthwhile. When I find myself questioning whether a project still makes business sense, I start by revisiting the original business objective, the expected benefits, and the measures of success. From there, I examine what has changed, which assumptions still hold, and what evidence supports continuing. This helps me identify the specific weakness in the investment rather than treating the entire project as something to reject.

Once I understand where the concerns lie, I work with the relevant team to explore realistic alternatives. Together, we assess what completing the work would require and what the organization could gain or sacrifice by reducing scope, delaying delivery, changing direction, or stopping. If the remaining benefits no longer justify the investment, I would recommend redirecting resources toward more valuable work while accounting for existing obligations. My goal is to present the evidence and consequences clearly enough for the appropriate sponsor or leadership group to make an informed decision.

“A realistic plan does not make an unjustified project worthwhile, and a promising business case does not make an unrealistic delivery commitment achievable.”

Of course, presenting a recommendation is not the same as having the authority to approve it. On the professional services website engagement discussed earlier, I recommended removing a planned design deliverable, but the client needed to authorize that change. Once a decision is approved, the organization must address affected commitments, communicate changes to stakeholders, and determine how available resources will be used.

That distinction between influence and authority became particularly apparent during my time at another digital agency. Leadership directed us, as Project Managers, to persuade smaller retainer clients to increase their monthly commitments. We spent months working toward those increases, which often required clients to make the case for additional funding and secure approval from their own leadership. After several clients successfully increased their retainers, the agency secured a much larger account and decided not to renew many of those smaller contracts when they expired. I had no role in making or evaluating that decision, but I participated in communicating it to clients who were understandably upset, especially after the effort they had gone through to secure additional funding.

Experiences like this highlight how a change in portfolio priorities can affect existing relationships. Prioritizing a larger revenue opportunity may serve an agency’s commercial interests, but leadership also needs to consider commitments already made and the potential effects on clients. A Project Manager cannot always influence such decisions, much less control them. The responsibility for weighing those tradeoffs rests with the people authorized to make the investment decisions.

Measuring Delivery Against Business Value

Judging whether a project was worth the investment starts with defining success before work begins. Organizations need to establish the expected outcomes, how they will be measured, and what benefits would justify the cost. A website might launch successfully but fail to improve customer engagement, while a system upgrade might exceed its budget yet deliver meaningful improvements in efficiency or reliability. Meeting a delivery target provides useful information, but it cannot establish the full business value.

To understand that value, organizations need to look beyond delivery performance and examine what the work actually achieved. Delivery measures show how closely the work matched its approved scope, schedule, cost, and quality expectations. Business outcomes show whether something meaningful improved, such as customer experience or operational performance. Realized benefits indicate whether those improvements justified the investment through financial returns, reduced risk, regulatory compliance, or strategic value. Each provides different evidence.

The importance of making these distinctions becomes clearer when looking back at the luxury ecommerce engagement discussed earlier. The project exceeded its original budget expectations, but the website launched, the client was pleased, and the agency considered the work strategically valuable. Those facts establish certain delivery and client outcomes, but they do not establish the project’s exact profitability or the financial value of its longer-term portfolio benefits. Assessing the additional investment would require examining those considerations separately.

However, these evaluations shouldn’t happen only after a project is completed. Project Managers should monitor changing forecasts, risks, and assumptions about expected benefits so leadership can reassess continued investment. Sponsors and business owners must then evaluate whether the intended benefits materialize, sometimes months or years after delivery, while recognizing that other business conditions may influence the results. Stopping work because its remaining benefits no longer justify its costs and risks can also represent effective management. Completing the original deliverable is not the only way to make a sound investment decision.

Choosing What Deserves the Next Investment

Deciding which work is worth doing is ultimately about how an organization chooses to use its limited resources. Every investment limits what else it can accomplish. Financial pressures, internal incentives, and earlier leadership decisions can make it difficult to question approved work, even when its original justification has weakened. Strong leadership requires the willingness to reconsider those decisions without treating a change in direction as a failure. Project Managers can make the evidence, competing priorities, and consequences clear, but those with decision-making authority must be willing to act on that information. The goal is to direct the organization’s time, money, and people toward work that delivers justified value while meeting the obligations it cannot responsibly ignore.