Quick-Start for heart procedures
I helped design and build an app for a local Minneapolis health system that helps patients manage everything they have to know and do before and after a heart procedure.

This has been helpful to nurses and patients consolidate a large amount complicated instructions that was typically printed by nurses, curated on an inconsistent basis to be given to patients, and then managed by patients in a physical binder.
When we launched the app, we also provided a quick-start guide for nurses who needed to understand how the app works, and how to help patients get started with the app.
During the app build process, we were limited on what was technically feasible given our time and budget constraints. One big side affect of this was not having a "living" database to pull patients information into the app, or a way to tie that to authentication.

Because of this, a majority of the quick-start guide describe how to onboard patients and how procedure code system works because of its non-intuitive set up process.
While I lead the documentation project, I worked collaboratively with a designer to develop an outline and visualize the components we'd need to give nurses the right amount of information.
The structure of the guide followed a what/how narrative structure, first answering the question for nurses "What is Take Heart?" and then describing specifically how to create a code in their system, and how to help patients enter the code.
This process involved documenting a few basic steps in the simplest way possible. This came to life using an actionable headline with supporting detail in a body treatment to help facilitate where people may get confused.
From here, we provided FAQs to cover answers to questions about other features used in the process.
Once nurses could create a code for patients, we structured the guide to help nurses help patients. 
The patient instructions are ordered chronologically for how a nurse would onboard a patient to the app, starting with a template email we provided for them as a manual step so nurses understand exactly what they are sending.
We then separate information by use case: in some cases, patients will be downloading and using the Take Heart app for the first time to manage a heart procedure.
In our other use case, patients may already be using Take Heart, but need to enter a new procedure, or update their existing procedure.
Finally, we provide an additional FAQ for nurses related to patients entering codes to help them troubleshoot a few extra use cases and pain points we discovered in the design process.
At the end of the guide, we also provide reference screenshots of the manual onboarding process in the app in case the code process can't be used at all. This process is the same process a nurse would go through for a patient to generate a code, but the code generation helps take the strain off of patients to get started with the app.
Using an email feedback mechanism with a pilot group of nurses, we heard back that the app was designed well enough that the quick-start guide wasn't essential, but certain information in the FAQs was great to have on hand to communicate to patients.
It was also exceptionally helpful overall for nurses who were new to the healthcare system's process and didn't fully understand where to start with many of their existing process, like entering patient information to create a care plan.
This piece of documentation was a small win, but it helped prove to our client that education was a big part of launching new products.
We saw an opportunity to improve documentation processes like this by starting to document and articulate the story of the app and how to use it from the beginning of the project.
Often, this kind of work gets lots in the design process when we are so focused on solving specific problems, and this exercise helped my team see the bigger picture.
View the full Quick-Start guide using the following photo grid
Back to Top