For wireframes, content is also king.
Last week, Ishaan Kolluri shared our team’s current storyboards, concepts and user flows. This week, we created the wireframes, began serious user testing and documentation for next week’s iterations.
The biggest pain point in decision-making meetings is that an important decision maker doesn’t show up. Implementation consultants need their input in order to move on with the project.
Initially, we were very focused on our process: Fix the biggest pain point as best as you can, get feedback on your solution, repeat.
So we jumped into sketching screens with layout, IA and content ideas all scrambled in.
After sketches we moved on to wireframes in order to get feedback from implementation consultants and physicians. The content we put in, was informed by our research so far. However, we didn’t know the exact questions an IC would ask. So we used questions from documents ICs used to track decisions.
Allscripts implementation consultants understood our concept. The are the primary user in mind, so that was a relief.
However, the feedback we got from physicians was mostly confusion. They focused on the content and just got confused. The text we put in was better than lorem ipsum, but it still wasn’t enough in terms of what they needed to understand our prototype. Some bits of our user testing conversations went like this:
Physician: Are those bars on the left indicators of something?
Us: No, that’s just filler text. What do you think about the rest of the page?
P: I don’t know. Do you want me to fill the survey?
The rest of the user test continued on a similar fashion.
Takeaway for us: Filler content doesn’t get you very far. Try to go as high fidelity as possible in terms of the content.
But hey, we still got a lot of insights :)
PS. A huge shout out and thanks to our Allscripts Solutions Architect for user testing for us at 5 am while waiting for his flight this morning.
