Developing the manager doesn't develop the whole team. What changes when every person gets a coach of their own, and why architectural privacy makes it work.
.png)
Every manager development program starts with the same premise. If we develop the manager, the team will get developed. The manager learns to coach, the team gets coached. The manager builds people, the people get built.
Then the manager goes back to their job, and the math falls apart.
A typical Functional Leader has eight direct reports. Each report wants a quarterly growth conversation. Each report has a weekly 1:1 on the calendar. Add the leader's own work, their own boss, the calibration meetings, the hiring loops, the cross-functional politics, the offsite that just got moved to Thursday.
Development conversations are the first thing that slips when the calendar runs hot. Every leader knows this. They feel guilty about it. The next week comes and the same calendar pressure produces the same outcome.
Giving that manager a coach of their own helps them lead better. It does not free a single hour on the calendar. They still have to be the development engine for the eight people who report to them, because in every model that exists today, development is something a manager does to a team.
That model is the problem.
What if every person on the team owned their own growth? Not "took initiative" in the abstract sense the engagement survey asks about. Owned it the way the manager has always been expected to own theirs.
That requires something most people on most teams don't have: a coach of their own. Someone who knows their goals, holds them accountable to the work between sessions, prepares them for the conversation with their manager before it happens.
The problem with that idea is that it has always cost too much. A human coach for every IC was math that never worked. So we kept giving coaches to the executive layer and asking the manager to be the development tier for everyone below.
That math has now changed.
A coach for the leader. A coach for every person they lead. Two tracks running in parallel.
The 1:1 changes first. Less manager downloading the agenda, less manager extracting the update. The IC walks in already clear on what they want from the meeting, what they're stuck on, what kind of help they need. The conversation becomes a decision conversation, not an information conversation.
The hard conversation gets prepped in advance, by both sides. The manager has worked through how to deliver the feedback. The IC has worked through what they want to ask for, what they're going to push back on, what they want to take away. Both come in ready. The conversation actually lands.
Development stops being something the manager does to the team. It becomes something the team owns, with the manager as the partner in higher-leverage moments, not the sole engine.
This frame only works under one condition. The IC has to be able to be honest with their coach about what's going on, including the friction with their manager.
If the coach is something the manager or HR can see into, it stops being a coach and becomes a surveillance layer. The IC self-censors, the conversations stay shallow, the development work stalls.
This is the structural reason "give every IC a coach" hasn't worked at scale before now. The technology existed. The privacy boundary didn't.
What we built into Huckleberry is the bright line: individual coaching sessions are architecturally inaccessible to managers, HR, and admins. There is no compliance API, no eDiscovery path, no admin override. HR sees engagement metrics across the org and broad org-wide themes. Nobody sees who said what to their coach.
That's what makes the IC willing to be honest with the coach, which is what makes the development work real.
Time is the obvious answer. The less obvious one is leverage.
When the team is doing real development work with their own coaches, the manager's 1:1s get better. The check-in is shorter. The decision-level conversations get longer. The work the manager actually needs to do, advocating for their people, removing roadblocks, calibrating cross-team, gets the calendar space it always needed.
And the manager gets signal. "I noticed Maria came into our 1:1 this week with a clear ask, with three options she'd already thought through." That observation is data. The team is doing the work. Development is happening, whether or not the calendar ran hot that week.
For the manager, the relief comes from finally having a team that's developing alongside them. Not waiting for them.
Why not just give the manager a coach?
Because the manager doesn't have time. Coaching only the manager keeps the development burden on them. They still have to coach every report themselves. Coaching the manager and every person they lead means the development work happens in parallel, not in 1:1s the manager doesn't have time for.
Does this replace 1:1s?
No. 1:1s change. With both coaches running, the IC arrives prepared, the manager arrives prepared, the conversation moves faster and goes deeper. The 1:1 becomes a higher-leverage meeting, not an extra one.
Does the manager see what their team is working on with the coach?
No. Individual coaching sessions are private by design. The manager sees only what the IC chooses to bring into the 1:1. HR sees engagement metrics across the org and broad org-wide themes, never individual session content. The privacy boundary is what makes the IC willing to use the coach for real work.
How long before this shows up in team performance?
The first signal is the 1:1 itself getting better, usually within a few weeks of both coaches running. Behavior change on the things that matter (feedback culture, the hard conversations happening, retention) shows up over a quarter or two as the development cadence compounds.
.png)
.png)