Author’s Note: This blog entry is part of a series I started to explore two of today’s most popular eLearning rapid development tools: Articulate Studio and Adobe Captivate. Here is a link to an article that contains the whole Articulate vs. Captivate series.
In the previous blog entries, we have explored the major features of Articulate and Captivate, and discussed the strengths and limitations of each tool. Of course, there really isn't a winner. As I wrote at the beginning of this series, the only answer to the questions, “Which is better?”, is “It depends.” The tools have different strengths and the best fit depends on your needs.
And for larger organizations or those with more complex or varied learning needs, the answer to the question “Which should I buy?”, is often “Both.”
Here’s a summary chart that I think will help show where I think will highlight the strengths of the two tools. Of course, some of these items can’t be reduced to a simple yes-or-no answer, so this chart reflects my opinion in some cases.
In 2012, we will see new players joining the rapid eLearning tool game. For example, Articulate Storyline and ZebraZapps are already attracting a lot of attention. There is also the possibility of new releases of Articulate Studio, Adobe Captivate, and SmartBuilder.
One of the interesting trends that we have noticed is the rise of mobile learning, and how the rapid eLearning tools are quickly incorporating functionality that gives them the potential to create mLearning content. For example, most of the new tools can publish your project as HTML 5 or in the mp4 video format. This gives eLearning developers an easier path to get a course running on Apple mobile devices such as the iPad.
I expect to see more projects developed with these new tools in 2012 and I will be using them myself for Fredrickson's Learning business. As always, I'm glad to share my thoughts and findings with you and I appreciate your comments on these blog entries.
Thanks to everyone who attended our Self-Service Nation webinar.
During the webinar, I mentioned some of the navigation and other usability problems we found during a test we did on the City of Los Angeles' website. Here are some video clips from that test, so you can see the issues firsthand:
And here's the Self-Service Nation slide deck (.pdf). Again, thank you to everyone who attended. J. Hruby and I had a great time presenting and we hope you found it informative. Stay tuned for more webinars in the Fredrickson User Experience Webinar Series.
As we learned recently, Adobe has decided to stop releasing the new Flash Player for mobile devices after version 11. With so much eLearning courseware developed using Flash-based technologies, this announcement has naturally caused some turbulence in the learning community and raised some concerns about the future of online learning technologies. I had a good conversation with one of Fredcomm's best Flash developers last week about the future of development tools and trends for both mLearning and eLearning. Here is a summary that I'd like to share with you:
While the announcement about the mobile Flash player got a lot of attention, we believe that many may be reading more into Adobe's decision than is really warranted at this point. Adobe may be changing their direction as it relates to mobile devices, but this doesn't mean the end of the web as we know it.
It is certainly time to start thinking and learning about technologies like HTML5, but announcement of the discontinuation of the Flash mobile player doesn't mean that Flash is going the way of the dinosaurs.
Thanks to everyone who attended our seminar yesterday at the Minnesota IT Government Symposium. I hope you found it helpful and informative.
For those who didn't get a copy of the handouts, you can download a copy here.
Our November 8 Fredrickson Intersect meeting featured volunteer speaker Nancy Hoffman of the Minnesota Historical Society. Nancy reviewed with us the advantages and challenges of making available the data owned primarily by public-sector organizations. When given visibility and straightforward access, these volumes and volumes of data can be reused in ways that may make a significant difference in people’s jobs and lives.
You may view Nancy’s presentation and notes here.
See you at our February 14 meeting!
mLearning, or mobile learning, is not really something new. The origins of mLearning trace back to the 1970s or even before, when people took courses using audio tapes. Today, the evolving technology has made it more feasible and effective to deliver a richer learning experience through mobile devices such as smartphones and tablet computers. Some companies even have started offering various series of training courses using employees’ iPads.
mLearning offers exciting possibilities, but there are some basic considerations and differences that I think learning professionals need to consider or understand.
With newer and better mobile computing devices coming on the market every day, it’s very easy to become distracted by the technology side of mLearning. Remember, mLearning is still learning and the needs of the learner still need to be the first consideration.
You must ask the all-important questions: who is your audience? What do they need to learn on the go? Why do they need to learn it? The learners who choose mLearning usually do so because their workplace is not a fixed location, or their work environment doesn’t provide a good setting for learning.
Also keep in mind that many learners today prefer to learn small pieces in short intervals rather than take one long course. This is especially true for mLearning fans and it requires courses to be structured differently than conventional learning offerings. Additionally, mLearning can’t always be highly interactive or media-rich, but it has to find the right balance so that it meets the learner’s needs and expectations.
Now let’s look at the technology side of mLearning – the facet that is changing nearly every day. There is a huge variety of mobile devices and many variations in their capabilities; these facts can make developing mLearning quite challenging. For example, you can view your eLearning courses on a 10.1” Android tablet without a problem. But, the same course won’t look good, or even be readable, on a 3.5” Android smart phone.
Another issue is the media players that are standard on mobile devices. As you probably have already heard, your existing library of graceful Flash-based courses won’t work on Apple mobile devices such as the iPhone or the iPad. But they will work, at various levels, on the Android devices. You may have also heard that HTML5 is a “replacement” for Flash.
It’s important to understand the current state of HTML5. HTML5 could eventually be a solution to develop and launch courses that work across mobile platforms without dependency on the players. However, right now HTML5 is still immature and it has a long way to go before it becomes standardized and functional enough to be used in the way that Flash is used today. I offer this as general view of the current state of HTML5, and only to emphasize that right now this technology is not in a position to do what many have heard that it does…or could eventually do.
Another consideration is the way that touchscreens operate mobile devices. This is a very different method of user input compared to the more traditional mouse and keyboard input methods around which most eLearning is currently designed. In most cases, course developers and designers will encounter new challenges in developing mLearning interactions. Touchscreens also introduce unique usability issues. For example, the buttons have to be big enough to allow finger touches or movements and these bigger user controls therefore have an impact on the available screen real estate. The bottom line is that existing eLearning courses cannot really be “converted” to be effectively delivered as mLearning offerings. Because of the differences in learner needs and expectations combined with the different capabilities of mobile devices, courses need to be developed or redesigned specifically to function as mLearning offerings.
Finally, let’s look at the security issues. Many of the corporate eLearning courses and talent development curricula contain confidential or proprietary information. They cannot be pushed to the learners through the public app stores as conventional mobile apps are. It’s difficult to say much more in general about security concerns with mLearning other than to point out that the considerations can change once learning products go mobile. Essentially, learning and IT professionals need to consider what (if any) security risks are presented by introducing an mLearning offering, conduct appropriate testing, and take actions to make sure the required level of security can be maintained.
Thanks again to Jed Becher, Web Coordinator at the Minnesota Department of Natural Resources, for putting together the presentation for our August 9 Intersect meeting. Also, thanks to Rachel Dobbs, FredComm’s own analytics guru, for chiming in on how the Webtrends tool works in comparison with Google Analytics.
So many of us are curious about how analytics work, what we can use them for, how we can report on them to better serve our audiences and our marketing efforts…the list goes on. Jed’s overview gave us all a great start on understanding all of these complexities.
As promised, Jed provided links (from a DNR server) to his presentation as well as to an electronic version of Portent Interactive’s coding “cheat sheet” that he passed out in the presentation. The e-version can be expanded to a larger, more readable font so that you can really use it!
Link to the PowerPoint presentation
Link to Portent Interactive’s “cheat sheet”
Also, many of you already saw the email I sent with information from Marc Drummond of the City of Minnetonka about two upcoming Association of Webmasters events. Here’s another quick shout about both of these:
See you at our next Intersect meeting on November 8!
Author’s Note: This blog entry is part of a series I started to explore two of today’s most popular eLearning rapid development tools: Articulate Studio and Adobe Captivate. Here is a link to an article that contains the whole Articulate vs. Captivate series.
In my last blog entry in this series, I explored Articulate Studio in more detail. Now it’s time to do the same with Adobe’s Captivate.
Captivate is a comprehensive rapid eLearning development tool for creating software demonstrations, interactive simulations, and quizzes. Compared to Articulate Studio, Captivate offers a better workflow to take the developer from screen recording to the process of interaction building. Most Captivate projects follow the “see it, do it” approach. In the “see it” segment section, the learners watch a recorded demonstration. In the “do it” segment, the learners complete a series of tasks in the simulated environment -- for example, adding information to a customer’s account.
Like Articulate Studio, Captivate provides the users with some essential functionality, such as customized skins so that the look and feel can be modified. It also offers text/graphic animations, audio synchronization, interactive components, and publishing options for both web and LMS delivery.
Let’s take a closer look at these features.
To enrich the functionality of Captivate, Adobe has developed some add-on applications, such as text-to-speech, widgets, a review tool, and a quiz result analyzer and aggregator. Developers can find even more add-ons from Adobe Exchange server. Articulate has a similar online community, and encourages the developers to submit their customized interactions.
The main difference that I have observed between the two online communities is that the Adobe Exchange community tends to be more willing to share code and methods for free. Of course, these are often just the starting point, the developer then needs to finish the object. The Articulate community members, on the other hand, will often offer finished enhancements such as interactions, but because these are finished objects that took larger amounts of time to create, the members often want to charge a fee.
After comparing Articulate and Captivate side-by-side, we have seen a lot of similarities and a few significant functional differences. One of the biggest differences I can highlight is the development process and the mindset it takes to get the most from these tools. In the next entry, I will conclude this Articulate vs. Captivate comparison series by discussing my views of the circumstances and uses where I think each of these tools excel.
Marshall McLuhan would have turned 100 years old last Thursday, July 21. What would he have made of a world of smartphones and Facebook and nanotechnology?
Many of us today associate McLuhan with a couple of catchphrases – “the global village” and “the medium is the message” – and not much else. Even though Wired referred to him as “Saint Marshall” back in 1996, McLuhan today is more talked about than read, but that was probably the case even at the height of his popularity in the 1960s. Northrop Frye, a fellow professor of English and contemporary of McLuhan at the University of Toronto, said in 1988, “McLuhan was celebrated for the wrong reasons in the 1960s and then neglected for the wrong reasons later.”
I don’t pretend to be an expert on McLuhan. Although I read his Understanding Media (1964) as an undergrad, it wasn’t until grad school that I came to develop a greater appreciation and understanding of him. Part of the reason for that was having a professor who was one of only a few people to have written a doctoral dissertation under McLuhan’s supervision. (Many professors warned their students away from McLuhan due either to jealousy or to a perception that he was an academic charlatan.) Part of my interest was simply a result of timing; with the rise of the Web and of globalization through the 1990s, suddenly McLuhan seemed to make more sense to people. And part of it was a kind of national pride in the global influence of a fellow Canadian.
McLuhan’s thought is subtle and complex and has been frequently misunderstood. It’s a risky venture to go into print talking about it – you don’t want to sound like the pompous prof in Annie Hall who, trying to impress his date with his deep knowledge of McLuhan’s concept of hot and cool media, gets everything wrong and then is scolded by the master himself. I happen to have Marshall McLuhan right here...
The central idea at the heart of McLuhan’s work is that, in his own words, “all media, from the phonetic alphabet to the computer, are extensions of man that cause deep and lasting changes in him and transform his environment.” McLuhan defines media broadly – you could in fact replace that term with “technology.” For example, wheels are extensions of our feet, clothes of our skin, the telescope of our eyes, the computer of our central nervous system, and so on. In extending our different senses in different ways, each medium, or technology, changes the balance of our sensorium. “Such an extension,” he said, “is an intensification, an amplification of an organ, sense or function, and whenever it takes place, the central nervous system appears to institute a self-protective numbing of the affected area, insulating and anesthetizing it from conscious awareness of what’s happening to it.” And so we are as unaware of the new environment created by media as is a fish of the water it swims in. (He once said, “I’m not sure who discovered water, but I’m pretty sure it wasn’t a fish.”)
The first great disruption of the human sensorium, according to McLuhan, came with the introduction of the phonetic alphabet, which installed sight at the head of the hierarchy of senses. “Literacy propelled man from the tribe, gave him an eye for an ear and replaced his integral in-depth communal interplay with visual linear values and fragmented consciousness.”
The next great disruption came with the printing press:
If the phonetic alphabet fell like a bombshell on tribal man, the printing press hit him like a 100-megaton H-bomb. The printing press was the ultimate extension of phonetic literacy… Type, the prototype of all machines, ensured the primacy of the visual bias and finally sealed the doom of tribal man. The new medium of linear, uniform, repeatable type reproduced information in unlimited quantities and at hitherto-impossible speeds, thus assuring the eye a position of total predominance in man’s sensorium. As a drastic extension of man, it shaped and transformed his entire environment, psychic and social, and was directly responsible for the rise of such disparate phenomena as nationalism, the Reformation, the assembly line and its offspring, the Industrial Revolution…
The third great disruption came with the introduction of electronic communications technology:
The electric media are the telegraph, radio, films, telephone, computer and television, all of which have not only extended a single sense or function as the old mechanical media did… but have enhanced and externalized our entire central nervous systems, thus transforming all aspects of our social and psychic existence. The use of the electronic media constitutes a break boundary between fragmented Gutenberg man and integral man, just as phonetic literacy was a break boundary between oral-tribal man and visual man.
In the 1960s, with the effects of electrification in general, and of television specifically, so widespread and rapid, he saw it as essential to try to understand them. Many people misunderstood McLuhan to be celebrating a new post-literate electronic age, and all of the social upheaval that came with it. This was not necessarily the case. He was not really celebrating or damning anything – he was simply trying to understand. Similarly, his concept of the "global village” was misunderstood by some as a celebration of a new electronic age in which the world would have a Coke and learn to sing in perfect harmony. But this was not at all what he meant:
“The more you create village conditions, the more discontinuity and division and diversity. The global village absolutely insures maximal disagreement on all points. It never occurred to me that uniformity and tranquility were the properties of the global village … The tribal-global village is far more divisive – full of fighting – than any nationalism ever was. Village is fission, not fusion, in depth … The village is not the place to find ideal peace and harmony. Exact opposite. Nationalism came out of print and provided an extraordinary relief from global village conditions. I don’t approve of the global village. I say we live in it.”
McLuhan saw it as his role as a teacher to make people aware of the environment they are swimming in, the extent to which that environment is created by technology, and the profound effects it has on our biases and modes of thought. If that idea no longer seems as radical or strange as it once did, McLuhan is largely to thank for that.
Reading McLuhan today is as rewarding and fascinating as it ever was. He wasn’t right about everything (I’ve written “BS” in the margins a few times), and some of his ideas seem eccentric, but he was remarkably prescient about many things. For example, if you watch and listen to this RSA Animate video of a talk by Sir Ken Robinson on changing education paradigms, the ideas Robinson presents are very similar in many respects to ideas McLuhan proposed on education throughout the 1960s.
If you have a chance to dip into some McLuhan, you will have your own illuminating moments. A good starting point is an interview McLuhan did with Playboy, of all publications, in March 1969. I’ve quoted from it in this post because it presents an accessible summary of his thinking.
Another good entry point is the collection of essays he wrote with Edward Carpenter in Explorations in Communication: An Anthology, published in 1960 and available online. (You can get a free trial for a day from Questia.
If you really want to immerse yourself, The Gutenberg Galaxy (1962 ) is probably his best work.
Then you can tell me what he would think of smartphones, Facebook, and nanotechnology.
Looking for material for a leadership development program? Working on your own leadership skills? Seeking an alternative to leadership frameworks, checklists, and theories?
Learn Like a Leader will satisfy any of these objectives. It's a collection of of essays from leadership experts edited by Marshall Goldsmith, Beverly Kaye, and Ken Shelton. Each essay is about the writer's own learning experiences and lessons. You can dip in anywhere and get something useful within just a couple minutes. And with 35 different perspectives, it's easy to find some stories to really connect with.
The editors have supplemented the essays in several ways to support the readers' learning:
I compare this book to the kind of cookbook that's a bunch of stories interwoven with a few special recipes. Much more enjoyable than a how-to book, with just enough structure to turn inspiration into action.
I was in China a week ago (for work and play) and I came across a statue that immediately caught my attention. It was of a woman with three heads and four arms. I took a picture in front of it and sent it to a group of professional pals, saying . . . I have the answer to all our problems! There is so much to learn, that three heads are definitely needed . . . and then when you learn just some of what’s needed....four hands would certainly help in the multi-tasking that follows.
Then I thought about all the learning opportunities that we have in our field. Opportunities like the upcoming event in July. Personally, I always make time for events like this in my own professional life because they provide a chance to talk and learn from colleagues as well as from whoever is in front of the room.
As the person “in front of the room” on July 21st, I’ve thought a lot about what might make this a learning event that would be useful for your organizations, and one that would be personally useful as well.
I think that all too often, we in the human capital arena are “cobblers without shoes!” We work so hard to deliver to our customers and clients that we often don’t have time to try our own initiatives on for size! So, as I design the morning, know that I have two goals in mind. First, I want to tell you about my recent thinking about one of my niche areas – career development. I’ll to tell you where my thinking has gone, and how I believe we may need to deliver the message about careers differently, and where it is indeed still the same.
I also have another goal. That is to have you think about your own careers in this fast-changing field of ours, and consider the choices you might have ahead of you. I’ll be picking and choosing from some of the thinking of my colleagues who have looked at careers in our own field, and asking some provocative questions of all of you.
I’ve heard (from the sponsor and from my good friend Richard Leider) that you are a great group who enjoy getting time with your colleagues as well as time with a speaker. I will try to honor both.
I am on the road pretty continually (making up for three weeks away) till I see you in July. If you have questions, comments or thoughts…about the wide subject of careers in the ever changing world of ours and how to develop talent….let me know. I may not be able to answer, but I will definitely ponder your ideas.
See you soon.
One of the most important activities in life in general--and certainly in business--is building and keeping a network of friends and professional colleagues. Your network will serve you well in every area of your life. At Fredrickson Communications, we believe in the importance of networking so much that we've founded and continue to sponsor groups like the Fredrickson Roundtable for Learning Leaders. We have been building this network for nearly two decades and we continually work to expand the group throughout the business community in the Twin Cities.
While JIT (just in time) delivery can work well in training situations, it's definitely not a technique that works for networking. Don’t wait until you need a network to start building one.
Here are a few tips I'd like to offer you for successful networking:
I am continually shocked at how many bright, creative people don’t make time for this important task. It may seem as if I am writing to people who are new to the business world—I’m not. I’ve coached a number of high level executives (when they have lost their jobs) who thought they didn’t have time to build a network while they were working. Wrong! It’s important to make time and to learn how to build this into a natural part of your week.
Don’t know where to start? Give your networking efforts a boost by asking yourself this: Where do my peers gather in a group? If you don't know the answer, you have your first networking homework assignment: Find out!
For example, Fredrickson's Learning Leadership Summit on July 21 will attract over 125 leadership-level learning professionals. If you are a manager, director, VP or other leader in the Twin Cities' learning community, this is where your peers will be gathering. Not only will they have an opportunity to hear Beverly Kaye, but you’ll have a morning to spend with a hundred of their colleagues. Surely each and every one of them will have the opportunity to meet several new colleagues that they would like to have lunch with.
And that’s how networks are built—one person at a time.
In my eight years with Fredrickson, usability (a.k.a. user experience testing) has always held a special interest for me. It seems like such a “no-brainer” to me to spend a very minimal amount of time and budget – relative to the overall size and budget of many projects – to make darn sure that the users of the site/system/application will be able to do what they need to do or find what they need to find. When labels or language or the organization of information, etc. aren’t quite right, the time and money wasted via user frustration, lost customers, complaints around the water cooler, help desk time, etc. (the list goes on!) is a far bigger issue.
Our Fredrickson Intersect meeting on May 10 at the City of Roseville was dedicated to showing the process of usability testing in action. Our Director of Usability Services, John Wooden, came prepared with both a recording of a previous usability testing session and scenarios to do live testing with volunteers on a member’s website. It was quite the eye-opener for many who have not experienced it before. One member said, “I really liked last week’s session. I haven’t had any experience with usability testing (I’m ashamed to say) so I learned a lot. It was particularly interesting to watch the live volunteers.”
As is the case with any project or experience, when we’re “heads-down in it,” we don’t always see the reality of it as others might. Usability testing provides the irrefutable truth – real data – around whether something is really working for the users. Another member said, “I thought the presentation was GREAT. The live demo really illustrated how usability testing with real users doing real tasks sheds light on issues/problems site owners aren’t aware of. I kept wishing there were more developers from [our organization] there to see how important it is to get user feedback early and often.”
So, in my humble but somewhat experienced opinion, take Nike’s advice and Just Do It!
Here are a few resources where you can learn more:
As always, if you’d like us to bring an eye-opening presentation like this one into your organization, please .
Introduction: Raj Alphonse is a Fredrickson Communications' affiliate specializing in learning technology consulting. This blog entry is a lead-in to the April 14, 2011 meeting of the Fredrickson Roundtable for Learning Leaders where the featured discussion topic will be "The LMS Wishlist."
Have you run into a brick wall lately? I felt like I did when I saw an article in the March issue of the CLO magazine titled, “Assessing Learning in a Post-LMS World.”
Did I read that right? Post-LMS? Is the LMS dead? The world stopped for a moment, then I felt dizzy. In disbelief I asked Google, “Is the LMS dead?” and got 16,900 results, including an article titled “Is the LMS Dead?” from CLO magazine dated September 26, 2010.
In six months CLO Magazine has gone from pondering if the LMS was dead to a dissertation on a post-LMS world. The authors assure us that a “post-LMS world ... merely means that assessing learning only utilizing an LMS is becoming obsolete.” Sad, but true, there is ample evidence to support this notion. Just spell L-M-S out loudly to a gathering of training professionals and watch the reaction. No matter what LMS they use, everyone will have at least one gripe, one horror story, one wish. Summarize the feedback, and you can see the writing on the wall: the LMS badly needs to evolve.
Can this lumbering beast get its groove back? What can we do to make the feedback heard by those who can do something? Create a blog of gripes, a book of horror stories? That would be too negative.
Instead, how about we compile an LMS Wishlist and send it to the Beast Makers? A list that spells out what you want. And what you don’t want. A list that puts the spotlight on the gaps, goof-ups, and glaring omissions. A list that points to features no one asked for. A list to transform the “monolith” mindset of LMS designers into a “modular” mindset. A list to upgrade the evolutionary effort to a revolutionary one.
There is another benefit to drawing up a collective LMS wishlist: we can learn what everyone else wants, needs, likes, and dislikes. This is the beginning of a conversation about the future of the LMS because it shows us where learning professionals want to go and what they want to leave behind.
So please make a wish and make it known. This blog entry is just for that.
All wishes are welcome; no wish is too small, too large, nor too far-fetched. There are no limits to how many wishes you can have. Wishes may be related to operation, budget, technology, infrastructure, user interface, reporting, and whatever else you have.
And hurry please, before CLO Magazine starts thinking about an LMS autopsy report.
I have more information and links to share after the last part of our Intersect group's three-meeting series about accessibility on February 8:
Full CART services transcript of the meeting: Intersect February 2011 Transcript (.txt document).
PowerPoint Presentation used by Tanya Belanger at the February Intersect meeting. (.zip format for download)
Information about the Minnesota Science Museum of Minnesota's class on PDF Accessibility. This course is Part 4 of their Acrobat training series.
Information about EASI’s webinar series on accessible PDFs.
For more useful links, see my previous blog entry on this subject. Once again, our thanks to Tanya Belanger from Minnesota's Office of Enterprise Technology for all her contributions to this valuable Intersect discussion series.
Last week I saw a demo of 3M’s Visual Attention Service (VAS), a web-based application that applies an algorithm to predict with greater than 85% accuracy what users will focus on in the first 3-5 seconds of exposure to images. The predictions are based on 3M’s 30 years of research into the science of vision and take into account factors such as color, contrast, edges, size, and the presence of human faces.
If you design in-store displays, outdoor signage, or websites, VAS is a useful tool to add to your kit. Say you have put together three alternative design mockups for a website home page, and the home page needs to convey three key messages. Because website visitors tend to be impatient and make decisions very quickly, it’s important to know what they are likely to notice within 3 to 5 seconds. With VAS you can highlight three key areas of each home page design alternative and determine how successful each one is in quickly attracting user attention. You can then tweak your design and see what difference that makes.
In the examples below from Target’s home page (image taken on February 8), you can see what VAS predicts users will quickly notice.
So how is VAS different from eye tracking software?
The big difference is that eye tracking requires human subjects to determine what people actually look at. VAS makes a prediction based on an algorithm. So the main benefits relative to eye tracking are speed and low cost. (VAS is not free though. You will likely want to buy credits if you are going to be an occasional user or a subscription if you plan to use it frequently.)
The limitations of VAS are pretty obvious. It tells you what people are likely to focus on in the first 3 to 5 seconds, and that’s all. It does not tell you whether users will like and respond to those messages or images, whether users will stay on your site, or whether your site is easy to use. It doesn’t give you a lot of insight into how your users will think or behave. For that, usability testing is still the best option. In this way, VAS is a useful tool in the same way that spellcheckers and color contrast analyzers are useful tools. It has real value during the design process, but it can only tell you so much. It doesn’t replace getting feedback directly from real users.
Let me give you one quick example that helps illustrate this point. Humans are wired to focus on other human faces – we are drawn to look at them. (Think of LinkedIn profiles – you’re more likely to look at the ones with photos.) In a similar way, we are attracted to look at anything red. The example from Target demonstrates this well. But using red or including photos with faces is no guarantee of sustained attention and interest. I ran the home page of another site that we usability tested recently (which I can’t show you) through VAS and it predicted what I expected – that the two parts of the page with images of faces would be more likely to attract attention in the first few seconds than the other parts of the page. But regardless of whether our usability test participants noticed these images in the first few seconds, their comments and behavior indicated that they were not very interested in the sections associated with these images.
Despite our inherent interest in human faces and attraction to red, it goes without saying that the answer to drawing a user’s attention is not always going to be to display a photo of a woman in red. Users are sophisticated, and though they might initially notice certain images, if they associate them with advertising, or fluff, or if they consider them to be obvious stock photos, they are likely to actively avoid them. Large text, subtle color, and good contrast can also effectively attract attention and convey key messages – it doesn’t always have to be a face photo.
Give VAS a try and see what you think. Just bear in mind what precisely it is telling you, and what it isn’t telling you.
We've posted a new article over on the Articles page: Learning Trends - Where will they lead in 2011? If you haven't already, head over there and take a look.
And now give us your comments. Or even post a prediction of your own and let us see where you think the learning and development community is headed this year.
Over to you.
Author’s Note: This blog entry is part of a series I started to explore two of today’s most popular eLearning rapid development tools: Articulate Studio and Adobe Captivate. Here is a link to an article that contains the whole Articulate vs. Captivate series.
In the first entry of this series, I started a series to explore two of today’s most popular eLearning rapid development tools--Articulate Studio and Adobe Captivate. Now I’d like to talk about each of them separately and in more detail, starting with Articulate Studio. In the process, I’ll also discuss some of the best practices that may help with your development.
Just in case you’re new to Articulate Studio, I want to mention that there are four main components: Articulate Presenter, Engage, QuizMaker, and Video Encoder. If you need info or a refresher on what each component does, have a look at Articulate’s website.
Let me start by asking you a simple question: What is Articulate Studio?
The answer I most often hear goes something like this: “Articulate converts PowerPoint to a Flash presentation.” Technically, this is a true statement and it’s one of the factors that attracts many people to Articulate in the first place—it doesn’t require much in the way of programming skills to jump on board. Although using Engage and QuizMaker requires more practice, most users can get familiar with these Articulate Studio components in a short period of time.
For those shopping for rapid eLearning development capabilities, it can seem as if all you need to develop a good course is PowerPoint content to run through Articulate and out comes eLearning. This is an especially attractive proposition for those who are tasked with “converting” instructor-led training courses to be delivered as eLearning.
The problem that I hear over and over from both eLearning developers and actual learners is that the “PowerPoint look” of Articulate courses wears thin very quickly. Something’s missing, but what?
To answer this question, I have to stray a little from talking about tools and take a quick dive into instructional design. As you probably know, the traditional use of PowerPoint is in classroom-based training, which is also called synchronous or instructor-led learning. By contrast, Articulate eLearning courses are, of course, an asynchronous (self-paced) learning experience.
You probably see where I’m headed already: even if the course contains the same content, we have to take quite different approaches once the delivery medium changes. To substitute for the richness of activities and interactions that can take place in the classroom, we need to build a new layer of richer interaction and engagement on top of the content in the PowerPoint in order to make it effective as an eLearning course. When this layer is missing, people see the course as a shallow PowerPoint presentation, not as real learning.
I know that this problem is not just an Articulate Studio problem, but because of Articulate’s direct link to PowerPoint, it seems even easier for Articulate users to fall into this trap. Remember, a PowerPoint presentation is only one ingredient. One ingredient doesn’t make a cake.
Fortunately, Articulate Studio gives plenty of options to produce a richer eLearning course that goes beyond PowerPoint. For example, Engage interactions, quiz questions, Flash movies, and even customized Flash games. In addition, Articulate allows you to deliver your content through branched scenarios, which is another effective tool to keep learners’ attention.
Articulate Studio offers a lot of eLearning potential in one package. I’m not going to do a feature-by-feature list here--you can easily get that information elsewhere. Instead, I’d like to highlight just a few of features that I think are significant and either little-known or not often used to their potential:
After this discussion of my favorite features, I feel I have to deliver a brief word of warning. I’ve been using Articulate for about 7 years now and the product has evolved significantly. Many people used to see Articulate as a simple tool that would enable anyone to develop eLearning. This may or may not have ever been true, but what has happened over time is that eLearning developers and instructional designers have demanded more and more sophistication. And Articulate has largely delivered, but this means that to get the most out of Articulate, you have to be more and more skilled as a developer to take advantage of the richer features. Therefore, I think it’s best to look at Articulate as a “development suite” and the results really are closely linked to the developer’s skill and the instructional designer's understanding of how to design learning to take advantage of Articulate’s strengths.
Since most of the Articulate courses involve an audio presentation with closed caption text, it requires a different design approach in PowerPoint. Research indicates that when audio and static text are presented at the same time, audio is the most dominant and efficient channel. Therefore, it’s often a distraction if the bulleted text repeats the audio. In many cases, it’s more effective to replace bulleted text with graphical elements like photos, illustrations, and flowcharts, and animations.1
In my previous blog entry, we talked briefly about software training. Can I use Articulate to develop this training by itself? Again, it depends how and what you want to achieve in the training. If the training only involves demonstration, you can insert a series of screenshots on the PowerPoint slides, and then spice them up with the annotation tool in Articulate. Gerry Wasiluk posted some excellent information on this topic as comments to my first Articulate vs. Captivate blog entry.
Or, you may opt to use one of the screencasts tools, for example, the Screenr. With these tools, you can easily export your screencasts to video clips, and then insert it into your Articulate course later. However, if you want to drop in a comprehensive simulation in your course, I would say that Articulate is not your best option. If software simulation and is your goal, you should consider Captivate, which I will cover in the next entry in this series.
1 Of course, a transcript should be available so that learning content can be accessed by those who cannot hear the narration.
Author's Note: This blog entry was the beginning of a series of a series I started to explore two of today’s most popular eLearning rapid development tools: Articulate Studio and Adobe Captivate. Here is a link to Part 3 of this series.
The State of Minnesota is in the midst of implementing standards to make technology accessible for those who have hearing and/or vision impairment. This is an important and massive mission, and will take many years to get to a place where true accessibility is more “the norm” than not. But every baby step counts, especially to those who rely on assistive devices or other alternate ways to access information via technology.
On Tuesday November 9, the Fredrickson Intersect group helped facilitate training about this initiative by having Tanya Belanger of the Minnesota Office of Enterprise Technology present on how to make documents and presentations accessible. This was the second session of our three-part series about this specific undertaking.
We promised to make downloads of Tanya’s presentation, as well as the Social Security Administration’s Guide to Producing accessible Word and PDF Documents – a valuable resource which Tanya discussed in our session – available, so here are the links:
The Social Security Administration's Guide to Producing Accessible Word and PDF Documents (Microsoft Word document)
PowerPoint Presentation used by Tanya Belanger at the November 2010 Intersect meeting (.zip format for download)
Jed Becher from the DNR also sent this great document about improving accessibility with Adobe's InDesign: Creating Accessible PDF Documents with Adobe InDesign CS4 (.pdf document)
Finally, here's the full CART services transcript of the meeting: Intersect November 2010 Transcript (.txt document)
Many of us have had at least one frustrating experience with an interactive voice response (IVR) system – getting lost in a maze of menu options, never hearing an appropriate option, never being offered an option to speak to a customer service representative, arriving at a dead end, getting cut off during a transfer to a representative, and so on. My father ended up shouting at an IVR system with voice recognition because it kept saying, “I’m sorry, I did not hear you. Please choose from the following options …” Eventually, he just hung up.
IVR system usability has not received nearly as much attention as Web usability, and perhaps it’s no surprise that over the years IVR systems have collectively developed a bad reputation. This doesn’t mean there are no good ones, but if you ask people, most will tell you they don’t have a favorable impression of them. Instead of being perceived as useful tools for self-service, they are commonly thought to be obstacles deliberately placed between customers and a live human in an organization’s customer service department. In 2005, Paul English was frustrated enough with his IVR system experience to publish “The IVR Cheat Sheet,” which listed the codes that would allow a caller to speak directly with a representative in dozens of companies.
If an organization’s primary objective in having an IVR system is truly not to block customers from speaking to an agent or representative, but rather to try to provide a good automated self-service experience, then it needs to take IVR usability seriously, just as seriously as it takes the usability of its websites and applications.
In most cases, this means conducting usability tests. The methodology for usability testing IVR systems and websites is essentially the same in most respects. You need representative users from your main user groups, a list of task scenarios and key questions to ask, a quiet place to test, and for IVR testing, a phone with a speaker. (You can test an IVR script before it is recorded simply by having the facilitator read prompts and asking the tester to describe which options they would select.) We also use Techsmith’s usability testing software to record the calls (with tester permission) and to capture tester actions and feedback. By observing testers and listening to their questions and comments, usability analysts can learn what is working well in an IVR system and what needs improvement.
For example, in a recent test of a government IVR system, the overall feedback we heard was positive. This was already a relatively straightforward system to begin with – most of the prompts involved a simple binary choice: 1 for yes, 2 for no. Still, the test revealed dead ends in the menu, some common misunderstandings of prompts and transitions, and issues with the password process. And so now after testing, this organization is able to make their system even better and thereby reduce the number of callers who want or need to speak with a representative.
Of course, the major design constraint of any IVR system is that it is primarily an auditory medium. IVR systems require users to listen – often closely – and each option must be presented sequentially, which places a load on the user’s working memory. In contrast, the web is primarily a visual medium that can use layout, color, font size, text, and images to organize and present information. And links can offer a user tremendous navigational control and flexibility. The ability to see information and control pacing and progress are the key reasons why more users prefer doing self-service online than through an IVR system.
Still, even within the constraints of an IVR system, it’s possible to provide a good experience by following some important guidelines:
Note: Many lists of IVR system heuristics provide similar guidelines. One especially useful source that I consulted for this entry was Bernhard Suhm's article, "IVR Usability Engineering Using Guidelines and Analyses of End-to-End Calls," in Gardner-Bonneau and Blanchard's Human Factors and Voice Interactive Systems, 2008.
Author’s Note: This blog entry is part of a series I started to explore two of today’s most popular eLearning rapid development tools: Articulate Studio and Adobe Captivate. Here is a link to an article that contains the whole Articulate vs. Captivate series.
With the rapid eLearning development tools becoming prevalent in the market, course development is getting faster and some aspects are getting easier and less costly. Among the many eLearning rapid development tools on the market, Articulate Studio and Adobe Captivate have become the most popular and widely-used among our clients.
As an eLearning consulting company, we are often asked for advice on which is best, Articulate or Captivate? This question is often asked by corporate learning groups who want to choose a standard tool for use within their company or group.
I want to note here that when I refer to “Articulate” in these blog entries, I’m referring to the full Articulate Studio package. While it is possible to buy individual Articulate products (like Articulate Presenter), I don’t think this makes sense for most needs because without the full Articulate Studio, the functionality and results would be limited.
So which is better, Articulate or Captivate? Of course, there’s no clear way to answer this question except to say “it depends”. Both tools work well in different areas and for different reasons. I’ll start this series of blog entries with the things that both Articulate and Captivate have in common. In upcoming entries, I’ll look at what each tool does well and not-so-well.
I have to add that the skill and experience of the developer does still matter. These tools are often purchased with the expectation that anyone will be able to use them to create great eLearning courses. The problem is that as developers and learners have demanded more sophistication from the courses that these tools produce, the number of features and the complexity of using these tools has increased with each new version. Whichever tool you choose, there is no substitute for knowing how to use it efficiently and effectively. The more skilled and experienced you are at using these tools, the better your results will be.
Since I’m a developer, I can’t resist starting with ease-of-development. From this standpoint, both tools are relatively easy to jump into (at least at a basic level) without extensive coding knowledge or formal training. Basically, developers use the built-in templates to build courses by adding written learning content, creating interactive components, and then adding audio, and so forth. The templates take care of the user interface, the navigation, and other features so these don’t have to be built from scratch as they would if you were developing using other technologies like Adobe Flash.
Both Articulate and Captivate have a number of features in common:
Now we come to the point where the tools start to diverge. Articulate and Captivate work differently and each tool has advantages and disadvantages when it comes to certain features and uses. To understand which tool is a better choice, you need to consider the tools in light of you or your organization’s needs, and the types of training you develop or intend to develop. You also need to consider the developer skills you possess or, in the case of a corporate learning group, the skills you have available on your team.
In the following entries, I’ll walk through what I think are the key functions of each tool, the types of training that I think they work best for, and finally I’ll give some thoughts about developer skills, publishing and deployment concerns, and other considerations.
Author's Note: This blog entry was the beginning of a series of a series I started to explore two of today’s most popular eLearning rapid development tools: Articulate Studio and Adobe Captivate. Here is a link to Part 2 of this series.
We have some video highlights from this summer's fifth annual Learning Leadership Summit. Our theme was The Power of Purpose for Learning Leaders and our featured speaker was none other than Richard Leider, the international bestselling author of The Power of Purpose.
At Fredrickson Communications, we recognize that leading a learning organization is a unique challenge. We sponsor the Learning Leadership Summit to help this special brand of leader to grow and prosper, both personally and professionally.
The Summit was a huge success again this year and we had over 100 learning leaders in attendance. Richard was a fantastic, thought-provoking speaker and, as always, the Summit is the best networking opportunity in the Midwest for learning leaders.
Are you in a leadership role in a learning organization in the Twin Cities or surrounding areas of Minnesota and Wisconsin? If you'd like to be added to the invitation list for the 2011 Learning Leadership Summit, just .
Minnesota Public Radio recently aired an interview with Matthew Crawford, author of the bestselling book Shop Class as Soulcraft: An Inquiry Into the Value of Work. I have read this book and I think Crawford provides learning professionals with a lot to think about.
It’s not possible (for me, at least) to reduce Shop Class to a simple “here’s the point” statement. The book is an exploration of how our work, and our relationship to our possessions contributes (or fails to contribute, as is more often the case) to our sense of fulfillment as people. Along the way, Crawford touches on many other issues related to education, society, and the workplace.
The book does discuss some of what the title most directly implies: our societal view of the so-called “manual trades” and the related decline in the promotion and teaching of the trades as valid and secure ways to make a decent living. Crawford also does a very good job of challenging some of the myths of modern work, for example that there’s no thinking involved in so-called “manual” trades.
One of the main concepts of the book is Crawford’s exploration of individual agency, which is an ability to observe firsthand the effects of one’s actions on the world.
As we’ve marched toward becoming an “information society” of so-called “knowledge workers” our individual agency has rapidly declined. As knowledge workers, our jobs have become largely about doing a piece of a piece of a piece of a part of the whole. In other words, many of us today do work that is largely devoid of individual agency.
This represents an almost total reversal in the millennial-long trend of our development as a species, where we constantly increased both our technology and our individual agency. We used tools of growing sophistication and saw firsthand the product of our labors with these tools. Now that trend seems to be reversing and our relationship to our material possessions and tools is also changing from a position of master to that of servant.
Or let’s be honest, if we’re talking about any device with a power cord, we’re basically slaves.
If the tools of our “information society” fail to work, we’re helpless. If the object is even meant to be repaired at all (a very big “if” these days), our only option is to call a repair professional, or trudge to the dealership or the repair shop (if such an option even exists!) and implore the tradesperson to please, please fix it. Our relationship to our possessions has devolved and in many cases we've become more helpless bystander than owner. The start of a reasoned case for the value of the manual trades, perhaps? Read the book!
Shop Class doesn’t really offer solutions, but it provides plenty by way of perspective for HRD professionals. From the intellectual challenges of manual work to an exploration of why concepts like individual agency are so important to our sense of job satisfaction and fulfillment, there’s plenty that HRD professionals can take from this MPR interview and from the book.
Here’s the interview on MPR:
And here’s the book (just out in paperback) on Amazon.
Highly recommended!
Today at our annual Learning Leadership Summit, a person at my table brought up Daniel Pink's book Drive: The Surprising Truth About What Motivates Us (2009), saying how much she enjoyed it. A couple others of us concurred, and then we tried to name the three things that Pink says are of most importance to motivation for today's workforce. We remembered the first two things--mastery and autonomy--but none of us could think of the third. After looking it up, we had to laugh at the irony. The third item is purpose, and here we were participating in a session on that very subject.
Talking about purpose is not a fad. As the coincidence between Pink's work and Leider's work shows, there is a growing body of research that identifies a link between having a purpose and being happy and healthy. And of course, there are countless examples of the difference in success between companies and projects with clear purposes vs. those without. Finally, we all know the mantra about effective communication: purpose, audience, and scope.
Check out more on the subject at these resources:
In their well-known test of selective attention, psychologists Christopher Chabris and Daniel Simons asked test subjects to watch a short video in which two teams, one in black shirts, one in white shirts, move around and pass a basketball to one other. The subjects were asked to keep silent count of the number of passes made by the team wearing white.
About 25 seconds into the video, someone wearing a gorilla suit strolls into the middle of the passing game, beats their chest, and then strolls out again. The gorilla is on screen for nine seconds. The correct answer to the question about the number of passes is 15. But the real question was “did you see the gorilla?” About half of the test subjects did not.
Watch the video: http://www.theinvisiblegorilla.com/gorilla_experiment.html
In their new book, The Invisible Gorilla and Other Ways Our Intuitions Deceive Us, Chabris and Simon discuss the “illusion of attention” and our lack of awareness about the limitations of our perceptions, memories, abilities, and knowledge. (For example, more than 63% of Americans think they are more intelligent than the average American.) Their gorilla experiment demonstrates that when we focus our attention on one object or action, we can easily miss anything else going on around it. Other experiments found that people who missed seeing the gorilla had their eyes on it, but they didn’t see it because it was not what they were looking for.
Our tendency toward selective attention has implications for web interfaces. If you have ever participated as an observer of a usability test, you may have had the experience of watching a test participant fail to see what you perceive to be an obvious link, or button, or some other interface element. Seconds, or minutes, go by while the participant struggles, and you’re thinking, “Why in the name of all that’s good and decent can they not see that link? It’s RIGHT THERE! CLICK IT!!”
Users may miss a link or some other element for all kinds of reasons – lack of white space, crowding, small font, sub-optimal contrast – but one common reason is that the link (or button, or whatever) was like the gorilla in the experiment: users didn’t see it because it was not what they were looking for. In many instances, they were looking for other words – the words actually used didn’t match their expectations. They were looking closely for X and therefore didn’t see Y. So much of usability has to do with language, with using the keywords that match what your users have in mind. And even subtle differences can adversely affect a user’s ability to find what they are looking for.
Another common reason why users miss seeing what might seem blindingly obvious to a development team is that usage convention has led the user to expect one interface element when another has been used instead, such as a link instead of a command button.
Convention also leads us to expect certain elements in particular places – primary navigation at the top or on the left, a search box in the upper right, contact information in the footer, ads or other "fluff" on the right, and so on. If a user misses an interface element, it may be because it was not in the position they expected it to be, and therefore they simply didn’t see it.
One of the great benefits of usability testing is that it helps us to understand what users were actually looking for and what they expected – where was their selective attention focused? This in turn can help us design more effectively.
What do you think? Are there other implications for selective attention?
Many of our clients are Learning & Development departments in multinational companies. Anecdotally, it seems that most recognize the need to adapt learning and development methods to audiences in different cultures, yet lack the capacity and sometimes the strategy to make such adaptations. A good place to start for learning leaders, instructional designers, and trainers might be self-education. We're compiling a reading list of books and articles about global training and cultural awareness; we'll share it on our website once we've read enough of the items to make a decent list. I'd like to recommend two books. I've read one and I've read the table of contents of the other (the 7-page TOC was enough to ascertain that the book was relevant!)
Cultural Intelligence: Living and Working Globally, 2nd Ed., by David C. Thomas and Kerr Inkson. This book neatly presents a research-based framework and provides loads of examples of workplace situations where people operating from their cultural contexts misunderstood each other and missed or misinterpreted cues. The book is organized in a way that makes it useful as a field guide--there are chapters on cross-cultural decision-making, leading, negotiating, and teamwork. Even if you just page through to read the real-life situations, you will be enlightened.
Cultures and Organizations, 3rd Ed. (just released!), by Geert Hofstede, Gert Jan Hofstede, and Michael Minkov. Geert Hoftstede is one of the well-regarded researchers and authors on the subject of society-based culture. As with Cultural Intelligence, there are numerous ways to use this book besides reading it cover-to-cover. For example, there are tables that any tech writer would admire that contrast key differences in behavior between societies that are weak or strong in a particular cultural dimension, such as individualism (e.g., the US) versus collectivism (e.g., Japan). Here are just a few ways that I think these books are useful to the L&D profession:
I'd love to add your recommendations to our list. You can find me on LinkedIn.
I wrote in the latest Fredrickson eZine about a radio interview featuring Geek Squad founder Robert Stephens. The interview itself is interesting, but it started me thinking about Stephens’ observations about smartphones in terms of how this technology will eventually change workplace learning and development.
Here’s the interview, courtesy of Minnesota Public Radio:
If you can’t see the embedded audio player on this page, here’s the interview on MPR’s website.
I’m interested in your comments. What do you think of the arrival of the smartphone age? When and how will this technology change learning in the workplace?
Earlier this week, I attended a presentation by Robert Stephens, founder of the Geek Squad. He was speaking to the Minnesota Chapter of the Entrepreneurs Organization. I was excited to hear him because I’d also heard him on Minnesota Public Radio a couple of weeks ago, and one of his comments really stuck with me--essentially that curiosity is increasingly more important than expertise in many jobs.
Over the 20 years that I’ve been interviewing people for possible employment at Fredrickson, I’ve always listened for evidence of curiosity. That tells me two things: that the person is likely a life-long learner and that he or she is resourceful and will readily look up information at the time of need.
Stephens’ point about curiosity is timely as we watch many corporate learning organizations shift from a focus on “push” methods such as courses to “pull” methods such as wikis. Being curious and resourceful will help people use these self-service tools effectively. And having curious and resourceful people in a company will be essential to that company’s ability to build and benefit from an enterprise social network.
See www.robertstephens.com for more on what he presented to EO Minnesota and on MPR.
Measuring the effectiveness of training is a continual challenge. Many questions about measurement strategies exist, especially around how to accurately measure the business impact of training. Measuring the business impact usually involves measuring the changes that occur at what Kirkpatrick’s evaluation model classifies as levels three (behavior change) and four (business results).
Here’s an example of a level three measurement strategy and how I believe it contributed to a successful business initiative:
I was the manager in charge of training for a major SAP implementation. My team developed level three evaluation checklists for many processes and tasks that were, in turn, aligned to specific business goals.
For example, one of our business goals was decreasing the time it took to complete the month-end close process. The steps of the month-end close process and who was responsible and accountable for each step were documented and each step was aligned to the business goal of decreasing the time it took to complete the month-end close process.
By providing clear ownership and the tools to measure the individual steps of the process, we were able to confirm that each step was being completed accurately after implementation. In other words, we had achieved a behavior change, which is what Kirkpatrick classifies as a level three measurement of the effectiveness of training.
The result was that the month-end close process was reduced from 21 days to 5 days. Obviously, the learning solution did not cause this reduction by itself, but nobody questioned the value of the learning component’s role in the initiative. I believe that by providing the tools for the measurement and creating the measurement framework for level three, we actually helped drive level four results—a direct impact on the business.
I’ve also learned that level three measurements provide an excellent avenue for encouraging on-the-job follow-up by supervisors and others accountable for business processes, skills, and tasks.
I look forward to hearing your comments and thoughts, both here on the blog and at my ASTD presentation on February 19.
In the world of web application and site design, there’s been a trend over the last several years toward more multi-faceted “user experience designer” roles. According to the job descriptions, these people are expected to do it all: user research and task analysis, information architecture, interface design, graphic design, programming, usability testing and evaluation, project management, business strategy, presentations, and so on.
Though there’s reason to be skeptical that many of us can be truly outstanding in all of these skills and practice areas, let’s just say that Acme Design Agency does indeed have such people. Even in that case, is it really a good idea to have the same person, or team, involved in creating a design and then evaluating the usability (or user experience) of that design?
Teams can have the best intentions, but it’s tough to look in a hard, neutral, objective way at your own work. In the same way that good writers need good editors, user interface designers need an objective, unbiased evaluation of their products. That’s why it’s important to go outside the design team – and in some cases outside the company – and have a usability analyst conduct usability testing with representative end users, or at least do a heuristic evaluation.
Otherwise, there’s a temptation to be defensive, to look for validation and reasons to keep the work that’s been done, instead of trying to uncover flaws or weaknesses in presentation, navigation, interaction, or content. Design teams are a bit like parents – they aren’t likely to call their baby ugly.* They’re just not objective. (And in the case of parents and children, that’s usually a good thing!)
I’ve had to call a few UI design babies ugly over the years – well, in so many words – and though this has sometimes stung the designers or developers involved, it’s always helped them create better interfaces. And that’s the goal we’re all aiming for.
*Thanks to our client Kathy Bohlke, UI/U Manager at 3M, for making this analogy.
At the last meeting of the Fredrickson Roundtable for Learning Leaders, our discussion topic was social learning. In the course of the discussion, several books were recommended. I’m sorry, I don’t know who recommend each book, but here they are:
Enterprise 2.0: New Collaborative Tools for Your Organization’s Toughest Challenges
by Andrew McAfee
Harvard Business School Press, 2009
ISBN-10: 1422125874
Leaders Make the Future: Ten New Leadership Skills for an Uncertain World
by Bob Johansen
Berrett-Koehler Publishers, 2009
ISBN-10: 1605090026
There may have been more, so if you have additional recommendations, please mention them in a comment.
Dan Pink’s new book, Drive: The Surprising Truth About What Motivates Us (2009), in many ways picks up where he left off in his 2005 bestseller, A Whole New Mind: Why Right-Brainers Will Rule the Future.
In his earlier work, he uses the left and right hemispheres of the brain as a metaphor for describing the rising importance of a new type of work that is more creative, non-routine, and empathic. While work that depends on logical, linear, left-brain thinking can be easily automated and outsourced, work that depends on creative, non-linear, right-brain thinking will be more valued and less easily commoditized. Think MFA, not MBA.
In Drive, Pink again looks at the way the economy and the nature of work have changed and makes the case that business is out of step with what really motivates us. This time he uses the metaphor of the operating system:
• Motivation 1.0 was all about survival. 50,000 years ago on the savannah, our operating system was pretty basic.
• Motivation 2.0 was built atop Motivation 1.0 and was (and is) all about seeking rewards and avoiding punishments – carrots and sticks. Although this worked very well for a long time, and is still useful in many instances, it’s become an unreliable operating system in the new world of work. As economies have become more complex and our skills more sophisticated, Motivation 2.0 has begun to seem less effective. (See my piece on the Big Shift for a related study on how business has been underachieving for decades now.) As Pink writes, Motivation 2.0 “suggested that, in the end, human beings aren’t much different from horses – that the way to get us moving in the right direction is by dangling a crunchier carrot or wielding a sharper stick.” But as studies in behavioral science have shown, carrots and sticks really are not the best way to motivate us. Once we reach a level of compensation we believe is fair for the work we do, then what truly motivates most of us are not extrinsic rewards (compensation, parking spaces, etc.) but intrinsic values.
• Motivation 3.0 is all about three core intrinsic values: autonomy, mastery, and purpose.
Autonomy
In the context of managing people, autonomy is allowing employees the independence to determine the best way to meet established goals and targets. For example, as long as employees meet their goals ethically and responsibly, then it doesn’t matter if they show up at 9:00am or noon, or if they work from home. It means not standing over them with a carrot or stick. (And let’s face it, many managers find sticks easier to use than carrots.) Pink cites the positive example of the Results-Only Work Environment (ROWE), first used at Best Buy. (Hennepin County recently adopted the ROWE model.)
Mastery
Complete mastery is a goal we will never reach, but when we work on something we really enjoy, the work of achieving mastery is not so tedious. Ideally, the boundary between work and play dissolves and we enter what Mihaly Csikszentmihalyi described as “flow.” All of us should aim to find work that allows us to enter this flow state, and employers should create environments where this flow state is encouraged, where constant learning, constant opportunities to improve, are readily available.
Purpose
Purpose is all about doing work that matters to us. As Pink says, Motivation 2.0 “doesn’t recognize purpose as a motivator.” Instead, it’s “relegated to the status of ornament – a nice accessory if you want it, so long as it doesn’t get in the way of the important stuff.” But the desire for a meaningful purpose is central to what makes us human. Sure, extrinsic rewards are enough for some people, but for many of us, contributing to a larger purpose is crucial.
Motivation 3.0 and Social Learning
Pink cites numerous examples in Drive to show that allowing these values into the workplace does not mean sacrificing performance. In fact, it’s just the opposite. Embracing these values enables great performance.
Beyond the issue of fair compensation, the absence of these values from the workplace is the central reason why so many people are desperate to leave their cubicles and find something else. At the risk of sounding like I am sucking up to my employers, the presence of these values at Fredrickson is a key reason why I’ve been here for almost ten years.
But a big reason why I am interested in Pink’s argument is the way it connects so well with the case for social learning and enterprise 2.0, because it seems to me these related technologies and practices are very much in harmony with the idea of Motivation 3.0. For example, making social learning possible, allowing employees to learn from and contribute to enterprise blogs, wikis, forums, and more, putting tools and practices in place that improve knowledge flow – these are clearly related to the values of autonomy and mastery. (It’s no surprise that Best Buy – where ROWE began – is also a leader in enterprise 2.0 and social learning.)
So I’ll leave you with some questions:
• To what extent does your workplace encourage and provide a sense of autonomy, mastery, and purpose?
• Do you think Motivation 3.0 is compatible with good business performance?
• If you are involved with organizational learning, training and development, or a similar role, to what extent does your function encourage autonomy, mastery, and purpose? Alternatively, is training and development more closely related to a Motivation 2.0 environment?
• If you are a manager, what is your response to Pink’s argument? Is it too idealistic?
What do you think?
Watch Dan Pink’s TED presentation on Drive from July 2009: http://bit.ly/DV7xg.
Read Andrew McAfee on Enterprise 2.0: http://andrewmcafee.org/
Read Harold Jarche on Social Learning: http://www.jarche.com/
Almost twenty years ago, I wrote an article for STC about estimating work effort for creating user guides and online help systems. The article, “Stop Guesstimating, Start Estimating,” provided metrics for various types of content and tasks. I still get occasional notes from technical writers who say they’ve used the metrics successfully for many years.
I’m also asked these questions:
The answers to both question is “yes—as a starting point.”
The metrics represent hours of information gathering, writing, and revising that it takes to finish a countable unit, such as a page, a help topic, a glossary definition. But the process used to create the finished units can significantly affect the work effort. If you have a consistent process, then your metrics are likely to be very reliable.
However, if every project you do involves a different set of people and a different process, using historical metrics alone may lead to under-estimating the project.
As we’ve gathered metrics from projects in the past year, we have seen a variability of 50% in the work effort to create a page of content. It wasn’t that one course had more interactivity, or that there was more content on an average page in one course versus the other. It all came down to process for creating the content. Two recent projects illustrate this variability.
For one project, about 80 percent of the content was known and agreed on at the beginning of the project. The writer could use traditional methods of gathering information from subject matter experts and existing materials. She was then able to create a draft of the course content with the typical number of open issues that could be resolved during the review process.
For the second project, only about 10 percent of the content was known and agreed on when the writer began the project. As a result, the process she used to create the content was vastly different from that of the first project. She facilitated sessions in which the subject matter experts discussed what the policies should be. She then wrote the policies and identified areas that the group hadn’t yet addressed. When the subject matter experts saw the results of their work in writing, they re-thought some of the decisions they’d made. The writer revised the draft accordingly. This continued for about three review cycles.
The difference in work effort? A finished page in the first course took our typical metric of 2.5 hours a page. A finished page in the second course took 5 hours to create.
A collaborative and iterative process, as followed in the second project, is becoming more prevalent as change and work speed up in corporate life. The trick is to recognize before the project begins that such a process will--or could--occur so that you can estimate accordingly.
Molly Emmings also contributed to this blog entry.
The presenters in our last Intersect meeting on 11.17.09 had some valuable stories to tell about their respective intranet design and development projects. We thought it would be useful to share tips from the presentations, supplemented by some of our own thoughts.
1. Make sure you have upper management support and a strong project champion who understands the business value of an intranet and can keep driving the effort forward. Without this support, it’s very difficult for an intranet project to gain any traction.
2. Define a clear set of goals for your intranet site – for example, to serve as a communications hub, to be a central repository for documents, to eliminate the duplication of information, to support and enhance collaboration between divisions, and to break down organizational silos. The goals you define should inform your site’s design, organization, and feature set. They should also help you gauge the success of your site once it’s been deployed.
3. Develop a content governance process and related policies, because well-organized, up-to-date, and effective content doesn’t just happen. You need to assign one or more content “gatekeepers” who have ultimate responsibility for approving and publishing content. These gatekeepers should have a good grounding in effective writing for the web and basic usability.
4. Create a style guide that lists standards and guidelines to help ensure the site presents useful and effective content. The style guide should cover writing for the web, when and when not to use PDFs and other non-Web file types, image selection, optimization, and placement, use of acronyms and abbreviations, and so on.
5. Provide robust training to content creators and managers. This training should cover not only the mechanics of posting and updating content but also how to write and present content effectively for the web. Depending on the content management system (CMS) or authoring tool you are using, the technical portion of the training may require more or less time. If you are moving to a new CMS, the training will require substantially more time. If you have a dispersed employee population, web conferencing tools like WebEx are a useful option for training sessions.
6. If you are implementing a CMS for the first time, or if you are replacing one CMS with a different one, change management will be a critical piece of the project. Learning a new system, requiring new procedures and techniques, is usually daunting and even a little scary for many employees. A careful, thorough training program is a must in order to counter the inevitable fight-or-flight response.
7. Follow a user-centered design process. Get representative users involved by soliciting their input throughout the project, not just before the site goes live. Users can be involved via surveys, card sort exercises, discussion groups, and usability testing at different stages of design and development. Testing does not need to be a highly formal activity - testing with just a few people is better than not testing at all. This will lead to a more usable, effective site. In addition, by involving employees in the process, it’s much easier to get their acceptance of a new or updated site.
8. When organizing and labeling information, think beyond department- or division-based categories and include topic and audience-based categories as well (e.g., Employee Resources, Managers’ Toolkit, Workplace Resources, Reference Room, etc.). At some point, everyone is a new employee, and it is not always obvious which department is responsible for certain types of information. Even veteran employees don’t always have a clear idea of what all the departments do. This is a major weakness of intranet sites that use only department-based navigation categories.
9. Make sure the intranet provides information employees really need and want - that is what will drive traffic to the site. Use the home page to provide news, updates, and announcements.
10. Consider ways to incorporate employee content into the site, such as photos and bulletin boards. And strongly consider incorporating video, blogs, discussion forums and other means by which employees and managers can share information, ask questions, and get answers.
In addition to these tips, we’ve put together a short list of useful references.
http://www.usability.gov/
http://www.usa.gov/webcontent/
Garrett, Jesse James. The Elements of User Experience. 2002.
Krug, Steve. Don’t Make Me Think: A Common Sense Approach to Web Usability, 2000.
http://www.nngroup.com/reports/intranet/design/ This report reviews “The Year’s 10 Best Intranets.” Note that the examples are all from large companies in the private sector. The cost is $224 for a single copy.
Redish, Janice. Letting Go of the Words: Writing Web Content that Works, 2007.
See more of our recommended resources.
First of all, thanks to everyone who attended our seminar yesterday at the ASTD-TCC Regional Conference. It was great to meet all of you and J. Hruby and I both enjoyed the presentation and discussion. One point from yesterday really stuck in my mind and I thought it was worth exploring further here in the blog:
When you include users or learners in your review process for online learning, (and most in the seminar agreed that you should!) how should they be selected?
A couple of thoughts from me and then I’d love to hear your comments:
* Beware of reviewers who claim they can “represent” the actual learners! I’m just reiterating this because it was one of the best points that emerged from yesterday’s seminar. Thank you to the participant who shared a story that illustrated the problems that can occur when anyone other than an actual learner tries to speak for the learner.
Managers, supervisors, and highly-experienced employees may be eager to volunteer to be reviewers, but only real learners should represent the learner’s point-of-view.
* Select reviewers who represent appropriate skill and experience levels within the learner base. Area supervisors and highly-experienced employees may be eager to volunteer to be reviewers, but do they always represent the learner’s point-of-view?
* Think about what kind of feedback you want and communicate this clearly to the learner-reviewers. Be aware that when more experienced employees are involved in reviews, they’ll often want to influence the content and how it’s conveyed so that it reflects their experiences, views about how things should be done, etc.
That’s fine if this is the type of feedback you’re looking for and you’re in a phase where the content is still under development. Often times, however, we involve learners because we want opinions about the effectiveness of the content that has already been decided on. Make sure you understand what you want from your reviewers and then communicate that to them clearly.
Again, we really enjoyed yesterday’s seminar. Please share your thoughts and comments.
I believe strongly that corporate cultural fit matters to a person’s success and satisfaction in a job. I screen prospective employees with that in mind. And I’m pretty effective at it, and I dare say proud of the skill. Having shared beliefs about work and how to treat colleagues and customers helps a business run smoothly.
However, some recent reading has reminded me not to be so sure that I’m an authority on corporate cultural fit. Of course it’s important. But at what point can a quest for shared beliefs turn into a quest for people who think and behave just like oneself? And to what degree is corporate culture a U.S. concept that may unwittingly exclude or alienate people from other countries? Here are what prompted these questions:
I’m looking forward to conversations with colleagues in other businesses and other countries about their definitions and practices regarding corporate culture.
For those interested in the connection between the tips listed below and a study of five state Department of Revenue websites, read on past the list.
1. Organize primary navigation menus by audience when your users easily identify with an audience category (e.g., For Job Seekers, For Investors, For Students, etc.). My experience conducting usability tests supports the key result of a study published last year in the journal Technical Communication: “Navigation menus that contained links organized by audience were selected more often than menus that contained links organized by topic” (May 2008, p. 186).
2. Precede the audience name with “For” – it helps users quickly recognize that this is information for an audience, not about an audience. For example, in one usability study I led, there was more task success with the label “For Business” than with “Business” alone because users had a better idea of what to expect.
3. Provide a secondary topic-based menu to supplement the audience-based menu. Most users like to have more than one path to the same destination. In addition, some specialist users may not easily fit into any of the primary audience categories. Secondary topic menus can be useful in meeting their needs.
4. Guide the user’s eye to what is most important by means of placement, size, images, and subdued color. On a typical home page, this will usually be the primary menu, the secondary menu, and then news and features, in that order. When everything is presented in the same way, users have to take longer and work harder to orient themselves to the page.
5. List a selection of 4-5 popular or important links below each audience category. This will save a significant percentage of users a click to the main audience pathway page and allow them to go directly to what they are looking for.
As part of a recent project, we met with users of a state Department of Revenue (DOR) website and asked them to rate the home pages of five peer sites, focusing especially on navigation:
• Iowa Department of Revenue
• Louisiana Department of Revenue
• Massachusetts Department of Revenue
• Minnesota Department of Revenue
• North Carolina Department of Revenue
The users rated Louisiana the highest and Minnesota the lowest. So what did Louisiana get right and Minnesota get wrong? Here are a few summary points.
The Louisiana DOR home page presents three large audience categories front and center, each of which includes an attractive photo of a person, a subdued color, and four related links. These audience-based categories are very clearly the main doorways into the site for the three main audiences: Individual Taxpayers, Business Taxpayers, and Tax Professionals. A topic-based menu is evident just below the page header, but it’s obviously subordinate to the audience menu.
In contrast, finding the audience-based navigation on the Minnesota DOR home page is a little bit like playing “Where’s Waldo”. It’s there, but see how long it takes you to find it. The users in our study said they were not sure where to focus – the elements in the main body of the page all seem to have more or less equal weight. They did not feel the design guided their eye to the priority information.
This was also the issue users identified with the Massachusetts DOR home page, which they rated second lowest. Although it presents the audience categories by means of tabs near the top of the page, users felt this home page was “too busy” and “cluttered.” When users describe a page in this way, they are saying it is not easy for them to figure out where to focus first, second, and so on.
In the middle of the ratings were Iowa and North Carolina. Users did not like Iowa’s color palette – to them the lime green was an “odd” choice not suitable for a government agency. And they thought the font was too small. But for ease of use, Iowa came out slightly ahead of North Carolina because of its relative simplicity, the lack of scrolling required, and the selection of links provided for each audience category.
The top-rated Louisiana DOR home page is not perfect. The rectangular graphic links in the middle of the page look too much like advertisements and would be ignored by users, and the light grey font is a little hard to read and is too small in the news and announcements section. But overall, Louisiana’s home page provides a better front door than either Massachusetts’ or Minnesota’s.
I spend a lot of time speaking with people who would like to work for Fredrickson. I most enjoy the conversations with those who are curious and always learning. They expand their professional skills in spite of limited opportunities to do so in their current job. Many are artists, musicians, actors, athletes, or mentors outside of work. Or they are otherwise active in their communities or professional associations. Finally, they are interested in learning about other cultures and perspectives.
People with these traits, I’ve found, are often the most adaptable to change and the most productive amid change.
Yet I wonder whether there is still reluctance among job-seekers and employers to acknowledge and discuss how experiences outside of work contribute to what the person can bring to a particular job? Just today, I interviewed a person in the learning and development field. Her past career as a winter sports coach came up in conversation, and I expressed my surprise that she hadn’t included this experience on her resume. She had chosen to omit it out of concern that an employer would form a negative impression of her character and wonder whether she’d be asking for extra time off to pursue the coaching. I hope I convinced her that 1-on-1 sports coaching was directly relevant to 1-on-1 corporate leadership coaching!
I’d like to see “demonstrated life-long learner” become a standard requirement on all job descriptions.
Seeing articles, webinars, and presentations with this title makes me weary.
Yes, budget is important and yes, we should be fiscally responsible and good stewards of money. However, the question of tight budgets for training just doesn’t make much sense to me. The reason it doesn’t is because I’ve always been a firm believer in answering this question first - “Why are we providing training?”
If the answer to that question is that we are providing training to enhance, improve, or rectify some type of business problem, shouldn’t the budget question really be, “How do I show the benefit of this training in terms of the business problem?” If you answer that question, the answer to the money question should follow.
At Fredrickson we’ve long prided ourselves on sharing both what we know and what we think about topics through our seminars, articles, and the Fred Comm eZine.
The addition of the Fredcomm Blog gives us another way to continue to share our thinking about things that matter to us and we hope they matter to you as well.
The Fredcomm Blog won’t be written by one person, and it won’t be for just one audience. Instead, we’ll feature entries from anyone at Fredrickson who has something to say about any of our practice areas, from learning, to usability, to communications, we’ll get around to discussing it all in one blog.
I’ll hope you’ll bookmark this blog and return often.