From a Single Landing Page to a Working Lead Journey
At first glance, the page appeared to be doing its job. Traffic was reaching the site, the layout was clean, and the intent behind the offer was clear. However, when performance was reviewed more closely, it became apparent that users were not completing the journey in the way they were expected to.
Rather than assuming a traffic or messaging problem, the decision was made to break the experience down into individual steps and observe how real users moved through the page.
Identifying the real issue
Users were not dropping off because they lacked interest. They were dropping off because the journey was asking for too much, too early, and behaving inconsistently as they progressed. The experience introduced unnecessary friction at key moments, which caused hesitation and abandonment.
Progression between steps was not always clear, validation was triggering at inappropriate points, and submission logic was sometimes firing more than once. While data was being captured, it was not always reliable, which made it difficult to trust reporting or optimise the funnel with confidence.
On the surface, this looked like a landing page issue. In reality, it was a journey design problem.
Reframing the approach
The journey was simplified so that each step served a single, clear purpose. Early steps were reduced to the minimum required to establish intent, while later steps were redesigned to collect additional information only once users were ready to proceed.
Clear separation was introduced between navigation actions and submission events, ensuring that users could move through the journey without unintentionally triggering form submissions or creating duplicate entries.
Rebuilding for reliability
The journey was redesigned so that data is only stored once the user has meaningfully completed the process, rather than being captured prematurely at intermediate steps. Unique identifiers are carried cleanly through the flow, preventing duplication and ensuring that each journey can be accurately tracked from start to finish.
This approach allows analytics and reporting to reflect real user behaviour, rather than assumptions based on partial or unreliable data.
The outcome
The rebuilt flow reduces friction between steps, improves completion rates, and provides clean, dependable data for ongoing optimisation. More importantly, it aligns the technical implementation with how users naturally move through the experience.
Why this matters
This project demonstrates how identifying and removing hidden friction can transform a page from something that simply exists into something that works — quietly, predictably, and at scale.