Right-Sized Change Management: Applying PRINCE2 and ADKAR Without Unnecessary Bureaucracy
Change management is often associated with large transformation programmes.
We picture programme boards, detailed project plans, extensive stakeholder maps, communication workstreams and teams of specialists responsible for different parts of the change.
That level of structure may be appropriate in a large, complex organisation. However, the same approach would quickly overwhelm a smaller business.
This does not mean smaller organisations need less thoughtful change management.
The underlying steps are remarkably similar.
Whether a business has 20 employees or 20,000, people still need to understand why something is changing, what it means for them, what they need to do differently and how the new way of working will be sustained.
The difference is not whether structure is required.
It is how much structure is proportionate.
The Scale Changes, but the Core Questions Remain
A smaller organisation may not use formal terms such as business case, sponsor coalition, change impact assessment or benefits realisation plan.
Nevertheless, it still needs to answer the questions behind them.
Why is the change necessary?
What problem are we trying to solve?
Who is accountable for making it happen?
Who will be affected?
What needs to be delivered?
What might prevent it from succeeding?
How will we know whether the change has worked?
What will stop people returning to the previous way of working?
These questions apply regardless of organisational size.
In a larger business, the answers may be documented across formal governance, project and change-management products.
In a smaller company, they may be captured in a concise plan, a set of agreed actions and a regular leadership review.
The level of documentation changes. The need for clarity does not.
Smaller Does Not Always Mean Simpler
It is tempting to assume that change is easier in a smaller business because fewer people are involved.
Sometimes it is.
Decisions can be made more quickly. Leaders are closer to employees. Communication can be more direct. There may be fewer organisational layers and less distance between the person making a decision and the person expected to implement it.
However, smaller organisations bring their own challenges.
They may have:
Limited capacity to absorb disruption
Heavy dependency on a small number of individuals
Little separation between project work and business as usual
Fewer specialist change, learning or communication resources
Processes that have developed informally over time
Decision-making concentrated around a founder or small leadership group
Strong personal relationships that influence how change is received
Limited data against which to measure improvement
A large organisation may be complex because of its scale.
A small organisation may be complex because people, processes, relationships and responsibilities are tightly interconnected.
Changing one part of the business can quickly affect everything else.
What Larger Organisations Add
Larger organisations usually require more formal coordination.
A change may cross functions, countries, business units, systems and reporting lines. Different groups may experience the same programme in very different ways.
This creates a need for:
More detailed stakeholder segmentation
Formal governance and decision rights
Defined escalation routes
Coordinated communication channels
Structured learning and support
Dependency management
Consistent reporting
Benefits tracking
Local implementation networks
Clear tolerances for time, cost, scope, risk and quality
The danger is that the machinery of change can become disconnected from the people experiencing it.
A programme may have comprehensive reporting, polished communications and a detailed plan, while employees remain unclear about what is expected of them.
Structure is valuable only when it helps the organisation make better decisions, coordinate delivery and support adoption.
Applying ADKAR at Different Scales
The Prosci ADKAR model provides a useful way to think about the individual journey through change.
It considers five outcomes:
Awareness of the need for change
Desire to participate in and support the change
Knowledge of how to change
Ability to implement the required skills and behaviours
Reinforcement to sustain the change
Those outcomes are relevant in every organisation.
What changes is how they are achieved.
Awareness
In a small business, awareness may be developed through a direct and honest conversation led by the founder or managing director.
People can ask questions in the room, challenge assumptions and hear the reason for the change first-hand.
In a larger organisation, awareness may require executive alignment, leadership briefings, manager toolkits, intranet content, town halls and repeated communication across different channels.
The activity is different, but the desired outcome is the same.
People need to understand why the current position cannot simply continue.
Desire
Smaller organisations often have an advantage in understanding individual concerns because leaders work closely with the people affected.
However, personal relationships can also make resistance more sensitive.
A new structure, process or role may be interpreted as criticism of how an individual has worked for many years.
In a larger organisation, the range of motivations and concerns is broader. Different functions may see different benefits, risks or losses.
In both settings, desire cannot be created by communication alone.
People need to see that the change is worthwhile, credible and supported by leaders whose behaviour matches their words.
Knowledge
Knowledge is about understanding what to do differently.
A small organisation may provide this through demonstrations, coaching, process walkthroughs, peer support and practical documentation.
A larger organisation may require formal learning journeys, digital content, role-based training, manager guidance and support materials.
The mistake at either scale is assuming that telling people about the change means they know how to perform it.
Awareness explains why.
Knowledge explains how.
Ability
Knowing what to do does not guarantee that someone can do it under normal working pressure.
People may need opportunities to practise, receive feedback and build confidence.
Systems may need adjusting. Workloads may need to be reconsidered. Managers may need to coach new behaviours. Processes may need to be simplified.
In smaller businesses, ability can often be developed through close, hands-on support.
In larger organisations, it may depend on local managers and change networks translating a central design into practical application.
Reinforcement
Change can appear successful during implementation and then gradually disappear.
Old habits return. Workarounds emerge. Leaders stop asking about the new process. Measures focus on activity rather than outcomes.
In a smaller organisation, reinforcement may consist of regular leadership reviews, visible measures, coaching and continued attention to the new way of working.
In a larger organisation, it may include benefits tracking, performance measures, recognition, governance reviews and formal ownership within business-as-usual teams.
Reinforcement does not need to be complicated.
It does need to be intentional.
How PRINCE2 Supports Right-Sized Delivery
PRINCE2 is sometimes perceived as a heavyweight methodology designed mainly for large projects.
In practice, one of its most important principles is that it should be tailored to suit the project.
Tailoring does not mean abandoning control.
It means applying the method in a way that is appropriate for the project’s size, complexity, risk, importance and organisational context.
This distinction is particularly relevant when working with smaller organisations.
A growing business may not need lengthy reports, multiple boards or a large project-management structure.
It still benefits from clear ownership, agreed outcomes, manageable stages, risk visibility and defined decision points.
Continued Business Justification
Every change should have a clear reason for existing.
In a smaller company, this may be expressed in a one-page business case rather than a large formal document.
The essential questions remain:
What problem are we solving?
What will the change cost?
What benefits do we expect?
What happens if we do nothing?
Is the change still worthwhile as circumstances develop?
A concise business case can provide discipline without delaying action.
Defined Roles and Responsibilities
Smaller organisations often rely on shared understanding rather than explicit accountability.
This works until priorities compete or an important task falls between roles.
A right-sized approach might simply clarify:
Who sponsors the change?
Who manages the work?
Who makes key decisions?
Who owns the final outcome?
Who needs to be consulted?
Who will operate the new process once the project is complete?
This is not bureaucracy.
It is a way of avoiding confusion.
Managing by Stages
Breaking change into stages creates opportunities to review progress and make informed decisions.
A small project might use straightforward stages such as:
Diagnose the current problem
Design the future approach
Test it with a limited group
Refine and implement
Review adoption and outcomes
Each stage should produce something useful and create a clear point at which the organisation can decide whether to continue, adjust or stop.
Focusing on Products
PRINCE2 uses the term product to describe what the project must deliver.
For a business change, products might include:
A redesigned process
A new operating structure
Defined roles
A configured system
Training materials
A communication plan
A set of performance measures
A transition plan
An agreed support model
Defining these outputs helps prevent a project becoming a collection of meetings and activities without a clear end result.
Managing Risk Proportionately
Every organisation manages risk, even when it does not use a formal risk register.
A proportionate approach may involve a short, regularly reviewed list covering:
What could go wrong?
How likely is it?
What would the impact be?
What action can reduce the risk?
Who owns that action?
At what point does the issue require escalation?
The purpose is not to create paperwork.
It is to prevent foreseeable problems being ignored until they become urgent.
Tailoring Is Not the Same as Cutting Corners
There is an important difference between a tailored approach and an unstructured one.
Tailoring asks:
“What is the minimum level of governance and documentation required to deliver this change responsibly?”
Cutting corners asks:
“What can we avoid doing?”
The first removes unnecessary process while protecting clarity and control.
The second often removes the thinking that the process was designed to prompt.
A two-page plan that has been discussed, challenged and agreed can be more valuable than a 50-page document that nobody uses.
The goal is not more documentation.
It is better decision-making.
What Small Organisations Can Learn from Larger Ones
Smaller businesses can benefit from adopting some of the disciplines found in larger programmes.
These include:
Clear sponsorship
Someone senior must actively own the change, not simply approve it and step away.
Visible outcomes
The organisation should define what success looks like before implementation begins.
Stakeholder consideration
Even when relatively few people are involved, they may experience the change differently.
Risk management
Speed is useful, but it should not prevent the organisation considering foreseeable consequences.
Adoption planning
Implementing a system or process is not the same as embedding it.
Benefits review
The organisation should return to the original objectives and assess whether the expected value has been achieved.
These practices do not require a large change function.
They require focused attention.
What Larger Organisations Can Learn from Smaller Ones
Larger organisations can also learn from the strengths of smaller teams.
Direct communication
Employees often respond better to clear conversations than layers of highly polished messaging.
Faster feedback
Smaller organisations can identify practical problems quickly because leaders and decision-makers are closer to implementation.
Visible leadership
When leaders are personally present, employees are more likely to believe that the change matters.
Practical experimentation
Smaller teams can test an approach, learn and adjust without waiting for every detail to be perfected.
Clear connection to the customer
The reason for changing can be easier to see when the link between internal activity and customer experience is direct.
The challenge for a large organisation is finding ways to preserve these qualities while operating at scale.
The Role of a Freelance Change Professional
Not every organisation needs a permanent change-management function.
A smaller or growing business may need experienced support for a particular period of transition.
This could involve:
Diagnosing the current operating problem
Defining the desired outcome
Establishing proportionate governance
Mapping stakeholders and change impacts
Supporting leaders and managers
Developing communication and engagement activity
Coordinating implementation
Identifying adoption risks
Building practical measures
Transferring knowledge into the internal team
The value of an external practitioner is not in importing a large corporate process.
It is in bringing sufficient structure, objectivity and experience to help the organisation make the change successfully.
The approach should fit the business.
The business should not be forced to fit the methodology.
About Mark M Barton
I am a Change Management, Change Communications, Project Delivery and Operations professional with over 25 years' experience helping organisations deliver complex projects, improve operations and navigate organisational change.
Certified in both Prosci Change Management and PRINCE2, I work across change management, project delivery, operational improvement, internal communications and transformation initiatives, helping organisations achieve successful outcomes through both structured delivery and effective people engagement.
If I can help you, your team, or your organisation do reach out.
