Why Digital Transformation Is Now a People Strategy, Not a Technology Project

Most organisations still talk about digital transformation as if it is a technology upgrade.

New systems. New platforms. New devices. New tools.

Those things matter, but they are rarely the reason transformation succeeds.

Real transformation happens when people change how they work, how they decide, how they collaborate, how they learn, and how they measure progress.

Technology can enable that shift, but it cannot cause it on its own.

If you want digital transformation to stick, you need to treat it as a people strategy first, and a technology programme second.

The common misunderstanding

A typical transformation plan starts like this.

1. Choose a platform

2. Implement the platform

3. Train staff

4. Measure adoption

5. Move on

This approach assumes that the organisation is mostly fine, and only needs tools.

But in reality, transformation is often trying to solve deeper problems.

• Fragmented ways of working across teams

• Inconsistent decision making and unclear ownership

• Skills gaps and confidence gaps

• Competing priorities and overloaded staff

• Lack of a shared narrative about why change matters

• No clear definition of what success looks like

When these conditions exist, adding new tools can actually increase friction. People end up with more systems, more logins, more processes, and more cognitive load.

That is why so many transformations become expensive activity rather than meaningful progress.

The real challenge is capability, confidence, and culture

Digital change asks people to do at least one of the following.

• Work differently

• Teach differently

• Lead differently

• Communicate differently

• Measure impact differently

• Collaborate differently

That is not a training task. It is an organisational capability shift.

Capability is not just knowing which buttons to press. It includes:

• Confidence to try new approaches without fear of failure

• Judgement to choose the right tool for the right job

• Fluency in good practice, not just basic features

• Shared standards so teams can collaborate without chaos

• A culture that rewards improvement, not perfection

If the focus stays on technology, capability is treated as a final step. A quick training session, a few how to guides, and a hope that people will adapt.

If the focus shifts to people, capability becomes a core workstream with the same importance as procurement, implementation, and reporting.

A helpful reframe, from projects to behaviours

Instead of asking, “What system are we implementing” ask, “What behaviours are we trying to enable.”

Here are some examples.

Technology question

“What platform should we use for collaboration”

People strategy question

“What does good collaboration look like across our teams, and what habits do we need to build”

Technology question

“How do we roll out a new learning platform”

People strategy question

“How do we support staff to design learning that works well in blended environments, and how do we share good practice quickly”

Technology question

“How do we improve data and reporting”

People strategy question

“What decisions should data improve, who owns those decisions, and how do we make data part of everyday leadership”

This reframe changes everything. It puts outcomes and behaviours first, and makes technology the supporting layer.

Why adoption is not the same as impact

Many organisations measure success using adoption metrics.

• Number of active users

• Number of logins

• Completion of training

• Usage frequency

• Volume of content created

These measures are not wrong, but they are incomplete.

High usage does not guarantee better outcomes. Low usage does not always mean failure. People might be forced to use a system while still working badly. Or people might be using fewer features because they have simplified their process, which is a positive outcome.

Impact is the better measure.

Impact metrics might include:

• Reduction in time spent on manual tasks

• Faster cycle time for key processes

• Improved quality of communication and fewer misunderstandings

• Better learner experience and engagement

• Improved staff confidence and capability

• Increased consistency across teams and campuses

• Clear evidence of early wins that build momentum

Adoption is a signal. Impact is the outcome.

A people strategy designs for impact first, then uses adoption signals to adjust the approach.

The most overlooked ingredient is narrative

People support change when they understand three things...

1. Why change is needed, and why now

2. What will improve for them and for the people they serve

3. How they will be supported through the change

If those are not clear, people fill in the gaps. They create their own story, often based on risk...

• “This is cost cutting”

• “This is a way to monitor staff”

• “This will add workload”

• “This will disappear in six months”

• “This is just another initiative”

A strong narrative reduces fear and increases participation.

It should be simple, consistent, and repeated often. It should connect to real pressures and real opportunities. It should also be honest about trade offs.

A useful narrative structure is:

• The shift happening in the sector or market

• The risk of standing still

• The opportunity if we act

• The principles that will guide decisions

• What will change first, and what will not

• How we will support people

• How we will measure success

When leadership communicates this clearly, staff can see the point. They can also see where they fit.

