The B2B Podcast Index
Index
All categories
MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
MethodologySubmit
Best of:MarketingSalesSaaSFinanceHROpsLeadershipCustomer SuccessAI & DataProductStartups & FoundersRevOpsEngineering & DevTools
An independent project byFame
SearchBest episodesGuestsInsightsMethodologySubmit a podcast
Index/Leadership/Leadership & Management Reset Podcast
Leadership & Management Reset Podcast artwork

How to Hold Your Team Accountable - Episode 9

Leadership & Management Reset Podcast · 2026-04-29 · 20 min

0:00--:--

Key moments - from our scoring

Substance score

19 / 100

Five dimensions, 20 points each

Insight Density5 / 20
Originality4 / 20
Guest Caliber4 / 20
Specificity & Evidence3 / 20
Conversational Craft3 / 20

Sharon Smith reframes accountability beyond micromanagement by emphasizing visible ownership and progress rather than constant checking. The core problem many managers face - either chasing team members repeatedly or doing work themselves - stems from unclear expectations and lack of visibility into progress. Smith argues that regular one-to-one meetings are the underused tool that creates natural accountability: instead of random email check-ins, team members come prepared with updates on progress, risks, and support needs. She recommends managers reinforce visible accountability through specific recognition, set clear standards across the team, and address slip-page early through calm, constructive conversations. For line managers struggling with delegation and team oversight, this episode offers practical tactics for building trust while eliminating the anxiety loop that leads to micromanagement or overwork - specifically through consistent one-to-one structures, clarity on expectations, and recognizing ownership when it appears.

Key takeaways

  • →Accountability means making ownership and progress visible, not constant checking in - when team members communicate proactively about their work, it signals healthy ownership rather than drift.
  • →Regular one-to-one meetings are the most underutilized tool for building accountability; they shift team members from reacting to random check-ins to proactively preparing updates and sharing progress.
  • →Recognizing and calling out examples of good accountability (proactive flagging, early updates, follow-through) reinforces the behaviors you want to see and shapes team standards over time.
  • →When accountability isn't happening, address it directly but calmly by stating observed facts (missed deadlines, lack of updates) and discussing how to make progress more visible, rather than waiting or hinting indirectly.
  • →Setting clear expectations about what good looks like - in communication, response rates, standards, and effort - prevents frustration and ensures equitable accountability across your team.

In this episode

  1. 1The Accountability Problem: Delegation Without Visibility
  2. 2Reframing Accountability: Making Ownership Visible
  3. 3Recognizing Accountability Drift: Early Warning Signs
  4. 4One-to-One Meetings as a Cornerstone for Accountability
  5. 5Reinforcing and Recognizing Good Accountability
  6. 6Addressing Accountability Issues: Clear and Constructive Conversations
  7. 7Setting and Holding Team Standards
  8. 8Creating Consistency Through Regular Check-ins and Systems

Topics in this episode

difficult conversationsOne-to-one meetingsTeam delegationProgress visibilityMicromanagement avoidanceStandards and expectationsProactive communicationOwnership and responsibilityTeam trust and relationships

Questions this episode answers

What is the difference between accountability and micromanagement according to this episode?

Accountability means ownership becomes visible through progress updates and communication, not through constant checking in. Micromanagement is hovering and frequent check-ins; true accountability is about creating a structured space (like regular one-to-ones) where team members proactively share progress, so managers have clarity without needing to chase.

How can managers tell when accountability is starting to drift with a team member?

Early signals include deadlines being pushed back, work coming back unfinished, and updates becoming less frequent or stopping altogether. When communication fades and goes quiet, that's when a manager should recognize that ownership is slipping rather than waiting for obvious failures.

What role do one-to-one meetings play in building team accountability?

One-to-one meetings create a consistent, structured space where team members come prepared to share updates on progress, what's on track, risks, and where support is needed. This replaces random reactive check-ins and encourages forward thinking, preparation, and stronger ownership over time.

