Your managers account for 70% of team engagement. Most of them have never been told what good looks like.

Gallup's State of the Global Workplace 2025 found manager engagement has dropped to 27%. The lowest level in a decade, down from 30%. And Gallup's research on team performance puts managers at 70% of the variance in team engagement.

Translation: the people most responsible for your team's performance are also the most disengaged group in your company. They're flying the plane while losing altitude. And in most scale-ups, they're doing it without a flight manual.

A real manager competency framework is the manual. Not an HR document that lives in a PDF nobody reads. An operating model that defines what good management looks like at your company, who's where on the curve, and what they need to develop next.

This is how to build one that scales.

‍

What a Manager Competency Framework Actually Does

The phrase "competency framework" carries a lot of HR baggage. Most managers hear it and picture a 47-page document with five-point rubrics and behavioural anchors that nobody references after week two.

That's not the framework. That's a binder.

A useful manager competency framework does four things:

1. It names what good actually looks like, in behaviours a manager can perform on a Tuesday. Not "drives alignment." Something a person could be observed doing or not doing.
2. It locates every manager on the curve. Not a pass/fail. A specific position on each competency, so development can start from where someone actually is rather than where the org chart says they should be.
3. It gives feedback a shared vocabulary. "Be more strategic" is unactionable. "Your delegation is at Level 2, here's what Level 3 looks like" is a plan.
4. It tells you what to buy. Training budgets get spent on whatever vendor pitched most recently. A framework tells you which competency is weakest across your manager population and lets you buy for that gap specifically.

In practice, the framework is the connective tissue between three things that usually live in silos: performance reviews, learning and development, and the manager's own career trajectory. When it works, all three start pulling in the same direction.

This blog sits inside our broader guide to new manager training for HR leaders, which covers the full program design.

‍

Why Generic Frameworks Don't Work for Tech Scale-Ups

The most common mistake we see in Series B+ companies is buying a generic competency framework off the shelf and force-fitting it to the org.

Korn Ferry, DDI, and Center for Creative Leadership all sell versions of this. They're not bad. They're just designed for organizations that don't move at startup speed. The competencies they list, "fosters cross-functional collaboration," "drives strategic alignment," "champions change," are accurate but useless. They describe outcomes, not behaviours. They don't tell a 28-year-old first-time engineering manager what to actually do on Tuesday.

Tech scale-ups need something different. Four things change:

• Speed of the transition. Enterprise managers get two years and a training program before they own a team. Your engineering manager got promoted on a Friday and had four direct reports on Monday. The framework has to be learnable in weeks, not absorbed over years.
• The IC gravity problem. At a scale-up, the manager is usually still the best individual contributor on the team, and the work is still on fire. Generic frameworks assume the manager has stopped doing the work. Yours hasn't. The framework has to name that tension directly.
• Decision velocity over process compliance. Enterprise competencies reward managers who follow the process. Scale-up competencies have to reward managers who make good calls fast, with incomplete information, and own the outcome.
• Fewer competencies, held tighter. Fifteen competencies is a binder. Six is a framework a manager can actually hold in their head while running a 1:1.

That's why we build manager competency frameworks from a specific set of six core competencies tuned for tech scale-ups, not 15 borrowed ones tuned for everywhere.

‍

The Six Core Competencies for Tech Scale-Up Managers

These six show up consistently across five years of Team Dynamics Assessment data: 78 organizations, 900+ respondents. Teams with managers strong on all six outperform on retention, velocity, and engagement. Teams with managers weak on more than two consistently struggle, regardless of IC talent on the team.

‍

1. Psychological Safety as a Practiced Skill

This is the foundation. Without it, the other five competencies don't compound. A team that doesn't speak up doesn't develop, doesn't surface risks early, and doesn't innovate.

What it looks like in practice:

• They say "I don't know" in front of the team. Regularly, and without flinching. The manager's own fallibility is what makes everyone else's admissible.
• They respond to bad news with curiosity instead of consequence. When someone brings a problem early, the first reaction is questions, not blame. Managers who punish early warnings stop receiving them.
• They actively solicit dissent. "What am I missing here?" asked in a way that produces real answers, not polite silence.
• They close the loop. When someone speaks up and it changes a decision, the manager names it out loud. Nothing builds safety faster than visible evidence that speaking up worked.

