Some conversations are difficult because of the subject. Others are difficult because of the uncertainty. You know you need to say something, but you don’t know how the other person will react. Will they become defensive? Upset? Angry? Dismissive? So you put it off. You think about it on the drive home. You replay possible versions of it in your head. Sometimes you even lose sleep over it. But avoiding the conversation rarely makes the issue go away. And there are ways to approach these conversations that are more likely to reduce defensiveness and create a better outcome. In this session we’ll explore how to approach uncomfortable conversations with greater clarity and confidence. We’ll look at how to: describe what is happening without making it personal explain the impact of the behaviour or situation make expectations clear listen properly to the other person’s perspective reduce unnecessary confrontation keep the conversation focused on what needs to change The aim is not to make every uncomfortable conversation easy. It is to help you approach it in a way that gives both people the best chance of leaving with a clearer understanding of: What is happening. What impact it is having. And what needs to happen next.

The reality of becoming a manager, particularly when somebody has been promoted because they were technically good and then left to get on with it.

It is very easy to look at someone who seems disengaged, quiet, slow to act or less enthusiastic than they once were and think:

Most managers want honesty from their team. They want people to speak up. Challenge ideas. Raise concerns. Admit mistakes. Ask for help. Share a different point of view. But saying “my door is always open” does not automatically make people feel safe enough to walk through it. People are constantly reading the environment around them. What happens when somebody disagrees with the manager? What happens when someone makes a mistake? What happens when bad news is delivered? What happens when somebody says, “I don’t think this is working”? If people see others being dismissed, embarrassed, blamed, interrupted or labelled as difficult, they learn very quickly what is and is not safe to say. And sometimes silence can look like harmony. Meetings are polite. Nobody argues. Everyone nods. But underneath, people may be withholding concerns, disagreeing privately or simply deciding that there is no point speaking up. In this session, we’ll explore what helps people feel able to be honest at work and what can quietly shut that honesty down. We’ll look at: trust — do people believe their manager will respond fairly? psychological safety — can people raise ideas, questions, concerns and mistakes without fear of humiliation or punishment? how managers react in the moment — because one poor reaction can have a much bigger impact than we realise disagreement — creating space for healthy challenge without turning it into conflict mistakes — whether they become opportunities to learn or reasons to blame listening — not just inviting people to speak, but showing that what they say is taken seriously power and hierarchy — recognising that speaking honestly to someone more senior can feel risky inclusion — noticing whose voices are heard most often and who may be holding back follow-through — if people raise concerns and nothing ever changes, eventually they stop raising them And I think one of the strongest points is this: Psychological safety is not about everybody being comfortable all the time. People still need to be challenged. Standards still matter. Accountability still matters. There will still be difficult conversations and disagreements. It is about creating an environment where people can say what needs to be said without fearing that doing so will damage their standing, relationships or career. The central message could be: If people only tell you what they think you want to hear, you are not getting the information you need to lead well. And perhaps the closing question: What happens in your team when someone says, “I disagree”? Because the answer to that tells you an enormous amount about the culture.

Most organisations want high performers. Of course they do. People who deliver results, solve problems, win business, keep things moving and make a strong contribution are incredibly valuable. But what happens when that same person is also creating problems around them? Perhaps they are dismissive of colleagues. Maybe they undermine others, dominate meetings, refuse to collaborate, take credit, blame others when things go wrong or leave a trail of frustration behind them. Sometimes everybody knows. The team knows. The manager knows. And yet nothing really happens because the person is seen as too valuable to challenge. That is where things become difficult. Because if someone consistently gets results at the expense of everybody around them, are they really performing well? In this session, we’ll explore what managers can do when somebody’s output is strong but their behaviour is having a negative impact. We’ll look at: what performance really means — results matter, but so does how those results are achieved the impact on the wider team — morale, trust, collaboration and retention why managers sometimes tolerate poor behaviour — fear of losing a key person, dependence on their expertise or reluctance to tackle conflict clarity of expectations — are behavioural standards as clear as performance targets? giving direct feedback — helping someone understand not just what they are doing, but the effect it is having accountability — what happens if the behaviour continues? fairness — what message does it send to everyone else when one person appears to be allowed to behave differently because they get results? development — whether the person can change with the right feedback, coaching and support And I think there is another important angle: High performance can sometimes hide poor leadership potential. Someone may be brilliant technically or commercially and still not be ready to manage people. If we promote purely on results without looking at behaviour, emotional intelligence and impact on others, we can create a much bigger problem later. Performance is not only what you achieve. It is also the impact you have while achieving it. Consider, if everybody behaved like your highest performer, would you have the culture you want?

