There is a quote I came across some years ago that stayed with me: “We don’t design things for what they are, but for how they ought to be.” It struck me because it captures a truth that many people miss. Too often, people build around present limitations instead of building toward the best possible outcome. They become trapped by bottlenecks, excuses, shortages, and current conditions. They design around weakness instead of designing around truth.

But real progress does not come from accepting broken conditions as permanent. It comes from asking what the right version should look like, then working backward from there.

That is the difference between reacting to circumstances and creating solutions.

Designing Beyond the Current Situation

Many people approach problems by focusing only on what exists today. If money is short, they lower standards. If systems are weak, they tolerate disorder. If resources are limited, they accept poor execution. If the environment is difficult, they normalize mediocrity.

That mindset is common, but it is dangerous.

When you design only for current conditions, you preserve the very problems holding you back. You build systems that inherit dysfunction. You create products that solve symptoms instead of causes. You normalize struggle and then call it reality.

But designing for how it ought to be means something different. It means stepping back from present chaos and asking:

What is the ideal outcome?

What is the real root problem?

What would excellence look like here?

What standards should exist, even if they do not exist now?

What solution would remain strong if circumstances improved tomorrow?

That shift changes everything. Instead of being trapped by what is, you begin constructing what should be.

 

First Principles Thinking

This way of thinking aligns closely with first principles reasoning.

First principles thinking means stripping away assumptions, trends, copied ideas, and inherited limitations. It means reducing a problem to its most basic truths, then rebuilding the answer from the ground up.

Instead of asking, “How is everyone else doing it?” you ask:

What should this actually cost?

How well should this truly work?

What materials are genuinely required?

How can it be made simpler?

How can it be replicated at scale?

What is the most efficient and highest-quality version possible?

This approach is powerful because many accepted systems are inefficient simply because nobody challenged them. Many industries are expensive because waste became normal. Many products are poor because bad standards became tradition.

First principles thinking refuses inherited mediocrity.

It asks not what exists, but what should exist.

 

How It Ought to Be in Projects

Projects fail for predictable reasons. Poor planning. Weak organization. Lack of discipline. No systems. Bad communication. Insufficient funding. Emotional decisions. Inconsistent execution.

Yet many teams act surprised when failure arrives.

A serious project should be built around the core ingredients of success:

Clear planning

Proper organization

Reliable tools

Strong execution

Relationship management

Honest measurement

Adequate funding

Continuous refinement

Then one must repeat what works and eliminate what does not.

Simple, but not easy.

The phrase how it ought to be matters here because it demands completeness. You do not skip critical parts because they are inconvenient. You do not avoid budgeting because money is uncomfortable. You do not ignore systems because structure feels rigid. You do not avoid accountability because feelings may be hurt.

If a project requires discipline, then discipline is not optional.

Many ventures die painful deaths not because success was impossible, but because people tried to bypass fundamentals. They wanted outcomes without structure. Growth without sacrifice. Results without standards.

That is fantasy.

Reality rewards those who respect how things ought to be.

 

How It Ought to Be in Product Building

Products deserve the same seriousness.

A product should first solve a real pain. If it does not remove friction, save time, create joy, reduce cost, increase power, or improve life in some meaningful way, then it should question its own existence.

Too many products are built because people want to launch something, not because something needs to exist.

That is backwards.

The correct order is:

1. Solve a painful user problem

What frustration exists? What inconvenience keeps repeating? What need is underserved?

2. Deliver the best possible solution

Not just a solution. The best realistic solution you can produce with available skill and resources.

3. Make it beautiful and intuitive

Good products should work well. Great products should also feel right. They should be pleasant, elegant, and clear.

4. Execute with seriousness

Ship something worthy. Refine relentlessly. Improve based on reality.

No excuses.

That is how it ought to be.

The Problem of Excuses

This principle is often neglected in places where constraints are real. In many African countries, including Ghana, funding limitations, weak infrastructure, unstable systems, and bureaucracy are genuine problems.

Those challenges are real.

But there is another problem that is also real: excuses.

Sometimes people use external hardship to justify internal carelessness. They substitute emotion for rigor. They lower standards before effort has even begun. They convince themselves that poor execution is inevitable.

It is not.

Constraints may explain difficulty, but they do not excuse disorder. Scarcity may slow progress, but it does not require sloppiness. Limited resources do not force weak thinking.

Often, the difference between stagnation and growth is not money first. It is honesty first.

Are we doing this the right way?

Are we using the right materials?

Are we solving the real problem?

Are we disciplined enough?

Are we telling ourselves comforting lies?

Those questions matter more than pride.

 

Truth Before Comfort

To move forward, individuals and nations alike must learn to confront truths early.

If funding is required, say so.

If skills are missing, admit it.

If the product is weak, improve it.

If leadership is poor, replace it.

If standards are low, raise them.

Comfort delays progress. Truth accelerates it.

The people and organizations that win long term are rarely the most emotional. They are usually the most honest, disciplined, and committed to fundamentals.

We Build for Strength, Not Weakness

 

The central lesson is simple:

We should not create systems based on our weakness.

We should not lower standards because of present discomfort.

We should not normalize dysfunction because it is common.

We should build for strength.

We create for what is right, not what is easy.

We organize for what works, not what excuses demand.

We produce for what users deserve, not what laziness permits.

We plan for excellence, not for survival alone.

That is how serious people operate.

 

Final Thought

The future belongs to those who can imagine better standards and then submit themselves to the discipline required to reach them.

Many people wait for perfect conditions before doing great work. They wait for money, support, certainty, and comfort.

But progress begins the moment you reject that mindset.

Build not for what things are.

Build for how they ought to be.