{"id":230,"date":"2015-02-16T16:32:40","date_gmt":"2015-02-16T16:32:40","guid":{"rendered":"http:\/\/www.minotaurdesign.com\/blog\/?p=230"},"modified":"2021-04-06T14:10:05","modified_gmt":"2021-04-06T14:10:05","slug":"users-way","status":"publish","type":"post","link":"https:\/\/www.minotaurdesign.com\/blog\/2015\/02\/16\/users-way\/","title":{"rendered":"It’s Users All The Way Down"},"content":{"rendered":"

Sometimes in the process of defining your users, you\u2019ll discover that, much like turtles<\/a>, there are layers upon layers of them just waiting for their stories to be told.<\/p>\n

Background<\/h2>\n

Joining a company<\/a> late in 2014 as their new UX professional (and founding member of a growing team) has been an eye opening experience. Not only have I been able to finally practice what I\u2019ve been preaching and learning the last few years, but I\u2019ve been exposed to the healthcare industry – which is entirely new to me. Tons to learn = tons of fun.<\/p>\n

Anyone in experience design must carefully consider their users\u2019 goals, circumstances, capabilities and habits. This is one way for us to get out of our own heads and as far into our users\u2019 heads as possible – avoiding the trap of designing for the users we\u2019re most familiar with: ourselves.<\/p>\n

Identify the users we\u2019re serving is a great place to start.<\/strong> This sounds simple and it can be – but it can also be a complex puzzle (with all the edge pieces hiding and the corner pieces eaten by your dog.)<\/p>\n

What my company does<\/h2>\n

At a high level, we provide a secure and efficient communication platform for the healthcare industry. The platform helps patients, practice staff and hospital staff efficiently contact physicians.<\/p>\n

The problems we solve:
\n<\/strong><\/p>\n

    \n
  1. handling the bazillion ways that physicians within a hospital or practice setting need to be contacted depending on situational context.<\/li>\n
  2. sending information to a physician in a way that is secure and does not violate laws around the privacy of protected healthcare information (PHI).<\/li>\n
  3. maintaining a fine balance between the needs for privacy and accessibility on the part of the physician.<\/li>\n<\/ol>\n

    Who are our users?<\/h2>\n

    User (Turtle) #1: Our external users<\/h3>\n

    This group includes doctors, nurses, acute care staff<\/strong> and hospital \/ practice management<\/strong>. They\u2019re the obvious answer to the \u2018who is our user\u2019 question – the system was designed to meet their needs and everything revolves around maintaining and enhancing the capabilities that our platform extends to them.<\/p>\n

    If we push out a buggy feature or misjudge the utility of an enhancement and sacrifice something more vital, these are the people who feel it the most. We should be in close contact with representative members of this group, testing things out and gathering feedback constantly. This group will (and should!) receive the highest prioritization when it comes to evaluating features, to doing user research and to planning and executing usability testing. That said, don\u2019t stop here!<\/p>\n

    User (Turtle) #2: Patients<\/h3>\n

    Our healthcare professionals are themselves serving another group of users: their patients<\/strong> at member hospitals and practices across the country. These are the folks that our external users are under oath to care for, and who they went to school for a dozen years to serve.<\/p>\n

    This is the group who pays the price for inefficient communication practices. It\u2019s the folks who have seen their premiums and deductibles climb year after year and who in too many cases don\u2019t have insurance at all. They pay dearly for any healthcare they receive. This is you and me, when we visit our family doctor or when we land in the emergency room after falling off the roof in an ill-advised attempt to save money on chimney repair.<\/p>\n

    While we can\u2019t prioritize designing for this group over the others, we should always consider the impact of our decisions on these people.<\/p>\n

    User (Turtle)#3: Internal Users<\/h3>\n

    We have another group of users not immediately obvious to the naked eye: our internal users<\/strong>. These are the folks that use a suite of applications to onboard new external users and that support their needs on a 24\/7 basis, 365 days a year.<\/p>\n

    They don’t use the exact same set of tools as our external customers, but they’re touching the same data and hitting the same systems. Their needs are also much more diverse since they service every type of external user and must become experts in the task flows for those users. This is no small feat, as the training required for these folks to become proficient runs from a full week to a staggering 3 months.<\/p>\n

    When considering the needs of this user group, striving to avoid introducing further complexity is a big priority. Beyond that, a large part of your backlog might revolve around taking steps to reduce that complexity even further (and therefore lighten the cognitive load of using the system).<\/p>\n

    If you\u2019re in this situation, your company\u2019s bottom line could be affected nearly as much by internal facing changes<\/em> as it is by changes that affect your external users.<\/p>\n

    User (Turtle) #4: Executive Team<\/h3>\n

    You\u2019d think we had all the bases covered, but there\u2019s actually one more group of users to touch on. Let\u2019s call it the owner\/executive team<\/strong>, made up of company ownership and senior leadership in both your external users\u2019 companies and your own organization.<\/p>\n

    The goals and tasks of this group tend to be pretty straightforward, and sometimes seem pretty far removed from what the other three groups of users are concerned with. That said, while I don\u2019t recommend placing too much weight on designing for this group, I do believe it\u2019s a mistake not to consider their needs. Pulling off a win-win effort that enables this group to hit their goals tends to be a self-reinforcing success for a company.<\/p>\n

    Wrap Up<\/h2>\n

    If you only take one thing from this article, know that accommodating anything less than every group of users in your designs is a Bad Thing.<\/p>\n

    Imagine that your executive team has seen the effect that your team\u2019s UX design and development work has had on the bottom line – and so they foster a culture that values and encourages such efforts on an ongoing basis. This belief is folded into the company\u2019s core values, and soon the sales, support and product development teams are all on the same page.<\/p>\n

    Your external users consistently see improvements, enjoy using your product and feel that their feedback is valued and acted upon. Inevitably these happy professionals pass those benefits on to their own customers . For our patients user group that manifested through cost savings, less time in the waiting room or waiting on a surgery date, and better quality of care.<\/p>\n

    Your internal users don\u2019t have to jump through hoops to support the customers since the support tools they have been given are performant, intuitive and easy to use.<\/p>\n

    Wouldn\u2019t that be a beautiful place to work? Are you ready to make it happen?<\/p>\n","protected":false},"excerpt":{"rendered":"

    Sometimes in the process of defining your users, you\u2019ll discover that, much like turtles, there are layers upon layers of them just waiting for their stories to be told. Background Joining a company late in 2014 as their new UX professional (and founding member of a growing team) has been an eye opening experience. Not … Continue reading It’s Users All The Way Down<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[23,2,4,19,20,21,3],"tags":[34,69,67,68,28,66],"class_list":["post-230","post","type-post","status-publish","format-standard","hentry","category-communication","category-design","category-development","category-information-architecture","category-interaction","category-usabillity","category-visual-design","tag-design-2","tag-interaction","tag-product","tag-product-development","tag-user-experience","tag-users"],"_links":{"self":[{"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/posts\/230","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/comments?post=230"}],"version-history":[{"count":9,"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/posts\/230\/revisions"}],"predecessor-version":[{"id":323,"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/posts\/230\/revisions\/323"}],"wp:attachment":[{"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/media?parent=230"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/categories?post=230"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.minotaurdesign.com\/blog\/wp-json\/wp\/v2\/tags?post=230"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}