Feedback is one of the most useful development tools we have. Yet in many workplaces, people only really expect feedback when there is a problem. Something has gone wrong. Performance has slipped. Behaviour needs to change. And of course, sometimes that feedback is necessary. But if feedback only appears when something is wrong, it can start to feel threatening. A much healthier approach is to make feedback part of the everyday culture of a team or organisation. That means recognising what is working well. Helping people understand the impact they have. Giving useful suggestions that help them grow. Encouraging people to ask for feedback rather than waiting for it. And making it safe to give feedback upwards and sideways too. When feedback becomes normal, honest and two-way, the tougher feedback can become easier to hear because it is no longer associated only with failure or criticism. In this session, we’ll explore how to make feedback a useful part of everyday working life — rather than something saved for appraisals or difficult moments. We’ll look at how to: give feedback that is clear, specific and useful recognise what someone is doing well, not just what needs to change focus on behaviour and impact rather than personality create a culture where feedback flows in more than one direction make developmental feedback feel normal approach tougher feedback with clarity and respect when it is needed And I think the closing thought could be: Good feedback should help people understand themselves, build on what they do well and know what they can do differently.

Managers are often expected to be the steady one. The person who keeps things moving. Who reassures the team. Who absorbs pressure from above. Who explains changing priorities. Who deals with problems before they reach everyone else. And often, they do all of that while trying not to let the team see just how much pressure they are under themselves. But managers are people too. They can feel overwhelmed, frustrated, uncertain and exhausted. They can lose sleep over decisions, difficult situations, conflicting demands and the feeling that whatever they do, somebody will be unhappy. The trouble is, the more capable someone appears, the easier it can be to assume they are coping. So while they are busy supporting everyone else, nobody asks: Who is supporting them? In this session, we’ll explore the pressure managers can carry and what happens when they are expected to keep absorbing it without enough support. We’ll look at: conflicting priorities — what happens when different people are asking for different things protecting the team — when this is helpful, and when the manager starts carrying too much alone pressure from above — translating difficult messages without becoming the shock absorber for everything boundaries — recognising what is yours to carry and what is not asking for support — why competent people can find this surprisingly hard creating your own support network — peers, mentors, coaches and people you can think aloud with warning signs — noticing when pressure is becoming unsustainable rather than simply “a busy patch” organisational responsibility — because supporting managers should not rely entirely on the manager being brave enough to ask I’d also bring in something important here: having your team’s back does not mean shielding them from every uncomfortable reality. Sometimes good leadership means being honest about what is happening while protecting people from unnecessary noise, blame or chaos. There is a big difference between supporting your team and absorbing everything for them. And I think the central message could be: Strong managers need support too. You know who in your team comes to you when things are difficult. Who do you go to?

Most organisations want their people to grow. They invest in training. Coaching. Leadership programmes. Workshops. Qualifications. All of that can be hugely valuable. But development works best when people are involved in it — not when it is simply done to them. There is a big difference between: “We think this would really help you. What do you think?” and “You’re going on this course.” One creates ownership. The other can create resistance before the development has even started. Sometimes the problem is that somebody has been sent to training when the real issue is something else. Maybe expectations are unclear. Maybe the manager has avoided a difficult conversation. Maybe the person does not see the need to change. Maybe they are already overwhelmed. Maybe the organisation has decided what the solution is before really understanding the problem. And coaching is exactly the same. Coaching can be incredibly powerful — but only if the person is willing to engage with it. You cannot coach someone into development they do not want. In this session, we’ll explore how to make development more useful, relevant and likely to stick. We’ll look at: starting with the real need — what problem are we actually trying to solve? involving the person — giving people a voice in what development would be most useful readiness — is the person willing and able to engage? training versus coaching — understanding when each is appropriate manager responsibility — not using development as a substitute for honest conversations application — what happens after the workshop, course or coaching session? support and follow-through — helping people practise and apply what they have learned individual differences — recognising that not everybody learns or develops in the same way ownership — helping people take responsibility for their own growth I’d also include a point that I think is very Liaise: Development should be done with people, not to people. That doesn’t mean people only ever develop in areas they enjoy. Sometimes there are very real capability gaps that need addressing. But people are far more likely to engage when they understand why the development matters, have had an honest conversation about it and can see how it will help them. The key message could be: Development is most powerful when the person understands the need, has some ownership of the process and gets the opportunity to use what they have learned. And perhaps the closing question: Before you book the course, appoint the coach or design the workshop — have you actually asked the person what they need?

A team can look perfectly harmonious from the outside. People are polite. Meetings are friendly. Nobody is openly arguing. But that doesn’t necessarily mean everything is healthy. Sometimes there are things bubbling away beneath the surface: Lack of trust. Unspoken resentment. People avoiding difficult conversations. Cliques. Frustrations that never quite get addressed. People agreeing in meetings and then saying something very different afterwards. And actually, complete harmony isn’t always the goal. Healthy teams should be able to disagree. Different opinions, challenge and debate can lead to better decisions — provided people feel safe enough to speak honestly and trust one another enough not to make disagreement personal. The danger is not difference. It is the hidden, destructive stuff that quietly erodes relationships and eventually affects performance. So this session would look at how managers can recognise what may be happening beneath the surface, create the conditions for more honest conversations and build the kind of trust that allows healthy disagreement without damaging the team.

