Designing the Journey to Change

The recent challenges around ScotRail’s new booking app(this will open in a new window) are a reminder that launching a new digital service isn’t just a technical exercise. It is also a user experience, service design and change-management challenge.

To be clear, this isn’t about pointing fingers. Most organisations going through a major digital transformation will recognise the same underlying reality; that replacing a core service that people rely on every day is hard. Really hard.

Especially when that service is something as time-sensitive and stress-loaded as getting a train ticket when you’re already running late.

For users, buying a ticket is often something they need to do quickly, sometimes while rushing for a train. It is not a leisurely browsing experience. It’s functional, habitual, and often done under pressure. That means even small changes in layout, wording, login flow, or payment steps can feel much bigger than they look on a design specification.

When a familiar journey changes overnight, people don’t experience it as “a new system has launched”. They experience it as “something I know how to do has suddenly become harder”.

That shift in perception is important, because it explains why even well-intentioned improvements can lead to frustration if the transition isn’t handled carefully.

It’s rarely just about the technology

When digital services replace older systems, the focus naturally goes to whether the new platform works.

Does it load? Can it process payments? Are the APIs stable? All of that matters, of course.

But from a user experience perspective, the bigger challenge is often continuity. People are not starting from scratch. They arrive with existing accounts, saved preferences, railcards, season tickets, and mental models built up over years of use.

If any of that doesn’t carry over smoothly, users don’t see it as a “missing feature”. They see it as something broken.

For example, the new Scotrail app required users to re-register and create a new password. While that may have been important for security reasons, it immediately created an additional barrier for people transitioning from the previous app. Existing tickets also reportedly did not transfer to the new app, adding further friction to the transition.

That’s why transitions are often the most fragile part of any digital transformation. The greatest risk may not be the new system itself, but the bridge between old and new experiences.

What can organisations learn?

There are some consistent patterns that appear when major digital services do not meet user expectations. They are worth keeping in mind for any organisation planning a major digital change.

Think beyond launch day

A successful release isn’t just about whether the new system works in isolation. It’s about how people move from the old experience to the new one. That includes:

• How the change is communicated
• Whether users understand what they need to do
• When the change takes place
• What support is available
• Whether existing information, tickets or preferences are carried over
• How easily users can recover when something goes wrong

If the transition is rough (like existing tickets not being migrated to the new app) the perception of the entire project suffers, even if the underlying system is technically solid.

Test realistic journeys, not just individual features

It is relatively easy to test login screens, payment flows, or timetable searches in isolation.

It’s much harder - but far more important - to test complete, end-to-end journeys that reflect real life.

For a rail app, that could include:

• A returning user trying to find a saved ticket
• Someone switching between devices
• A passenger buying a ticket in under a minute while standing on a platform
• A user with a railcard completing a purchase
• Someone activating an outbound and return ticket on the same day
• A passenger trying to resolve an error while travelling
• A user accessing the service with assistive technology

One of the reported issues with the Scotrail app was that users were unable to activate a second (return) ticket on the same day as the outbound ticket. While the function of activating a single ticket worked correctly, the wider user journey of activating tickets for a one-day return trip, did not. These are the moments that define the experience.

Organisations sometimes underestimate how quickly a handful of usability issues can become a business problem. Failed customer journeys can generate spikes in support calls, refund requests, lost transactions and negative publicity.

That’s why testing complete user journeys with representative users isn’t just good UX practice – it’s an important form of risk management.

Accessibility must be part of the foundation

Inclusive design and accessibility should be treated as fundamental principles in any major digital transformation, not as checks carried out at the end of delivery.

Travel is a high-pressure, real-world environment where poor design choices can have a particularly significant impact on users. People may be using an app outdoors, in bright light, on a crowded platform, with limited connectivity or while trying to catch a train.

Accessibility also goes beyond compliance. It means recognising the diversity of people using the service, including:

• People using screen-readers or other assistive technologies
• People with cognitive or learning differences
• People with temporary or situational impairments
• People in noisy, bright or distracting environments
• People who are tired, stressed or in a hurry

A successful transition should ensure information is clear, interactions are seamless, content remains readable in different conditions, and errors are easy to understand and resolve.

The new ticket selection could be problematic for users with different impairments, due to low colour contrast issues, icons with no explanation, and an unintuitive reading order for screen-readers.

Embedding accessibility from the outset improves the experience for everyone - particularly in a frequent, time-sensitive service like rail travel.

Roll out changes gradually where possible

Big-bang launches are sometimes unavoidable, but they carry risk.

Phased rollouts, soft-launches, beta groups, or regional pilots can surface issues that don’t appear in controlled testing environments. They can also reduce the impact when something unexpected happens, because fewer users are affected at once.

A gradual rollout creates opportunities to:

• Observe real-world behaviour
• Identify unexpected user needs
• Validate communications and support materials
• Monitor accessibility and usability issues
• Fix problems before they affect the entire user base

Where a full phased rollout is not possible, organisations can still consider smaller ways to reduce risk. These might include allowing users to continue accessing the previous service for a limited period, providing clear fallback routes or delaying migration for particularly complex user groups.

Keep listening after launch

One of the most important - and often overlooked - parts of any digital service is what happens in the first few weeks after release. Real-world usage always reveals things that no amount of pre-launch testing can fully predict. The organisations that do well here are the ones that proactively communicate with users, monitor feedback, and respond quickly when issues arise.

Post-launch activities should include:

• Reviewing support queries and complaints
• Monitoring task completion and transaction data
• Identifying repeated error messages or failure points
• Speaking to users who have struggled with the service
• Checking whether accessibility issues are being reported
• Communicating clearly about known issues and available workarounds

This is not simply about reacting to negative feedback. It is about treating launch as the beginning of an ongoing learning process.

A service that listens and responds can recover from early problems. A service that appears to ignore users may quickly lose their trust.

Change is a user experience in itself

We often think of user experience as something that applies to screens, buttons, and journeys. But change itself is also an experience. And it’s one that can either build confidence or erode it.

If users feel supported through a transition, they’re far more likely to forgive early teething issues and continue using a new system. If they feel abandoned or confused, even relatively small problems can cause lasting damage to their trust in the organisation.

That’s why digital transformation isn’t just about building better products. It’s about designing better transitions.

The work continues after launch

It’s easy to think of go-live as the finish line. In reality, it’s more like the halfway point.

Even with the best research, design and testing, launch is not the end of the journey. It is the point where a product or service moves from controlled research environments into the reality of everyday use, revealing behaviours, needs and challenges that could not always have been anticipated.

That’s when the real learning begins and when trust can be either strengthened or degraded.

Post-launch insight is essential to understanding what is working, what needs refinement and where further improvements can be made. Digital transformation should be viewed as an ongoing process of learning and optimisation, not a one-off delivery milestone. The most successful services continue to evolve based on ongoing evidence from the people who use them.

Designing with confidence

Ultimately, successful digital transformation is about managing risk as much as delivering technology.

Understanding users, researching how they interact with existing services, designing thoughtful transition journeys, and thoroughly testing complete end-to-end experiences all help uncover issues before they reach customers.

Organisations that invest in user research, usability testing and accessibility throughout the development lifecycle are better placed to:

• launch with confidence
• protect their reputation
• reduce costly post-launch fixes
• support a wider range of users
• deliver services that customers trust and want to use

If you’re working on a digital transformation and want to ensure your service is truly usable, inclusive, and resilient from day one, User Vision can help.

We support organisations with usability testing, end-to-end service evaluation, accessibility audits, and inclusive design reviews to give teams the confidence that transitions work for real people in real contexts.