To create a new product design fitting to the increased requirements of Flybox.io that evolved from a campus emergency notification service to a cross-industry communication and safety platform
Business Analyst, 2 UX/UI Designers
3 Months of active work
Research, scope definition, prioritization, end-to-end user flows for four user roles (over 100 screens); supporting documentation, UI/UX design, dev support
Operable MVP on the implementation stage (as of time of posting this case study), including full product design, design system, and product documentation
Flybox.io is a communication and safety platform that enables its customers to send and receive location-based notifications under full anonymity of their personal data.
It was initially designed as a campus messaging platform for sending alerts in life-threatening cases such as a natural disaster, an active shooter, or a hostage situation. The unique advantage of the platform was an opportunity to immediately reach and inform everyone within an emergency area without tracking their data or violating privacy in any other way.
Business owners very much enjoyed the idea to send context-specific information to their clients without making them download an app or requesting GPS permission.
The original version was good for nothing except demonstrating the viability of the idea and efficiency of the algorithm. But it could not show high marketability and attract new funding.
That is why we decided not to redesign the existing version but to start the work from scratch.
We encountered a project with huge untapped potential in a relatively new market. Therefore the research could not give much information about the established trends and practices in this field. So it was critically important to clarify the business objective and the product requirements set by its key stakeholders.
Thus we conducted comprehensive user research and workshops to create personas based on their pain points.
As the product was built on an innovative technical algorithm of non-tracking messaging, exhaustive clarification of its technological standards was vital to the total output value.
Based on the client’s requirements we created a clear end-to-end flowchart to capture and visualize all the complex variables and processes underpinning the Flybox technology.
As the product’s technological and market niche represented largely uncharted territory, active brainstorming and ideation were absolutely indispensable.
Thus we have initiated a workshop with the involvement of both our design team and the company stakeholders. Its main deliverables included elaborate user personas, user scenarios, and the customer journey map.
Despite the newness of the technology and the little-explored market, our client already had quite a few competitors. While most of them had different technological solutions, they all targeted the same customer segment and pursued similar business objectives.
To secure our client, we have researched both direct and indirect competitors to understand their edges and weaknesses, so that we could address a user's needs and pain points in a better way.
During the UX design stage, the team concentrated their effort on functional requirements (e.g. communication range) and non-functional requirements (e.g. usability and accessibility). We ensured their compliance with the business objectives and selling points from marketing and monetization perspectives.
The emergency button is a core feature of the product. It represents an algorithm for sending emergency messages to all users within and/or between locations without tracking their personal data.
The challenge was to make a user flow fast, easy, and intuitive. We approached the problem by implementing a location-based quick filtering option, message templates, and other streamlining solutions.
As Flybox already matured from a simple emergency notification platform to a multi-purpose communication-and-safety service, we had to envisage a more complex communicative system adaptive to various environments and specific needs of customers.
This included options for providing informational support, notifying about special offers, or making relevant real-time announcements. We also designed a planning function to manage messaging based on users’ location.
Along with design source files, the Cieden team prepared supporting documentation. Its key deliverables included: a general system overview; user cases and user stories; roles/permission matrix; acceptance criteria; BPMN process diagrams; end-to-end user flows.