We'll refine your ideas into a hi-fidelity simulation, ready for user testing and development.
We believe in investing our design time in visual outputs. Our design process will refine the output from the Discovery Workshop into your final product. We'll craft wireframes, map processes, and build a hi-fidelity user experience to meet your needs.
At the end of the process, you will have a usable simulation you can use for testing with real users, or for development.
What we'll do
For each user, we'll draw out the things they'll want to do within the application. This helps to outline user acceptance testing scenarios and illustrates what the system will need to do.
(User or Business) Process maps
For areas of complexity, we'll map out the process visually, so we can be sure our code meets those needs. This could be for something the user needs to do, or logic within the code to make the app function properly.
We use wireframes to create the best possible experience for your app. Wireframes don't include any interface design, but focus on page structure and interactions. This guarantees the user can achieve what they need to.
Your project is an elephant, and we'll eat it one bite at a time. We'll break it down it into all its constituent parts. At this stage in the process, we'll first identify the big pieces, called "Epics" and then break them down further, into "User stories".
All software must have a sitemap! This shows all the screens that will exist in the application, and how they connect to each other.
Hi-fidelity design & simulation
This is the exciting part. We'll gather everything we have learned and create a User Interface (UI) to go with the experience we have designed. The output of this is a high-fidelity simulation you can use for testing with your users, and we can use to develop.
User stories & acceptance criteria
Once you are happy with your interface, we'll can write everything down. This is where we'll start to expand the User Stories, to include details of exactly what the user wants.
The User Stories are written like this:
“As a [user role], I want [something], so that [reason]”
We then add in all the detail on what the user wants, how it fits into the application and most importantly, why we want it. This is not about technical jargon, it is a method for describing the wants of the user.
Say hello 👋
If you have an idea, or a project in mind that you want to work with us on, we'd love to hear from you. Say hi and tell us a little about you and we'll get right back to you. Or why not get a free review of your idea now.