Discovery workshop
Interviews, competitive research.
01
When the Client contacted us, the team was already experiencing some issues in the communication workflow that had a visible influence on the effectiveness of their everyday work. Having multiple channels that were used for communication and order management, the organization saw that the inefficient information chain resulted in miscommunication and delays.
The challenges:
Interviews, competitive research.
01
Creating user personas, designing user flow, user story mapping.
02
Defining the MVP,
preparing information architecture,
paper prototyping, user testing.
03
Designing user interface,
creating style guide.
04
Event Storming workshops,
adding new features.
05
Building a solution that works is best done in close collaboration with the end users – the people who will be using the tool. We observed Visline employees at work and had the opportunity to see the challenges they face and ask them about these. These observations helped us understand the importance of proper team interactions in the company and we found out that the communication issues that occur affect the quality of service but also the employees’ efficiency and motivation as they were experiencing higher levels of stress.Their frustrations revolved around the inability to get access to the right information when it was needed.
During the UX workshop, after we have explored the needs of end users and the details of the then workflow, we listed ideas on automating the process and started wireframing. The first low fidelity prototypes were prepared on paper together with the Client’s team. Along the way, we also prepared the user story map and determined the scope of the minimum viable product (MVP).
At the beginning of the development process, we explored the Client’s IT infrastructure in detail, focusing on listing all the software and tools the company was using. At the same time, we reviewed the company’s use of cloud services to find ways of optimizing cloud architecture. We used the results of the workshops and our observations to design the application’s architecture along with cloud structure. We built 3 separate environments for development, testing, and production, and equipped the system with a fully automated pipeline that allowed for deployment between these without downtime.
We worked on the project following the guidelines of Agile product development, starting with strategic planning and preparing the backlog, through development in sprints with internal daily Scrum meetings, to weekly progress reports and demos delivered to the client. We maintained close collaboration with the Client’s team to allow for faster delivery of increments and timely exchange of all the necessary information. Staying in touch on a regular basis is crucial at every stage of the project, but especially in the design phase, when it’s easier to implement changes in comparison to doing so in the development phase – it’s easier, so it saves our Clients’ time and money.