The hiring’s underway and the team’s grown, but you’re now in the bit no one talks about on the funding call. The part where your new joiners are wondering what “Level 3” actually means, your first-time managers are winging it through 1:1s, and your spreadsheet-based pay review is not quite holding up under pressure.
This is where the ‘people’ questions start piling up.
How do we structure progression when half the company joined in the last six months? Are our pay bands still fair, and are they defensible? What are we doing for managers beyond hoping they figure it out? And how are we making any of this work for a hybrid team we only half see in person?
It’s the messy middle. The levelling frameworks, the pay clarity, the manager support systems, and the kind of employee experience that keeps people engaged when no one’s physically in the same room.
We’ve seen what works and where it quietly breaks.
Levelling frameworks: the foundation most companies delay too long
Almost every scaling company we work with hits this point. Titles get messy. Promotions start to feel a bit improvised. People are asking what it takes to move up, and you realise the answer is different depending on who’s asking and who’s answering.
That’s when you need a proper levelling framework.
This helps create a shared language for how roles work, what growth looks like, and how decisions get made, especially when you’re hiring at pace or merging teams that joined under different assumptions.
What goes into a levelling framework?
Here’s a stripped-back example of how levelling can work in practice. The real version might be dozens of roles across different tracks, but even a simple model like this helps managers and employees speak the same language:
| Level | Role expectations | Signals for progression |
| Level 3 (IC) | Executes defined tasks, collaborates closely with others, asks for guidance often | Independently owns small projects, demonstrates consistent delivery |
| Level 5 (Senior IC) | Leads projects end-to-end, mentors juniors, trusted with complex delivery | Recognised as a domain expert, shapes technical/product direction |
| Level 6 (Manager) | Leads a team, balances delivery and people management, supports career growth | Builds team capability, delivers through others, influences org outcomes |
This is key because if no one knows what “Senior” means, or how it differs from “Lead,” or why two people with the same title are paid differently, things start to unravel; trust, motivation, comp reviews, all of it.
We’ve helped companies like Shiftmov re-level 200+ employees after years of ambiguity. It wasn’t easy, but it was one of the most valuable things they could’ve done at that stage. Not just because it made progression fairer and pay more structured, but because it gave their managers something solid to work from. No more guessing.
If you’re scaling and you don’t have a levelling framework, it’s probably costing you more than you think. In inconsistent offers. In retention risks. In internal tension no one’s quite able to name yet.
And if you’ve got something that’s half-finished or inherited from a previous team? That’s common. It’s also fixable.
The real work is aligning what people do with what the business needs, then giving it enough structure that everyone can actually use it.
Up next: what happens when levelling meets pay.
Rethinking pay: flexible, fair, and under a microscope
Once you’ve got a levelling framework, the next question is almost always pay. Who’s ‘in band’? Who’s ‘out of band’? Are we still competitive? Are we fair? Are we ready to explain it?
And yes, the EU Pay Transparency Directive is looming (2026 isn’t that far away). But even if you’re not legally on the hook yet, you’re going to feel the pressure because candidates will be asking, employees will be comparing and as for investors? They might be the ones who care far more than you expect.
What we’re seeing now (and what we’re helping clients build) is a move away from the “just trust us” approach. That doesn’t fly when you’re 100+ people with funding rounds behind you. Teams want to understand how decisions get made. Not down to the last pound, necessarily, but enough to know it’s not arbitrary.
This might include structured pay reviews that map to levelling, transparent salary bands that actually match your hiring market, and flexibility to adapt across countries, currencies, and stages, without losing the signal that your process is thought-through and fair.
(And yes, that means deciding whether London and Lyon are the same band. Hint: They’re probably not.)
The strongest pay strategies are structured. At scale, pay needs to be explainable, consistent, and connected to how the business operates. Here’s what that looks like when it’s working:
What scaling companies need from a modern pay strategy
| Pay system element | Why it matters at scale |
| 📊Pay bands aligned to levels | Helps managers and employees understand where they sit and what’s next |
| ✅ Clear review process | Avoids ad hoc or inconsistent decisions, especially as team size grows |
| 📄 Flexible frameworks by geography | Supports fairness without pretending £1 in London = £1 in Lyon |
| 💰 Equity and bonus clarity | Candidates and employees want to know how variable comp is earned, not just offered |
| 📩 Documentation and communication | You don’t need to publicise everything, but you do need to be able to explain it |
This touches everything, including hiring decisions, internal mobility, retention, and even leadership credibility. If your pay system doesn’t make sense internally, it won’t stand up to external scrutiny.
And when that scrutiny comes (which it will), it helps to have your house in order already.
Manager development: the quiet scaling bottleneck
The fastest way to frustrate a team? Promote someone into management and hope for the best.
Almost everyone’s done it. You’ve got a brilliant engineer, designer, or PM. They’re great at what they do. You’re growing fast, so you give them a team. And then… You sort of leave them to figure it out.
Which might make sense, at least on paper. You’ve got too much going on. There’s no time to build a manager training program. And besides, they’re smart. They’ll work it out.
Until they don’t.
What we see again and again, especially in Series A to C companies, is that unprepared managers quietly become one of the biggest blockers to team performance and retention. Not because they’re bad managers, but because no one’s actually shown them what good looks like. Not for your company. Not in your context. Not with your challenges.
They’re trying to coach, give feedback, run performance reviews, manage up, handle team dynamics, and maybe ship work at the same time. It’s a lot.
But instead of one-off training sessions or a handbook in Notion, you need to build real support systems:
- What does a good 1:1 look like here?
- What’s the process when someone’s struggling?
- Who helps them learn how to give hard feedback without breaking trust?
- How are they expected to manage career progression if there’s no structure behind it?
Most first-time managers often struggle because no one’s told them what’s expected, how to give feedback, or what to do when someone’s underperforming. These are fixable problems.
Support systems for new managers (that most companies delay too long)
| Area | What managers often lack | What scaling companies provide |
| Clear expectations | “What does good look like here?” | Defined role of a manager, success metrics, levelling clarity |
| Feedback structure | Ad hoc 1:1s, no idea how to deliver feedback | Feedback frameworks, training on how to give/receive well |
| Career conversations | Avoided, or handled inconsistently | Tools and prompts tied to levelling and growth pathways |
| Performance signals | Unsure how to identify or address underperformance | Structured calibration, documented behaviours per level |
| Peer learning / support | No one to talk to, isolation in hybrid teams | Manager roundtables, Slack channels, async enablement |
| Role transition coaching | IC to manager shift left mostly unacknowledged | Structured support for mindset and identity change |
The companies that get this right tend to think in terms of manager enablement. They give people the tools, the time, and the context to lead well, and they take it seriously because they know the cost of not doing it.
(And if you’re scaling, every new team = another first-time manager. This isn’t slowing down.)
Next up: how all of this plays out when your team isn’t in the same place anymore.
Employee experience in a hybrid world: where retention actually happens
Let’s be honest, “employee experience” used to mean snacks, socials, and maybe an onboarding checklist someone put together three roles ago. That doesn’t cut it anymore. Especially not when half your team is remote, a third are hybrid, and the rest are new enough that they’ve never even seen the office.
The companies we work with that retain well (even during awkward growth phases) tend to treat experience like an actual design challenge. Something you structure, test, and improve over time.
It starts early.
- Is your onboarding genuinely helpful, or just a sequence of meetings that leave people guessing what they’re supposed to do?
- Can someone see their progression path, or are they still asking “what’s next for me here?” six months in?
- Does feedback feel routine and useful, or rare and reactive?
- Is the culture actually felt beyond the leadership Slack channel?
The best companies build a hybrid culture around structure, visibility, and meaningful interactions. Here’s what that looks like:
| Where hybrid often breaks | What resilient companies build |
| Disjointed onboarding | Consistent, structured onboarding (remote + async ready) |
| No clear path for growth | Visible, documented progression frameworks |
| Performance reviews feel subjective | Level-based evaluation tied to real examples and feedback |
| New joiners feel disconnected | Built-in team intro loops, cross-functional connection points |
| Feedback only happens when things go wrong | Regular check-ins, supported by managers who’ve been enabled |
None of this is flashy. And to be honest, that’s the point. It’s the invisible stuff that makes people stay or quietly start replying to recruiters.
We’ve seen companies completely rethink this, tightening the feedback loops, setting clearer expectations, and giving managers the tools to support people properly (see previous section).
If you want a hybrid workplace to work long-term, the experience has to be consistent. Not identical, but coherent. People need to feel like they’re part of something, even if that something happens on Zoom.
What scaling companies do differently
They build the things most teams put off, like levelling frameworks, structured pay, manager support, and real employee experience, before they’re technically urgent, because they’ve seen what happens when you don’t.
This is the work that quietly holds everything else together.
At Scede, we’ve helped dozens of teams build these people strategies. Sometimes from scratch, sometimes as a much-needed reset, but always with an eye on the real world: What needs to work now, and what needs to scale next.
If you’re at that point where ‘people’ questions are starting to pile up, or you want to get ahead of them, our advisory team can help.
We’ll meet you where you are. And we’ll build what works.
From levelling frameworks to manager enablement, Scede People helps you scale with clarity, fairness, and real structure.
Want more insights on scaling your talent acquisition? Follow Scede on LinkedIn for strategies that actually work.