Asher's Blog

I love constraints. I do not always enjoy what they feel like while I am inside them, but I love what they can produce. Limited money, limited talent, difficult infrastructure and an unforgiving deadline force you to answer questions that abundance allows you to postpone. What is genuinely important? What can be removed? What must work? What can we do with what is already available?

I have gone through seasons in business when the resources I wanted were simply not available, and those seasons forced some of my clearest and most creative decisions. Constraint removes the comfort of solving every problem by spending more money or hiring more people. It makes intelligence operational.

This is why one of the familiar interview questions asks how well a person works under pressure. The question is sometimes used carelessly, particularly by companies that have confused permanent chaos with ambition, but there is a meaningful quality underneath it. When the obvious resources disappear and the deadline remains, can you still think clearly enough to find another route?

Constraint is beautiful when it sharpens judgment. It becomes destructive when it is merely poor planning repeated indefinitely. The difference matters.

Abundance can hide weak thinking

When a company has significant capital, it can respond to uncertainty by increasing expenditure. It can hire another team, buy more software, engage consultants, launch several campaigns at once and enter multiple markets before understanding which action creates value. Some of those investments may eventually work, but abundance can delay the moment when leaders have to identify the essential mechanism of the business.

Constraint brings that moment forward. If you can fund only one experiment, you must decide what you need to learn most urgently. If you can hire only one person, you must understand which capability is truly missing. If your customers have limited purchasing power, you must design a product whose value is obvious and whose delivery cost does not destroy the business.

This is one reason companies built in difficult African markets can develop unusual strengths. Founders often operate with expensive capital, unreliable infrastructure, fragmented regulation and customers who cannot afford to pay for unnecessary complexity. Those conditions are real disadvantages, but they can also produce businesses that are careful with cash, resilient in operation and capable of delivering value under conditions that would overwhelm a company designed only for abundance.

The danger is romanticising hardship. Poor infrastructure wastes time and capital that could have been used productively, and founders should not pretend that every obstacle is a gift. The beauty is not in the absence of resources itself. It is in the disciplined creativity that can emerge when people refuse to let the constraint become the final answer.

Constraints force priorities to become visible

Many organisations claim to have priorities until two important things compete for the same resource. At that point, the true priority becomes visible.

If everything is described as urgent, the company has not prioritised; it has simply distributed anxiety. A real priority implies that another worthwhile activity will wait. Limited resources make this unavoidable and therefore useful. The team must choose which customer problem, feature, market or operational weakness deserves attention now.

A founder can use constraint deliberately by asking questions such as: if we could improve only one part of this product in the next month, which change would create the greatest improvement in customer outcomes? If we could pursue only one distribution channel, which one would teach us most about repeatable demand? If we could track only three numbers, which ones would tell us whether the business is becoming healthier?

These questions are not exercises in pessimism. They reveal the structure of the problem. Even when more resources later become available, the understanding produced by scarcity remains valuable because the company knows where additional capital can be most productive.

Less money can produce better design

Money expands possibility, but it does not automatically improve judgment. A team with limited funds must often solve the customer’s core problem before it can add the surrounding sophistication. That pressure can produce a simpler and more useful product.

Consider a company building for small businesses that cannot afford long implementation projects, specialist administrators or extensive training. The product must explain itself, accommodate imperfect data and create value quickly. The constraint imposed by the customer’s time and budget becomes a design standard. Complexity that might survive in an enterprise product with consultants and dedicated support becomes impossible here.

The same principle applies internally. When a company cannot afford to automate every process immediately, it must decide which part deserves engineering effort and which part can remain manual while the team learns. When it cannot buy every technology tool, it must understand the workflow well enough to choose the few tools that matter.

Some of the most elegant solutions emerge because the team was not permitted to hide confusion behind more features, more employees or more expenditure.

Limited talent changes how leaders build people

In many markets, the exact experience a startup needs may be difficult or expensive to find. A founder can complain indefinitely that the talent market is inadequate, or can treat the constraint as a design problem.

This may mean hiring for intelligence, character and learning speed rather than insisting that every candidate has already done the job in an identical company. It may mean borrowing experienced talent through advisers or consultants while developing younger full-time employees. It may mean documenting knowledge so that the organisation does not repeatedly depend on a few individuals.

Constraint can also force leaders to give people meaningful responsibility earlier. An employee who might have remained a narrow specialist inside a large organisation may learn to understand customers, operations and commercial consequences because a smaller team cannot afford rigid boundaries. That exposure can develop unusually capable leaders.

