How managers can run structured accountability groups for their teams
When Google studied what separated its best managers from the rest in Project Oxygen, the behaviour that came out on top was not technical brilliance or vision — it was being a good coach, as David Garvin documented in Harvard Business Review in 2013. The practical problem is that most managers are told to "coach more" and given no structure for doing it. A weekly team accountability group is that structure: it turns coaching from a vague instruction into a rhythm you can actually run.
TL;DR
The highest-value development a manager can give a team is a coaching rhythm they run themselves, not an occasional external course. In practice that means a weekly accountability group: each person sets a short commitment, reports on last week's, and names a blocker, while the manager asks questions and clears obstacles rather than assigning work. It beats one-to-ones alone because it adds peer visibility and social commitment, which lift follow-through. The one trap that ruins it is mixing the group with appraisal — the instant people suspect an admitted stumble will surface in a rating, honest disclosure stops. Keep the development space and the formal review explicitly separate, and handle genuine performance concerns privately.
What does it mean for a manager to coach their team?
Coaching is not motivational speeches, and it is not doing the work for people. It is helping a team make its own progress visible and helping each person get unstuck.
The shift is from a manager who assigns and inspects to one who asks and removes obstacles. In a coaching posture you spend less time telling people what to do and more time asking what they are trying to achieve this week, what is in the way, and what would help. The team keeps ownership of the work; you own the conditions that let them do it well.
A manager-led accountability group is the simplest container for that posture. It gives the coaching a fixed home — one recurring session, a predictable shape — so it happens every week instead of only when someone is already in trouble. That regularity is the whole point, for the same reason a coaching rhythm beats a one-off training day: behaviour changes through repetition, not insight.
Why do accountability groups work better than one-to-ones alone?
Because a group adds something a one-to-one cannot: peers.
When someone commits to a specific action in front of colleagues they respect, the likelihood they follow through goes up. Not because anyone is policing them — because a quiet, healthy social accountability to peers is a stronger motivator than a private promise to the boss that no one else will ever check. The group also makes learning contagious: when one member describes how they unblocked a stalled piece of work, everyone in the room takes the lesson, not just the person who asked.
This does not make one-to-ones redundant. The private channel is where the sensitive, the personal, and the difficult belong — career worries, feedback that would sting in public, anything genuinely confidential. The right structure is both: the group for weekly momentum on shared and individual goals, the one-to-one for depth. A manager who runs only one-to-ones is doing coaching in a format that quietly caps how much accountability and peer learning the team can generate.
How do you keep coaching separate from appraisal?
This is the trap that kills manager-led groups, and it is worth being blunt about.
The accountability group only works if people are honest about what did not go well. The moment a team member suspects that admitting "I didn't get to this, I was stuck" will resurface in a performance rating, they stop admitting it. The group turns into a weekly performance of everything going fine, which is worse than useless — it hides exactly the problems coaching exists to surface.
So the rule, stated out loud and then held: the group is a development space, and nothing said in it feeds a rating. Here is the opinion, and it is not a soft one — a manager who cannot resist quietly banking group disclosures as appraisal evidence should not run the group at all, because they will get compliant theatre and mistake it for a healthy team. Keep the formal review on its own cadence and in its own conversation. If a real performance concern emerges, deal with it privately in the one-to-one, using the public-praise, private-correction rule that governs any group a manager runs.
What does a manager-run accountability group look like week to week?
Take Rebecca Ansah, who leads a nine-person customer support team at a SaaS company in Bristol. Her people were competent and busy, but development happened only at the annual review, and improvement goals set in January were forgotten by March. She started a weekly accountability group inside one private space.
The rhythm is deliberately small:
- One commitment each. Every Monday, each person posts a single development or improvement commitment for the week — not their whole workload, one thing they want to move.
- A Friday check-in. A short structured check-in with three fixed prompts: did you move it, what got in the way, what do you need. Ninety seconds to answer.
- A private individual goal. Each person also holds a longer-arc goal — a skill they are building over the quarter — visible only to them and Rebecca, so personal development isn't performed for the group.
- Rebecca coaches, she doesn't grade. Her replies are questions and offers of help, never scores. When someone is blocked, her job is to clear it or connect them to whoever can.
In Bitir this runs as one private group for the team, a recurring weekly check-in for the Friday rhythm, and per-member goals visible only to the member and Rebecca — so the shared momentum is public within the team while individual development stays private. After a quarter, Rebecca's read was simple: the commitments people had been forgetting between annual reviews were now moving weekly, and two members had raised blockers in the group that she would never have heard about until something broke.
The managers we work with often put it like this: "I didn't need another framework. I needed a reason for my team to say out loud, every week, what they were actually working on and where they were stuck." That is what the rhythm buys.
Questions we're asked about manager-led coaching groups
How big should a manager's accountability group be?
The same range that works for coaching generally: roughly five to nine people. Below five and there is too little peer variety; above nine or ten and the weekly check-in gets too long for everyone to be seen. A larger team is better split into two groups than run as one silent feed — the same size logic we set out in the group size guide.
How often should the group meet or check in?
Weekly is the default for most teams — frequent enough to build momentum, rare enough not to become noise. The check-in can be asynchronous rather than a live meeting: members post their commitment and Friday update in their own time, and the manager responds across the day. What matters is that it is every week, at a predictable time.
What if a team member won't engage with the group?
Treat it as a coaching signal, handled privately. A member who stays silent is usually either unclear on the point of the group, uncomfortable being visible, or quietly disengaged — and the place to find out which is a one-to-one, not a public nudge. Fix the cause in private; never call out non-participation in front of the group, which only confirms the fear that the group is being used to judge them.
How does Bitir support a manager-led accountability group?
Bitir gives the manager one private group for the team, a recurring weekly check-in for the commitment-and-review rhythm, and individual goals visible only to each member and the manager. Shared momentum stays visible within the team while personal development stays private, and the whole quarter is captured — so the manager can see the pattern rather than reconstructing it from memory at review time.
Coach your team on a rhythm, not once a year
Run one private group, a weekly check-in for commitments and blockers, and private per-member goals — so development happens every week and you can see it.
Start Your Group