Digital Transformation

Why starting with technology is the fastest way to fail

When technology becomes the starting point, it quietly defines the solution before the problem has been properly understood.

Why digital work that begins with platforms and systems often ends up constrained by them, and why better strategy starts with the problem instead.

05 August 20246 min read

In short

Why digital work that begins with platforms and systems often ends up constrained by them, and why better strategy starts with the problem instead.

Why technology feels like the sensible place to start

It rarely feels like a mistake at the time. In fact, it often feels like a sensible place to start. There is usually pressure to move forward, to make something tangible, and technology provides something concrete to anchor that momentum.

Discussions quickly centre around , , , and capabilities, and from that point on, the direction begins to form around what those systems can support.

What makes this difficult to challenge is that it creates an immediate sense of progress. There are options to compare, to evaluate, and decisions that feel actionable. It becomes easier to define workstreams, assign ownership, and begin shaping a plan.

From the outside, it looks structured and purposeful.

However, that structure is being built on an assumption that the problem is already understood, when in reality it has often been defined indirectly through the lens of the technology itself.

Starting with technology creates momentum quickly, but it often means the shape of the solution is being set before the problem is properly understood.

How the technology starts shaping the problem

As a result, the conversation shifts away from understanding and towards adaptation. Instead of asking what the business is trying to achieve or where users are experiencing , the focus moves to how those needs can be accommodated within the chosen .

Requirements start to emerge based on what the technology allows, rather than what is actually required. Over time, the begins to reflect the and limitations of the rather than the outcomes it was originally intended to support.

Because this happens incrementally, it rarely feels like a conscious trade-off. Each decision is justified in isolation, and each step appears reasonable when viewed on its own.

However, the cumulative effect is that the work becomes increasingly constrained by choices that were made before the problem was properly understood.

By the time this becomes visible, a significant amount of effort has already been invested in shaping the direction, making it difficult to revisit those early decisions without disrupting the progress that has been made.

Key takeaway

When technology comes first, the strategy often ends up adapting to the system instead of defining what the system needs to support.

What happens once those early choices are baked in

At that point, the focus tends to shift towards making the chosen approach work rather than questioning whether it was the right approach to begin with.

Teams begin to introduce workarounds, adjust , and layer additional complexity in order to bridge the gaps between what is needed and what the can deliver.

None of this is intentional, but it is a direct consequence of starting from the wrong place.

The technology has effectively defined the boundaries of the solution before the problem itself has been fully explored.

What changes when technology enters at the right stage

In contrast, when technology is introduced at the appropriate stage, it plays a fundamentally different role.

The work begins with a clear understanding of what needs to improve, where the exists, and what outcomes are being targeted. This understanding is shaped through exploration, challenge, and , rather than assumption.

Only once that foundation is established does the conversation move towards selecting the technology that can best support it.

This approach creates a much clearer for .

Technology is no longer driving the direction, but supporting it.

become explicit rather than implicit, and are understood in relation to the problem rather than discovered during .

As a result, the remains aligned to its original intent, and the technology becomes an enabler rather than a limiting factor.

Why the difference only becomes obvious over time

The difference between these approaches is not immediately obvious, as both can produce plans that appear credible in the early stages.

However, over time, the impact becomes increasingly clear.

When technology is used as the starting point, the work becomes shaped by its limitations.

When the problem is properly understood first, technology becomes a tool for delivering a well-defined outcome.

Most digital initiatives do not fail because of the technology itself, but because it was introduced before there was sufficient around what needed to be solved.

Starting with technology creates a sense of momentum, but it often to decisions that are difficult to unwind and a direction that becomes increasingly constrained over time.

LET'S WORK TOGETHER

Ready to improve your product?

UX, research and product leadership for teams tackling complex digital services. The work usually starts where things have become harder than they need to be: unclear journeys, inconsistent products, competing priorities, or teams trying to move forward without a clear direction. I help simplify the problem, shape the right next step, and turn complexity into something people can actually use.

Previous feedback

Will Parkhouse

Senior Content Designer

01/20