More on how FLOW came to life
Since our intention was to penetrate a new market, it was critical that we updated our personas to match the expanded segment of our users who will be using the product.
Through extensive research, internal/external surveys, and customer interviews, we were able to create personas that properly encapsulated the users who would get the most out of KiteDesk.
After defining the personas, we started to look at all the feedback we've been getting from users and stakeholders to establish those features that really make these persona's lives easier while increasing productivity and performance.
This lead to the writing of use cases for each of the themes/epics we uncovered from our research.
With our personas and use cases complete it was time to start creating user flows. These flows were used heavily when considering how the UI could accommodate the use cases.
Wireframing and documenting the use cases in a way that development could easily digest and develop the features. This was no simple task. At last count there were close to 50 different screens that needed one form of wireframe/requirements or another.
For a more detailed look at this wireframe, you can download it here...
Another example of a wireframe for reaching out to a prospect. Users have the ability to send an email via a WYSIWYG editor complete with templates, dynamic fields, and video.
For a more detailed look at these wireframes they can be found here...
Instead of going right into development, it was critical that we secure additional funding and get commitments from current users to be part of our early adopter and beta programs.
Having a clickable prototype allowed us to create a video of how the software would not just look and feel but how it would behave.
The prototype was later used in user sessions to garner priceless feedback.