Are We Solving the Right Problems? A Philosophical Lens on Engineering

By SANATH THILAKARATHNA

In the world of engineering, we pride ourselves on solving problems.

We apply math, science and logic to create systems, products and structures that make life better, faster, safer and more efficient.

But have we ever stopped to ask: What is a problem? What does it really mean to solve one? And are we always solving the right ones?

Let’s ask philosophical questions that lie at the heart of engineering itself.

What Is a Problem in Engineering?

In engineering, a problem is often defined as a gap between the current state and a desired state, framed by constraints like time, cost, materials, ethics and functionality. However, this definition is far from neutral. It is a construct, shaped by the mental models, experiences and perspectives of everyone involved in the engineering process. How a problem is perceived often determines what kind of solution will be sought.

Several forces influence this framing:

• The assumptions of the design team, such as which trade-offs are acceptable
• The expectations of clients or users, which may reflect biases or incomplete understanding
• The technical norms, standards and codes that govern the field
• The economic and political climate, including funding priorities and stakeholder agendas
• The cultural and historical context, which affects how certain problems are even recognized

Example: Building a dam may be seen by engineers and policymakers as a rational solution to a water scarcity issue. It checks boxes for storage capacity, irrigation and power generation. Yet for downstream communities, it can mean displacement, loss of livelihoods and ecological degradation. In that sense, solving a hydrological problem introduces a humanitarian one.

Another example: The introduction of facial recognition to improve public security may simultaneously generate new problems of surveillance, privacy violation and social inequity.

Thus, the first philosophical insight is this: Problems are not inherently objective. They are filtered through cultural lenses, social structures and value systems.

Are We Solving Problems or Shaping Them?

Engineers don’t just solve problems; they also define them.

Every decision we make in framing a problem influences the outcome. This includes:

• What data do we choose to measure, and what do we ignore?
• What outcomes do we value most: efficiency, safety, equity or sustainability?
• Which constraints are assumed immutable, and which are open to creative negotiation?

When we define a problem, we are also embedding a worldview into the design process. For example, framing urban congestion as a traffic-flow problem may lead to more roads and highways. Framing it as a mobility and equity issue might instead lead to public transit investment and pedestrian infrastructure.

The act of design is inherently interpretive. It involves translating human needs, economic pressures, technical limitations and ethical questions into a coherent system. The boundary between “problem” and “solution” is often porous. In many real-world cases, the solution reshapes or even redefines the original problem:

• A product that solves one pain point may expose another previously hidden.
• A technical fix might change user behavior in unexpected ways.
• A design constraint reinterpreted may reveal new opportunities entirely.

In this way, engineering is not just a reactive discipline. It is constructive and participatory, shaping not only the material world but also the problems we collectively decide to address.

The Problem of Over-Specification

Modern engineering often deals with wicked problems – complex, interconnected challenges like climate change, energy and healthcare. These problems don’t have clear definitions or final solutions.

Trying to reduce them to a narrow, well-bounded technical task can strip away critical nuances.

Example: Designing a fuel efficient car is a technical achievement. But does it solve the transportation problem if the roads are still congested, cities are unsafe for pedestrians and carbon emissions remain high?

Sometimes engineering solves the wrong problem very well.

The Philosophy of Optimization

Engineers love optimization. We build systems to be faster, lighter, cheaper, stronger. But this begs the question:

Optimize for what? And for whom?

Optimization assumes we have clear objectives. But in real life, stakeholders have competing goals, moral concerns and differing values.

Example: A factory design that optimizes for output may compromise worker well-being. A sensor network that maximizes data coverage might reduce privacy. We can’t ignore that every engineering decision has ethical implications.

Technology as a Problem Generator

Here’s the paradox: Engineering not only solves problems, but it also creates new ones. In our pursuit of technical progress, we often introduce unintended social, environmental and behavioral consequences that must be reckoned with – sometimes decades later. This is not a flaw of engineering, but a reflection of its deep entanglement with society and evolving values.

• Cars solved transportation – but created accidents, pollution and urban sprawl.
• Plastic solved packaging – but now chokes ecosystems.
• The internet solved global connectivity – and now fuels misinformation.

Does this mean we should stop innovating? Absolutely not. But we must acknowledge that solving a problem is never the end of the story. Every solution has consequences, intended and unintended. The rapid advancement of technology can outpace our societal and regulatory ability to manage its side effects. This is why engineers must increasingly collaborate with ethicists, ecologists, policymakers and communities to anticipate ripple effects, create adaptive frameworks and design technologies that serve both current and future generations responsibly.

Reframing Engineering with Philosophy

Bringing philosophy into engineering doesn’t make us slower, it makes us more thoughtful, deliberate and ethically grounded.

It reminds us to:

• Ask why we’re solving this problem in the first place, and whether the problem definition is ethically and socially valid.
• Consider who benefits and who bears the cost, including marginalized or future communities who may not be part of the design process.
• Reflect on long-term effects, not just short-term metrics like profit, efficiency or speed-to-market.
• Accept ambiguity when certainty is not possible and remain open to revising assumptions and models as we learn more.
• Recognize that some problems require collaborative wisdom, drawing insights from policy, ecology, ethics and sociology
• Resist the temptation to see technology as neutral or universally beneficial.

This is the essence of critical design thinking, not just building things right, but building the right things in the right way, with awareness of context, consequence and complexity.

From Solvers to Stewards

In the 21st century, engineers are no longer just technical experts. We are shapers of systems, societies and futures – with influence extending beyond the physical artifacts we design into the very fabric of human behavior, societal structure and global sustainability.

To live up to that role, we must balance our problem-solving mindset with ethical reflection, systemic awareness, cultural sensitivity and humility. This means acknowledging uncertainty, listening to diverse voices, engaging in interdisciplinary dialogue and being open to outcomes we may not fully control.

Because sometimes, the greatest contribution of an engineer is not just finding a better answer but courageously asking a better question – one that opens up space for more inclusive, responsible and transformative solutions.

Sanath Thilakarathna is a lecturer in mechatronics engineering with CINEC.