Most Manager Development Fails Before It Scales. These Four Questions Will Tell You Why.

Author: Martyn Newman

Most organisations already know that manager behaviour matters. The harder question, and the one I rarely hear asked clearly enough, is whether any given approach will actually work beyond a small pilot, a senior cohort or a short burst of enthusiasm. That is where most decisions go wrong.

On paper, plenty of options look promising, whether framed as a manager development programme, a leadership initiative or something more specialised. In practice, the test is harder. Will managers use it? Can it reach the wider population? Will it hold up inside the organisation? And can it improve effectiveness without creating trust issues? Those are the questions that determine whether an investment in behaviour change delivers or quietly disappears.

1. Can it work beyond a small cohort?

This is the first test, and in my experience the most revealing. Many development approaches look effective when delivered to a contained group with high attention and strong sponsorship. The harder question is whether the same quality of support can reach the broader manager population without becoming heavy, inconsistent or too expensive to sustain.

This is where organisations often fall back on cascade: equip the senior group, then hope the effect spreads down through the management layer. Sometimes it does. It is rarely enough on its own. The pressures, behaviours and decisions that shape day-to-day execution sit much deeper in the organisation. Reaching that layer has historically meant more work, more coordination and more cost for CHRO and L&D teams.

If the answer still depends on a handful of facilitators, repeated workshops or a level of manual effort your team cannot maintain, the limits will show quickly. Real value comes when better behaviour spreads across the layer of management that shapes everyday execution, not when it stays contained within a well-supported minority.

2. Will managers actually use it?

Good intentions are not a delivery model. Managers are already under pressure, with limited time and competing demands. If support relies on spare capacity, perfect habits or sustained enthusiasm, adoption will be uneven. That is not a motivation problem. It means the approach does not fit real work closely enough.

The better question is whether it helps in the moments that actually matter: before a difficult conversation, during a period of change, when judgement is under pressure, or when a manager needs a practical prompt rather than another theory-heavy intervention. I have seen well-designed programmes fail at this test repeatedly. If support feels distant from day-to-day work, managers will find a reason not to use it, and they will not be wrong to do so.

3. Can you see progress without creating trust issues?

Development only works when people feel safe engaging with it. If support feels too close to monitoring, adoption drops and the whole proposition weakens. This is a tension I see in almost every serious rollout conversation: leaders and L&D teams need useful signals, whether support is being used, whether engagement is building, whether the investment is moving beyond activity into something more meaningful. But managers need to know that participation is not being used against them.

That balance is not impossible to achieve, but it requires clarity. You need enough visibility to lead well, and clear enough boundaries to protect trust. If an approach cannot explain where that line sits, it is not ready for serious deployment.

4. Will it deliver inside the organisation, not just on paper?

This is where good intentions meet operational reality. The question is not whether an idea sounds convincing in a proposal. It is whether it can be introduced cleanly, adopted consistently and turned into something that changes behaviour where it matters. Can managers use it without being taken out of the day job? Can CHRO and L&D teams roll it out without creating another layer of administration? Can it fit the organisation as it is, while still being robust enough to shift behaviour over time?

If an approach adds work, complexity or friction faster than it adds value, the impact will be limited. The real test is whether it fulfils its promise inside the organisation, not in a controlled pilot where every condition has been set up in its favour.

Why these questions matter.

They determine whether behaviour change will spread, hold and make a measurable difference, or remain one more initiative that looked better in the planning than in the doing.

This is precisely why the concept of a Behavioural Operating System matters. If you want better manager behaviour at scale, isolated interventions will not get you there. You need a practical way to assess, support, reinforce and track progress across the organisation without creating unnecessary complexity or eroding the trust that makes development possible. That is what OpenEQ was built to do.

These questions come from twenty years of working with organisations on behaviour change at scale. OpenEQ was built to answer all four in practice, not just in principle: psychometric assessment that identifies individual behavioural patterns, personalised coaching delivered across the full manager population, sustained reinforcement embedded in the flow of work, and progress tracking designed with trust as a non-negotiable.

Watch the demo and judge for yourself.