However, constraint cannot justify placing unprepared people into critical roles without support. The founder still owes customers and employees a competent system. The creative response is to design supervision, training and controls that allow potential to grow without transferring unreasonable risk to the customer.

Infrastructure constraints should shape the product

A product built in a conference room can assume perfect connectivity, modern devices, consistent power and customers who understand every digital convention. Reality may be less cooperative.

If customers experience unreliable internet, the product may need to preserve work, reduce unnecessary data usage or make interruptions recoverable. If payment infrastructure is inconsistent, the company may need strong reconciliation, multiple routes and clear communication when a transaction is delayed. If businesses still depend on spreadsheets, the product may need to respect familiar workflows before it can persuade users to adopt a more structured process.

The wrong response is to build as though the constraint does not exist and blame customers when adoption is poor. The better response is to allow the environment to influence the architecture. A well-designed product does not merely function in ideal conditions; it understands the conditions in which the customer actually works.

Sometimes solving for a constrained market produces advantages elsewhere. Software that is simple, resilient and economical can travel into other markets where customers are tired of expensive, overcomplicated systems. The local limitation can become the source of global competitiveness.

Pressure reveals, but it should not become permanent

The interview question “How well do you work under pressure?” is useful only if we define pressure carefully. A difficult deadline, an unexpected incident or a period of scarce resources can reveal composure, initiative and creativity. Constant confusion created by weak leadership reveals something else: an organisation that has made emergency its operating model.

Good pressure concentrates attention around a meaningful constraint. Bad pressure comes from unclear priorities, avoidable last-minute changes, understaffing and leaders who expect heroics instead of building systems. The first can strengthen a team; the second gradually destroys judgment and trust.

People need enough space to think. Creativity under constraint does not mean creativity under exhaustion. A team may produce an extraordinary rescue during a crisis, but if it must perform the same rescue every week, the company has failed to convert learning into infrastructure.

The proper use of pressure is to discover capability and expose weakness, then improve the system. The founder should ask what the constrained period taught the company, which workaround deserves to become a process and which source of pressure should never be allowed to recur.

Create useful constraints before reality creates dangerous ones

Leaders do not have to wait until the company is running out of money before using constraint as a tool. They can create boundaries that improve thinking while the business remains healthy.

A team can limit the time allowed for an experiment, cap the amount of money invested before evidence appears, reduce the number of features in a release or require a proposed project to identify the one customer outcome it will improve. These constraints prevent ambition from becoming unstructured expansion.

A useful constraint is specific and connected to the objective. “Spend less” is vague. “Test whether this channel can produce ten qualified opportunities before spending another amount” creates a decision rule. “Build faster” is vague. “Release the smallest version that lets five customers complete the full workflow” focuses the team on learning.

Artificial constraints can also protect creativity from organisational habits. Asking a team how it would solve a problem without hiring anyone may reveal an automation or partnership opportunity. Asking how the product would work if the customer had only a basic phone may expose unnecessary complexity. The company may later choose to spend more or build for better devices, but the exercise forces assumptions into view.

Constraint needs an expiry condition

One of the lessons founders must learn is that what works during validation can become a bottleneck during growth. A small team may manually serve early customers in order to understand the problem, but the company should know when that process must be standardised or automated. Extreme frugality may protect the business at the beginning, but refusing to invest after repeatable demand has appeared can limit the opportunity.

Every important constraint should therefore have an expiry condition. What evidence would justify more investment? At what customer volume does the manual process become unsafe? Which performance level indicates that the company should hire specialist talent? When does a workaround begin to damage service quality?

Constraints should force learning, not imprison the company inside its earliest methods. The discipline is to remain economical without becoming timid, and to recognise when the next stage requires resources that the previous stage wisely avoided.

Creativity is the refusal to accept the obvious route

The deepest value of constraint is that it interrupts automatic thinking. When the usual route is unavailable, you have to examine what the outcome actually requires. You begin to see assets you overlooked, partnerships you did not consider, processes that can be removed and people whose capabilities had not been fully used.

Constraint asks whether the expensive way is necessary, whether the conventional way is correct and whether the problem can be approached from another direction. It makes the mind search.

I love constraints because I have seen them unleash that search in me. They have forced me to think, to build models, to find another source of cash flow, to reconsider how work is organised and to discover that a problem I believed required more resources sometimes required a clearer idea.

Capital, talent and infrastructure can accelerate important work, and we should build societies and companies in which people have greater access to them. Yet abundance produces its best results when it meets the clarity developed under constraint.

The goal is not to remain deprived. The goal is to allow limitation to teach you what excess might have hidden. Once you know what truly creates value, additional resources can multiply intelligence rather than subsidise confusion.