What should managers do when a team member is not taking accountability?

Address it early and directly while staying calm and constructive. Smith recommends being specific about what you've noticed (e.g., 'I've noticed deadlines have slipped and I'm not always seeing updates on time') and opening a conversation about how to make progress more visible going forward, rather than hinting indirectly or waiting for improvement.

How does recognizing visible accountability help shape team behavior?

When managers notice and call out ownership, responsibility, and proactive behavior - even in small ways - it reinforces what good looks like. Over time, what gets noticed tends to become more consistent across the team, helping establish equitable standards of effort and accountability.

What our scoring noted

Our reviewer’s read on each dimension, with quotes from the episode.

Insight Density

5 / 20

The episode is almost entirely composed of well-known management platitudes - hold one-to-ones, recognise good behaviour, address drift early. The modest reframe of accountability as 'ownership becoming visible' is the only marginally non-obvious idea, but it is not developed with any depth or nuance. Extensive padding and repetition dilute even the basic points.

One helpful way to think about accountability is that ownership becomes visible.
The more you step in, the less space that is for someone to fully own it.

Originality

4 / 20

Every idea here - structured one-to-ones, positive reinforcement, setting clear standards, having candid conversations - is textbook management content recycled without any contrarian angle or first-principles reasoning. The plant-watering metaphor is colourful but trivially decorative rather than intellectually generative.

Think of it as your weekly watering or your monthly watering or however regular you do your one to ones. Think of it as the time that you water.
what gets noticed tends to become more consistent

Guest Caliber

4 / 20

This is a solo-host monologue by Sharon Smith; no credentials, organisational scale, or practitioner track record are established in the transcript. She presents as a coaching-style thought leader rather than an operator who has led and measured accountability systems at meaningful scale.

So today, I want to explore a slightly different way of approaching accountability.
if you're wanting some support and having difficult conversations, then please listen to episode 7 of this podcast where I've taught that through.

Specificity & Evidence

3 / 20

There are no named organisations, no data, no metrics, no timelines, and no real case studies anywhere in the episode. All examples are hypothetical scripts ('it might sound something like…') and the advice stays entirely abstract throughout.

it might sound something like I've noticed you flagged that early that was really helpful. Thank you.
I've noticed a few deadlines have slipped, and I'm not always seeing updates out of time. Can we talk about how to make progress more visible going forward?

Conversational Craft

3 / 20

The episode is a solo monologue with no guest, no interviewing, and no substantive follow-up or challenge dynamic. Rhetorical questions directed at the listener substitute for real dialogue, and the structure meanders with considerable repetition rather than building a sharp argument.

So I should reflect on this a useful place to start might be.
The questions #ah that the Lane manager might ask don't need to be complicated.

Conversation analysis

Computed from the transcript - who did the talking, and the words that came up most.

Most-used words

team33member16accountability13manager12start10happening10ones10clarity9ownership9support9feel8delegated8progress8back8forward7line7

Episode notes

If you've ever delegated something… and then found yourself quietly wondering, "Is this actually getting done?" - this episode will feel very familiar. Because holding your team accountable isn't about chasing updates or stepping in to fix things yourself. And it's not about micromanaging either. In this episode, I explore a more grounded, practical approach to team accountability - one that creates clarity, shared ownership, and consistent progress without the constant follow-up. You'll learn: Why accountability often breaks down, even when you think you've been clear The subtle signs that ownership is drifting (before it becomes a problem) How to use 1:1 conversations to naturally build accountability into your team rhythm What to say when expectations aren't being met - without creating tension or avoidance How to reinforce accountability through simple, specific recognition This episode is especially useful if you're finding yourself chasing updates, carrying work that isn't yours, or questioning whether your team are really taking ownership. Because accountability isn't about control. It's about making ownership visible - for you and for your team.

Full transcript

20 min

Transcribed and scored by The B2B Podcast Index.

