Header Comment

This blog will keep you updated with what is going on with me, my new inspirations, and what is coming across my desk.
Please comment if you want to know more about what I am working on. Enjoy!

Showing posts with label portfolio. Show all posts
Showing posts with label portfolio. Show all posts

Saturday, April 21, 2012

Expanders – Creating a System


The Expanders - Creating the System project teaches users the methodology for creating word expansions.  The presentation is elevated by the clever use of six different Engage interactions.  This keeps the user active and thinking, rather than simply watching.  The interaction also break the material up into digestible sections, and thus avoiding information overload.

Sound interesting?  Download the ZIP, and take a closer look.


Wednesday, April 18, 2012

The HIPAA Project

With the HIPAA project I worked closely with the Legal Department.  As you might imagine, they can be a tough customer as they have a tendency to be very verbose and very adamant about how the message is to be relayed.  You will want to avoid words like ad hoc or improvisation around them.

After a few preliminary meetings, I realized that the presentation was going to be very dry and very text driven.  With this in mind, I knew I would need to break up the flow of the presentation with bright energetic images.

Five things I really like from this project are:
1.  The All-White Template – This allowed me to use colorful images without them clashing with the Presenter Template.
2.  Big images – These allowed me to create real visual interest and draw the user into the project.  Also, they helped to break up monotony of bullet-driven slides.
3.  Clustering – Clusters are the artistic bunching of small, less interesting images.  When combined they are dynamic and bring otherwise boring material to life.
4.  Do’s and Don’ts – These slides break the mold, because they don’t use bullets; a common sight in PowerPoint Presentations.
5.  Call out boxes – These draw interest to particularly weighty points.  Also, for warnings I used “pink boxes” in opposed to red text; I find this effect less jarring and more professional looking.

Let’s take a closer look:

Monday, April 16, 2012

Deployment: Independent Study Courses

Often I am tapped to provide my expertise to the development and implementation of new policies, projects, and procedures.  I think it is because of my ability to see the long view, from information gathering to completion. I find that ample time and thought are given to specific designs and messages and to what metrics to record, but at the expense of deployment methodology and sound taxonomy.  So I find my most useful role is as a deployment specialist, or in reality, the person who can envision the training from the user’s perspective.

Here is a recent Independent Study Course I put together.  It’s not flashy, but I find the users happily conform to this method much better than the other practices that have been implemented in the past.  

I have a few simple deployment rules:

1.  Deploy the information in as concise a method as possible.  
Think instructions, not lessons.  Break areas into digestible sections to which a user can return.  Promote the idea that everything they need can be found right here.  The deployment technology employed may not be the most conducive to learning, so you need to pioneer new ways to reach the user and be willing to revamp any parts that do not work.


2.  Always welcome the user.  
Most users are nervous and unfamiliar with online learning, so setting a positive tone early helps.



3.  Tell the user what they need to know to succeed and nothing more.  
I know this is near impossible, as training often has to be written before a product is released or in anticipation to other confidential changes.  However, too many distractions can lead users to remember all the things you told them to ignore.  I was pained to have to add the reference to the previous payroll system, but it was so embedded into the training materials that we decided a comment was unavoidable.


4.  Tell the user what you expect from him or her.  
These can be work-specific goals, but many times they are simple instructions.  Also, by setting time limits you encourage users to work, and not procrastinate.


5.  Do not overwhelm the user with choices. 
The Syllabus must be straight path with no deviation.  I suggest having a definitive order in which the modules of the course are to be completed.  Free or exploratory navigation is fine within a single module, but not for the course as a whole.


6.  Do not confuse the user with complicated emails or alternate training scenarios.  
In this case the Additional Training is clearly separated from the Primary Training.  Also, by including the Reference Materials as part of the course, we eliminated two emails.


7.  Anything important is worth saying more than once.  
You don’t need to explain it, just state it.

Friday, November 11, 2011

Remedy Completed

It's Friday, and the Remedy Project is done.  The extended deadline gave me the latitude to try some new techniques; and I'm excited to say, they were a success.  It's always a good feeling when you get to use all your new tools.  Also, I have to say how happy I am with the new Articulate suite. Now it is so easy to synchronize colors for a truly seamless design.


Of note: You really want to check out how I used Engage Tabs to create a Watch and then Try scenario (1:40).  The Watch It and Try It are built in Captivate. Also, I used Engage Layouts throughout the project, any linked them together nicely.