A giant lock on top of a snowcapped mountain. The lock is open and in the keyhole is a man sitting in a brick room. The sky has hues of blue, orange, and purple.

Tackling the Maddening Problem of Digital Product Access

The access experience is broken.

The Problem of Complexity

Making the Access Experience Less Painful

First, agree with reality.

Assess your digital products right now.

  • Talk to your call center. Ask your call center to report on the number and percentage of support calls associated with passwords or log-in issues. Identify the most common complaints. Track this regularly.
  • Dig into analytics. Research analytics and/or server logs to identify recurring usage patterns around access. Consider using a third-party tool (e.g., CrazyEgg, Hotjar) to more precisely hone-in on user activity.
  • Survey your user base. Ask people directly about their sign-up, log-in, or password recovery experiences.
  • Observe and track user behavior. Observe people dealing with log-in and attempting password recovery. Don’t help. Just watch and learn.

Align your team to the problem.

  • Set responsibility. Give a small team ownership over the access experience. Be sure to include a UX pro (who may be in charge) and a content strategist.
  • Make immediate adjustments. Based on your research, start by addressing high-value, easy-to-fix issues. Break the work into small, digestible chunks, something you can turnaround in roughly 1–2 weeks.
  • Prioritize bigger fixes. Some issues will take more effort. List them by value and effort. Have your special-purpose team prioritize them. Start a formal project that addresses the top priority.
  • Iterate based on research. Make user research and careful consideration of new technical possibilities continuous. There is always more to learn. You can always get better.

Think multi-channel.

Meticulously design for failure.

  • Spend time here. People have terrible trouble understanding and recovering from errors largely because dev teams don’t pay enough attention to these situations. Carve out time on your project schedule to ensure careful modeling and testing of what happens when things don’t go as your users expect.
  • Reassess error handling from the ground up. Have your UX lead rethink how and when you display errors, what those errors say, and how users are guided from error to resolution. Do not assume you are already doing this well.
  • Test edge cases. Dev teams are practiced at accommodating rare but possible usage scenarios. Build on this by making sure all edge cases are assessed not just for proper function, but also for excellent user experience. Your UX lead can show the way.
  • Rethink everything. Immediately have a content strategist assess and rethink every single user-facing word, detail, and interaction associated with log-in failure and password recovery. Speaking of which…

Use simple, plainspoken language.

Adopt basic UX best practices.

  • Follow UX guidelines for forms. Build every form field, element, and action according to UX standards for form interaction. Many books have been written and millions of pixels devoted to defining these guidelines. Start with Web Form Design: Filling in the Blanks by Luke Wroblewski. This will get you started in the right direction. The main thing: Do not assume your forms are already foolproof.
  • Be wary of out-of-the-box solutions. Pre-made UI solutions, especially ready-to-use forms offered by content management systems, are not known for their UX rigor. Error handling and accessibility are often lacking. Customization (in this case bringing forms up to snuff) is usually difficult and time-consuming. Don’t accept expedient plug-and-play solutions at the cost of usability.
  • Make your products accessible. Log-in experiences are frustrating enough already. Don’t compound the problem by making things harder on disabled people (a much larger segment of users than you may realize). Ensure everything you make conforms to WCAG AA guidelines. Bonus: By making your product accessible, you’ll fix a host of other usability problems in the process.

Avoid common pitfalls with help content.

  • Ditch “discoverable” tool tips. We’ve all seen little icons next to form fields, perhaps a box with a question mark inside. On click or roll-over these icons expand or pop-up a dialog box to show instructions, definitions, or explanatory content. Unfortunately, these discoverable conventions are seldom found by users. They are rarely accessible and prove especially problematic on mobile devices.
  • Be judicious with contextual instructions. If you must offer field-level instructions, position verbiage immediately near relevant form fields, ensure this content is always visible, and have a professional content strategist write every word. Drastically limit word count.
  • Do not invest in elaborate Help sections. People generally visit help links as a last resort. They will often call first, even though they dread automated attendants. This should tell you something about their expectations for your glorious online help content. Even when help sections are accessed, content is often not immediately relevant or organized in a way that makes finding a solution easy. Don’t waste money here.
  • Avoid long paragraphs. Do not introduce or decorate any form, interaction, or key email with copious text. Get right to the point and stay on the point. These words are nearly always ignored. Even a sentence is often too much. Always use as few words as possible.
  • Don’t rely on “Frequently Asked Questions.” FAQ content is ill-suited for solving immediate problems. This sort of content is better for promoting high-level understanding of a product, service, or process.
  • Offer step-by-step instructions for novice users. If your product targets a mass audience, step-based instructions (in this case, for logging in and getting access) can help. Put these instructions on a separate screen and follow all content guidelines in this article.
  • Make the access process simple in the first place. It’s best not to need instructions or help at all. If your interactions are simple, headings clear, and error messages understandable, your users will have little need for elaborate directions.

Test your access process with users.

  • Test prototypes. You can test almost any process early, when work is still low-fidelity (e.g., paper sketches or rough wireframe prototypes). You’ll uncover big problems before you advance your product too far.
  • Test the real thing. Nothing stops you from testing your current, live process with real users. You are virtually guaranteed to learn something new and vital.
  • Test with disabled users. If you really want to make your products accessible, test them with folks who use screen readers or assistive technology. Just because you comply with WGAG guidelines does not necessarily mean disabled users can easily use your product.
  • Invite developers to watch. Always invite the people who write code to witness user tests. Nothing changes the mind or sparks innovation quite like watching people struggle with something you’ve built.
  • Make it a habit. User testing works best when you do it continuously, as a standard part of product evolution. Establish a regular schedule and stick to it.

You can improve the access experience.

About truematter

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store