I've never particularly liked travelling with large groups or being told where to go by somebody else. I prefer to find out for myself. - Michael Palin
The concept came up with the idea that as individuals we love travelling and when visiting new places we wanted to explore the culture and live with the locals instead of going to all the tourist-y sites.
- ConceptPen and paper
- PrototypingPrinciple App
- Gif AnimationsPrinciple App
- WritingSublime Text 2
- Code and MarkupSublime Text 2
- HostingDigital Ocean
My Design Process
We followed the design thinking process for designing our solution, which started off with interviewing people and then creating affinity walls and then finding & validating a solution, which was followed by market assement and creating a pitch that was presented to various companies in New York.
The discovery process involved taking user interviews around the topic of travelling and trying to find more consistent issues that people have while planning the travel and why travelling itself.
The discovery process also laid out creating affinity map, that heped us organize various prolbems into categories and understand how they affect the behaviour of people and then further target and narrow down our problem search.
Discovery stage, with the help of interviews and affinity mapping allowed us to categorize areas with problem. Finally the area that we wanted to work in the domain of travel was that of planning and collaboration. The presentation of which looks something like below.
After narrowing our solution, we had to make sure that we aren't offering something already in the market and being used, which is why we needed a market assestment.
We pulled in some market numbers of the flights, to prove the potential market exists and that we have a space in this huge domain of travel.
The sketching was a significant part but mostly just to allow us to have some sort of tangible prototype that we could then use to help validate our solution before going ahead with any high fidelity prototypes
The validation process help us guide our further changes and direct our focus in the right places, i.e. the planning and collaborating and a way to resolve conflicts which help create custom itenaries.
Once we were confident of the prototypes and the flows that our user agreed upon, we had some corrections and we went to create something more tangible and concrete that could be used to present during our pitches.
One of the biggest challenges in the process was trying to capture what the users really need, instead of directly asking them. Observing users wasn't a possibility for us, but the interviews did help is understand the problems better.
Users don't know what they want
The first takeaway that we came to at a very early stage was that, "Users don't know what they want". This was understood when we had questions like "what do you think should be improved, all it did was create new hypothetical solutions and they were later rejected by that user itself.
Interview people you don't know
The second takeaway was that people who are in your friend circle will always give you more positive and helping answers because they have the innate need to help you.
Room for Improvement
The app can certainly take in more features (each with their own user validation process), because as of now we have made this very extensive application, going narrower should be of primary purpose to us.
There are some moments that I cherised during that trip, you can find them here.