Improving how well a team functions usually comes down to a few disciplined habits: clear goals, visible measures, honest feedback and fast correction when something drifts. In management, driving performance means creating conditions where people know what matters, how they are doing and what to change next. This article focuses on practical ways to lift results, handle underperformance fairly and keep improvement going in a way that feels realistic for UK workplaces.
The quickest gains come from clearer goals, tighter feedback and fewer bottlenecks
- Performance improves fastest when managers define outcomes clearly instead of relying on effort alone.
- A small set of useful metrics is better than a dashboard full of numbers nobody acts on.
- Regular check-ins beat the annual review because they catch problems while they are still easy to fix.
- Underperformance should be handled as a support and accountability issue, not a surprise attack.
- The biggest leadership gains usually come from removing friction, not adding pressure.
What performance improvement really means in management
I do not treat performance as a personality trait. I treat it as the result of three things working together: clear direction, usable capability and a work environment that does not keep tripping people up. If any one of those is weak, output drops even when effort is high.
That is why the best managers look past the headline result. They ask whether the team understands the goal, whether the process is sensible and whether people have the tools and confidence to deliver. Strong performance is rarely an accident; it is usually a system that has been tuned well enough to make good work easier than bad work.
Once you define performance that way, the next question is what to measure without drowning the team in noise.
Measure the right things before you try to improve them
Most teams do not have a measurement problem. They have a selection problem: too many metrics, not enough meaning. I prefer a small dashboard that combines outcome, quality and speed, because that gives you a fuller picture without turning management into spreadsheet theatre.
| Measure | What it tells you | What can mislead you |
|---|---|---|
| Output or delivery rate | Whether work is actually getting finished | Volume can rise while quality falls |
| Error or rework rate | How often work needs fixing | Low rework may hide under-ambition |
| Cycle time or turnaround | How quickly work moves through the system | Speed alone can reward rushed decisions |
| Stakeholder satisfaction | Whether internal or external customers trust the team | Friendly feedback is not always a true quality signal |
| Milestone hit rate | How predictable delivery really is | Milestones can be set too softly or too aggressively |
For project teams, milestone hit rate often says more than hours logged. For service teams, response time and first-contact resolution can be far more useful than raw activity counts. In 2026, that matters even more because AI dashboards and project tools can make everything look measurable; I still want managers to ask whether the number changes what they do on Monday morning.
A useful rule: if a metric does not change a decision, it is probably decorative. Measure less, but make the measures sharper. Then use them in conversation, which is where improvement really starts to move.
Why regular feedback beats the annual conversation
In the UK, Acas advises regular performance reviews for employees and says they should happen at least once a year. I would treat that as the floor, not the target. The managers who get the best results use shorter check-ins every week or two, because feedback lands better while the work is still fresh.
CIPD’s guidance points in the same direction: feedback works best when it is regular, timely and focused on improvement. That simple point is easy to ignore, yet it changes everything. A vague comment at the end of a quarter is weak; a specific note delivered soon after the work is much more likely to change behaviour.
When I run a performance conversation, I keep it tight:
- What went well and why it worked
- What got in the way
- What one thing to change before the next check-in
- What support or decision is needed from me
That format keeps the talk practical and prevents the meeting from becoming a review of someone’s character. Once feedback becomes routine, it is much easier to deal with problems early.
How to handle underperformance without making it messy
When someone is not meeting the standard, I start with the gap, not the emotion. What is the expected outcome, how far off is the current result and for how long has the gap existed? That sounds obvious, but it stops managers from jumping straight to frustration or vague criticism.
My simplest sequence is this:
- State the standard in plain language
- Check whether the issue is skills, clarity, workload, motivation or something outside work
- Agree targeted support, such as coaching, shadowing, training or a smaller milestone set
- Set a review date and document what success looks like
If the person can do the work but is choosing not to, the issue is usually conduct rather than capability. That distinction matters because the response changes: one route is about support and learning, the other is about behaviour and accountability. The best managers do not rush either route; they make the distinction carefully and fairly.
Handled well, underperformance conversations are not punitive. They are a way to restore confidence, focus and pace before the problem spreads to the rest of the team.
The leadership habits that move results fastest
There is a long list of management behaviours that can help, but a few have an outsized effect. I pay most attention to the habits that reduce confusion and protect attention, because those two things tend to limit performance before talent does.
| Habit | What it changes | Why it matters |
|---|---|---|
| Clear priorities | Removes guesswork | People stop spending energy on the wrong work |
| Short 1:1 check-ins | Creates early warnings | Small issues stay small |
| Specific recognition | Reinforces the right behaviour | Teams repeat what gets noticed |
| Barrier removal | Improves flow | Many performance problems are process problems in disguise |
| Decisive coaching | Builds capability | People improve faster when the next step is obvious |
One mistake I see often is managers confusing availability with support. Being reachable is not the same as helping someone perform better. Real support means making the next decision easier, the next task smaller or the next process cleaner.
Teams usually rise when managers spend less time inspecting output and more time shaping the conditions around it. That leads naturally to the question of how to keep gains from fading once the busy period returns.
The 30-day reset I would use to keep improvement from fading
If I had to lift a team’s results quickly, I would not start with a grand transformation. I would run a 30-day reset: pick three priorities, define one measure for each, and agree a check-in rhythm that is short enough to sustain.
- Week 1: confirm the current standard and identify the biggest bottleneck
- Week 2: narrow the focus to the few behaviours or process steps that matter most
- Week 3: remove one friction point, such as delayed approvals, unclear ownership or duplicate reporting
- Week 4: review the evidence, not the mood, and decide whether to scale, adjust or escalate
The point is not to chase a perfect system. The point is to build a repeatable one that makes better results more likely next month than they were this month. When that habit is in place, performance stops depending on bursts of motivation and starts coming from a management rhythm people can trust.