Episode 9 - How to Hold Your Team Accountable - TRANSCRIPT - (This transcript has been created with AI, and therefore there may be errors.) The LEADERSHIP & MANAGEMENT RESET Episode 9- Podcast How to Hold Your Team Accountable with Sharon Smith Let me start with something that might feel familiar. You've delegated something you've explained what needs to happen or at least you think you've done so as clearly as you could at the time. And then things go a little bit quiet you're not hearing anything from the person you delegated to.

And you can't see things moving forward. So you start wondering, has it been done? Are they perhaps stuck? Maybe they've just got too much workload and they haven't started yet?

Has it slipped down that priority list like you're thinking it may have? So what do you do? You may be checking you drop a quick email saying hey just checking in on this. Or maybe you don't because you don't want to come across as hovering or as micromanaging.

And over time it often goes one of two ways. You either find yourself following up more and more because you're becoming increasingly anxious about what's happening. Or you end up picking it up and doing it yourself. And neither option feels good for you.

Let's face it. You've got your own workload. You don't need to be chasing. You don't need to be doing.

One of them faces feels like it's micromanaging which you don't want to be doing you don't want to be known as the manager who micromanagers and the other can feel like you're carrying more than you should. You have got plenty to be getting on with. And that just gets really draining over time. So today, I want to explore a slightly different way of approaching accountability.

One that helps create clarity without needing to constantly chase or step in. So let's get started. Let's start by gently reframing what accountability means because it's something that can be interpreted in a lot of ways. As often associated with control or checking in frequently.

But it doesn't necessarily have to look like that. One helpful way to think about accountability is that ownership becomes visible. In other words, it's not just that something has been delegated. It's that you can see progress happening along the way.

Now that might look like someone following through in what they said they do. Or sharing updates before something becomes an issue. Not after the fact, but early enough for you to make any adjustments that you need around by support or timelines or whatever that might be. Or that person taking responsibility without needing a reminder, which is really you know that's a cherry on the cake, isn't it?

And here's a subtle chef that can make a difference. Delegating something clearly doesn't always guarantee accountability. And it's really worth remembering that you can delegate something to a tip member of your team. That doesn't always mean that they are going to take ownership and accountability of it.

But when progress is visible, when you know what's happening, it becomes much easier for you as a line manager to trust that things are moving forward. And when that visibility isn't there. That's often where the uncertainty starts to creep in. From your point of view as the line manager, not knowing what's happening not knowing if there's momentum going forward.

And perhaps also from the team member you've delegated to because they're perhaps not sure what it is really that you're after. And so are sitting on it. Rather than asking for further support or making a start. So when accountability starts to to drift, it's not where you want things to be.

But often that doesn't show up in obvious ways. That drift can be more gradual. So for example, deadlines might get pushed back so we've got we've got project creep there where things happen and and. Where our team member might say I'm not quite there yet so you push back the deadline a little bit.

Something might come back, not quite finished, so you might ask for an update and something that's meant to be done not quite finished. And updates might become less frequent or they might even stop altogether. That quietness can be and perhaps should be an early signal for you as a lead manager. Because when your team member is really owning something, there's usually some level of communication around about it because they're keen to share with you their progress.

When that team member isn't communicating with you. When it starts to fade and go quiet. That's when things start to feel unclear. And you start to feel and manager that things are happening.

So you then naturally might start to think about it more. Okay? You follow up a little bit more. You're holding it in your head a little bit more and all of a sudden it becomes extra baggage that's not used to hold because you've delegated it.

And so that responsibility is starting to drift back towards you, okay? Simply because you're not fully confident that it's being handled properly. And that's where it become can become a bit of a cycle. The more you step in, the less space that is for someone to fully own it.

Now, I love a one to one. I love the role of a one to one and I think one to ones are crucial for any line manager to ensure that people have clarity on what they've been delegated. And know that they have your support. When they are struggling.

So when we're thinking about improving our team members accountability. Rather than checking in more often. Or staying closer to the work by observing you know going into files seeing if there's been progress done. Sometimes it's less about having those.