Most first-time managers think safety is a personality trait. It's a practiced skill with specific behaviours. The framework names the behaviours so managers can practice them. Our full guide to psychological safety at work covers the mechanics.

‍

2. Feedback Fluency

The single highest-impact skill in management is the ability to give clear, specific, behaviour-based feedback in real time. And to receive it the same way. Most managers are weak here for two reasons. They were rarely given good feedback themselves, and they're terrified of damaging the relationship.

A competent manager:

• Gives feedback within 48 hours of the behaviour, not at the quarterly review. Feedback decays. A specific moment discussed on Thursday is coachable. The same moment raised eleven weeks later is an ambush.
• Uses Situation, Behaviour, Impact instead of character judgment. "You're not detail-oriented" is a verdict. "In the deck yesterday, three of the revenue figures didn't match the model, and the client caught it before we did" is a conversation.
• Separates the coaching conversation from the evaluation conversation. People can't learn and defend themselves at the same time.
• Asks for feedback on themselves and visibly acts on one piece of it. The fastest way to make feedback normal is to receive it publicly.

If your managers are saving feedback for quarterly reviews, you don't have feedback. You have an HR ritual. Use the SBI model as the framework default and train the muscle.

‍

3. Delegation and the Empowerment Spectrum

The Empowerment Spectrum runs from Controlled to Managed to Coached to Empowered. A great manager moves their team rightward over time, consciously. Every direct report should be moving from Controlled toward Empowered on at least one dimension every quarter.

What this looks like:

• Controlled. The manager decides, the report executes. Correct for a brand-new hire on a high-stakes task. Wrong as a permanent state.
• Managed. The report proposes, the manager approves. The training-wheels stage.
• Coached. The report decides, the manager asks questions before and debriefs after. This is where most development actually happens.
• Empowered. The report owns it outright. The manager finds out at the readout.

The competency is knowing which mode each person is in on each dimension, and deliberately moving them one notch. Managers who hold everyone at Controlled aren't cautious. They're the bottleneck. Our guide to delegating without losing your standards covers the handoff mechanics.

If your managers are working more hours every quarter, they're failing this competency. Output that requires founder-level energy doesn't scale.

‍

4. Coaching Over Solving

The shift from IC to manager is the shift from "I know the answer" to "I help my team find the answer." Most new managers get this intellectually and fail at it tactically.

The competency:

• They ask before they tell. The instinct to solve is the strongest instinct a promoted IC has. Resisting it for even thirty seconds is the whole skill.
• They let people be wrong in ways that aren't expensive. A report who makes a recoverable mistake learns more than one who was rescued. The judgment is in knowing which mistakes are recoverable.
• They coach the thinking, not the answer. "What are you optimizing for?" and "What would have to be true for the other option to win?" build a decision-maker. Handing over the answer builds a dependent.
• They know when to stop coaching and just decide. Coaching a person through a decision at 4pm on a Friday when production is down is not coaching. It's abdication.

A leading indicator of this competency is the ratio of statements to questions in a manager's 1:1s. Good managers ask roughly twice as many questions as they make statements. Struggling managers are the inverse.

‍

5. Operating Cadence Discipline

Tech scale-ups break when the meeting rhythm doesn't keep up with the team's complexity. A competent manager runs their team on a deliberate operating cadence: weekly 1:1s, weekly team meeting, monthly performance check-in, quarterly OKR review.

The framework specifies:

• Weekly 1:1s that don't get cancelled. Rescheduled once is fine. Cancelled twice signals to the report exactly where they rank.
• A weekly team meeting that ends in decisions, not status. If nothing was decided, the meeting was a newsletter that took an hour.
• A monthly check-in on performance and growth, separate from the tactical 1:1. Different conversation, different cadence, different energy.
• A quarterly OKR review the team actually prepares for. Not a retroactive scorecard. A real look at whether the bets were right.

The specific format we use is in our accountability system for meetings. The cadence is what replaces founder-level coordination as the company scales. Managers who can't hold the cadence become the new bottleneck.

