How to Build a Team That Takes Responsibility, Makes Decisions and Solves Problems

Does this sound familiar?

An employee walks into your office.

“We've got a problem.”

You stop what you're doing.

Listen to the problem.

Work out the solution.

Tell them what to do.

Then 20 minutes later, somebody else appears.

“What should I do about this?”

You solve that one too.

By the end of the day, you've dealt with everybody else's problems – but haven't completed the work you actually needed to do.

If your employees keep bringing every problem to you, the issue isn't necessarily that you've got the wrong employees.

You may have accidentally created a business where:

Problem → Owner → Answer

has become the normal way of working.

And every time you immediately solve the problem, you reinforce that behaviour.

If you want to change it, your employees need to gradually become better at:

Thinking + Deciding + Taking Responsibility + Solving Problems

Here's where I would start.

Why Do My Employees Bring Every Problem to Me?

Before blaming the team, understand why it's happening.

There are several possible reasons:

• They don't know what they're allowed to decide.
• They're frightened of making a mistake.
• You've previously criticised independent decisions.
• They haven't received enough training.
• Responsibilities aren't clear.
• Processes don't exist.
• Managers aren't managing.
• It's simply easier to ask you.
• You've trained them to expect an answer.

Sometimes the behaviour isn't caused by employees avoiding responsibility.

It's caused by the way the business has been structured.

1. Stop Automatically Giving Them the Answer

This is the first change I'd make.

Employee:

“What should I do?”

Instead of answering, ask:

“What do you think we should do?”

If they don't know, ask:

“What options do we have?”

Then:

“Which option would you recommend?”

This feels slower initially.

That's because it probably is.

But you're developing the employee's ability to think rather than simply providing another answer.

The objective is to move from:

Problem → Owner → Answer

towards:

Problem → Employee thinks → Employee recommends → Decision

And eventually:

Problem → Employee solves it.

2. Ask for Solutions, Not Just Problems

Create a simple expectation:

Don't just bring me a problem. Bring me your recommended solution as well.

That doesn't mean employees should hide problems.

You absolutely want to know about important issues.

But instead of:

“Customer X is unhappy. What should I do?”

you want:

“Customer X is unhappy because the delivery was late. I've looked at what happened and recommend we apologise, refund the delivery charge and offer a priority delivery next time. Are you happy with that?”

Now you're developing commercial judgement.

3. Find Out Why They Don't Want to Decide

If an employee continually avoids making decisions, ask why.

Perhaps they're thinking:

“Last time I made a decision, I got criticised.”

Or:

“I don't know how much I'm allowed to spend.”

Or:

“Nobody has explained what I'm responsible for.”

Or:

“If I ask the boss, I can't be blamed if it goes wrong.”

Each problem requires a different solution.

Don't simply label someone:

“They won't take responsibility.”

Find the underlying cause.

4. Clarify What They're Responsible For

Employees struggle to take ownership when roles are vague.

Ask them:

“What are you responsible for making happen?”

If they can't answer clearly, you may have a role-clarity problem.

For example, instead of:

“Sarah helps with customer service.”

use:

“Sarah is responsible for ensuring all customer enquiries receive a response within two working hours and routine complaints are resolved within two working days.”

Now there's an outcome.

Responsibility becomes much clearer.

5. Give Them Authority to Match the Responsibility

This is critical.

Imagine telling an employee:

“You're responsible for customer complaints.”

Then they need your approval to:

• Give a refund.
• Replace an item.
• Offer compensation.
• Change a delivery.
• Make an exception.

They're not really responsible for complaints.

They're responsible for passing complaints to you.

Create decision-making boundaries.

For example:

Customer Service

Refund under £100 → Employee decides.

£100–£500 → Manager decides.

Over £500 → Owner approval.

The exact figures depend entirely on your business.

But employees need to know:

“I am allowed to make this decision.”

6. Create Clear Escalation Rules

You don't want employees making every decision independently.

Some issues genuinely should reach you.

Make the boundaries clear.

For example:

Escalate to me when:

