Running a business is, in many ways, a continuous exercise in problem solving.
A customer complains.
A supplier is late.
Sales suddenly slow down.
An employee makes an expensive mistake.
Your costs are rising.
The website stops working.
A process that worked when you had five customers falls apart when you have fifty.
And occasionally, something happens that makes you stare at your desk and think:
“How on earth am I supposed to fix this?”
Welcome to business ownership.
The good news is that you don’t need to be naturally brilliant at problem solving.
You need a good process.
Good problem solving is not about having an immediate answer to every problem.
It is about being able to take a messy situation, break it down, understand what is actually happening and work towards a sensible solution.
Let’s look at how.
1. Don’t Confuse Symptoms With Problems
This is one of the most important ideas in business problem solving.
Imagine your sales have fallen by 20%.
Is the problem:
“Sales are down”?
Not necessarily.
That’s a symptom.
The real problem might be:
- Fewer customers are contacting you.
- Your conversion rate has fallen.
- Existing customers are buying less.
- A major customer has left.
- Your prices have become uncompetitive.
- Your sales team is following up less effectively.
- A competitor has entered your market.
- Your product no longer meets customer expectations.
“Sales are down” tells you what is happening.
It doesn’t tell you why.
And you can’t reliably fix a problem until you understand its cause.
2. Ask “Why?”
One of the simplest problem-solving techniques is also one of the most useful:
Why?
Suppose customers are complaining that orders are arriving late.
Why?
Because orders aren’t being dispatched on time.
Why aren’t they being dispatched?
Because the warehouse team doesn’t receive the order information until late afternoon.
Why?
Because sales staff are entering orders manually at the end of the day.
Why?
Because the order system doesn’t automatically transfer information from the sales platform.
Now you have a very different problem.
The original complaint was:
“Orders are late.”
The underlying problem may actually be:
“Two systems don’t communicate, creating a manual process that delays order processing.”
Those are very different problems.
3. Don’t Stop at the First Explanation
The first explanation you hear is not necessarily the root cause.
Imagine an employee misses a deadline.
You ask why.
They say:
“I didn’t have enough time.”
That’s an explanation.
But ask another question:
“Why didn’t you have enough time?”
Perhaps they were given too many tasks.
Or perhaps the task took longer because they weren’t trained.
Or perhaps the instructions were unclear.
Or perhaps they spent three hours fixing an unrelated problem.
Keep investigating.
You are not trying to interrogate someone.
You are trying to understand the system.
4. Look for Root Causes
A useful distinction is:
Symptom: What you can see.
Root cause: What is actually creating the problem.
For example:
Symptom: Customers are complaining about slow responses.
Possible root cause: Customer enquiries are going into three different inboxes and nobody knows who is responsible for answering them.
If you only tell employees:
“Please respond to customers faster.”
you may get a temporary improvement.
But the underlying system remains broken.
A better solution might be:
“All enquiries go into one shared inbox, with a clearly assigned person responsible for monitoring it.”
Fix the cause rather than repeatedly treating the symptom.
5. Define the Problem Clearly
Before trying to solve a problem, write it down in one sentence.
Not:
“Everything is a mess.”
Try:
“Customer enquiries are taking an average of 36 hours to receive a response.”
That’s much better.
Now you have something measurable.
You can investigate it.
You can discuss it.
You can eventually determine whether you’ve fixed it.
A well-defined problem is already partly solved.
6. Use Data Where Possible
Business owners sometimes make decisions based on impressions.
“Customers don’t seem interested anymore.”
“The team is less productive.”
“We’re spending far too much money.”
Maybe.
But check.
Look at:
- Sales figures
- Customer numbers
- Conversion rates
- Response times
- Complaints
- Refunds
- Delivery times
- Costs
- Profit margins
- Employee workload
- Website traffic
- Repeat purchases
You don’t need an enormous analytics department.
Often, a simple spreadsheet can reveal something important.
You might discover that:
“Sales feel slower”
actually means:
“Sales are down 8%, but only in one product category.”
That makes the problem considerably easier to investigate.
7. Separate Facts From Assumptions
This is one of the biggest improvements you can make to your decision making.
Imagine you say:
“Customers don’t like the new product.”
Is that a fact?
Probably not.
It might be an assumption.
The facts might be:
- Sales are 15% lower than the previous version.
- Refunds have increased.
- Three customers have complained about the interface.
- Website visits have remained stable.
Now you have something to investigate.
Perhaps customers don’t dislike the product at all.
Perhaps they simply don’t understand how to use it.
Never let an assumption quietly become a fact.
8. Talk to the People Closest to the Problem
As a business owner, you may think you understand everything happening in the business.
You don’t.
And that’s normal.
Your employees may see problems you never notice.
Your customer service team may know exactly why customers are unhappy.
Your warehouse staff may know why orders are delayed.
Your salesperson may know why prospects aren’t buying.
Ask them.
Questions like:
“What do you think is causing this?”
“Where does the process usually break down?”
“What makes this harder than it needs to be?”
“If you could change one thing, what would it be?”
You may receive some very useful answers.
9. Be Careful With Blame
When something goes wrong, people naturally look for someone to blame.
Who made the mistake?
Who forgot?
Who didn’t check?
Who was responsible?
Sometimes individual responsibility genuinely matters.
But before blaming someone, ask:
“What made this mistake possible?”
Suppose an employee sends a customer the wrong price.
You could say:
“You should have checked the price.”
Fair enough.
But then ask:
Why was the incorrect price available in the system?
Why wasn’t it flagged?
Was the employee trained?
Was the price list outdated?
Did the process make it easy to make this mistake?
You may discover that the employee made an error and the business had a weak process.
Both things can be true.
10. Look for System Problems
As a business grows, many problems that initially look like “people problems” turn out to be system problems.
For example:
“The team keeps forgetting to follow up customers.”
Maybe.
Or perhaps there is no follow-up system.
“Employees keep making ordering mistakes.”
Maybe.
Or perhaps the ordering process is confusing.
“Nobody knows what they’re supposed to do.”
Maybe.
Or perhaps responsibilities have never been clearly defined.
When the same mistake happens repeatedly, don’t just tell people to be more careful.
Ask:
“What is the system allowing to happen?”
11. Brainstorm Before Judging
Once you understand a problem, generate possible solutions.
Don’t immediately decide that your first idea is the answer.
Write down possibilities.
For example, customer response times are too slow.
Possible solutions might include:
- Hire another person
- Reassign responsibilities
- Create a shared inbox
- Introduce response-time targets
- Automate simple enquiries
- Create standard responses
- Improve staff training
- Change the software
- Reduce unnecessary enquiries
- Improve the website’s information
Some ideas will be terrible.
That’s okay.
You can evaluate them afterwards.
The first stage is about generating possibilities.
12. Ask “What Else?”
A remarkably useful question is:
“What else could we do?”
You’ve come up with a solution.
Ask it again.
And again.
Why?
Because your first solution is often the most obvious one.
Suppose sales are falling.
Your first thought might be:
“We need more advertising.”
What else?
Improve the website.
What else?
Contact previous customers.
What else?
Change the offer.
What else?
Improve conversion rates.
What else?
Introduce a referral programme.
What else?
Now you have choices.
13. Evaluate Solutions Properly
Not every possible solution is a good one.
A useful way to evaluate an idea is to consider:
Impact
How much difference could this make?
Cost
What will it cost?
Time
How long will it take?
Risk
What could go wrong?
Complexity
How difficult will it be to implement?
Reversibility
If it doesn’t work, can you easily undo it?
This prevents you from choosing solutions simply because they sound impressive.
14. Beware of Expensive Solutions
Business owners sometimes respond to problems by spending money.
Problem:
“Our team is too busy.”
Solution:
“Hire another person.”
Perhaps.
But first ask:
Why are they too busy?
Maybe the team spends ten hours a week doing unnecessary administrative work.
If you eliminate that work, you may solve the problem without hiring anyone.
Before spending $20,000 to solve a problem, ask whether a $500 process improvement could achieve most of the same result.
15. Don’t Automate a Bad Process
Technology is wonderful.
But it can also help you do the wrong thing faster.
Suppose your sales process contains seven unnecessary steps.
You decide to automate all seven.
Congratulations.
You now have an extremely efficient bad process.
Before automating something, ask:
“Should we be doing this at all?”
Then:
“Can we simplify it?”
Then:
“Can we automate it?”
That order matters.
16. Prioritise Your Problems
Small businesses can have dozens of problems at once.
You cannot solve all of them today.
Trying to do so usually means solving none of them properly.
Create a list.
Then consider each problem based on:
- Impact
- Urgency
- Cost
- Risk
- Ease of fixing
A useful question is:
“Which problem, if solved, would make the biggest difference?”
Solve that one first.
17. Don’t Let Urgent Problems Crowd Out Important Ones
This is a classic business trap.
Your inbox is full.
A customer needs a reply.
The printer isn’t working.
A supplier wants a call.
Someone needs approval.
These things feel urgent.
Meanwhile, your pricing structure is outdated and your business has no proper sales process.
The urgent problems get attention.
The important problems get postponed.
Eventually, the important problems become urgent.
Set aside time for important problems before they become emergencies.
18. Look for the 80/20 Effect
You will often find that a small number of causes create a large proportion of your problems.
For example:
- 20% of customers create 80% of complaints.
- One product creates most returns.
- One process causes most delays.
- A small number of expenses account for most unnecessary spending.
The exact percentages don’t matter.
The principle does.
Ask:
“Are a few causes creating most of the pain?”
If so, focus there.
19. Test Small Solutions
You don’t always need to completely redesign the business.
Sometimes you can run a small experiment.
Suppose customer response times are too slow.
Instead of immediately purchasing new software, try:
“For the next two weeks, one person will monitor the shared inbox from 9 am to 11 am each day.”
Measure the result.
If response times improve dramatically, you’ve learned something.
Small experiments reduce risk.
20. Don’t Be Afraid of Pilot Projects
A pilot is simply a limited trial.
For example:
“We’ll introduce the new process to one team for four weeks before rolling it out across the company.”
This allows you to discover problems while the consequences are still small.
Pilots are particularly useful for:
- New software
- New procedures
- New products
- New pricing
- New marketing campaigns
- New employee policies
You don’t need to get everything perfect before testing an idea.
21. Define What Success Looks Like
Before implementing a solution, decide how you will know whether it worked.
Suppose you introduce a new customer service process.
Don’t simply say:
“Let’s see how it goes.”
Decide:
“Our target is to respond to 90% of customer enquiries within one business day.”
Now you have a measurement.
After four weeks, you can ask:
Did it work?
Without a definition of success, almost any result can be rationalised.
22. Give Solutions a Deadline
Some problems are endlessly discussed.
Meetings happen.
Ideas are suggested.
Everyone agrees something should be done.
Then nothing happens.
Avoid this by assigning:
- An owner
- A specific action
- A deadline
For example:
Problem: Customer enquiries are taking too long to answer.
Action: Create a shared customer inbox.
Owner: Sarah.
Deadline: Friday.
Success measure: 90% of enquiries answered within one business day.
Now it’s an actual plan.
23. Don’t Solve the Same Problem Repeatedly
This is one of the most frustrating experiences in business.
Something goes wrong.
You fix it.
Two weeks later, it happens again.
You fix it.
Then it happens again.
At some point, stop asking:
“How do we fix this?”
and start asking:
“Why does this keep happening?”
Repeated problems are often signals that a process needs to change.
24. Create Checklists
Checklists are incredibly useful for recurring tasks.
They are especially helpful when:
- Mistakes are expensive
- Tasks happen infrequently
- Several people perform the same task
- There are multiple steps
- Important details are easy to forget
For example, a new employee onboarding checklist might include:
- Contract completed
- Payroll information collected
- Email account created
- Software access granted
- Equipment issued
- Safety training completed
- First-week meeting scheduled
Nobody has to rely entirely on memory.
25. Standardise Repeated Work
If you solve the same problem repeatedly, consider creating a standard process.
Instead of:
“Every time a customer complains, we figure out what to do.”
create:
Customer Complaint Process
- Acknowledge complaint within one business day.
- Record the issue.
- Investigate the facts.
- Determine responsibility.
- Offer an appropriate solution.
- Confirm resolution with the customer.
- Record any lessons for the business.
Now the business has a system.
26. Learn From Mistakes
A mistake is expensive if you make it once.
It becomes even more expensive if you learn nothing from it and make it again.
After a significant problem, ask:
What happened?
Why did it happen?
What should we have noticed earlier?
What can we change?
How can we prevent it happening again?
This is sometimes called a post-mortem or lessons-learned review.
It doesn’t need to be complicated.
Even ten minutes can be valuable.
27. Don’t Punish People for Raising Problems
This is extremely important for business owners.
If employees learn that bad news gets them blamed, they will eventually stop bringing you bad news.
And that is dangerous.
Imagine an employee discovers:
“We may have a problem with this order.”
If they expect to be shouted at, they may keep quiet.
Three days later, the customer discovers it.
Now the problem is much bigger.
Create a culture where people can say:
“I think we have a problem.”
without immediately being attacked.
You can deal with responsibility afterwards.
First, find out what is happening.
28. Reward Early Warnings
You can even reinforce the behaviour you want.
If an employee says:
“I noticed this process is causing errors, and I think we should fix it.”
respond positively.
“Good catch. Let’s look at it.”
They have just saved you from a future problem.
Employees who identify problems early are valuable.
29. Beware of “Quick Fixes”
Quick fixes are not always bad.
Sometimes you need one.
A website is down.
Get it back online.
A customer has been charged incorrectly.
Refund them.
A shipment is missing.
Replace it.
But then ask:
“What caused this, and do we need a permanent fix?”
Otherwise your business becomes dependent on constantly putting out fires.
30. Learn to Distinguish One-Off Problems From Patterns
Not every mistake requires a new system.
Someone accidentally sends an email to the wrong person.
That may simply be human error.
But if it happens every week, investigate.
You don’t want to create a 14-step procedure every time someone makes a minor mistake.
Ask:
“Is this an isolated event or evidence of a recurring problem?”
That distinction will save you a great deal of unnecessary bureaucracy.
31. Don’t Overcomplicate the Solution
A problem has been identified.
You hold a meeting.
Five people brainstorm.
Someone suggests a complicated new system.
Another suggests a committee.
Someone proposes twelve approval steps.
Before long, a simple problem has produced a complicated solution that creates three new problems.
Ask:
“What’s the simplest solution that is likely to work?”
Simple is often better.
32. Know When You Need Help
Being a business owner does not mean knowing everything.
Sometimes the right solution is to ask someone who knows more.
You may need:
- An accountant
- A lawyer
- An IT specialist
- A marketing professional
- An engineer
- An HR specialist
- An experienced mentor
- An industry expert
There is no prize for solving every problem yourself.
The skill is knowing when the problem has moved beyond your expertise.
33. Be Careful With Advice
The opposite mistake is asking ten people for advice and becoming more confused than before.
You ask:
“What should I do?”
Person A says one thing.
Person B says another.
Person C has a completely different opinion.
Remember:
Advice is information, not instruction.
Consider it.
Evaluate it.
Then make your own decision.
34. Don’t Make Big Decisions in a Panic
When something goes badly wrong, there is a strong temptation to react immediately.
Sometimes that’s necessary.
Often it isn’t.
If the problem isn’t genuinely urgent, give yourself some time.
Take a walk.
Write down the facts.
Talk to someone sensible.
Sleep on it.
A calm decision made tomorrow is often better than an emotional decision made in five minutes.
35. Use a Decision Journal
For important decisions, write down:
- What problem are we trying to solve?
- What do we currently know?
- What assumptions are we making?
- What options did we consider?
- Why did we choose this option?
- What result do we expect?
- When will we review it?
This creates a useful record.
Months later, you can look back and ask:
“What did we think would happen?”
and:
“What actually happened?”
You will learn a great deal about your own decision making.
36. Don’t Confuse Confidence With Certainty
You can make a good decision without being certain.
Business rarely gives you perfect information.
You might think:
“I’m 70% confident this is the right approach.”
That’s okay.
You don’t need to wait until you have 100% certainty.
Ask:
“Do we have enough information to make a reasonable decision?”
If yes, act.
Then measure the result.
37. The Five-Step Problem-Solving Process
If you want one simple framework to remember, use this:
Step 1: Define the problem
What exactly is happening?
Step 2: Find the cause
Why is it happening?
Step 3: Generate options
What could we do about it?
Step 4: Choose and act
What is the best practical solution?
Step 5: Review
Did it work?
If not, what did we learn?
That’s it.
You can apply this to an enormous range of business problems.
38. A Practical Example
Imagine your business is receiving too many customer complaints about late deliveries.
Step 1: Define the problem
You discover that 18% of orders are arriving after the promised delivery date.
Step 2: Find the cause
You investigate and discover that most delays happen because orders aren’t being dispatched until the day after they are received.
Step 3: Generate options
Possible solutions include:
- Hire more staff
- Change warehouse hours
- Improve order processing
- Automate order notifications
- Change the delivery promise
- Improve stock management
Step 4: Choose and act
You discover that the biggest problem is manual order entry.
You introduce an automated process and assign one employee to monitor exceptions.
Step 5: Review
After six weeks, late deliveries have fallen from 18% to 5%.
The solution appears to be working.
Notice what you didn’t do.
You didn’t immediately hire three more people.
You investigated first.
39. Build a Problem-Solving Culture
As your business grows, problem solving should not be the owner’s responsibility alone.
Encourage your team to ask:
“What isn’t working?”
“Why isn’t it working?”
“What could we do differently?”
“How can we prevent this happening again?”
You want employees who don’t simply say:
“There’s a problem.”
You want people who say:
“There’s a problem, I think I know why, and here are two possible solutions.”
That’s a much more valuable organisation.
40. Your Business Will Never Be Problem-Free
This is perhaps the most important lesson.
You are never going to reach a magical point where every process works perfectly and nothing goes wrong.
Businesses change.
Customers change.
Employees change.
Technology changes.
Competitors change.
Markets change.
Problems are part of the job.
The objective isn’t to eliminate problems.
It is to become better at dealing with them.
Your First Problem-Solving Exercise
Choose one recurring problem in your business.
Not the biggest problem.
Choose one that annoys you regularly.
Now write down:
1. What exactly is happening?
Avoid vague language.
2. How often does it happen?
Use numbers if possible.
3. What is the impact?
Money? Time? Customers? Stress? Reputation?
4. Why is it happening?
Keep asking “why?” until you get beyond the obvious symptom.
5. What are three possible solutions?
Don’t stop at the first idea.
6. Which solution is simplest to test?
Start there.
7. How will you know whether it worked?
Choose a measurement.
8. When will you review it?
Give yourself a date.
Then do something.
Because ultimately, problem solving isn’t about having clever ideas.
It is about turning a problem into an understanding, turning that understanding into a decision, and turning the decision into action.
The best business owners aren’t people who never encounter problems.
They’re the people who can look at a messy situation, take a breath, ask the right questions and think:
“Okay. Let’s work out what’s really going on.”