How do we read failure not as a moral judgment, but as a signal revealing changes in the market, finance, and technology?

In economic news, we often hear: “The project failed,” “The plan stumbled,” “The sector did not succeed.” Automatically, we look for the culprit: the manager? The design? The decision? But the economy - like any large system - does not operate this simply. Often, “failure” is a gap between intention and outcome, or between values that seemed logical at the time of decision, which later changed. Therefore, failure may be less of a “scandal” and more of a signal: a sign telling us that reality has moved faster than our assumptions.

What is meant here is not necessarily moral or individual failure, but economic or operational stumbling when the project can no longer deliver what was promised or continue with the expected efficiency.

To understand the idea without heavy terminology, imagine any project as a promise built on three things: financing (how we pay), operation (how it continues), and context (how it lives within a city, market, and technology). If one of these is disrupted, “failure” may appear even if the idea is good.

Failure is not in the “thing”… it may be in the system that supports it

A clear example of this is housing. Many housing projects start with a beautiful social promise: suitable units, nearby services, and an environment that preserves people's dignity. They often succeed at the moment of opening because the construction is complete. But true success begins after the opening: maintenance, cleanliness, security, facility management, and response to complaints. Here, a simple yet crucial economic point emerges:

  • Establishment cost: what we pay once to build the project.
  • Operating cost: what we pay each year to keep the project suitable for living and service.

Much of the stumbling occurs when we accurately calculate the establishment cost but neglect the operating cost. What was once a “housing project” turns into a place that exhausts people instead of serving them—not necessarily because the design is flawed, but because the operation was not financially and managerially supported over time.

To illustrate: if a housing complex is built at a high cost, but only a very small percentage is allocated for maintenance that does not keep pace with rising material and labor costs, then malfunctions accumulate. An elevator breaks down here, repairs are delayed there, then the quality of facilities declines, leading to a negative reputation. At that point, it is said: “The project failed.” But the real indicator is: failure of operational sustainability, meaning the supporting system has deteriorated, not that the idea was worthless from the start.

This type of “failure” teaches us something important economically: when you see a housing project stumbling, ask: is the problem in the building… or in the maintenance budget and service management? Because the outcome for people is the same, but the remedy is entirely different.

Technical failure: when the asset ages faster than its expected lifespan

The second type appears in today's environments built to serve “flows”: goods in logistics, and data in data centers. These facilities are not measured by the beauty of their facade, but by efficiency, speed, and reliability. However, they operate within a rapidly changing world: technology changes, efficiency standards rise, energy costs fluctuate, and security and reliability requirements tighten.

Here, “failure” becomes a different indicator: not necessarily administrative corruption, but accelerated obsolescence. This means that the facility may become less competitive before it completes its expected economic cycle. A data center built with a cooling or power distribution standard that was excellent a few years ago may find itself today less efficient than newer centers. In a market sensitive to operating costs, a small efficiency difference can make a significant decision difference: reducing operations, shifting loads, or investing anew in another location.

Even logistics face the same idea. A warehouse in a location that was ideal before the city expanded may become trapped by congestion or limited access. A distribution plan built on certain flows may change when trade patterns shift or supply chains are re-engineered. Stumbling appears as if it is a “project failure,” while at its core it is a signal of a shift in economic geography: where are goods moving? Where are orders gathering? Where has the cost become lower?

Sometimes failure creates a “margin” that seems small: a 10% efficiency difference in energy, or a slight drop in the maintenance budget, or a one-point increase in interest rates that adds weight to financing. These margins are what change the fate of a project over the years. So do not just look for a huge number; watch the details that raise operating costs or accelerate obsolescence.

How to read failure as a reader… without getting lost in blame?

Instead of asking “who is to blame?”, try four clear questions:

  1. What was the project supposed to achieve?
  2. What actually happened after operation?
  3. What changed: prices? Energy? Technology? People's behavior?
  4. Is the problem in the asset itself, or in the system that funds, operates, and protects it?

Then, “failure” transforms from a hurtful word into a tool for understanding. It reveals what we rely on without seeing it: maintenance budgets, energy costs, technological changes, and policies that keep the place alive or let it age.

At Yamama Insights, the idea is not to justify failure or celebrate it, but to use it as a lens: because what fails today may be the most explanatory of how the economy is changing—who bears the cost of this change, and what needs to be redesigned: the idea… or the system that supports it.