Intangible Benefits and Externalities in Project Evaluation

1. Beyond the Numbers: What Are Intangible Benefits?

In our cloud migration case, the benefits were tangible—dollars saved on hardware and electricity. But what about benefits like improved team morale, enhanced brand reputation, or a more streamlined workflow? These are intangible benefits.

An excellent resource from the software engineering field defines these as "knowledge assets."

As the reading suggests, intangible benefits are real, even if they don't have a price tag. In your experience as a software developer and manager, you've likely encountered many:

• Internal Improvements: Refactoring a legacy codebase might not immediately increase revenue, but it can boost developer productivity, reduce bugs, and lower long-term maintenance stress.
• Customer-Facing Improvements: A redesign of a user interface could lead to higher customer satisfaction and loyalty, which is valuable but difficult to quantify in the short term.
• Strategic Alignment: Developing a new platform using a modern tech stack might position the company to enter new markets or attract top engineering talent.

This diagram helps categorize these benefits and highlights a key challenge: the further into the future or the more strategic the benefit, the harder it is to measure.

2. Looking Outward: Understanding Externalities

Our analysis so far has focused on the project's impact on the firm (the "private" perspective). But projects can also affect parties not directly involved in the transaction. These side effects are called externalities.

To grasp this distinction, let's first contrast a purely financial analysis with a broader economic one.

The video introduces the idea that a project has wider impacts. Externalities are those impacts—costs or benefits—that affect "bystanders."

• Negative Externality: A cost imposed on others. The classic example is a factory that pollutes a river. The public bears the cost of a contaminated water supply, even though they didn't buy or sell the factory's product.
• Positive Externality: A benefit conferred on others. A company that invests in creating a major open-source software library creates a positive externality. Other developers and companies can use that library for free, reaping benefits from the original company's investment.

This next video provides a sharp definition and a memorable example of a negative externality.

For technology projects, externalities can be subtle but significant:

• Example (Negative): A new ride-sharing app might increase traffic congestion and put downward pressure on wages for traditional taxi drivers. These are societal costs not borne by the company or its users.
• Example (Positive): Building a new office might revitalize a neighborhood, increasing business for local shops and raising property values. The company doesn't directly capture this value.

3. How to Describe What You Can't Measure

If these factors are so important but can't be put into a B/C ratio, what do we do? We identify, describe, and qualitatively assess them. The goal is to provide a structured narrative alongside the financial numbers.

As noted in the MIT OpenCourseWare materials on Cost-Benefit Analysis (resource ID LINK), intangibles are a core challenge in project evaluation. They are defined as benefits that are "either unquantifiable (such as scenic effect of a highway) or they can be quantified but is difficult to value in a market sense (life saving impact)."

Instead of giving up, we can use scoring models to add rigor to our qualitative descriptions. This turns a vague statement like "it will improve our brand" into a more structured assessment.

Look at this example of a scoring matrix for evaluating the intangible impacts of R&D projects.

This framework provides a disciplined way to think through and present intangible benefits. When you propose a project, you can use a similar model to show stakeholders how it aligns with strategic goals, even if you can't assign it a direct dollar value. You could rate a project on a 1-5 scale across dimensions like:

• Strategic Fit: How well does this project align with our 3-year business plan?
• Knowledge Building: Will this project develop critical new skills in our team?
• Competitive Advantage: Does this give us a unique capability that competitors can't easily replicate?
• Customer Satisfaction: How much will this improve the user experience?

This approach doesn't give you a magic number, but it provides a defensible and transparent basis for comparison, ensuring these vital factors are not ignored.

Conclusion

Today, we've moved beyond the strict confines of financial calculation to embrace a fuller picture of project value. You learned how to identify crucial non-monetary factors that are often decisive in technology projects.

• Key Takeaways:
  • Intangible benefits are non-physical assets that create value for the firm, such as improved processes, employee knowledge, and brand reputation.
  • Externalities are the side effects of a project that impact third parties, creating either costs (negative) or benefits (positive) for society.
  • A comprehensive project evaluation must account for both tangible and intangible factors.
  • While intangibles are difficult to price, they can be systematically identified, described, and assessed using qualitative frameworks like scoring models.

Preview of the Next Lesson

We've just introduced the idea of using scoring models to assess intangibles. In our next lesson, we will put this into practice. We will focus on how to apply non-monetary scoring models to compare projects with significant intangible factors, giving you a hands-on tool for making complex trade-off decisions.