3. The development of a mid-fidelity prototype

Design research

The development of our prototype followed an iterative design model that began initially with design research. This includes the customer journey map, personas, empathy maps, etc. as discussed in this article. We chose to have our design tone of voice to be serious​, informal, respectful​ and enthusiastic and our UI look and feel to be minimalistic​, fresh​ and modern.

User journey and tasks

The user journey we initially envisaged, as seen below, identified 8 steps with the aim of creating an improved experience for our users and identified opportunities for us to create those improvements.

Paper prototypes

We each individually generated paper prototypes with varying degrees of emphasis placed on the filters, CV creator/editor, application process and chatbot. We went through each prototype together and identified the strengths that could be brought to the combined prototype. All prototypes from this stage can be found here.


The initial wireframes created were based off the group paper prototype and can be found here. They included an illustration depicting our chatbot, which was removed based on lecturer advice.

Home page
Filters page
CV upload screen

Final digital interactive prototypes

Our digital interactive prototypes cut down on our task because we had created a process that was too large for us to achieve within the project timeframe. As such, it was reduced to finding a job that was interesting, with and without the chatbot. We explored the potential of using BotSociety for our prototype, however we ultimately decided to stay with Figma as we opted for a method that didn’t employ Natural Language Processing.

The first iteration can be found here and the second iteration can be found here.

Filters sample
Chatbot interaction
Onboarding screen

How and why interaction design principles and patterns were selected and applied to final product

Throughout the redesign of the selected pathway of Indeed we considered the design principles and patterns that we would implement. Some of the principles defined by Jacob Nielsen that we used, and where we used them, are as follows:

Prevent errors if possible: In the chatbot, we made the response options buttons. This prevented errors that may occur through typed responses that the bot would struggle to understand such as misspelling. We initially were pursuing the route of a Natural Language Processing bot, though we diverted from this pathway due to the potential for errors to occur, thus frustrating the user.

Maintain consistent standards: We used Google Materials to include icons and materials that users would understand from the use of other apps.

Ensure users can easily undo/redo actions: There are “back” buttons or “X” buttons on screens or elements that users can use to end the operation if desired and a navbar for users to leave their current position and return to a previous one, such as Home.




Love podcasts or audiobooks? Learn on the go with our new app.

Reflection Point: Patterns and flows

More ‘e’

Challenge 01 : Design Thinking

“Onward” — A Media Design Thesis Project

I Ran a Design Exercise as a UI/UX Intern

Man pointing at whiteboard full of post-it notes during a meeting

Wireframe Challenge

Is it Worth Modelling Your Projects in 3D?

Fitt’s Law in User Interface

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Liz Nolan

Liz Nolan

More from Medium


Bebé or not a bebé?

Hermit Crabs

NFUP, Registered on CMC(CoinMarketCap)