When "Going Digital" Doesn't Change Anything

Plenty of organisations invest in shiny new platforms, roll out dashboards, and migrate documents into the cloud and still find that day-to-day work feels stubbornly the same.

The gap between tool adoption and business improvement is not rare: Gartner reports that, on average, only 48% of digital initiatives enterprise-wide meet or exceed their business outcomes targets.

What separates the organisations that get genuine outcomes from those that only digitise the surface is rarely the technology itself. The difference is leadership, clarity of purpose and the ability to build confident teams who can adapt processes as the business evolves.

Leadership Makes Digital "Real" or Keeps It Cosmetic

Transformations fail quietly when digital work is treated as a side project, delegated to a small team, or pushed through as "an IT thing". The organisations that succeed tend to have leaders who do three unglamorous things consistently:

• Set a clear direction for what success looks like (in business terms, not feature lists)
• Create governance that keeps decisions moving and progress visible
• Stay involved long enough to remove blockers and reinforce the change

That leadership emphasis matters because transformation is a series of decisions, not a single launch date. Gartner's research highlights a "Digital Vanguard" group where 71% of initiatives meet or exceed targets and attributes that outperformance to CIOs and CxOs co-owning digital delivery end-to-end (shared accountability rather than traditional sponsorship).

In other words, where leadership treats outcomes as responsibility, not something the tool should magically produce, digital becomes operational, not ornamental.

Start with Outcomes, Then Work Backwards

Organisations that "go digital on the surface" often start by mapping what they already do and asking "how do we automate this?".

The stronger approach flips the question: "What outcome is the organisation trying to improve, and what is the simplest path to get there?"

This is not just theory. High-performing digital teams borrow heavily from service design disciplines that insist on beginning with user needs. The UK Government's design principles open with "Start with user needs" and explicitly emphasise iteration ("Iterate. Then iterate again").

For commercial organisations, "user needs" might mean customers (faster resolution, clearer communication and fewer handoffs) and employees (less rework, fewer spreadsheets, easier approval flows). When outcomes are held front-and-centre, tool decisions become easier and temptation to digitise everything simply because it exists becomes much easier to resist.

Don't Digitise a Broken Process

A common reason digital programmes disappoint is that they preserve bad workflows in a new interface. That can even make things worse: the same inefficiencies get embedded into systems, multiplied across more users, and became harder to change because they now feel "official".

This idea has been around for decades in business process thinking. Michael Hammer's well-known argument in reengineering is blunt: instead of "paving the cow paths", organisations should use technology to redesign processes for dramatic performance improvement, not merely automate what already exists.

Outcome-driven organisations therefore ask tougher questions early:

• Is this step necessary at all?
• Who benefits from it: the customer, the business or nobody?
• What assumptions are embedded in the workflow, and are they still true?

That last point matters because transformation reveals unknowns. Many teams only discover what doesn't work once they are halfway through implementation. Organisations that succeed assume this will happen and plan for it.

Build Digital Confidence, Not Just "Rollouts"

Even the best-designed systems fail if people don't know how to use it, don't trust it, or don't see why it helps them. This is where superficial digitalisation often shows itself: training becomes a one-off demo, adoption is assumed and teams are expected to "figure it out" while also doing their day jobs.

The benefits however depend on real usage. Prosci frames ROI as heavily dependent on adoption and effective usage, and describes "human factors" that constrain returns, including speed of adoption, ultimate utilisation and proficiency.

That's why organisations that get outcomes invest in capability building as part of delivery, for example, practical workshops where teams learn what the tool can do, what it can't do, and how to model processes properly. When people understand a platform's capabilities and limitations, they make better design decisions, avoid over-engineering, and spot faster routes to value.

There's also a strategic workforce angle. Gartner notes that only 16% of CIOs surveyed prioritised building a technology workforce enterprise-wide (beyond IT), warning that this limits the ability to get value from digital investments.

Choose Tools That Let Teams Adapt Because the Business Will

One of the most practical differences between outcome-driven and surface-level digitalisation is the choice of tools. Surface-level efforts often pick systems that are rigid, require specialist intervention for every change, or force the business to contort its workflow to match the software.

Outcome-driven organisations expect change: new products, new compliance requirements, edge-case customer needs and shifting operational constraints. Tools that are forgiving, configurable, easy to refine and able to evolve without constant redevelopment, give teams room to learn and adjust without restarting the programme every quarter.

This is also where governance and agility meet. BCG's research states that 70% of digital transformations fall short of objectives, and highlights success factors including leadership commitment (from top through the middle), agile governance and progress measurement against clear goals.

The implication is simple: success comes from pairing adaptable tools with teams who have the confidence and permissions to keep improving the way work flows.

A practical way to operationalise adaptability is to choose a platform that your team can configure and evolve without constant redevelopment or specialist intervention. This is where Kinabase is designed to help: instead of forcing the business to contort around rigid software, Kinabase supports modelling real workflows as they actually run, then refining them as the organisation learns, customer requirements shift, or new services are introduced. As Kinabase brings data, process stages, and operational context into one flexible system, teams can adjust fields, stages, approvals and reporting as needs change.

Furthermore, without starting the project again every time the business changes direction. The result is a toolset that reinforces continuous improvement: leaders can keep outcomes front-and-centre, and teams can make iterative updates with confidence rather than treating "go-live" as the end of the journey.

Measure the Right Things and Make Them Visible

Digital transformation becomes "surface-level" when success is measured by outputs: number of licences, workflows created, documents migrated or features switched on. Outcome-driven organisations measure what changed in the business:

• Customer response and resolution times
• Rework rates and error reduction
• Cycle times for approvals and delivery
• Team capacity freed for higher-value work
• Service consistency across edge cases

Tracking these metrics helps leadership stay anchored in outcomes, makes progress tangible and highlights where processes need redesign rather than more automation.

What It All Adds Up To

The organisations that get genuine business outcomes don't treat digital as a purchase. They treat it as a leadership-led change in how work gets done. This is built on clear outcomes, honest process redesign, continuous learning and tools that can adapt as reality changes.

When leadership stays involved, teams understand the "why" and the organisation is willing to challenge assumptions rather than preserve them, digital stops being a veneer. It becomes capability and that capability is what turns platforms into performance.

Sources

• Gartner Press Release (Oct 22, 2024): Digital initiatives meeting/exceeding outcome targets; Digital Vanguard; enterprise-wide workforce skill priority. https://www.gartner.com/en/newsroom/press-releases/2024-10-22-gartner-survey-reveals-that-only-48-percent-of-digital-initiatives-meet-or-exceed-their-business-outcome-targets
• BCG (Oct 29, 2020): "70% of digital transformations fall short"; success factors including leadership commitment and agile governance. https://www.bcg.com/publications/2020/increasing-odds-of-success-in-digital-transformation
• Prosci: Benefits dependent on adoption and usage; Human Factors of ROI (speed of adoption, utilisation, proficiency). https://www.prosci.com/blog/roi-change-management / https://www.prosci.com/blog/3-factors-of-change-which-define-or-constrain-project-roi
• UK Government Design Principles: Start with user needs; iterate. https://www.gov.uk/guidance/government-design-principles
• Michael Hammer (reengineering): Warning against automating existing poor processes ("paving the cow paths"). https://folk.idi.ntnu.no/thomasos/paper/hammer_reengineering.pdf
• MIT Sloan (Ideas Made to Matter, May 18, 2021): Importance of combining leadership capability with digital capability; prioritising employee experience, customer experience, and operations. https://mitsloan.mit.edu/ideas-made-to-matter/digital-transformation-has-evolved-heres-whats-new