Random touch points and more about having a structure in place. And that's where I come back to one to ones. I think they are one of the most useful and sometimes underused tools for. Team managers and for leaders.

A one to one. Rather than being about. One to one's become a consistent space where accountability naturally says. So instead of updates happening randomly throughout the week, there's a shared understanding.

This is when I come prepared to give my update. And the questions #ah that the Lane manager might ask don't need to be complicated. They can be things like okay so what progress has happened since we last spoke? What's on track?

What might we be at risk of dropping here? Where would support help? So instead of the team member reacting to check-ins, those random ones that you've been doing up till that point the person is coming ready to share. So over time that consistency that regular one to one can encourage more forward thinking.

More preparation. And a stronger sense of ownership. Which often means less chasing overall for you. I know a lot of leaders really don't like doing one to one's because they feel it's time out of their diaries it's time out of their own workspace.

It's time. They sometimes feel like it's in fact time for micromanaging and it's not. What it is is time for support, but it's also time for team accountability. You're not going into one to one with a big stick shaking it at your team member.

You're actually watering your team member. Think of it as your weekly watering or your monthly watering or however regular you do your one to ones. Think of it as the time that you water. And support and feed that member of your team just as you would a plant.

You are asking your team member. What help they need? How is it going? What it's looking like?

You might even do some coaching conversations and ask them what they would do differently or what they're learning from this or what they would do next. So really encourage and have these one to ones as regularly as possible, so that you are satisfied as a line manager, that you have, um, knowledge of what's happening, knowledge about your team members' clarity, knowledge about the pace and direction of the work. But it's also an opportunity for you to build a trusting relationship with your team member.

And also for them to grow. Another great way to develop team accountability is to reinforce what's working. It's something that can be easily overlooked as a leader. That acknowledging when accountability is already happening.

So it's really easy to focus on what's not working because you know we are highly um aware of when things aren't going well. But that's only part of the picture of the work that your team do. When you notice someone taking ownership when they take responsibility when they are proactive. Even in small tiny ways.

It can really help to call it out. It doesn't need to be over the top. But it might sound something like I've noticed you flagged that early that was really helpful. Thank you.

Or I appreciated the update before it became an issue. Thank you. Or I saw how you followed that through. That was great.

Thanks very much. Simple specific recognition. Because over time, what gets noticed tends to become more consistent. And that helps shape what good looks like across the team.

But of course, there are times when ownership isn't there. It's just not showing up in a way that you'd hoped for if you've set your expectations and your standards for your team and how you want to work. And it's not being addressed. By one member or more of your team, they are not taking ownership.

Then this can become really difficult for you as a line manager to address it. It can be tempting to wait and see if things improve. Or to hint. At it indirectly, but often what helps most is being clear and I've spoken about clarity.

before and often. But being clear while staying calm and constructive. And if you're wanting some support and having difficult conversations, then please listen to episode 7 of this podcast where I've taught that through. But if you were, wanting to approach a member of staff who is not being accountable.

And doing that in a can we, you might want to see something along the lines of, I've noticed a few deadlines have slipped, and I'm not always seeing updates out of time. Can we talk about how to make progress more visible going forward? Now that keeps the tone open, but it still brings clarity to what's happening. It's very clear what you as a line manager have noticed.

It's very clear that the expectations and time frames are not being met. And that clarity are those that clarity that you've observes are facts. And you need to have a conversation about how to shift that. No, and one to ones if you're having them that would be part of your ongoing conversation and actually if you're having regular one to ones then accountability should be in place already.

But if one to ones are not in place and you are noticing things have slipped, then you have to dress it sooner rather than later, because the longer you leave it, the more likely you are going to have to pick up the work yourself. Because the progress has fallen so far behind that now needs emergency all hands on deck approach. And you've actually not dealt with the behaviours of your team member. Setting and holding the standard of your expectations for the people who are in your team and how we you all should work is really important.

