Practical guideBy Andrew Nelson8 min read

Organisational Change: Design Behaviour, Not Just Attitudes

Communication matters, but change becomes real when the environment makes the desired behaviour clear, practical and easier to repeat.

Published Updated

Executive Takeaways

  • Awareness is not the same as action; people also need the tools, opportunity and feedback required to behave differently.
  • A change plan should identify the first observable behaviour and remove friction around performing it.
  • Communication, leadership signals and system design must reinforce one another — infrastructure alone is not enough.

The bottom line

Many change programs invest heavily in explaining why people should think differently, then leave the working environment largely unchanged. The result is familiar: employees can repeat the message, but the old behaviour remains faster, safer or more rewarded.

A more practical approach begins with behaviour. Define what people need to do differently, examine the conditions around that action and redesign the tools, defaults, cues and feedback that shape it. Attitudes still matter, but people are more likely to believe a change when the organisation makes the new behaviour possible and reinforces it consistently.

What kerbside recycling teaches about change

Recycling is a useful Australian illustration because it makes the system visible. Education is important, but a household also needs a collection service, a clearly identified bin, usable instructions and confidence about what happens next.

Current Australian and Victorian recycling guidance treats infrastructure, consistent visual cues, accessible information and feedback as connected elements. Sustainability Victoria’s behaviour research notes that systems should minimise sorting effort and use reliable visual signals. NSW environmental guidance similarly recognises that education must address physical, social and cultural influences, not only individual knowledge.

The lesson for organisational change is not that providing a bin automatically changes an attitude. It is that desired behaviour becomes more likely when the environment removes practical barriers and makes the next action obvious.

Start with the first observable behaviour

Change language is often too abstract to guide action. Leaders ask people to be more customer-centric, innovative, accountable or collaborative without defining what another person would observe if the change were happening.

Translate the ambition into a small number of behaviours attached to real moments. Customer-centricity might mean involving a customer before funding a concept. Accountability might mean every strategic initiative has one decision owner and a review date. Collaboration might mean a cross-functional risk review before a commitment becomes expensive to reverse.

The first observable behaviour creates a practical design problem. Leaders can now ask what information, authority, tool or incentive is missing when that moment occurs.

Run a friction audit

People often continue an old behaviour because the organisation has optimised for it over many years. Forms, approvals, metrics, meeting rhythms, software and job boundaries all contain instructions about what is normal.

A friction audit follows a person through the desired action and records every point at which the old path is easier. It should include practical friction, such as extra steps or missing access, and social friction, such as uncertainty about whether a manager will support the choice.

  • Is the desired action clear at the moment a choice is made?
  • Does the person have the information, authority and capability to act?
  • Which system default still points towards the old behaviour?
  • What competing target or incentive punishes the new behaviour?
  • How quickly does the person receive useful feedback?

Design tools, cues and defaults around the work

A tool can be physical, digital or procedural. It might be a decision template, a new meeting agenda, an automated prompt, a protected budget, a visible workflow or a short checklist used before approval.

The best tool does not add another layer of administration. It reduces ambiguity or effort at the precise point where the new behaviour is required. Consistent labels and cues matter because they become a source of truth under pressure, just as clear bin colours and signs support correct sorting.

Defaults are especially powerful. If every business case must begin with the non-customer problem, the organisation no longer relies on individuals remembering to add that perspective at the end. If evidence reviews are scheduled when a pilot is approved, learning becomes part of the process rather than an optional follow-up.

Use feedback to make progress believable

People need to see whether the new behaviour is producing a useful result. Feedback should therefore be close enough to the action to support learning and specific enough to guide the next attempt.

Avoid measuring only attendance, communications opened or training completed. These are implementation activities, not evidence of changed work. Track the behaviour itself and the outcome it is intended to influence.

  • How often was the new behaviour performed in the relevant situation?
  • Where did people revert to the old path, and what friction was present?
  • What customer, quality, speed or risk signal changed?
  • Which part of the design should be adjusted before wider rollout?

Communication still matters — but it must match the system

A behaviour-led approach is not an argument against communication. People deserve to understand the reason for a change, how decisions were made and what the organisation expects. Education can build capability and help people interpret unfamiliar situations.

The problem arises when the message and the system contradict one another. Leaders cannot ask for experimentation while punishing every failed test, or ask for cross-functional ownership while rewarding functions only for local targets.

Credibility comes from alignment: the message explains the choice, leaders model it, tools make it practical, incentives reinforce it and feedback helps the organisation learn.

A practical sequence for a change initiative

Change is more credible when people can experience a better way of working rather than merely hear about one. Start small enough to learn, but design the test around real organisational conditions so that the evidence can support a meaningful decision.

  • Name the business outcome and the two or three behaviours most likely to influence it.
  • Observe the current workflow before designing training or communications.
  • Identify friction, conflicting incentives and moments of uncertainty.
  • Prototype the smallest tool, cue or default that could support the new behaviour.
  • Test with a real team, measure behaviour and outcome signals, then adapt.
  • Scale the surrounding leadership, capability and system changes together.