A look into my process.
how I think, work, and document my projects.
A look into my process.
how I think, work, and document my projects.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.
Redesigning a booking flow
DD/MM/YYYY
The client came to me with a booking flow that was losing users halfway through. Nobody was completing it. My first step was figuring out why, so I mapped out every single touchpoint and looked at where people were dropping off. Turned out the form was asking for too much too soon, and the visual hierarchy wasn't guiding the eye anywhere useful.
I stripped it back. Broke the form into smaller steps, made the primary action obvious on every screen, and let the illustrations carry some of the emotional weight. The result was a flow that felt lighter, even though we hadn't removed a single required field.