Normally over time every team develops a sense of what's expected. whether you've actually clearly stated that or not as a line manager. And when those expectations are consistent, people will respond to those expectations. They do so differently.

Someone actually step up and some many a bit more support and actually that are those that will take much longer to adjust. But part of leadership is making that standard visible. Now that's not in a forceful way, but it's in a clear and steady way. Where everyone understands what good looks like here what good service looks like here if you're got if you have outer facing clients.

What good standard of recording looks like here, what good standard of communication and email correspondence looks like here. What good standard of response rate to something looks like here? Because when you don't have that clarity. Then different levels of effort and ownership are then undertaken by your team.

And that's where frustration can start to build. Because there's no equity of effort. So as far as you're concerned as a leader, that's something you want to avoid completely. You want your team to be all working, happily, all working very hard, being productive, being forward thinking and all taking ownership and responsibility for what's been delegated to them.

And for that to happen, it is really important that you set good standards and you hold them. And you hold them because you are having regular conversations about what work looks like through one to one's. So I should reflect on this a useful place to start might be. Where in your team does accountability feel a little unclear right now?

So who's not stepping up? Who's not sharing updates? Who is not holding the standard that you've set? And then what's one small shift that you could do tomorrow?

That could help your team member make their ownership their responsibility more visible to you. Now, what do I mean by that? Simple terms. How can they share their progress with you easily so that you are satisfied that they are taking their role and the work that's delegated to them seriously and that they're moving it forward?

Often, it's not about using a manager doing more, but it's about you doing things differently. You need to create that space that allows the conversations about clarity. For your team about where they are, what they're doing, how they're doing it. At the pace that they're doing it and having those conversations consistently.

So that it, the expectations there, the team member is on top of the work they're feeding back to you regularly. And you're not having to do those random chasing. Wondering to yourself. Are they on it or are they not?

And when you are consistent in your practice. And remember, this is not micro management. This is organisational focus when you're consistent in your systems and how you expect your team to deliver to you. By feeding back to you in regular one to ones.

Time frame dependent, obviously on the project and the urgency of the work. Then things will start to fall into place and you will be more knowledgable about what's happening. And you will be camera and you will feel your role later because you are not overthinking things. You're chasing less you're carrying less and there's more of a shared sense of responsibility across your team.

Because through your one to ones as well, they know you have their back. Because every time you're asking them. What can you do to help or support them? So if this resonated, you might share it with someone who else who's navigating similar challenges.

And I'll see you in the next episode. Have a good one.

Related episodes across the Index

Other episodes covering the same guests and topics, from across The B2B Podcast Index.

  • 173 - How to have a difficult conversationYour Business Hour · on difficult conversations80 / 100
  • Emotional intelligence in customer success with Jenelle FridayCS School · on difficult conversations78 / 100
  • How to manage the priorities between the executive team and the investorThe Private Equity Podcast, by Raw Selection · on difficult conversations72 / 100
  • Leadership Is a Contact Sport: How to Stop Avoiding the Tough StuffThe Visible Leader · on One-to-one meetings62 / 100
  • 175 | Setting Expectations That Remove Confusion (and Reduce Your Stress by 70%)Women of Faith in Leadership · on difficult conversations61 / 100
  • Why Do Leaders Avoid the Conversations That Would Actually Fix Everything? | Neuroscience in LeadershipAI Cafe Conversations · on difficult conversations59 / 100

More from Leadership & Management Reset Podcast

All episodes →
  • How to Run Better Meetings That Actually Lead Somewhere - Episode 1048 / 100
  • Leadership Overwhelm Explained - Episode 840 / 100
  • Why Leaders Avoid Difficult Conversations - Episode 750 / 100
  • Episode 6: What is Self-Leadership? A Practical Guide for Overwhelmed Leaders47 / 100
  • Episode 5: Nice vs Kind Leadership: Why Being "Nice" Can Undermine Your Team49 / 100
Explore the best B2B Leadership podcasts →
All Leadership & Management Reset Podcast episodes →