Manager answers

How should a manager structure a 1:1?

A good 1:1 structure should start with the team member's agenda, avoid becoming a status update, make room for concerns and motivation, and end with clear actions.

For people managers7 minute readLast reviewed 23 July 2026

I like to open my one-to-ones in the same way: "What would you like to talk about?" Start there, listen properly, then move through your own topics.

The structure should protect the purpose of the meeting. It should not turn the person into a passenger while you run through a script. The key is to get the raw material from them early, make notes, then come back through each point in a useful way.

  1. Ask what they want to talk about.
  2. Listen and write down the points they raise.
  3. Ask about concerns, morale or friction.
  4. Cover development occasionally, not necessarily every week.
  5. Raise your own feedback or expectations.
  6. Review actions and ask what they need from you.

How do you discuss work without making it a status report?

It is reasonable to ask if the individual has any challenges. I would just steer away from going into the work in detail. That is not what a one-to-one is for.

If they bring blockers to the meeting, ask why they have not brought them up earlier or in the meeting that is more appropriate. You are not telling them off for raising a problem. You are making clear that blockers should not wait for a private weekly meeting.

The practical line: work can come up in a 1:1, but the meeting should not become your main delivery-management system.

How do you include motivation and morale?

I keep these questions simple and high level. Ask where they see themselves in a year's time. Ask what they enjoy doing. Ask if there are ways to improve their role.

Once you understand what the individual is trying to achieve, you can try to align the business's goals with their goals. That does not mean you can give them everything they want. It means you have a better chance of making the role meaningful and realistic.

Development does not need to appear in every single 1:1. I would probably cover it monthly, or roughly one in every three or four meetings.

How should feedback be introduced?

If I believe someone has not done the job I expect, either in delivery or quality, I would usually start by asking how they think the work went.

In many cases, they already know. They may say their performance was not up to scratch before you have to say it directly. There may also be legitimate reasons that you do not know about yet. Starting with a question gives them the opportunity to assess their own performance and share information without you beginning in a confrontational way.

That does not mean avoiding the feedback. If they are below expectations, you still need to make that clear. The question just gives the conversation a better starting point.

How should the meeting end?

At the end, review the points discussed and the actions each person has taken away. Make it clear that notes will be shared if that is your process.

I always like to end with the same question: "Is there anything else you need from me?" It is a useful final check. Sometimes the most important point comes out right at the end.

Use the rhythm every week

Turn the structure into a reusable system.

Your First 1:1 System gives you a practical meeting flow, prompts and documentation structure you can use with every direct report.