One-to-ones held every other week reduce the risk of burnout by 84%, according to a Forbes survey of 20,000 employees. Yet in many Swedish organisations, the formal development conversation between manager and employee (in Sweden, the medarbetarsamtal) still happens once a year, from a template nobody has looked at since the last time. The gap between those two realities is where engagement quietly leaks away.
The quality of a development conversation comes down to the questions you ask, and how prepared both sides are. This article gives you a practical bank of questions: more than 40 concrete questions sorted by conversation type, an example of what a good exchange sounds like, and a preparation checklist for both manager and employee.
A development conversation is a structured, recurring one-to-one conversation between a manager and an employee, covering the work situation, wellbeing, performance, development and what the employee needs from their manager. It is not a status update on tasks, and it is not a salary negotiation, those are separate conversations with separate rules.
The evidence for doing these conversations well, and often, is unambiguous. According to the research summarised in our guide to the different types of development conversation:
In other words: the annual ritual is out of step with what employees actually want. A better rhythm is quarterly formal conversations plus a short check-in every one to two weeks. The question bank below covers both.
A development conversation fails or succeeds before it starts. Both sides should prepare, and both should know the agenda in advance. We cover preparation in more depth in our article on preparing for a development conversation, but here is the short version.
Different conversations need different questions. Below, the bank is sorted by the four themes most development conversations cover: development, goals, wellbeing and career, plus the short recurring check-in.
Note the last three: asking for feedback on your own leadership is not optional. Research cited in our conversation-types guide shows employee engagement increases dramatically, by as much as 1,250%, when organisations use active listening methods, and listening starts with the manager inviting critique.
Research published in the Journal of Applied Psychology, referenced in our guide, shows employees perform better when they understand the significance of their work, which is why the first two questions on this list matter more than the goal itself.
Questions are only half the craft; the follow-up is the other half. Compare a typical exchange with a better one. The weak version: "How's your workload?", "Fine, a bit busy.", "Good, let's move on." Nothing was learned. The stronger version digs one level deeper:
Manager: How is your workload, sustainable, tight, or too much? Employee: Tight, but manageable. Manager: How long has it been tight? Employee: Since March, honestly. Manager: What is the one thing that, if we removed it, would make the biggest difference? Employee: The weekly reporting. It takes half a day and I'm not sure anyone reads it. Manager: Let me find out who actually uses it. If nobody does, we cut it. I'll come back to you by Friday.
Three follow-up questions, one concrete commitment, one deadline. That is what turns a conversation into change, and it is why every development conversation should end with the same closing question: "What have we agreed, and who does what by when?"
Even a brilliant annual development conversation cannot compensate for eleven silent months. Problems with workload, team friction or motivation build over weeks, not years, and by the time the annual conversation arrives, the employee may already be halfway out the door. That is the case we make in why annual development talks should be replaced with regular check-ins.
The practical model is a layered one:
Pulse data and conversations reinforce each other. If the temperature on workload drops in the survey data, the manager knows to open the next check-in with the wellbeing questions, instead of discovering the problem months later. This is where a platform like Winningtemp helps: not by replacing the conversation, but by telling managers which conversation to have, with whom, and when.
A good development conversation covers four themes: development ("which results are you most proud of?"), goals ("what bottlenecks prevent you from reaching your goals?"), wellbeing ("how sustainable is your workload?") and career ("where do you want to be in two years?"). Choose five to eight questions rather than covering everything, and always include one question inviting feedback on your own leadership, such as "what can I do better to help you succeed?"
The recommended rhythm is a formal development conversation every quarter, complemented by a short check-in every one to two weeks. A Forbes survey of 20,000 employees found that one-to-ones held every other week reduce burnout risk by 84%, and over half of office workers say they want performance conversations at least monthly, a single annual conversation is no longer enough.
Development conversation is the umbrella term for structured one-to-one conversations between manager and employee, covering work situation, wellbeing, performance and development. A performance review is one specific type, focused on the employee's performance and professional development. Other types include goal-setting conversations, pay reviews and recurring short check-ins.
Prepare four things: two or three concrete achievements since the last conversation and why they worked; one obstacle that makes your work harder than it needs to be; a rough direction for where you want to be in one to two years; and one piece of feedback for your manager. Ask for the agenda in advance if you have not received one, and write down what is agreed at the end of the conversation.