Why regular 1:1 meetings
A one-on-one is a regular slot between a manager and an employee, devoted to that person: their work, obstacles and development. Without a record and an agenda it quickly turns into small talk or a task review, and after a few weeks nobody remembers what was agreed.
A common rhythm is a meeting every week or every two weeks, for half an hour, and a broader development conversation once a quarter. Regularity matters more than frequency: a meeting that keeps getting cancelled stops making sense.
The structure of a good meeting
- A pulse to start
Before the meeting the employee marks their mood and workload on a scale of 1 to 5. A drop shows up straight away, before it becomes a problem.
- The employee's points first
It's their time. The points they added go first.
- Then the manager's points
Information, requests, feedback.
- Goals and development
Briefly every meeting, more broadly once a quarter: progress on goals, competencies, the training budget.
- Agreements
Who, what and by when. Every agreement lands on the task list of the person doing it.
Ready question sets help with meetings that aren't routine: onboarding a new person, a quarterly review, a drop in motivation, career development. Every manager can have their own versions.
Feedback with the FUKO model
FUKO is a simple Polish feedback model that turns a generality (“you need to try harder”) into specific information.
- Facts
What happened, without judgement. “At the last three team meetings, the report was ready only during the meeting.”
- Feelings
How it affects me. “It worries me, because I don't have time to read it before the decision.”
- Consequences
What follows for the team or the work. “We make decisions without current data.”
- Expectations
What I expect from now on. “Please have the report ready the day before the meeting.”
The same model works for praise and for feedback to a manager. Recorded in the tool, it isn't lost and can be revisited at the quarterly review.
What to require from a tool
Privacy is the condition for honesty
If an employee suspects HR or management will read their words, the meeting becomes a formality. That's why the rules have to be built into the tool, not just written down: meeting content is visible only to its two participants, HR and management see numbers (how many meetings, whether on time), and mood averages appear only from several people up, so nobody can be singled out.
Meeting records are employees' personal data. Before you roll out a tool, agree with HR and the data protection officer who has access to what and how long you keep the records.
Terms from this guide
- FUKO
A Polish feedback model: facts, feelings, consequences, expectations.
Questions and answers
How often should 1:1 meetings happen?
Most often every week or every two weeks. Regularity matters more than frequency, and it's better to reschedule a meeting than to cancel it.
Isn't a notebook or a shared document enough?
To start with, yes. A tool makes sense when a manager has several people, you want to track goals and agreements, and HR needs to know whether meetings are happening without reading their content.
Who should run the agenda?
Both sides. When only the manager writes the agenda, the meeting easily turns into a briefing.