After going through the data from the user testing, interviews and discussions with the team I grouped behaviour patterns and common goals to create 2 personas. I intended to use them for this project and for them to be used by the team in future sprints.

In all honesty I didn't find them too useful. Having a summary of the users we're designing for was good but it wasn't something that I found myself returning to often. I feel that if it was more detailed, created as a group effort and used for larger projects it will be easier to see the value.

I thought it would be valuable to look at platforms that did something somewhat similar to ours and analyse how they dealt with the issue of saving and organising for quick retrieval. The three platforms I looked at were Quora, Instagram and Evernote.

Each platform uses systems that best suited to the type of assets that they need to save. Some worked better than others but testing them helped me to decide which method would work best for Medwise.ai and which elements would be most important.

Speed was important in both saving and retrieval. Reducing friction - especially in retrieval - would be vital to allow the user to work in fast paced environments like the emergency room of a hospital without much interruption.

Personalisation in Organisation would allow the user to customise the system in a way worked best for their way of working and the jargon used in their specialism.

Entering into the ideation phase, I felt that before putting pen to paper it'd be useful to define the main user journeys. These ended up being:

1. Bookmarking the Q/A set from your search results
2. Applying a tag/category to that Q
3. Being able to find and/or search that desired Q/A set

I then began to draw wireframes and sketch how these might look built on top of the platform that we already had.

This process continued into low-fidelity wireframes. Here are some examples of first adding a bookmark then tagging within the same flow.

Retrieval is main part of the function. I was debating between two different ideas; a search box with the list of tags beneath arranged by most recent used. Or an alphabet pad that the user could click and bring up tags that started with that letter. Each had their pros and cons.

I was happy to have been able to finish this project, but there are a few things I would've changed. As mentioned before, being present with the user wasn't possible. I believe a UX designer or somebody with interviewing experience may have been able to get even more useful responses from the users.

Testing my solution with users also would've been preferred. I was able to do so with the team (that included a doctor) and friends and got positive responses. Knowing how well or poorly it worked with real users in their environment would've given me unbiased data to work with.

I learnt a lot working on this project and at Medwise.ai as a whole. Things were fast-paced and what we worked on was changing week to week. I didn't have all the resources or support I wanted at times, which is understandable as people had different priorities. I now get that it's the nature of the work. Besides, it gave me a chance to improvise and do the best I could with what I had, which can only be useful as I advance in my career.