• There's a significant legal issue.
• Health and safety is involved.
• A key customer relationship is at risk.
• Financial exposure exceeds £X.
• The situation falls outside our normal process.
• The business's reputation could be materially affected.

Everything else should ideally be dealt with at the appropriate level.

This prevents both extremes:

Everything comes to you

and:

Employees make decisions they shouldn't.

7. Create Processes for Repeated Problems

If the same problem keeps reaching you, stop solving it individually.

Create a process.

Suppose employees continually ask:

“What do we do when a customer hasn't paid?”

Create a credit-control process.

For example:

7 days before due date → Reminder

Due date → Reminder

7 days overdue → Telephone call

14 days overdue → Escalation

30 days overdue → Formal procedure

Now the answer exists within the business rather than only in your head.

8. Stop Answering the Same Question Twice

This is a useful rule.

If somebody asks:

“How do I do this?”

answer them.

If somebody asks the same question again a week later, don't simply answer it again.

Ask:

“Where should we document this so nobody needs to ask next time?”

Turn repeated questions into:

• Processes.
• Checklists.
• Templates.
• FAQs.
• Training.
• Videos.

Every repeated question can identify a gap in your systems.

9. Develop Managers Who Actually Manage

If you have managers but employees still bring everything directly to you, something isn't working.

Ask:

Why didn't this go to the manager?

Possible reasons include:

• The manager lacks authority.
• Employees don't trust their judgement.
• The manager doesn't make decisions.
• You've trained employees to bypass them.
• You keep overriding managers.
• Reporting lines aren't clear.

If somebody is responsible for managing a team, allow them to manage.

Otherwise, you have the cost of management without gaining the benefit.

10. Stop Undermining Your Managers

Imagine an employee doesn't like their manager's answer.

So they come to you.

You give them a different answer.

What have they learned?

“If I don't like the manager's decision, ask the owner.”

That undermines your management structure.

Where appropriate, your response might be:

“Have you discussed this with your manager?”

If yes:

“What did they decide?”

Unless there's a good reason to intervene, support the agreed management structure.

11. Make People Accountable for Outcomes

If employees are responsible for outcomes, they have more reason to solve problems.

For example:

Instead of:

“Answer customer emails.”

make them responsible for:

“All customer enquiries receive a response within two working hours.”

Instead of:

“Chase invoices.”

make them responsible for:

“Keep overdue debt below the agreed target.”

Instead of:

“Schedule the team.”

make them responsible for:

“Ensure jobs are appropriately resourced and delivered on schedule.”

Outcomes create ownership.

12. Use KPIs to Support Accountability

Employees need to know how performance is measured.

Useful measures might include:

Sales

• Conversion rate.
• Sales value.
• Gross margin.
• Follow-up activity.

Customer Service

• Response time.
• Complaints.
• Resolution time.
• Retention.

Operations

• Jobs completed.
• On-time completion.
• Rework.
• Productivity.

Finance

• Debtor days.
• Overdue debt.
• Invoicing accuracy.

Good KPIs reduce the need for the owner to constantly supervise activity.

You can measure the result.

The “What Do You Recommend?” Rule

This is one of the simplest changes you can introduce.

Every time an employee brings a non-emergency problem, ask:

“What do you recommend?”

At first, they may say:

“I don't know.”

Don't immediately rescue them.

Ask:

“If I wasn't here, what would you do?”

Then:

“What are our options?”

Over time, employees start anticipating the question.

Eventually they arrive saying:

“We've got a problem, and here's what I think we should do.”

That's exactly what you want.

Use a Simple Problem-Solving Framework

Teach employees a repeatable approach.

When a problem occurs:

1. What's the problem?

Describe it clearly.

2. What's causing it?

Don't just deal with the symptom.

3. What options do we have?

Identify possible solutions.

4. What's your recommendation?

Choose an option.

5. What happens next?

Take action.

This gives employees a framework rather than simply telling them:

“Be more proactive.”

Ask “What Have You Tried?”

Before solving the problem, ask:

“What have you tried already?”

If the answer is:

“Nothing.”