‍

6. Career and Growth Planning

The single most common reason high performers leave scale-ups isn't compensation. It's the absence of a credible career trajectory. The manager owns that conversation.

A competent manager:

• Knows what each report wants next, in their words, not the org chart's. And can say it out loud without checking notes.
• Runs a real career conversation quarterly, separate from performance. Annual is too slow. A senior engineer re-evaluates their trajectory roughly every quarter, and if you're not in that conversation, someone else's recruiter is.
• Creates stretch inside the current role. Most growth doesn't need a promotion. It needs a bigger problem.
• Advocates upward with specifics. A manager who can't make a concrete case for their report's promotion in two sentences hasn't been paying attention.

This is the competency that connects management to retention. It's also the one most managers underweight, because there's no Slack notification telling them to do it.

‍

The Manager Competency Assessment

The framework is only useful if you can measure where each manager actually is. We use a simple four-level rubric per competency.

Each manager is assessed twice, by self and by their manager, across all six competencies. The gap between self and manager scores is often more useful than the absolute scores. A manager who rates themselves Level 3 on feedback while their manager sees Level 1 has a feedback problem and a self-awareness problem at the same time.

Run the assessment quarterly. Don't tie it to performance review. The point is development, not judgment. The moment it becomes "this affects your bonus," people answer to score well instead of to learn.

‍

The Rollout Plan: 90 Days From Framework to Habit

Most companies fail at frameworks because they treat the launch like a software release. Big announcement, training session, then back to business. Frameworks need to be embedded, not launched.

This is the 90-day rollout that works:

Days 1 to 15. Adapt the framework to your company. Take the six competencies above. Add or modify based on your stage, geography, and culture. Get five senior managers in a room and pressure-test the rubric against three real people they manage. If the framework can't sort those three correctly, fix it.

Days 16 to 30. Pilot with one team. Pick the highest-impact manager (usually a director with 4 to 8 direct managers under them). Run the full assessment cycle once. Capture what worked, what was confusing, what got skipped. Iterate.

Days 31 to 60. Train all managers on the framework. A 90-minute session, not a half-day workshop. The session is split: 30 minutes on the framework itself, 60 minutes practicing the assessment on each other in pairs. Hands-on. No slides past the 30-minute mark.

Days 61 to 90. Run the first full assessment cycle. Every manager assessed by self and by their manager. 1:1 conversations specifically about the gaps. Every manager leaves with a development plan tied to specific competencies and specific actions over the next quarter.

The development plan is the artifact that determines whether this becomes culture or paperwork. If managers can't tell you in one sentence what they're working on this quarter and why, the rollout didn't take.

‍

How the Framework Drives Real Development

Once the framework is in place, three things compound that didn't before.

New manager onboarding gets faster. New managers know exactly what's expected and where they need to grow. The framework replaces "figure it out" with "here's what good looks like, and here's where you are today." Pair it with a structured first 90 days plan and the ramp compresses further.

Performance conversations get sharper. Instead of "be more strategic," managers receive feedback in the framework's language. "Your delegation is Level 2. Here are the three behaviours at Level 3. Pick one to practice this month."

Investment in middle management compounds. Training, coaching, and peer learning all anchor to the same framework. The company stops buying generic leadership training and starts buying targeted development for actual competency gaps.

The six competencies map to the foundational levels of the Six Levels of High-Performing Teams. Psychological safety is Level 1. Delegation is Level 2. Feedback fluency and operating cadence are Level 3. Get the manager layer right and the levels above start compounding on their own.

The framework isn't the goal. The goal is managers who develop on purpose instead of by accident. The framework is just the most reliable mechanism we've found for making that happen at scale.

‍

Conclusion

The companies that scale through the Series B to C transition without breaking culture are the ones that took middle management seriously. They built the operating manual, used it to assess where managers actually are, and built development plans that closed real gaps.

A competency framework won't fix a bad manager. But it will reveal them earlier, develop the good ones faster, and give your strongest people a real reason to stay and grow inside the company. That's worth the 90 days it takes to roll out.

Choose hard.

‍

‍

Frequently Asked Questions: