{"id":10106,"date":"2016-04-12T10:50:56","date_gmt":"2016-04-12T15:50:56","guid":{"rendered":"http:\/\/www.mrc-productivity.com\/blog\/?p=10106"},"modified":"2023-03-13T16:17:22","modified_gmt":"2023-03-13T21:17:22","slug":"9-tips-for-building-business-applications-that-users-actually-use","status":"publish","type":"post","link":"https:\/\/www.mrc-productivity.com\/blog\/2016\/04\/9-tips-for-building-business-applications-that-users-actually-use\/","title":{"rendered":"9 tips for building business applications that users actually use"},"content":{"rendered":"

\"Education\"Summary: For many organizations, user adoption is a big problem. Developers spend months building applications that the users requested, only to see low adoption rates upon completion. How can your business can address this problem? How can developers deliver business applications that users actually use? In this article, we explore 9 tips for improving user adoption. <\/em><\/span>
\n<\/a><\/p>\n

\"photo
photo credit: Marco Bellucci<\/a> via photopin<\/a> cc<\/a><\/figcaption><\/figure>\n

User adoption is frustrating problem for IT departments. Sometimes, it just doesn\u2019t make sense.<\/p>\n

The process often goes something like this: The business users request a solution. The development team gathers requirements, and then spends month building the solution. They deliver an application that perfectly fits the specifications.<\/p>\n

And then, the same users who begged for that application don\u2019t use it once it\u2019s built.<\/p>\n

This process is both frustrating and wasteful. Think of all the hours that went into building those business applications. Think of all the effort that the developers could have spent on other tasks.<\/p>\n

Why does this happen? Or, perhaps a better question: How can you fix it? How can you improve user adoption for your business applications?<\/p>\n

Today, let\u2019s answer those questions. Here are 9 tips for creating applications that users actually use.<\/p>\n

1. Understand the squeaky wheel rule<\/h3>\n
\"photo
photo credit: jackmac34<\/a> via pixabay<\/a> cc<\/a><\/figcaption><\/figure>\n

Sometimes it feels like \u201ceveryone\u201d requested an application, but then only a few people use it once it\u2019s complete. Why does this happen?<\/p>\n

One possible answer: Maybe everyone wasn\u2019t asking for it.<\/strong><\/p>\n

The first step in creating an application that people use, is understanding who is asking. Or, perhaps more importantly…who ISN\u2019T asking for it.<\/p>\n

In every organization, you\u2019ll find \u201csqueaky wheels.\u201d These are users who make far more (and often louder) requests than the average user.<\/p>\n

The problem is, a few \u201csqueaky wheels\u201d give the impression that the majority of users want a solution–when in reality you have a handful of users making all the noise.<\/p>\n

\u201cIt\u2019s unlikely a large number of potential users were consulted or surveyed about the prospective app,\u201d says Nigel Ravenhill<\/span><\/a>, a Marketing Consultant. \u201cRather, I imagine that it is a small number of vocal champions for the idea that pushes the project forward. The needs of the masses, whose adoption behaviors and lack thereof lead to low adoption rates upon completion, are often insufficiently considered.\u201d<\/p><\/blockquote>\n

2. Identify the primary users<\/h3>\n

With some projects, the developer follows the specifications to the letter. They deliver a solution that perfectly fits the requirements. It\u2019s a perfect fit.<\/p>\n

Then, the users don\u2019t use it.<\/p>\n

What happened? Sometimes, it\u2019s the simple problem of requirements that were created by a non-user. Maybe the department manager created the requirements on behalf of the users in his\/her department. Maybe they weren\u2019t designed by a primary user.<\/p>\n

As explained below, if you want to create applications that users adopt, you must first identify, and speak to the primary users.<\/p>\n

\u201cThe problem many developers run into when creating business applications is that every aspect of the design, from feature-set to user interface, is designed with the buyer in mind,\u201d says Marko Kovac, CEO & Co-Founder, Repsly Inc<\/span><\/a>. \u201cIn many cases, the buyer is neither the primary, nor the sole user of the product within their organization. When it comes time for the end-user to use the product, they are often left feeling as though they are completing an additional task on top of their regular workload. The application offers these users no additional immediate benefits, and so engagement remains low, eventually petering out.\u201d<\/p><\/blockquote>\n

3. Understand the user’s needs (Don\u2019t assume you know better)<\/h3>\n

One of the primary stumbling blocks in development projects is communication. The goals, needs, and expectations of the project are not clearly defined before starting the development phase.<\/p>\n

What happens? Sometimes the users expect developers to read their minds. Other times the developers (incorrectly) assume they understand the requirements.<\/p>\n

Still other times, the developers believe they can create a solution that’s even better than what the user requested. After all, developers understand the potential capabilities of an application better than users ever will, so they can create a far superior solution…right?<\/p>\n

The problem is, this “better” solution doesn’t always match up with the user’s expectations. If you want to build an application that users actually use, truly understand their needs–and then create the solution they request.<\/p>\n

\u201cEvery developer has great ideas and concepts,\u201d says Anthony Jullien, Director of IT at Dupray Inc<\/span><\/a>. \u201cGuess what? The majority of people don\u2019t think like we do. We are extremely left-brain people. Remember that your ultimate goal is to make the user happy. If he or she isn\u2019t, then they won\u2019t be using your app.\u201d<\/p><\/blockquote>\n

4. Observe the actual end users in their native environment<\/h3>\n

Now, maybe you identified the actual users. You received specifications directly from them. You understood their needs and goals.<\/p>\n

Yet, they still don\u2019t use the application. Why?<\/p>\n

These conversations often get lost in translation. Sometimes the users don\u2019t properly explain their needs, or they don’t know exactly what they want. Other times it feels like the users and developers are talking two different languages.<\/p>\n

How can you avoid this miscommunication, and the wasted time associated with it? As explained below, first-hand observation is a great way to understand user needs.<\/p>\n

\u201cObserve the actual end users in their native environment (i.e. the place where they actually use, or will use, the application),\u201d says Geri Winters, Author of “Why Agile is Failing at Large Companies: (and what you can do so it won’t fail at yours)<\/span>“. \u201cDo this before designing a solution. Importance: You will see things in the environment that no one will ever think to tell you but that will be extremely important to the adoption of the solution.\u201d<\/p><\/blockquote>\n

5. Get actual users involved early<\/h3>\n
\"photo
photo credit: nuggety247<\/a> via pixabay<\/a> cc<\/a><\/figcaption><\/figure>\n

Let\u2019s suppose that you identified the actual users, gathered requirements, and even observed them in their native environment. Then, you create and deliver the application…and still see poor adoption.<\/p>\n

Here are a few issues that can cause this problem:<\/p>\n

First, some requirements can still get lost in translation, resulting in an application that doesn’t meet the user\u2019s expectations.<\/p>\n

Second, after seeing the application, the users realize that their requested solution isn\u2019t exactly what they need.<\/p>\n

Third, sometimes their needs have changed from the time they requested the application until it was developed.<\/p>\n

How can you avoid this issue? Take an iterative approach to development. Get the actual users involved from the start. Create a minimum viable product (MVP) and get user feedback early. Your goal is delivering a usable application quickly, getting feedback, and adjusting along the way.<\/p>\n

\u201cThe user adoption problem is much easier solve than most people think when it comes to delivering business applications that people actually use,\u201d says John Geletka, EVP of Digital Strategy at Duffy<\/span><\/a>. \u201cBusiness users spend more time with their applications in front of screen than any consumer and therefore they need special attention when it comes to the design and development. Getting a business user, not just the owner involved in the design through rapid prototyping and testing and beta programs always makes a difference. This extreme level of involvement can be uncomfortable to some, but it always creates a more well rounded application that people will use because they feel they\u2019ve had a part in the creation.\u201d<\/p><\/blockquote>\n

6. Copy from the best<\/h3>\n

Over the past decade or so, the importance of interface design has skyrocketed. With the rise of easily accessible, simple applications, user expectations have risen dramatically. They expect the same level of usability they get in their consumer applications.<\/p>\n

The problem is, many developers don\u2019t have the luxury of working with interface designers on their business applications. They\u2019re in charge of the application, as well as the look and feel.<\/p>\n

How can they develop an application interface that users enjoy? Here\u2019s one tip: Don\u2019t try to reinvent the wheel. As explained below, you have plenty of great options to mimic. Examine the most popular applications you can find, and take interface ideas that you can use in your application.<\/p>\n

\u201cIt\u2019s quite easy to take an app that\u2019s popular \u2013 to understand why it\u2019s popular, then leverage the experience,\u201d says Lewis Daniels, Founder of Salvador Partners<\/span>. \u201cEven if one is selling ice cream and your app is boring accounting software \u2013 make sure your thumb buttons slide, getting to settings feels natural \u2013 the colours suite your audience. Too many people try to get overly creative \u2013 learn from the guys who have spent millions on researching why a button goes there. You don\u2019t see a car with its steering wheel in the back seat. (yet anyway)\u201d<\/p><\/blockquote>\n

7. Identify the application champions<\/h3>\n
\"photo
photo credit: PublicDomainPictures<\/a> via pixabay<\/a> cc<\/a><\/figcaption><\/figure>\n

In my experience, companies who are most successful with user adoption share a common characteristic: They have a product champion. They have someone within the company who takes the reins and drives the solution forward.<\/p>\n

How important is a product champion? I\u2019ve seen projects go from near failure to raging successes as a result of a product champion. Companies who were about to abandon the application suddenly find that it\u2019s an integral part of their business. Why? Because someone stepped up and became the product champion.<\/p>\n

\u201cWhen talking about enterprise apps, it can get a little complex,\u201d says Victor Sanchez, Product Manager at ForceManager<\/span><\/a>. \u201cYou need to understand that applications often bring about large corporate change (digital transformation) within the businesses you\u2019re trying to help. And change is not always welcomed with open arms. There are key players involved with implementation that need to be convinced of the app\u2019s ability to positively transform their business. Make it clear that it aligns with their corporate culture and by implementing the application they\u2019ll save \u201cX\u201d amount on \u201cY\u201d and increase \u201cZ\u201d amount by \u201cX\u201d.\u201d<\/p><\/blockquote>\n

8. Invest in onboarding<\/h3>\n

When you boil it down, low user adoption rates typically stem from a couple of problems: Users either don\u2019t understand how the application will help them, or they don\u2019t understand how to use it.<\/p>\n

In the previous points, we\u2019ve explored ways to create applications that fit the user\u2019s needs. But, even the most useful application in the world is unused if they don\u2019t know how to use it.<\/p>\n

To truly improve user adoption, don\u2019t skimp on the onboarding process. Set up training that not only teaches users how to use the application, but also explains how it helps them solve problems that they face.<\/p>\n

\u201cIt\u2019s crucial that developers invest time and effort in the onboarding process of their application,\u201d says Julian Rothkamp, CMO at fournova<\/span><\/a>. \u201cWhile you are familiar with your software, it\u2019s unknown territory for a new user. A well-thought-out setup wizard as well as a helpful product documentation will considerably increase the adoption rate of your application. Users will be more likely to experience the value of your product and integrate it into their tool chain.\u201d<\/p><\/blockquote>\n

9. Set up proper analytics<\/h3>\n

Sometimes the users don\u2019t take the time to provide adequate feedback on the application. They just use it, abandon it, and move on…all without telling the developer why.<\/p>\n

As mentioned above, getting the users involved early is critically important. That input is necessary in the application development. But, also set up analytics to observe how users use the application. It will help you understand where they\u2019re struggling, and what areas need work.<\/p>\n

\u201cPerhaps the most important thing is analyzing performance and defining what counts as success and what is failure,” says Gal Shvebish, VP of Product at Moburst<\/span><\/a>. “If the product does not reach the goals set in terms of performance, user satisfaction or functionality, proper analytics should help you pin-point the issues before it gets too late and users lose faith in the product.”<\/p><\/blockquote>\n

Summary<\/h3>\n

These are just 9 tips for improving user adoption, but the list could certainly be much longer. If you would like to add anything to this list, I\u2019d love to hear it. Feel free to share in the comments.<\/p>\n","protected":false},"excerpt":{"rendered":"

Summary: For many organizations, user adoption is a big problem. Developers spend months building applications that the users requested, only to see low adoption rates upon completion. How can your business can address this problem? How can developers deliver business applications that users actually use? In this article, we explore 9 tips for improving user …<\/p>\n

9 tips for building business applications that users actually use<\/span> Read More »<\/a><\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-global-header-display":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","slim_seo":{"title":"9 tips for building business applications that users actually use - mrc's Cup of Joe Blog","description":"Summary: For many organizations, user adoption is a big problem. Developers spend months building applications that the users requested, only to see low adoptio"},"footnotes":""},"categories":[8],"tags":[15],"class_list":["post-10106","post","type-post","status-publish","format-standard","hentry","category-education","tag-web-development"],"_links":{"self":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/10106","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/comments?post=10106"}],"version-history":[{"count":11,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/10106\/revisions"}],"predecessor-version":[{"id":14688,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/10106\/revisions\/14688"}],"wp:attachment":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/media?parent=10106"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/categories?post=10106"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/tags?post=10106"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}