Most managers want people who take responsibility. People who follow things through. Who make decisions. Who speak up when something is going wrong. Who do not need to be chased constantly. But accountability does not happen just because we tell people to “take more ownership”. Sometimes the manager may actually be part of the problem. If expectations are unclear, priorities keep changing, decisions are constantly overridden, people are micromanaged, or they are criticised every time they take initiative, it is hardly surprising if they eventually stop stepping forward. People need to know what they are responsible for, what good looks like and how much freedom they genuinely have to make decisions. In this session, we’ll explore what helps people take greater responsibility for their work — and what can unintentionally get in the way. We’ll look at: clarity — do people really understand what is expected of them? ownership — have they genuinely been given responsibility, or just tasks? accountability — what happens when commitments are not followed through? expectations — are standards clear and consistent? trust — are people allowed to make decisions without everything being taken back off them? the manager’s role — are we encouraging responsibility, or accidentally creating dependence? We’ll also explore the difference between supporting someone and rescuing them. Because if a manager repeatedly steps in, fixes the problem, makes the decision or picks up the unfinished work, the short-term problem may disappear — but the person never gets the opportunity to develop real ownership. The aim is not to leave people unsupported. It is to create an environment where people are clear about what they own, feel trusted to act, and understand that responsibility includes following through. I think the strongest closing line is: Accountability works best when people know what is expected, have the authority to act, and understand that their choices have consequences.

Have you ever found yourself thinking: “I’ve told them this three times.” And yet somehow, nothing changes. The temptation is to assume the other person is not listening, does not care, or simply cannot be bothered. Sometimes that may be true. But sometimes the problem is not that the message was never delivered. It is that the message was never really received. We often think communication has happened because we have spoken, emailed or explained something clearly from our own point of view. But communication is not complete until there is shared understanding. The other person may have heard something different from what we intended. They may not understand why it matters. The expectation may still be vague. There may be competing priorities. They may disagree but not feel comfortable saying so. Or perhaps we have been giving instructions without ever checking what is getting in the way. In this session, we’ll explore what happens when messages do not seem to land and how managers can communicate with greater clarity and impact. We’ll look at: clarity — have we actually explained what we need, or assumed it was obvious? understanding — how do we know the other person has interpreted the message as we intended? listening — communication is not simply waiting for our turn to speak assumptions — the things both sides think the other person “should already know” context — what else is happening that may affect how the message is heard? individual differences — people process information and respond to communication differently checking back — confirming understanding without sounding patronising curiosity — asking why something has not happened rather than simply repeating the instruction louder accountability — once expectations really are clear, what happens if nothing changes? And I think there’s an important point here about repeating ourselves. If we say the same thing in the same way five times and it still isn’t working, the answer may not be to say it a sixth time with added volume. 😄 Sometimes we need to change how we communicate. The central message could be: Communication isn’t what you said. It’s what the other person understood. And I’d probably end with: Before you say “I’ve told them”, ask yourself: Have I made it clear? Have I listened? And do we both understand what needs to happen next?

Most managers do not set out to damage a team. Quite the opposite. They want people to do well. They want the work to get done. They want a team that is capable, motivated and reliable. But good intentions do not always lead to good impact. A manager can unintentionally create tension, dependency, silence, frustration or disengagement through the way they communicate, make decisions, respond to mistakes or handle pressure. Sometimes it is obvious. Sometimes it is much more subtle. A manager might: step in too quickly and solve everything themselves communicate differently with different people without realising how unfair that feels tolerate poor behaviour because someone gets results avoid difficult conversations until problems become much bigger change priorities constantly without explaining why ask for ideas but then ignore them micromanage people they do not fully trust overload the most capable people because “they’ll get it done” fail to recognise what people are doing well create uncertainty simply because they are under pressure themselves None of those things necessarily make someone a bad manager. But repeated over time, they can have a real effect on trust, motivation, confidence and how well the team works together. And that is the point of this session: Managers shape the experience of work far more than they sometimes realise. In this session, we’ll explore some of the everyday behaviours that can either strengthen a team or quietly pull it apart. We’ll look at: self-awareness — understanding the impact your behaviour has on others consistency — people need to know where they stand trust — how it is built, lost and sometimes unintentionally undermined communication — particularly when pressure is high fairness — how inconsistency or favouritism can quickly damage a team autonomy — knowing when to support and when to step back accountability — tackling issues rather than allowing resentment to build recognition — noticing contribution before people start wondering whether anyone cares the ripple effect — how one manager’s behaviour can influence the mood, performance and culture of an entire team And I think we should make one important point very clearly: A manager does not have to be a bully or behave appallingly to damage a team. Sometimes it happens through small, repeated behaviours that gradually erode trust. Equally, managers can have an enormous positive influence through equally small behaviours: Listening. Keeping promises. Explaining decisions. Being fair. Admitting when they got something wrong. Giving people credit. Having the conversation that needs to be had. So the session should not feel like “Here are all the ways managers get it wrong.” It should feel much more like: “Here is the influence you have — and how you can use it well.” The central message could be: You do not need to be a perfect manager. But you do need to understand the impact you are having. And the closing question is probably: If you asked your team what it feels like to be managed by you, what do you think they would say?