3 steps to increase user adoption and ROI: #1 Use Simple Terms

Step #1: Describe the business problem and solution using simple terms

User Adoption - Simple is BeautifulI dare you.

I dare you to ask someone to describe their current project to you.

If you take me up on my dare, you’ll probably hear the person ramble on much longer than necessary. When they’ve finally finished talking, you will most likely not have a very good understanding of the business problem or how the project intends to solve it.

Why is this?

Here are three reasons why this is the case.

1. We are not prepared with a well-structured explanation of our projects (yes, the concept of the Power of a Canned Response works here too).

2. We don’t focus on the problem-impact-solution-benefit combo (focusing too much on the solution).

3. We tend to over complicate explanations, and if we are in a technical role, we often overuse technical terms.

Meet Max and his not-so-great project description

Max is in a meeting with a group of people, which includes stakeholders for a new project that he’s recently been assigned to lead. The discussion turns to a challenge that relates to the scope of Max’s project. He decides it would be helpful to provide a description of his project to the group.

Here’s what Max says:

“I just got assigned to lead a project that . . . uh . . . kinda relates to this. We’re in the process of working out the details right now, but um . . . uh . . . well basically,  we plan to create a  . . . um . . . a SharePoint portal [author’s note: if this sounds like you check out my post Killing the dumb um]. We are going to leverage AD FS, so SSO should be handled. Anyway, it will support streamlined access and collaboration on documents especially with the SSO piece.  We are going to allow access to documents currently housed in distributed data repositories. I think the plan is to support both internal docs and docs at partner sites . . . well for most partners as a few have a better solution already. Anyway, we’re also going to leverage the workflow features of SharePoint too. You can do a lot with that. Um…I guess that’s all…<trailing off>. Oh, and we’re thinking about . . . . oh . . . I think I already mentioned that. Anyway, it should be pretty cool.”

It should be pretty cool?

Are you kidding me?!

Max was just speaking to a room full of people that included stakeholders for his project, and he ends with “It should be pretty cool.” Actually, that’s the least of the issues with his message. Let’s take a look at the bigger ones.

[Read more…]