Skip to content
People HubLeadership & Management

Performance Conversations Before They Become Performance Problems

Here's the pattern we see constantly: an employee's performance slips. The owner notices but says nothing — it feels minor, they're busy, maybe it'll.

Nick Lucock
Nick Lucock

6 Aug 2026 · 5 min read

Performance Conversations Before They Become Performance Problems. Photo: Livestock (Beef and Sheep) at work

Address performance slips early and small, inside a standing one-on-one rhythm, rather than saving them for a formal meeting a year later. Early feedback is lower-stakes, more likely to fix the issue, and is what makes any later formal step fair — an employee can't correct feedback they never received. Be specific and recent, focus on the behaviour, and agree what changes.

Here's the pattern we see constantly: an employee's performance slips. The owner notices but says nothing — it feels minor, they're busy, maybe it'll self-correct. Months pass. The slippage normalises, resentment compounds, and the eventual conversation arrives carrying a year of stored frustration, to an employee who is genuinely shocked because nobody ever said anything. Every option at that point is expensive. The cheap option was the small conversation a year earlier. Here's how to build the habit — and the fair process behind it.

Why early and small beats formal and late

A performance issue raised inside two weeks is a coaching conversation; the same issue raised after a year is an indictment. Early conversations are lower-stakes for both sides, easier to deliver without emotion, and far more likely to actually fix the problem — most underperformance is unclear expectations, missing skills, or unnoticed obstacles, not bad faith. They're also what makes any later formal step fair: an employee can't course-correct on feedback they never received, and a tribunal will ask exactly that question.

The structural fix is a standing rhythm: a short regular one-on-one with each direct report where work, blockers and feedback are normal agenda items. Feedback delivered inside an existing rhythm is information; feedback that requires a special meeting is an event.

How to say it so it lands

A simple structure beats charisma every time:

Be specific and recent. "The last three quotes went out past the 48-hour standard — the Hendersons one took six days" is workable. "Your attitude lately" is not. Behaviour and outcomes, never character.

Say the standard out loud. Much underperformance is a standards gap: the expectation lived in your head. State what good looks like, concretely.

Ask before prescribing. "What's getting in the way?" surfaces the real cause more often than owners expect — a broken process, an overloaded queue, a home situation, a skill gap they're embarrassed about. The fix differs wildly by cause; diagnose first.

Agree the change and the check-in. What will be different, by when, and when you'll review it together. A feedback conversation without a follow-up date is a wish.

Then write three lines in a file note — date, what was discussed, what was agreed. Not theatre, not a "warning"; just a contemporaneous record. If everything improves, it's never needed. If it doesn't, it's the difference between a defensible process and your word against theirs.

When it doesn't improve: the formal path

If informal feedback hasn't shifted things, escalate deliberately rather than emotionally. A fair process looks like: a meeting where the issues are put clearly with examples and the employee genuinely gets to respond (including a support person if they wish); clear required standards and a reasonable timeframe with the support needed to meet them — training, resources, a written improvement plan for anything substantial; documented review points; and honesty throughout about possible consequences. Procedural fairness isn't bureaucracy — for businesses exposed to unfair dismissal claims it's the whole ballgame, and even where the small-business exemptions and the Fair Work Ombudsman's Small Business Fair Dismissal Code provide some shelter, following a fair, documented process is what keeps you inside it.

Two traps to avoid at this stage: the sudden paper trail (a year of silence followed by three warnings in three weeks reads exactly like what it is) and the performance-conversation-as-ambush (issues raised for the first time in a formal meeting, with no chance to have fixed them earlier).

The conversation owners forget: the good performers

Performance conversations aren't only corrective. The flip side of the avoidance habit is that strong performers hear nothing either — and people who hear nothing assume nobody noticed. The same one-on-one rhythm carries recognition, stretch opportunities and "what do you want next" conversations. Your best people leaving for want of a ten-minute conversation is the most preventable loss in small business.

FAQ

What if the employee gets upset or defensive?

Expect some of it; it's human. Stay on behaviour and standards, acknowledge the reaction without retreating from the substance, and offer to continue the next day if emotions are running the meeting. A paused conversation beats an abandoned one.

How long should an improvement period be?

Long enough to genuinely demonstrate change for that kind of work — typically four to twelve weeks depending on the role and issue. Timeframes that are obviously too short look like a process being run for show, because they are.

Do I really need to document informal chats?

Three lines, yes. Not as a weapon — as memory. Patterns only become visible in writing, and fairness later depends on evidence of what was said earlier.


People issues are usually system issues wearing a name badge. Our free Business Health Check covers the people side alongside finance and operations — five minutes, honest answers.

If this is the problem you are working on, Valont’s People hub runs hr & ir advisory and award compliance as part of a connected back office, and the award finder shows where to start.

About the author

Nick Lucock

Nick Lucock

Chief Executive Officer, Valont

Nick Lucock is the Chief Executive Officer of Valont and leads its day-to-day operations across Finance, People, Operations and Growth. He runs the team that does the work Valont publishes about: the bookkeeping, BAS and payroll runs, the award interpretation on every pay cycle, the IT and security layer, and the advisor cadence that keeps an owner's back office current. Nick writes the practical side of Valont's library, the processes, systems and tools that keep Australian SMEs compliant and growing, and he is the author of most of the operational articles on the site. He works with owners across construction and trades, health, hospitality and professional services.

LinkedIn →

Want to know where your business stands?

Take our free Business Health Check, it takes 5 minutes and gives you a clear picture across finance, people, operations, and growth.