Transformation succeeds when it has the right operating model

A people strategy requires a delivery model that matches the complexity of change.

Many programmes fail because ownership is unclear. Everyone is involved, so nobody is accountable.

A practical operating model includes:

Executive sponsorship

A visible sponsor who clears obstacles and protects focus.

Programme leadership

A named lead who coordinates workstreams and owns delivery.

Cross functional team

Representation from operations, digital, learning, support, data, and communications.

Local champions

People embedded in teams who translate strategy into day to day practice, and feed reality back to the programme.

Feedback loops

Regular listening, rapid adjustment, and evidence based decisions.

A communications engine

Not occasional updates, but a planned rhythm that builds confidence and momentum.

This is what makes transformation feel like progress rather than disruption.

The practical framework, what a people first transformation looks like

Below is a comprehensive approach that works across education, public services, and growth organisations.

1. Start with outcomes and pain points

Define the outcomes in plain language...

• What must improve

• Who experiences the improvement

• What success looks like in day to day reality

• What gets easier, faster, or better

Then map the pain points...

• Where work is slow

• Where quality drops

• Where communication breaks

• Where staff feel overloaded

• Where learners or customers experience friction

This creates a shared problem definition. It stops transformation becoming a shopping exercise for tools.

2. Define the behaviours you want to enable

Identify the behaviours that will drive those outcomes...

For example:

• Staff share resources and practice in a consistent way

• Teams plan collaboratively with visibility across sites

• Leaders use data for decisions, not for reporting only

• Learners experience a coherent digital journey

• Support teams can resolve issues quickly using shared processes

This turns strategy into tangible expectations!

3. Design capability as a journey, not a training event

Capability building should include...

• Baseline assessment, confidence, skills, readiness

• Targeted pathways for different roles

• Peer learning and communities of practice

• Drop in support, coaching, office hours

• Practical templates that make the new way easier

• Recognition for early adopters and good practice

Training should focus on real tasks, not features.

“Here is how to run a blended session well”

“Here is how to collaborate on planning across campuses”

“Here is how to communicate with your cohort consistently”

“Here is how to use data to improve outcomes”

When capability is designed like this, adoption becomes a natural consequence.

4. Reduce cognitive load and protect time

Change fails when it adds workload.

A people strategy actively removes friction.

• Simplify processes before adding tools

• Remove duplicate reporting

• Create consistent standards and templates

• Provide protected time for early adopters and champions

• Avoid launching too many initiatives at once

• Sequence rollout so staff are not overwhelmed

If people do not have time, they cannot change, even if they want to.

5. Build an early wins plan

Early wins are not a nice to have. They are the fuel !!

Plan for them intentionally.

• Choose use cases that matter and are visible

• Pick teams that are willing and supported

• Measure impact quickly

• Share stories widely

• Show practical examples, not abstract claims

The goal is to create belief.

Belief creates momentum. Momentum creates scale

6. Create simple, credible measurement

Measurement should answer two questions....

• Is this improving outcomes

• What should we change next

A balanced measurement set might include...

Experience

Staff confidence, learner satisfaction, reduced friction.

Capability

Skills progression, peer sharing activity, quality of practice.

Delivery

Milestones, participation, responsiveness, issue resolution.

Impact

Time saved, quality improvements, improved consistency, better outcomes.

Keep it light enough to maintain. Heavy measurement becomes a burden and undermines trust.

What leaders should do differently

If you are leading transformation, the biggest shifts are:

• Spend as much time on people and operating model as on technology

• Treat communications as a core delivery workstream

• Invest in capability pathways, not one off training

• Build a cross functional team that can actually deliver change

• Protect time and remove friction, or adoption will stall

• Plan early wins, then communicate them relentlessly

• Measure impact in ways that matter to staff and service users

Technology is still important. It just is not the first problem to solve.

A final thought

The organisations that get this right do not just become more digital.

They become more capable.

They learn faster. They share practice better. They make decisions with more clarity. They deliver more consistent experiences. They adapt to change without burning out their people.

That is why digital transformation is now a people strategy.

If you want help turning this into a practical plan for your organisation, including operating model, communications approach, capability pathways, and impact measurement, Wislo can support the early stages and set you up for successful delivery.