then perhaps the issue didn't need escalating yet.

Create an expectation that employees make an appropriate attempt to solve routine problems before passing them upwards.

This encourages initiative.

Don't Punish Every Mistake

If employees believe every mistake results in criticism, they'll naturally avoid decisions.

Why take the risk?

It's safer to ask you.

Distinguish between:

A reasonable decision that didn't work

and:

Carelessness, repeated poor judgement or ignoring agreed processes.

The first can become a learning opportunity.

If employees aren't allowed to make any mistakes, they'll never develop the confidence to make decisions.

Create Safe Decision Boundaries

Not every mistake has the same consequences.

Let employees develop decision-making skills in lower-risk areas.

For example:

Low financial impact + Reversible decision

Employee decides.

Medium impact

Manager decides.

High financial/legal/safety impact

Escalate.

This lets people develop without exposing the business to unnecessary risk.

Coach Instead of Rescue

There's an important difference.

Rescue

Employee brings problem.

You solve it.

Coach

Employee brings problem.

You ask questions that help them solve it.

For example:

“What outcome are we trying to achieve?”

“What's stopping us?”

“What options do we have?”

“What are the risks?”

“What would you recommend?”

“What are you going to do next?”

It may take longer today.

But it can save you enormous amounts of time in the future.

Create Decision-Making Principles

Processes can't cover every possible situation.

That's where principles help.

For example:

Customer Service

Protect the long-term customer relationship while remaining commercially reasonable.

Pricing

Never discount without receiving something of value in return.

Purchasing

Choose the best overall commercial option, not automatically the cheapest.

Complaints

Resolve the problem as close to the customer as reasonably possible.

Principles help employees make decisions when no exact process exists.

Give Employees Access to the Information They Need

Sometimes employees ask you because you have information they don't.

Perhaps only you know:

• Customer history.
• Pricing.
• Margins.
• Supplier arrangements.
• Budgets.
• Previous decisions.

Ask:

“What information would they need to make this decision without me?”

Then provide appropriate access.

You can't expect good decisions from people who don't have the information required to make them.

Explain the Commercial Impact

Help employees understand how the business works.

For example:

A salesperson shouldn't only understand revenue.

They should understand why margin matters.

An operations manager should understand why overtime and rework affect profitability.

A customer service employee should understand the value of customer retention.

Commercial understanding improves decision quality.

Use Weekly One-to-Ones

Instead of employees interrupting you constantly, create structured time.

For example, a weekly one-to-one could cover:

Results

Problems

Decisions

Development

Priorities

Actions

Unless something is genuinely urgent, employees can save issues for the scheduled conversation.

This can reduce constant interruption while still providing support.

Create an “Urgent vs Important” Rule

Employees need to understand what actually requires immediate escalation.

For example:

Urgent

• Safety issue.
• Serious customer escalation.
• System failure stopping operations.
• Significant financial risk.

Not Urgent

• Routine scheduling.
• Minor customer query.
• Standard purchase.
• Normal operational decision.

Without clear boundaries, everything can feel urgent.

And everything ends up with you.

Make the Team Solve Problems Together

You don't need to be the only source of knowledge.

If an employee has a problem, could they ask:

• Their manager?
• A colleague?
• Another department?
• The internal knowledge base?

Build a business where expertise exists across the team.

The route shouldn't always be:

Employee → Owner

Use Team Meetings for Problem Solving

A useful section in your team meeting could be:

Problems We Need to Solve

But add a rule:

Anyone raising a problem should also bring at least one possible solution.

Then the team can discuss:

Problem

↓

Options

↓

Decision

↓

Owner

↓

Deadline

Now you're building collective problem-solving capability.

Recognise Employees Who Take Ownership

If you want more ownership, notice it.

For example:

“I liked the way you dealt with that customer issue. You understood the problem, considered the commercial impact and resolved it without unnecessarily escalating it.”

That's more useful than simply:

“Good job.”

You're reinforcing the behaviour you want repeated.

Stop Rewarding Helplessness

This happens unintentionally.

Employee A asks you everything.

You spend hours supporting them.

