In every role that I’ve had, I’ve had to remind myself and my team that we are not our users. \u00a0When you’re a software engineer creating a software application, it’s very easy to see yourself as the user. \u00a0It was true when I worked at IBM on databases, it was true when I worked at Microsoft on Office:Mac, and it was true when I worked at VMware on vSphere.<\/p>\n
In each of those instances, while we as the application development team did use our applications in one way or another, we weren’t representative of our real users. \u00a0We had more knowledge of how computers and software work in general. \u00a0We had more knowledge of how our specific applications work, and many other related applications too. \u00a0We were far more likely to use our software deeply. \u00a0When I was at Microsoft, I learned that, as an organization, we sent and received significantly more email than other organizations of our size and general structure. \u00a0This meant that I couldn’t project from my usage of Outlook to other users. \u00a0I had more email, I had more folders, I had more events on my calendar, and I was far more likely to use deep features in that application.<\/p>\n
I find myself having a similar conversation in healthcare user experience. \u00a0We are very patient-focused. \u00a0Being patient-focused is excellent. \u00a0We have a lot of empathy, which is also excellent. \u00a0In using the term “patient”, we can project ourselves into the situation — after all, we’ve all been patients at one time or another. \u00a0My doctor refers to me as her patient, even when I’m just in for a checkup.<\/p>\n
But I am not the patient here. \u00a0When I project myself into the patient’s situation, it is easy to forget that I probably differ from the real patient. \u00a0I am a reasonably healthy and well-educated 39-year-old married woman in Silicon Valley. \u00a0Not only that, but I have also learned quite a lot about how healthcare works in the past few months. \u00a0Most patients don’t have the benefit of the knowledge that I have acquired. \u00a0And if I’m considering the user experience for the patient, they are probably not, or are no longer, a reasonably healthy person.<\/p>\n
This point is very important. \u00a0Someone who is reasonably healthy is better able to make well-informed decisions. \u00a0We have a limited amount of cognitive resources available. \u00a0There are only so many decisions that we can make in a day. \u00a0That’s why habits are so powerful: a habit is (at least!) one fewer decision to make in a day. \u00a0If you always have a latte and a banana on your train ride to work1<\/a><\/sup>, you don’t have to expend cognitive resources thinking about what to have for breakfast that day, and thus you have more cognitive resources to use later in the day. \u00a0People who are in pain or who are stressed have fewer cognitive resources available to them than people who aren’t in pain or stressed.<\/p>\n In creating a healthcare user experience, I have to remember that our patients have probably had a life-altering diagnosis. \u00a0They could have had a long and difficult journey to get to that diagnosis. \u00a0They are probably tired, and in pain, and stressed. \u00a0They are already dealing with a difficult situation. \u00a0We have to create a healthcare user experience that doesn’t have an undue cost of cognitive resources at a time when the patient has few, if any, to spare.<\/p>\n In every role that I’ve had, I’ve had to remind myself and my team that we are not our users. \u00a0When you’re a software engineer creating a software application, it’s very easy to see yourself as the user. \u00a0It was true when I worked at IBM on databases, it was true when I worked at … Continue reading you are not the user<\/span> \n