arrow_back

🌏 TripScout

A while ago me and my teammates at Despark were approached by TripScout to add some new features in their working application. TripScout is a trip application with more than 100,000 users created by exciting people who are eager to travel and learn about new places.



Services

UX Design UI Design Prototyping Documentation



Challenge

1. How to introduce new features for creating trips and itinerary maintenance, while keeping the flow smooth and user-centric.

2. How the new features should keep the application visuals consistent.



Process

The product team provided user stories and feedback documentation, which showed that an urgent need for adding new features is important if they want to improve the experience of their application. While having those user stories I was able to rethink the product and apply the features. What came out of it was a sitemap which showed connectivity between all the existing features and the one that were about to be introduced.


Adding the user stories as part of the flow and attaching them to specific areas in the flow-map made the document understandable.



There were two cases for the "Trip profile" existing and not existing case. That's why I presented both flows in different parts of the map so we have the full spectrum of requirements even in the mapping phase.



Once me and the product team made a re-evaluation of the documentation. We entered the wireframe process. Having the flow mapping the whole journey before we even start doing layouts made the process super smooth.



The wireframes were approved fast what was interesting to work on now was the implementation of the visual language. While making the designs consistent to the current visual logic we found out that a real live documentation was needed, due to the choices that were made in the past. We needed clear definitions of components.
That type of documentation let the development team to ship features faster and the communication between our teams to be smoother. It was like we spoke the same language.

Conclusion

Every team should create their own documentation by implementing the fundamentals of a systematic language. Using methods from code and the knowledge that I gathered from the Atomic design practices I was able to execute a information documentation which led then to a faster shipment of new features and more time for prototypes. Our first workshop took 14 days, the second one was done for just 6 days. We did not loose time to create new components, using the current one we were able to spend more time on prototyping and testing out our ideas.
















Referral

"Boris a fantastic strategist and designer and was highly impactful on the end-to-end design of a critical feature set for our app. He has the ability to quickly understand both the user and the business and create simple and elegant, yet highly-functional designs. He is highly receptive to feedback but not afraid to speak the truth when suggestions defy what is best for the user. On top of all of that, he's generally pleasant, has a great sense of humor, and not afraid of hard work. I'd gladly work with Boris again and recommend him to anyone that needs to solve a complex design problem."

TripScout Co-founder | Andy Acs





Boris Kirov