Employee B solves problems independently.

You barely speak to them.

Who gets most of your attention?

Employee A.

Be careful that your behaviour doesn't accidentally reward dependency.

Spend time developing and recognising the people demonstrating ownership too.

What If an Employee Keeps Making Poor Decisions?

Then you need to diagnose why.

Is it:

Skill?

They need training.

Knowledge?

They need more information.

Experience?

They need supervised practice.

Confidence?

They need encouragement and progressively greater authority.

Clarity?

Responsibilities aren't clear.

Attitude?

They don't want responsibility.

Capability?

The role may exceed their current ability.

Different causes require different responses.

Don't treat every performance problem as a training problem.

What If My Employees Don't Want Responsibility?

Some people prefer clear instructions.

That's not automatically a problem.

Not every employee needs to become a senior decision maker.

But every role should still have an appropriate level of ownership.

A useful conversation might be:

“This role requires you to make routine decisions within these boundaries rather than escalating everything to me.”

Make expectations clear.

Then support and measure performance.

Create an Escalation Matrix

This can be extremely effective.

For example:

SituationEmployeeManagerOwnerRoutine customer query✓

Complaint under £100✓

Complaint £100–£500

✓

Major account complaint

✓✓Routine supplier order✓

New supplier agreement

✓

Major contract

✓Safety/legal issue

✓

Adapt it to your business.

Now employees have clarity about what belongs where.

Measure How Often Problems Reach You

You can turn owner dependency into a measurable number.

For two weeks, record:

How many employee problems reach me each day?

Then categorise them:

• Needed my involvement.
• Could have been handled by a manager.
• Employee could have solved it.
• Process was missing.
• Responsibility was unclear.

Suppose you receive:

40 problems per week.

And only 10 genuinely require you.

You've identified 30 opportunities to improve the business.

Set a target to reduce unnecessary escalations.

Don't Aim for Zero Questions

That's not the objective.

A team that never asks questions could be just as worrying.

You want employees to escalate the right things.

The goal is:

Fewer unnecessary questions

and:

Better-quality questions.

Instead of:

“What should I do?”

you want:

“Here's what happened, here's what I've checked, here are the options and here's what I recommend.”

That's a much stronger organisation.

Your Management Style May Be Part of the Problem

This can be difficult for owners to recognise.

Ask yourself:

Do I jump in too quickly?

Do I constantly correct people?

Do I override decisions?

Do I insist things are done exactly my way?

Do I give responsibility but retain all authority?

Do I secretly enjoy being needed?

If yes, your team may simply be responding to the environment you've created.

Changing employee behaviour sometimes requires changing owner behaviour first.

Move From Answers to Questions

A useful leadership transition is:

Early Business

Owner provides answers.

Growing Business

Owner asks questions.

Developed Team

Employees provide answers.

That doesn't mean you stop leading.

It means your role becomes developing other people's ability to think and act.

From Employee Dependency to Employee Ownership

Here's the progression you're trying to create:

Stage 1

“What should I do?”

Stage 2

“I think we should do this. Is that okay?”

Stage 3

“I'm going to do this unless you see a problem.”

Stage 4

“I've dealt with it. Here's what happened.”

Stage 5

Routine issues no longer reach you.

That's how you gradually build a business that doesn't depend on the owner for every answer.

A 30-Day Employee Accountability Plan

Here's a practical way to start.

Week 1 – Measure

Record every employee problem brought to you.

Categorise why it reached you.

Week 2 – Clarify

Choose the biggest recurring areas.

Define:

• Responsibilities.
• Authority.
• Escalation points.

Week 3 – Systemise

Create processes for repeated problems.

Start asking:

“What do you recommend?”

instead of immediately providing answers.

Week 4 – Review

Look at:

How many issues still reach me?

Which employees are becoming more independent?

Where are the remaining bottlenecks?

Then repeat.

The Bigger Goal: A Business That Can Operate Without Constant Owner Intervention

Stopping employees bringing every problem to you isn't just about having a quieter day.

It affects your ability to:

