How to Improve Team Performance with Clear Processes and Expectations
When the same problems keep coming up with your team, it is easy to assume you have hired the wrong people.
Deadlines slip. Standards drop. People ask for more money or threaten to leave. Managers disagree about who is performing well, while you keep stepping in to sort everything out.
It looks like a people problem.
But before you decide somebody is difficult, unmotivated or simply not good enough, there is another question worth asking:
Have they been given the clear processes and expectations they need to succeed?
When expectations, progression routes and performance measures are unclear, people create their own way of navigating the business. Not because they are trying to cause problems, but because there is nothing else for them to follow.
That is exactly what I found inside a business recently.
How Unclear or Missing Processes Lead to Performance Problems
I’ve spent most of the last fortnight building a pay framework. Rate bands, skill criteria and a lot of very small decisions about what someone should earn for what they can actually do.
The technicians had, by most accounts, started running the show. They were demanding pay rises. Some were threatening to walk. Performance was slipping. If you had asked anyone there a month ago what the problem was, they would have said it was the people.
But when we looked at the data and sat down with the managers, something became obvious.
The team were reacting to the situation they had been given.
There were no published rates. No clear skill criteria. Nothing that said:
“If you can do this, you earn this.”
The only way to earn more was to demand more.
Pay had ended up reflecting who was best at asking, rather than who was best at the job.
That isn’t simply a people problem. It is a process gap, and the team had filled it the only way they could.
Is It a Skills Gap or an Expectations Gap?
After fifteen years of leading teams, I fundamentally believe that most people want to do a good job.
Of course, there are exceptions. I have met a handful of people throughout my career who genuinely did not care.
But when somebody is not doing a good job, it usually comes down to one of two things:
| What is happening? | What might be behind it? |
|---|---|
| They cannot do what you are asking | They may not have the skills, experience or support the role requires. |
| They do not know what you are asking | The expectations, measures or process have not been made clear enough. |
If somebody does not have the skills, continuing to ask the same thing of them is not fair. They may need training, different responsibilities or a role better suited to what they can do.
But far more often, they simply do not know what good looks like.
That is usually much easier to fix. It is also the one founders neglect most often.
Are Your Expectations Clear to Everyone Else?
Think about the complaint you have made twice this month about a person or team.
Maybe they are not keeping you updated. Perhaps deadlines keep slipping, information is always missing or a task only moves forward when you chase it.
Now ask yourself:
Where have I written down what should happen?
Does the person know what good performance looks like?
Do they know when and where to provide updates?
Do they know which decisions they can make themselves?
Is their performance being measured consistently?
Are different managers giving them different instructions?
If you cannot point to a clear expectation, you may have found the real gap.
The complaint is not necessarily about the person. It may be about the thing that was never properly said out loud.
Clear Processes Give Your Team Something to Follow
Founders often put off writing processes because it feels like admin.
There is always something that seems more urgent. A client needs an answer. A proposal needs sending. Somebody in the team has another question.
But without clear processes, you spend even more time reacting.
You chase updates. Hunt for information nobody can find. Sort out access somebody should already have. Follow up on work that was supposed to happen last week.
None of these things feels significant enough to be the problem. But added together, they create founder overwhelm and keep you stuck in the middle of everything.
Good business systems for growth are not enormous manuals that sit untouched in a folder. They are simple, useful instructions that help people understand:
What needs to happen
Who is responsible for it
When it needs to be done
Where information should be recorded
What a good result looks like
That is what creates operational clarity.
It is also how you begin to scale without doing everything yourself.
A Simple Playbook for Closing the Gaps
You do not need to document your entire business at once. Start with the problems that keep coming back.
1. Find the Recurring Complaint
Choose one complaint you have made more than once recently.
What keeps going wrong? What should happen instead? Who needs to take responsibility, and what do they need to know?
Then look for where that expectation has been written down.
If it has never been clearly documented or communicated, start there.
Sometimes the answer is a process. Sometimes it is a checklist, a template, a deadline or a clearer definition of who owns the task.
You are not creating paperwork for the sake of it. You are removing the guesswork.
2. Publish the Route, Not Just the Rule
Do not only tell people what the decision is. Show them what they can do next.
A pay framework should not simply tell employees what they earn. It should show them how they can progress.
In this case, the technicians will be able to see:
Which skills sit within each pay band
What they need to demonstrate
Where their current gaps are
How developing their skills can increase their pay
That takes the personal negotiation out of it.
It is no longer about who asks most loudly, who a manager likes or who is threatening to leave. It is about the skills required for the role.
More importantly, it gives people something they can act on.
The same principle applies to promotions, additional responsibility and development opportunities. If there is a route forward, make it visible.
3. Check What Your Systems Already Know
Before asking everyone what they think, look at the information you already have.
Halfway through a managers’ meeting, somebody pulled live retention data for each technician from the booking system.
We had been debating who was performing well.
The data ended most of that debate in about 90 seconds.
Many founders are guessing at numbers their software has been quietly collecting for years. Depending on your business, that might include:
Customer retention
Repeat bookings
Missed deadlines
Complaints
Project profitability
Response times
Quality checks
Data will not tell you everything about somebody’s contribution. But it gives you a better starting point than assumptions or whoever has the strongest opinion in the meeting.
Check What Behaviour the Process Will Create
Every process has a flipside.
If you reward speed, quality may drop.
If you pay more for Sundays, nobody may want to work Saturdays.
If you reward the number of jobs completed, people may start choosing the easiest ones.
Whenever you introduce a new process, target or incentive, ask:
What behaviour will this actually create?
Not what you hope it will create. What people are likely to do when the new rule meets the reality of a busy working day.
A good operations strategy considers both.
Clear Processes Make Accountability Fairer
Creating a process does not mean avoiding difficult conversations or excusing poor performance.
It makes those conversations clearer.
Once expectations have been communicated, documented and supported, you can hold people accountable for meeting them.
The employee knows what is required. The manager has something objective to refer to. Both sides can see where the gap is and agree what needs to happen next.
Without that structure, accountability can quickly feel personal. With it, you can manage performance more consistently and give people a fair opportunity to improve.
Your First Step Towards Better Team Performance
Before you decide you have a difficult employee, check whether they have been given the clear processes and expectations they need to succeed.
Choose one problem that keeps landing back on your desk. Write down what should happen, make the expectation visible and check whether your systems can tell you what is really going on.
You may still find that somebody is not right for the role.
But you will know you have given them the clarity, tools and support to do the job properly. If a difficult conversation is still needed, you can have it based on something more useful than frustration.
If team issues and missing processes are keeping you far too involved in the day-to-day, find out how my operations consultancy for growing businesses can help you understand what is really going on and put the right structure in place.
For more honest conversations about what it really takes to grow a business, sign up to the free Monday Mover. Every week, I share stories, lessons and practical advice from the world of operations.
Lydia Hawkridge
The Operations Bestie™
I help business owners untangle the operational side of growth by identifying the gaps, bottlenecks, unclear systems and inconsistent processes that can prevent businesses from scaling sustainably.
Stronger operations create stronger foundations for growth. You can explore my operational support services here.
