Recently, while working on a client project, the planned desk reference was called into question. Should we print it? This one deserves some brief background.
The users are executives who are launching a blog. Most in the group are very technically savvy, but let’s face it, don’t we all grab for the print when we’re on one screen and don’t want to open three more to learn how to do it? User research shows that a simple printed desk reference aids users in learning and retaining new software functions. They may not use it after a few weeks, but it jumps starts learning.
Now, this does not need to be fancy – not branded or overly designed. Just readable. It’s about the content in this case. Can I pick it up and immediately get what I need? It requires great headlines, subheads and bullets for scanning. Â
Such a tool can be especially useful for users who travel a lot. They may be on a poor connection and not want to access other pages for the how-tos. Just toss the small reference piece in their briefcase and off they go. Especially if they can do what they need to through their phone, such as a new blog post from their phone. Who wants to log in to get to all the how-to content?
We consider a desk-side print piece a best practice when helping users, at any level, learn new software functionality. It’s a small investment in getting productive faster.
Recent Comments