Performance Management: What Actually Works at Scale-Up
- Blog@M923

- 13 hours ago
- 3 min read
Performance management is one of the most consistently avoided topics in fast-growing tech businesses. Founders who are brilliant at product thinking and development often find people performance conversations uncomfortable, time-consuming, or — at the early stage — seemingly unnecessary when everyone is rowing in the same direction.
When the team workforce strength rises to fifteen, twenty, thirty people. Expectations that were once implicit become invisible. Standards that the founding team held naturally start to drift. And suddenly, performance management isn't uncomfortable — it's urgent.
Here's what actually works for tech scale-ups trying to build performance systems that scale without killing the culture that got them there.
The Core Problem: 'Informal' Works Until it Doesn't
Most tech scale-ups manage performance informally in the early stage — and rightly so. When you're a team of five or eight, alignment is visible and feedback is constant. The founder knows what everyone is working on, calibrates expectations in real time, and addresses issues quickly because the team is small enough to make that possible.
The moment that finely balanced performance equilibrium breaks, is different for every business, but it's almost always tied to a specific headcount threshold — typically somewhere between five and twenty people. At that point, the founder can no longer directly observe everyone's output or manage their input. Middle management emerges, sometimes formally, often not. And the informal performance system that worked brilliantly at four people starts producing inconsistency, unspoken frustration, and — if left unaddressed — exits. Or at best, a gradual but seismic organisational implosion.
What a Functional Performance Framework Looks Like

The most effective performance management models and systems in tech scale-ups, share a few consistent characteristics. They're simple enough that managers actually use them. They're connected to business goals so that individual performance has visible organisational meaning. And they separate development conversations from rating or reward conversations — because mixing the two kills honest dialogue.
A practical framework for a tech scale-up typically includes quarterly and or yearly objective-setting tied to OKRs or team priorities, depending on product-to-market maturity and product development iteration stage. A lightweight monthly one-to-one structure focused on progress and blockers, and a more formal bi-annual conversation that addresses development and, where relevant, pay. The probation review — increasingly critical under the Employment Rights Act 2025 — should be a genuine structured assessment, not a rubber stamp.
Performance Management - The Manager Problem
The most critical path of performance management fails in tech scale-ups isn't the framework — it's that managers have never been taught to have the conversations the framework requires.
Technical leads promoted into management roles, early employees given reports because of tenure rather than people skills, and founders who delegate performance responsibility without equipping the people they're delegating to — these are the failure points. A performance framework without manager capability is a document that lives in a Google Drive folder.
Investing in manager training — specifically in how to give clear, constructive feedback, how to have difficult performance conversations, and how to document concerns appropriately — is not a luxury at scale-up stage. From January 2027, when unfair dismissal protections strengthen significantly, it becomes a legal necessity. (Read ERA - What Tech Scale ups must do)
Practical Starting Points
• Implement a structured quarterly / annual OKR or goal-setting process — even a lightweight one creates shared reference points
• Build a simple one-to-one template that managers use consistently — questions, progress, blockers, development
• Separate the development conversation from the pay conversation — they serve different purposes and conflating them limits honesty
• Make probation reviews a genuine process with mid-point and end-point assessments, documented outcomes and clear expectations
• Train managers in feedback and performance conversation skills before they need them in a high-stakes situation
• Address underperformance early — the longer it runs undocumented and unaddressed, the narrower the options become.
Performance management done well isn't bureaucracy — it's how fast-growing teams maintain clarity, fairness and the cultural standards that attracted good people in the first place. Getting it right at scale-up stage is significantly easier than trying to retrofit it once the problems are already embedded.




Comments