Staff development conversations: what the 6th edition asks for and how to run one
Practice Managed team3 min read
A good development conversation tells your team member what's going well, where they'd like to grow and what help they'll get. The RACGP Standards ask you to have one with each employed team member and to write it down. This guide explains what's needed and gives you a simple way to run one.
What the Standards ask for
5th edition (what your next visit uses): criterion C3.2 asks that your practice has performance discussions with each team member, and that you regularly monitor how the team is going. The guidance gives every six months as an example, says the discussions aren't meant to be disciplinary, and asks managers to write down the discussion, the actions agreed and any development needs.
6th edition (what is coming): criterion F4.D says the practice discusses professional development with each employed member of the practice team. The guidance says:
- managers need to write down the key points, the actions and the development needs
- the conversations are collaborative and separate from salary reviews
- good practice includes scheduled conversations, realistic goals, tracking progress, two-way feedback, and finding learning such as training and mentoring
How often?
The 6th edition doesn't set a time. The RACGP's business toolkit suggests a regular review at least once a year. That's RACGP advice rather than a Standards rule. Shorter, informal catch-ups in between are fine too.
How to run one
- Book it ahead, in work hours, somewhere private. Give the team member the template beforehand so they can think about it.
- Start with what's gone well since last time.
- Check the role. Is their position description still right? The 6th edition guidance says staff sign their position description to show they understand their role.
- Talk about strengths and areas to grow, and ask for their feedback on the practice too.
- Agree a few realistic goals that suit them and the practice.
- Plan the learning: courses, mentoring, and any training that's due, such as CPR.
- Write down the actions: what, who and by when.
- Set the next date, then both sign, and give them a copy.
It's not a performance warning or a pay talk
Keep the conversation about development. Don't raise a performance problem here for the first time, and keep pay for a separate meeting. The RACGP's toolkit says to deal with underperformance as soon as you notice it, not save it for the review. The Fair Work Ombudsman's guide to managing underperformance explains how.
Our free staff development conversation template has a section for each step, with space for both of you to sign.
We check every fact against official sources, but rules change. Always check the official source before you rely on it.
Want to know where the rest of your practice stands? Take the free readiness check: ten yes-or-no questions, your score straight away, and a to-do list sent to your inbox.
Sources
- RACGP Standards 6th edition, F4 Induction, training and supporting performance
- RACGP Standards 5th edition, Criterion C3.2 Accountability and responsibility
- RACGP General Practice Business Toolkit: managing employees' performance
- Managing underperformance best practice guide (Fair Work Ombudsman)
Read next
- staff development
- performance review
- professional development
- RACGP
- 6th edition