Week4. Testing & Iteration
After 3 weeks of research and prototyping, my team has come up with some creative solutions. Evaluating design ideas is one of the most difficult parts of the design process. In some cases, designers are too subjective when choosing a design concept, failing to consider whether it will actually solve the user’s problem. Also, it’s common that they do not spend enough time analyzing competitors, which leads to recreating a similar product that works less effectively. To select the best solution, we researched some design methods and decided to use the MosCoW method to prioritize ideas.
The acronym MoSCoW represents four categories of initiatives: must-have, should-have, could-have, and won’t-have, or will not have.
We did a quick session to write down features and characteristics of our solution, and decided to move forward with “Must Have”.
Assumption:
By allowing people to make their own name badges upon visiting a clinic, we can promote LGBTQ community recognition and acceptance, and strengthen human connections between healthcare providers and patients.
To further examine our assumption, we were suggested to do quick user testing. However, due to time limitations, we couldn’t have anyone from our target user group to help us with it.
Although gaining feedback from our target audience is crucial, we figured our second choice is conduct usability testing on non-target audiences because:
- Design should ultimately apply to all patients during their hospital stay, so the experience is designed for them all.
- LGBTQ patients do not wish to be excluded, so only thinking about their experiences in the hospital environment could lead to undesirable results.
As for usability testing, we will separate it for non-LGBTQ users and LGBTQ users, and our first test will be for non-LGBTQ users.
However, when it comes to user testing, a lot of concerns come to mind when we look at our prototype.
- Do users feel like displaying their identity in the hospital environment?
- What information should users put on their name badges?
- How much time does it take to complete a name badge design and execution?
- What format is the most suitable for the name badge?
- What devices and tools are needed in this process?
- Does it interfere with the existing check-in process?
We felt hesitant to test out our initial prototype, so we spent more time refining it until we created the entire user journey.
Touchpoint:
Version A: Desktop + Physical name badge
Version B: Mobile App + Physical name badge
As we do not know what devices are currently being used for NYULH patient check-in, we created desktop and mobile versions. After A/B testing, we will decide which one to keep.
User flow A
User flow B
Next Step
We plan to use Maze and Useberry for remote usability testing. I personally have great experience with both especially for non-moderated testing. And we will make iterations based on the testing results.
