The most interesting business opportunities are not always new problems. Sometimes they are old problems everyone stopped questioning.
There is a strange point in the life of a bad system when people stop calling it bad.
- They adapt.
- They learn the workaround.
- They add another step to the process.
- They keep a second spreadsheet because the first system cannot do what they need.
- They copy information from one application into another.
- They wait three days for something that should take three minutes.
- They memorize which button does not work properly.
- They warn new employees about the process.
Eventually, the workaround becomes part of the job.
And once enough people learn how to live with a problem, the problem becomes almost invisible.
That is a mistake.
Because an accepted problem is still a problem.
And in business, accepted problems can be opportunities hiding in plain sight.
The Workaround Is Evidence
When a system does not meet people’s needs, people rarely stop everything and demand a redesign.
They compensate.
That compensation can take many forms:
- spreadsheets built around software limitations;
- handwritten notes beside supposedly digital systems;
- repeated copying and pasting between applications;
- unofficial procedures employees teach one another;
- extra staff hired primarily to manage administrative friction;
- repeated phone calls to complete simple transactions;
- customers maintaining their own records because they do not trust the system;
- manual verification of information that already exists digitally;
- or entire workflows created to compensate for one poorly designed step.
Those workarounds matter.
They are not merely signs that users are creative.
They can be evidence that the underlying system is failing to perform part of its job.
A workaround effectively says:
“The system stops here, so the human has to finish it.”
Sometimes there is a good reason for that.
Sometimes there is not.
The business opportunity begins with learning the difference.
Friction Has a Cost Even When Nobody Measures It
A problem does not need to appear as a line item on an accounting statement to cost money.
Suppose a task wastes only five minutes.
That sounds insignificant.
But then ask:
- How many times is it performed?
- How many employees perform it?
- How often does it cause an error?
- How often must the error be corrected?
- How much training is required to explain the workaround?
- How many customers abandon the process because of it?
- How much attention does it steal from more valuable work?
Small inefficiencies scale.
Ten unnecessary clicks may not matter once.
Ten unnecessary clicks performed thousands of times become something else entirely.
The same applies to:
- duplicated data entry;
- unnecessary approvals;
- poor communication between systems;
- confusing interfaces;
- repetitive verification;
- avoidable customer-service contacts;
- fragmented records;
- and processes dependent on someone remembering what happens next.
Organizations often become very good at absorbing these costs.
That does not make the costs disappear.
It merely makes them familiar.
Familiar Is Not the Same as Efficient
This is where organizations can fool themselves.
If employees can successfully operate a complicated process, management may conclude that the process works.
Technically, it does.
But that is an extremely low standard.
There is a difference between:
- possible and efficient;
- functional and well designed;
- trained around and intuitive;
- accepted and acceptable.
A process can produce the required outcome while still wasting enormous amounts of time and attention.
A piece of software can technically contain every necessary feature while making those features miserable to use.
A business can successfully serve its customers while forcing those customers through unnecessary friction.
The question should not simply be:
Does it work?
A better question is:
How much unnecessary effort is required to make it work?
That is a very different measurement.
The Best Opportunities May Look Boring
People often imagine innovation as something dramatic.
A revolutionary device.
A breakthrough technology.
A completely new market.
A product nobody has ever imagined.
Those opportunities exist.
But there is another category that receives far less attention:
making an annoying, expensive, repetitive, confusing, or unnecessarily complicated thing simply stop being annoying, expensive, repetitive, confusing, or unnecessarily complicated.
That may involve:
- eliminating duplicate data entry;
- reducing a ten-step process to three;
- automatically routing information to the correct person;
- combining fragmented tools into one workflow;
- replacing repetitive administrative work with automation;
- improving visibility into a process people currently have to chase;
- removing unnecessary intermediaries;
- making a complex system understandable;
- or giving users direct control over something that previously required support staff.
None of those ideas necessarily sound futuristic.
That is precisely why they are easy to overlook.
Businesses do not pay for futuristic.
They pay for useful.
Look for the Complaints Everyone Says With a Shrug
Some complaints arrive with anger.
Others arrive with resignation.
The second kind can be more interesting.
Listen for phrases such as:
- “Yeah, it does that.”
- “You just have to refresh it.”
- “We keep another spreadsheet for that.”
- “Call them after you submit it.”
- “It usually takes a few days.”
- “Only Sarah knows how to do that.”
- “Make sure you save a copy yourself.”
- “We tried changing it once.”
- “That is just company policy.”
- “That is how the industry works.”
The important part is not the wording.
It is the resignation.
These statements often describe a problem that has existed long enough for people to stop expecting it to be solved.
That should attract attention.
Not because every complaint deserves a startup.
But because habitual frustration is useful information.
Not Every Annoyance Is a Business
There is an important distinction here.
Finding a bad process is not the same thing as finding a viable business.
Some problems survive because solving them would cost more than tolerating them.
Others exist because of:
- regulatory requirements;
- security constraints;
- physical limitations;
- rare edge cases;
- contractual obligations;
- competing stakeholder needs;
- or tradeoffs that are invisible to the person experiencing the inconvenience.
Sometimes a seemingly ridiculous process exists because something much worse happened before it existed.
That is why the Ulfhednar Labs approach cannot stop at:
“This is stupid.”
The next questions matter more.
Is the Problem Real?
Does the frustration represent meaningful wasted time, money, risk, or opportunity?
Is It Repeated?
A recurring problem is generally more valuable than an occasional annoyance.
Is It Widespread?
Does one person dislike the system, or do thousands of people compensate for the same limitation?
Is the Workaround Expensive?
Time, staffing, training, mistakes, support calls, customer abandonment, and operational complexity all matter.
Can the Cause Actually Be Changed?
Solving a symptom while leaving the underlying constraint untouched creates another workaround, not a better system.
Would Anyone Pay to Remove It?
A frustrating problem can still have no viable market.
That final question matters.
A better system has to create enough value for someone to care that it exists.
Do Not Automate a Bad Process Too Quickly
Modern technology creates another temptation.
Find an inefficient process.
Add automation.
Problem solved.
Except sometimes automation simply allows a bad process to operate faster.
Before automating a workflow, ask whether every part of that workflow should exist.
If a process contains:
- unnecessary information collection;
- duplicate entry;
- three approvals;
- manual transfer;
- verification;
- another approval;
- and final processing;
the answer may not be building an AI agent capable of navigating all seven steps.
The better answer may be discovering that Steps 2, 4, and 6 should not exist.
This distinction is important.
Automation asks how to perform the process more efficiently.
Systems thinking asks whether the process itself makes sense.
Both are useful.
But they are not the same thing.
And systems thinking should usually come first.
The Human Labor Hidden Inside Software
Some software does not really automate work.
It relocates it.
A company replaces a staffed process with a digital platform, but the platform then requires the customer to:
- interpret confusing instructions;
- enter information the organization already possesses;
- resolve errors themselves;
- monitor the status manually;
- contact support when the automated workflow fails;
- and repeat information to the human who eventually handles the exception.
The organization may describe that process as automation.
The user may experience it as unpaid administrative labor.
That difference matters.
One useful question when evaluating any system is:
Who is doing the work now?
If technology eliminates ten minutes of employee work by creating twenty minutes of customer work, the process may have become cheaper for the company without becoming better overall.
That may still be a rational business decision.
But it should not be confused with good system design.
There Is Opportunity in the Gap
This is where accepted problems become interesting.
There is often a gap between what a system technically provides and what people actually need.
Inside that gap are:
- manual work;
- wasted time;
- repeated frustration;
- unnecessary expertise;
- avoidable mistakes;
- poor visibility;
- duplicated effort;
- and unmet expectations.
Businesses are frequently built inside those gaps.
Not because the founders invented a new human need.
Because they noticed an existing need being served badly.
The opportunity is not necessarily to create another product.
- Sometimes the opportunity is to remove the reason three existing products are necessary.
- Sometimes it is to eliminate a process.
- Sometimes it is to connect two systems.
- Sometimes it is to expose information.
- Sometimes it is to make an expensive capability accessible.
- Sometimes it is simply to design something around the way people actually behave instead of the way somebody assumed they would behave.
Ask What People Have Stopped Asking For
When people encounter a problem for the first time, they ask why it exists.
After enough repetition, they stop.
That transition is important.
Because people eventually stop requesting improvements they no longer believe are possible.
The absence of complaints does not always mean satisfaction.
Sometimes it means surrender.
That creates an unusual challenge for anyone looking for better systems:
You cannot rely exclusively on people telling you what they need.
You also have to observe what they have learned to tolerate.
Look for:
- repeated workarounds;
- unofficial processes;
- unnecessary manual effort;
- fragmented tools;
- tribal knowledge;
- repeated mistakes;
- customer confusion;
- tasks everyone hates but nobody owns;
- and procedures defended primarily by their age.
Those are signals.
Not proof.
But signals worth investigating.
Better Systems Often Begin With an Obvious Question
There is no shortage of people searching for the next enormous technological breakthrough.
There is nothing wrong with that.
But while everyone is looking toward the horizon, there are thousands of problems sitting directly in front of us.
Problems that are:
- understood;
- repeated;
- expensive;
- annoying;
- measurable;
- and largely ignored.
Some have remained for years.
Some for decades.
Not because nobody could possibly solve them.
Because everyone became accustomed to the workaround.
That is one of the ideas Ulfhednar Labs intends to keep returning to.
When something seems unnecessarily difficult, do not immediately accept the explanation that this is simply how things work.
Ask why.
Understand the system.
Find the constraint.
Measure the friction.
Determine whether the workaround has become more permanent than the problem deserves.
And then ask the question that can turn an everyday frustration into something much more interesting:
What would this look like if we stopped accepting it?