Abstract
Organisations can complete a system implementation or introduce a new operating model while familiar working practices continue. This article examines how everyday behaviour connects delivery activities to the business outcomes that justify transformation. Drawing on practitioner interpretation and research on technology-enabled change, behavioural conditions and information systems success, it considers why required actions, leadership expectations and operating arrangements need to be examined together. It also distinguishes behavioural adoption from evidence of realised value. The implication for executives and transformation leaders is to connect intended outcomes with observable practices and the conditions supporting them, then sustain attention beyond go-live.
organisational transformation; behaviour change; business value; operating model; leadership accountability; benefits realisation
When delivery is complete and the work still looks familiar
I’ve worked on enough transformation programmes over the years to know that organisations can become very good at implementing change without necessarily changing very much.
A new system goes live, an operating model is launched or responsibilities are reorganised. There will usually be a communications plan, training and a presentation explaining the future. The organisation has reached a visible milestone, often after considerable effort.
Then you return several months later and find familiar practices continuing. Spreadsheets sit alongside the new system. Teams have developed local variations of the agreed process. Decision rights have been documented, but difficult decisions still return to the same senior leader.
I think these observations deserve more attention than a general conclusion that people have failed to adopt the change. They raise questions about what the transformation was expected to achieve, the behaviours on which those outcomes depend and whether the organisation has made those behaviours workable.
The implementation is part of the investment’s purpose
When an organisation introduces an enterprise system, the technology can easily become the centre of the transformation. Progress is tracked through design, configuration, testing, training and go-live. These are necessary delivery activities, with identifiable outputs and completion points.
The reason for investing usually reaches further into the business. Leaders may want reliable information, clearer accountability, less duplication or better customer service. Those ambitions depend on what people do with the system and how the organisation uses the information it produces.
Markus (2004) examined technology-enabled organisational change and argued for integrating technical solutions with complementary organisational changes. Her analysis highlights the limitations of treating the technology as a completed solution to which organisational change is subsequently added. This provides a useful research foundation for examining implementation and working practices together.
An unreliable system still needs a technical response. A poorly designed process may need redesign. Attention to behaviour helps us understand how those conditions affect the work; it does not make technical quality or operational design less important.
The behavioural dependencies are often inside the business case
One question I find useful is: what will people actually need to do differently for the intended outcome to occur? I mean that quite literally. What will someone need to do differently on an ordinary Tuesday morning?
Consider a hypothetical organisation introducing a shared customer system to improve service across functions. A salesperson may need to record information that previously stayed in personal notes. A service team may need to consult that record before responding. Managers may need to use the shared information when allocating work and resolving problems.
Entering a record is therefore only one part of the change. Its usefulness depends on the information being relevant and reliable, other teams being able to access it, and the record influencing subsequent decisions. A system populated with information that nobody trusts or uses may satisfy an activity measure while leaving the intended benefit uncertain.
These examples are illustrative, rather than accounts of a particular client engagement. They show why a broad ambition such as “better visibility” needs to be connected to the actions and decisions through which visibility becomes useful.
Define the behaviour and the conditions together
Bringing the behavioural question forward helps make the design problem more precise. It gives leaders and delivery teams something concrete to examine alongside requirements, processes, information flows and decision arrangements.
It also requires attention to feasibility. A request for employees to maintain shared information raises questions about time, access, responsibilities, information quality and the other records they are expected to keep. Describing the desired action without examining these conditions leaves much of the design work unfinished.
The COM-B model describes behaviour through the interaction of capability, opportunity and motivation (Michie, van Stralen and West, 2011). It includes knowledge and skills, the surrounding physical and social conditions, and deliberate and automatic motivational processes. The model is a framework for examining behaviour, rather than proof of what is causing a particular organisational problem.
My application of that perspective is to define the required practice and investigate its conditions together. The behaviour clarifies what success would involve in everyday work. Examining the conditions helps establish whether the proposed operating arrangements can support it.
The current approach may still serve a purpose
When people continue using an old process, I would want to understand what it is doing for them before deciding how to respond. A workaround might compensate for missing functionality, bridge a dependency between teams or satisfy an expectation that the transformation has left in place.
In the hypothetical customer system example, a manager might continue requesting a separate spreadsheet every Friday. Maintaining both records would then be part of meeting the manager’s expectation. Repeating the instruction to use the shared system would leave that duplication unresolved.
Equally, the spreadsheet could contain information that the organisation genuinely needs and has not provided for elsewhere. Removing it without understanding that function could create another operational problem. Its continued use is a reason to investigate, rather than sufficient evidence of either resistance or a necessary exception.
What interests me is the relationship between the formal design and the arrangements people rely on to get work done. The explanation can sit across several teams, which makes the choice of response more demanding than a reminder to comply.
Leadership behaviour is part of the operating model
Leaders’ decisions belong in the same examination. Documented decision rights will have limited practical effect if leaders routinely take decisions back. Expectations of cross-functional collaboration can also compete with performance arrangements that reward each leader primarily for their own function’s results.
These tensions can arise through decisions that seem reasonable in isolation. A leader may request a familiar report because they trust it, or retain a decision because the consequences feel significant. The combined effect may be to keep the organisation dependent on arrangements it intended to change.
For me, this is a question of executive ownership. A programme team can identify conflicting expectations and recommend a response. It may lack the authority to change a functional performance measure, retire a reporting requirement or accept a different distribution of decision-making.
Those choices need to sit with leaders who can weigh their operational consequences. Asking employees to adopt a new approach while leaving such decisions unresolved transfers a conflict to people who may have little ability to resolve it.
Go-live begins a further period of learning
Go-live is a legitimate achievement. Reaching it can involve years of work and significant technical and operational risk. Behavioural preparation should already have been part of that work, but actual use provides further evidence about how the design functions under everyday demands.
Workarounds, recurring exceptions and repeated escalations can help reveal where the proposed way of working is difficult to sustain. They need to be interpreted carefully: some reflect a temporary learning period, while others expose a persistent design problem or an unresolved dependency.
I would want attention to those observations to continue beyond technical stabilisation. Otherwise, the organisation can close the programme while the business is still working out how to make the intended change function. Responsibility for those remaining decisions and for assessing the benefits needs to be clear.
Changed behaviour must connect to meaningful outcomes
Behavioural change provides evidence about how work is being performed. It still needs to be considered alongside whether the organisation is achieving the outcomes that justified the investment.
DeLone and McLean (2003) distinguish several dimensions of information systems success, including system use, user satisfaction and net benefits. They emphasise that measures must fit the context and that use and satisfaction cannot substitute for directly assessing benefits. Their work concerns information systems; it offers a relevant distinction for system-enabled transformation without establishing a universal test for every form of change.
In our illustrative organisation, more complete customer records would be worth examining alongside service outcomes and any additional burden on staff. The judgement requires attention to whose experience has improved, what costs or difficulties remain and whether other factors contributed to the result.
Bring the business outcome into everyday work
The implication is to connect the intended business outcome, the required working practices and the conditions around those practices from early in the transformation. That connection should remain visible through design, implementation and the assessment of results.
This requires judgement about interdependencies and trade-offs. A local improvement may create additional work elsewhere. A leadership decision may make a new process more credible or make it harder to sustain. Selecting a response calls for an understanding of the organisation that goes beyond the completion of individual deliverables.
The question I would keep returning to is what people are doing differently, under what conditions, and with what result. That is where the organisation can begin to judge whether its implementation is becoming the transformation it intended.
References
DeLone, W. H. and McLean, E. R. (2003). The DeLone and McLean Model of Information Systems Success: A Ten-Year Update. Journal of Management Information Systems, 19(4), 9–30. https://doi.org/10.1080/07421222.2003.11045748
Markus, M. L. (2004). Technochange management: Using IT to drive organizational change. Journal of Information Technology, 19(1), 4–20. https://doi.org/10.1057/palgrave.jit.2000002
Michie, S., van Stralen, M. M. and West, R. (2011). The behaviour change wheel: A new method for characterising and designing behaviour change interventions. Implementation Science, 6, article 42. https://doi.org/10.1186/1748-5908-6-42
Publication and disclosure notes
Adapted from Dr Liz Wilson’s article “Why Transformation Fails When We Focus on the Change Instead of the Behaviour”, originally published on thedrliz.com. https://thedrliz.com/why-transformation-fails-when-we-focus-on-the-change-instead-of-the-behaviour/
The customer system scenario and related organisational examples are hypothetical illustrations. They are not reported client cases or measurements of an intervention’s effectiveness.
The author is Founder & Editor of Transformation Expert Insights and works professionally in behavioural and organisational transformation.
AI assistance: OpenAI ChatGPT assisted with adapting the original article, restructuring the argument, drafting wording and identifying and checking references. The author is responsible for the published content.