People, Org & Change Management

Module 09

People, Org & Change Management

Org structure, incentives, culture, and the discipline of change. Most recommendations fail not because they're wrong but because people don't adopt them.

Here's the humbling fact that separates seasoned consultants from clever ones: most excellent recommendations fail — not because the analysis was wrong, but because the organisation didn't change its behaviour. People, incentives, and change are where strategy goes to live or die, and ignoring them is the fastest way to be right and useless.

Org structure shapes behaviour

How a company is organised — by function, by product, by region, or a matrix of these — quietly determines what gets prioritised, what falls between the cracks, and who fights whom. You don't need to redesign org charts, but you must read them: when a recommendation requires two departments that are measured on competing goals to cooperate, structure is the reason it'll stall. Often the real fix to a "strategy problem" is an organisational or ownership one — someone needs to actually own the outcome.

Incentives explain almost everything

"Show me the incentive and I'll show you the outcome." When people behave in ways that seem irrational, look at what they're actually rewarded for — bonuses, recognition, what gets you promoted, what gets you blamed. A sales team paid on volume will discount aggressively no matter how many times leadership says "protect margin." Before recommending that people behave differently, check whether the incentives even allow it; if not, the incentive is the thing to change, not the people.

Culture — the invisible operating system

Culture is "how things really work around here" — the unwritten norms that survive any poster on the wall. It's powerful because it persists without enforcement, and it eats strategy for breakfast: a brilliant plan that contradicts the culture loses. You can't change culture by announcement; it shifts through what leaders consistently reward, tolerate, and model. As a consultant, naming the cultural reality honestly ("the stated value is candour, but people who speak up get punished") is often more valuable than any framework.

Why change fails

Change initiatives fail in predictable ways: no real sense of urgency (people see no reason to leave the comfortable status quo), no clear vision of the after-state, under-communication (leaders explain once and assume it landed), and no early wins to build belief. People don't resist change because they're difficult; they resist because change is loss — of competence, status, routine, or certainty — and that fear is rational until it's addressed. Treating resistance as information ("what are they afraid of losing?") rather than obstruction is the unlock.

A simple, durable change approach

You don't need to memorise competing models — they rhyme. The reliable spine: establish why change is necessary now (urgency), paint a concrete picture of the after-state (vision), bring people along with relentless, two-way communication, remove the practical obstacles (tools, time, conflicting incentives), create early visible wins to convert skeptics, and embed the change so it survives once attention moves on. Most failed change skipped urgency or early wins.

Key takeaway

Analysis is the easy half. Recommendations live or die on structure, incentives, culture, and change. Before you propose what a company should do, ask whether its structure allows it, whether its incentives reward it, whether its culture will accept it, and how you'll bring people through the loss that change always is.

For Orelis & the app

This is the most common blind spot in AI-generated advice, and therefore your biggest opportunity. A tool that recommends a strategy without asking "will the incentives and culture actually allow this, and how would you roll it out?" is setting users up to fail. Building in an adoption/change lens — and surfacing the people-side risks of any recommendation — would make Orelis noticeably more grown-up than tools that stop at the clever idea.

Test yourself

Q1Leadership says 'protect margins,' but the sales team keeps discounting heavily. Before blaming the team, what do you check?
Show a worked answer
The incentives. If salespeople are paid and promoted on volume or revenue rather than margin, they're behaving rationally — discounting wins more deals, which is what they're rewarded for. The instruction contradicts the incentive, and incentives win. The fix isn't another memo; it's changing the comp plan to reward margin (or margin-aware revenue). Check what people are actually rewarded for before concluding they're being difficult.
Q2A flawless reorganisation plan is rejected by middle managers who 'just don't get it.' Reframe their resistance usefully.
Show a worked answer
Resistance is information, not obstruction. Those managers likely see a loss the plan ignores — of status, headcount, control, or hard-won expertise — and that fear is rational until addressed. Reframe: what specifically does each group stand to lose, and how does the plan acknowledge and cushion it? Often the plan is fine but the rollout skipped urgency, vision, and early wins. Engage the loss directly and much of the 'they don't get it' evaporates.
Q3Why is 'we announced the new strategy at the all-hands, so the change is done' a classic failure?
Show a worked answer
Because announcing is not adopting. One communication, treated as sufficient, ignores everything change actually requires: a felt sense of urgency, a concrete vision of the after-state, repeated two-way communication, removal of practical obstacles, and early wins that turn skeptics. Change is a loss people must be brought through, not a memo they receive. The announcement is the start of the work, not the end of it — and assuming otherwise is why most change initiatives quietly revert.