Printable Itinerary
Company: Wetu
Role: UI
Role: UI
Year: 2019
Background
Tour operators and travel agents can create an itinerary using Wetu's itinerary builder. The itinerary can be sent to their travellers as a digital version but can also be printed.
Wetu's aim is to create 4 different printable options that clients can select from, each having their own look and feel.
I was tasked with creating the second option. The requirements were to update the layout from the original version to have a more modern feel while still working within the constraints of MS Word and also making it look image rich.
Research
I researched various printed and online itinerary examples and compiled my research into an InVision board to aid discussions with my product manager.
Design
I introduced an image hierarchy to help travellers easily distinguish between different types of content when flipping through the itinerary.
Here is what these images look like in an itinerary
The introductory table has been redesigned to better handle translations. The number of columns has been reduced from 8 to 3. This is because when the itinerary is translated many foreign languages have longer words and so the words will have to wrap in the small columns.
The transport table has also been redesigned to better handle translations. The number of columns has been reduced to 3. Consistency has also been created. On the left you can see each transport type has a different number of columns and different headings. The new version information was grouped together under 3 headings to make it easier for travellers to scan the information.
What I would do differently
The brief was to create a new design and no limits were imposed. I was told to create anything I wanted.
When the project went into development we realised that we now had to work within the constraints of MS Word and layering the date and destination or name of accommodation over an image was quite challenging.
In future I would ask for the developer to be brought into the project earlier so that they could test to see if my ideas were feasible.
When the project went into development we realised that we now had to work within the constraints of MS Word and layering the date and destination or name of accommodation over an image was quite challenging.
In future I would ask for the developer to be brought into the project earlier so that they could test to see if my ideas were feasible.