• Delegate.
• Grow.
• Take holidays.
• Develop managers.
• Work strategically.
• Reduce your hours.
• Build a stronger business.

If every problem requires you, you're not simply the owner.

You're also the business's main problem-solving system.

That's difficult to scale.

What Should Employees Still Bring to You?

There will always be issues that appropriately require owner involvement.

Depending on your business, these could include:

• Major strategic decisions.
• Significant investments.
• Serious legal matters.
• Major financial commitments.
• Senior recruitment.
• Critical customer relationships.
• Significant reputational risk.

The objective isn't to remove yourself from important decisions.

It's to stop spending your day making decisions somebody else should be making.

Build a Team That Thinks Before It Asks

Imagine the difference.

Instead of hearing:

“We've got a problem. What should we do?”

you hear:

“We've got a problem. We've identified three options. I recommend option two because it protects the customer relationship and keeps us within budget. Unless you see something I've missed, I'll proceed this afternoon.”

That's not just an employee completing tasks.

That's somebody taking ownership.

And that's what eventually allows you to step away from day-to-day operations.

Want Your Employees to Take More Responsibility?

I'm Kim Wheatley, a business coach and mentor helping SME business owners across Essex and the UK.

I work with established SME owners who often find themselves spending too much time answering questions, solving employee problems and making decisions that shouldn't necessarily require them.

We can work on areas including:

• Employee accountability.
• Delegation.
• Leadership.
• Management.
• Decision making.
• Systems and processes.
• Productivity.
• Time management.
• Business growth.

The objective isn't to stop supporting your employees.

It's to develop a team that can think, make appropriate decisions and take responsibility without everything continually coming back to you.

Book Your Free Business Growth Accelerator Meeting

If you're constantly interrupted by employees asking what to do next, let's identify why.

During a Free Business Growth Accelerator Meeting, we can look at:

• Your current team structure.
• Employee responsibilities.
• Management.
• Delegation.
• Decision-making authority.
• Systems and processes.
• Accountability.
• Where the business still depends too heavily on you.

Then we can identify practical steps to help your employees take greater ownership.

Book your Free Business Growth Accelerator Meeting today.

Frequently Asked Questions

Why do my employees bring every problem to me?

Common reasons include unclear responsibilities, insufficient authority, lack of confidence, inadequate training, missing processes or a culture where the owner has traditionally made most decisions.

How do I get employees to solve their own problems?

Instead of immediately providing the answer, ask what they've already tried, what options they've considered and what they recommend. Give them clear decision-making boundaries and gradually increase responsibility as their capability develops.

How do I make employees more accountable?

Define clear outcomes, responsibilities, authority, measures and review points. Accountability works best when employees know exactly what they're responsible for and how success will be assessed.

What should I say when an employee asks me what to do?

For appropriate non-urgent issues, start with: “What do you think we should do?” Follow with questions about their options and recommendation. This encourages problem-solving rather than automatic escalation.

How do I stop employees being afraid to make decisions?

Clarify which decisions they're allowed to make, provide training and distinguish reasonable mistakes from negligence or repeatedly ignoring agreed processes. Increase decision-making responsibility progressively.

Should employees always bring a solution when they report a problem?

Not always. Serious safety, legal or emergency situations may require immediate escalation. But for normal operational problems, encouraging employees to think about potential solutions before escalating can help develop judgement and ownership.

How do I stop employees bypassing managers and coming directly to me?

Create clear reporting lines, give managers genuine authority and avoid routinely overriding them. Where appropriate, redirect employees back through their manager rather than becoming the alternative decision-maker.

What is an escalation matrix?

An escalation matrix sets out which decisions employees can make, which require management approval and which need owner involvement. It can reduce uncertainty and unnecessary escalation.

How can systems and processes improve employee accountability?

Processes clarify what should happen, who is responsible, what standard is required and when issues should be escalated. This reduces reliance on employees repeatedly asking the owner what to do.

Can a business coach help improve employee accountability?

Business coaching can help business owners create clearer responsibilities, delegation, accountability, management structures and processes while providing accountability for implementing those changes consistently.