BackpackEMR
BackpackEMR reached out to get feedback and additional ideas on how to intimate future features planned as well to get additional features that may address pain points not yet Identified internally. backpackEMR's main goal is to implement a metrics module for clients for donors, related organizations, and possible future volunteers.
Stakeholder Meeting
I met with Lori Most from backpackEMR to understand how backpackEMR functions, and I identified some growth points from what she shared with me. She also came to me with an internal growth point she wants to meet. Lori wants to better enable metrics within her company to be accessible to potential volunteers, interested organizations, and donors to the start-up. Many growth areas I identified will lead into Lori’s need of a “metrics module.”
Rapid Prototyping
After sitting with Lori for a few hours, I produced a few prototypes that I felt would be beneficial to her cause and add functionality for addressing pain points while maintaining the underlying vision of a metric module.
Stakeholder Dev Follow-up
During the follow-up meeting of the stakeholder, a developer that works at backpackEMR joined us to give additional technical feedback and provided point (AGILE) estimates of each feature being prototyped. These prototypes allowed for open discussion and precise visual displays to start as a talking point for how a finished feature might look, feel, and function. After this follow-up meeting, another iteration of changes was made to the prototypes for keno analysis.
Journey Map
I created a journey map of a medical practitioner based on a persona to represent pain points and design areas of growth. It works as a visual presentation tool and a way to organize data. This tool can help bring stakeholders and developers into agreement about which features should be focused on.
Keno Analysis
For the keno analysis, I took 10 realistic and relevant features from the second meeting with the dev and displayed them in a survey with a brief introduction and asked two questions for each of the features: "How would you feel if this feature were present?" and "How would you feel if this feature were absent?” Answers ranged from “I like it” to “I dislike it”. We were then able to calculate from this data the most efficient use of dev time in terms of hours of dev work in/satisfaction of users out. This is by no means a science of the field, but it is an excellent starting point for discussion and in conjunction with other tools it works well.
Annotated Wireframes
Finally, the last iteration of the wireframes will contain an annotation alongside the static wireframes to include ideas, functionality, and additional functionality behind the design. The annotated wireframes function both as a presentation tool as well as a standalone vehicle for a report so that stakeholders and other team members have a tangible, relevant, and accessible direction to take the project.
Reflection
BackpackEMR has been making waves in medical record systems without internet being a constant- something almost any company can't say they've completed. Working with BackpackEMR has showcased the need for being fluent in rapid prototyping. Going from concept ideation to a visual talking point is needed in a fast-paced environment that is BackpackEMR