In many small companies development is the thing everyone agrees is important and nobody schedules. The owner is busy, the employee does not want to add to the load, and a year later the best person on the team is looking at job adverts.
You do not need an HR department to fix this. You need one conversation a year per person, a short written outcome and a date to look at it again.
How it differs from a one-to-one
A regular one-to-one meeting deals with the current work: blockers, priorities, small feedback. The development talk looks at the next twelve months and beyond: what the person wants to learn, where they want to grow and what the company can realistically offer.
Keep the two apart. If the yearly talk is squeezed into a weekly slot, the urgent work wins every time. Book 60 minutes, away from the desk, and tell the employee a week ahead what it is for.
Also keep it apart from pay. A raise discussion makes people careful with what they say. If pay must be reviewed, do it in a different week.
Before the talk
Send the employee four questions and ask them to think about them, not to write an essay:
- What part of the last year are you proudest of?
- What took energy away from you, and what gave you energy?
- What would you like to be better at a year from now?
- What would make you stay here for another three years, and what could make you leave?
The last question is uncomfortable and useful. Say that you ask it because you would rather hear it now than in a resignation letter.
You prepare too. Write down three things: what the person did well (with two concrete examples), where you see room to grow, and what the company can offer. "Can offer" means things you control: time for a course, a project that stretches them, a mentor, a change of tasks. Do not write down anything that depends on budget you do not have.
During the talk
Aim for a ratio of about two thirds listening. A simple order works well:
- Ten minutes: looking back. Start with their answers to questions 1 and 2. Add your own examples.
- Twenty minutes: looking ahead. Go through question 3. Ask "what would that look like in practice?" until the answer is a task, not a wish.
- Ten minutes: reality check. Say what the company can and cannot do. Be honest about limits; a clear "not this year" is better than a vague "we'll see".
- Twenty minutes: agreements. Choose three and write them down together.
If the employee wants something you cannot give, do not argue. Write it down as a wish, explain why it is not possible now and say when you will look at it again.
The three agreements
Limit the outcome to three. More than that and nothing gets done.
| Agreement | Example | Owner | Date |
|---|---|---|---|
| A skill to build | Learn to run the monthly customer report without help | Employee | End of Q2 |
| A change in responsibility | Take over supplier ordering from the owner | Employee, with owner handing over | 1 March |
| Something the company does | Pay for a two-day course and free the time | Owner | Booked by 30 November |
Each line has one owner and one date. One of the three must be on the company's side. If all three are the employee's homework, the talk was a to-do list, not a development conversation.
Use plain wording. "Improve communication" is not an agreement; "present the weekly numbers to the team on Mondays" is.
What to write down
One page, kept by the manager and shared with the employee the same day:
- the three agreements with owner and date,
- one sentence on what the employee wants in the longer term,
- the date of the half-year check,
- anything the employee asked you not to share (and you respect that).
Store it where only the two of you and whoever must see it can read it. Employee development notes are personal data, and the rules on how long you may keep them and who may read them differ by country, so check them before you set up a shared folder.
The half-year check
Before you leave the room, put a 30-minute slot into both calendars, six months ahead. Use it to answer three questions: what was done, what got in the way and what changes in the remaining half year.
Most agreements fail not because people do not care but because nobody looks. Thirty minutes at the half-year mark are what turns an annual talk into an ongoing habit. If the situation has changed, rewrite the agreements; that is a sign the process works, not that it failed.
Common mistakes
- Promising what you do not control. "You will be team lead next year" is a promise. "I will give you the lead on the next client project and we'll review how it goes" is an agreement.
- Only talking about weaknesses. People develop faster when you build on strengths and then add one thing to improve.
- Cancelling the talk. A cancelled development talk tells the employee how much it matters. Reschedule within two weeks, never skip.
- Treating everyone the same. A junior may want skills, an experienced person may want less routine or more freedom. Ask rather than assume.
Where AI can help, and where it should not
An AI assistant can help you prepare: turn your notes into a one-page summary, suggest follow-up questions based on the employee's answers or draft the agreement page from your handwritten notes. It can also remind you of the half-year date and list the agreements due.
It should not assess the person, rank employees or decide who gets development opportunities. Do not paste sensitive personal notes into a tool your company has not approved for that purpose, and read every generated text before it is filed.
What to do this month
- List everyone on the team and write next to each name the date of their last real development talk. Most small companies find "never" more often than they expected.
- Book one 60-minute slot per person across the next two months, starting with the people you would least like to lose.
- Send the four questions a week before each talk.
- Prepare a one-page template with the three agreements, owners, dates and the half-year check.
- Add the six-month follow-ups to the calendar when you finish each talk.
It costs about two hours per person per year, including preparation and the check. It is one of the cheapest ways to keep the people you already have.
Sources
- CIPD, Talent factsheet: background on developing and retaining people.
- UK Information Commissioner's Office, Advice for small organisations: basics of handling employee personal data.