Archive for category Design
I just returned from a meeting in Seattle with distance education colleagues from several universities. Six of us traveled from the University of Wisconsin-Extension in Madison to the institution of our outstanding hosts at the “other” UW (University of Washington). We were joined by instructional designers, media developers, and distance education leaders from Georgia Tech, Northwestern, and Boston University. The meeting was a great example of how to gather a group of experts together to create a meaningful learning experience. This post is part reflection and part micro-case study.
The dean at UW-Extension had spoken with his peers about the distance learning groups in their institutions. He sent an email to see if there was interest in getting instructional designers and others in elearning departments together for a professional development opportunity. Representatives from five other institutions responded to the email. I agreed to start the ball rolling by setting up the first phone conference. We began phone conversations in September 2011 about whether the expense and effort of a face-to-face meeting would benefit our teams. The first point of discussion was about the format. I asked whether we needed yet another conference for our teams to attend. The steering group agreed that there was little value in that format because there are many conferences we can attend if we want a traditional event. I suggested that we try a loosely structured series of conversations. There would be no no PowerPoint or even show-and-tell, just semi-structured conversations and networking time.
These types of events can seem a bit risky if you are used to having lots of structure and predetermined content. Will we have enough to talk about? What if our work is too different to relate? Will everyone be able to participate? This group, however, immediately thought the format would work and we brainstormed about 20 topics.
Tools for the job
I started a Google doc and we began to use it as a central repository for topic ideas, the attendee list, and logistics (hotels, meeting info, etc). We then narrowed down our 20 topics to 6, each with 90 minute blocks over a 1 1/2 day event. We added 45 minutes for morning coffee and bagels, an extended networking lunch, and 15-minute breaks after each session so that we had plenty of mental “white space” around the topics.
In the Google doc, we created a table with the schedule and included an extra column for volunteer moderators. At first, no one ventured to put their name in the boxes. I sent an email explaining the moderator role as a facilitator, not an expert on a topic. Moderators needed to simply come prepared to throw a few questions out as conversation starters. The column filled with moderators as the event approached. Moderators began listing topic questions in the Google doc and created spaces for notes. As the event unfolded, the doc became a crowdsourced repository of links, notes, and ideas.
The event was held in a unique setting: the Center for Urban Horticulture just off the University of Washington campus. There reasons for holding the meeting there were largely pragmatic but there was some intent to get us out of a traditional conference space. The unique space made a big difference. People felt at ease as soon as they walked through a small garden to reach the classroom.
We started with introductions and then launched into the first conversation about LMS usage. Even though the moderator was prepared to keep the conversation going, there was no lull that required intervention. The first 90 minutes was almost over too soon and people continued talking into the break. After the break, people were seated and ready to go, no prompting or gathering required. The next topic, mobile learning, quickly picked up steam and carried us through to lunch. An extended lunch gave us time to get to know each other and take strolls along the nature paths down to the lake.
After lunch, we discussed how our institutions were approaching the use of media in elearning courses. This was not a deep technical discussion but showed remarkably different approaches to using video, interactive media, and dealing with faculty perceptions of media use. We ended the first day by describing how we work with faculty and subject matter experts as we build online courses. In all of the first day’s topics, the differences were more interesting than the similarities but we sensed a growing shared understanding about our work.
We made informal small group plans for dinner and left for the night. Unfortunately, a few of us never made it to dinner due to a bit of a debacle with a cab company, but that is a different story. When we returned the next morning, it was almost as if we had all been working together for years.
We discussed how we cope with the “firehouse of new technology” in our organizations. Working with online learning technology keeps us all on the bleeding edge at our institutions but maintaining our innovative spirit and continuing to invest is a significant challenge with tight budgets. In the final session, we had our only breakout session. People could choose to talk in-depth about online learning development tools or discuss managing the distance education enterprise. We could see the progress across groups because people were taking notes for both sessions in the same Google doc.
We came back together for a few minutes before we had to go our separate ways. Numerous ideas came out about how we could all work together to solve some of our shared challenges. Some of these ideas became next steps in the Google doc. The most popular idea was that this event was one of the more valuable professional development opportunities people had attended and it should be held at least annually. Boston anyone?
By the end of the meeting, our Google doc had expanded to over 15 pages of shared notes and we all gained a lot from sharing across institutions. More importantly, the format showed us that we had colleagues facing similar challenges and we could reach out when needed. I look forward to learning more with this group as a part of my extended network!
Rube Goldberg created incredibly silly contraptions to accomplish simple tasks. His work is now recognized through an annual contest. In the event, engineering students compete to create the most complicated and creative solutions that to solve simple problems. The official 2012 contest is approaching and has me thinking about how instructional designs can be over-engineered.
In March 2011 the University of Wisconsin-Stout team won the national competition (for the second year in a row) with a machine that completed 135 steps to water a plant. This year’s competition is to over-complicate inflating a balloon.
What is the value of creating a complicated, albeit creative, solution to a simple problem? For the students involved, they have fun and learn about engineering, physics, and the properties of various substances. The events promote science, engineering, and the programs at the schools involved. These activities are outstanding in every way except one: the outcome. The products these machines create are irrelevant.
As we create instructional technologies and designs, how many of them are Rube Goldberg machines? Designers create complex new technical schemes or media-rich products when much simpler and more elegant solutions will work. Everyone involved in such design processes learns a lot and the contraption might be fun to watch but is the end product worth it?
The answer is, of course, it depends. If the intended outcome is knowledge for the technologist, then such a design is a success. Similarly, if the users of the product participate in its creation, then it is also worth it (but this is a rare instance in most instructional product designs). If we want the output of the design to be the most important part of the process, then simple and elegant solutions yield better results.
Perhaps a Rube Goldberg instructional design competition would be a lot of fun: create the most complex instructional solution to teach someone a simple task…
the platform. The simple ability to “follow” fellow students and faculty even after a class semester ends opens many new learning opportunities. Pearson gave a few new details about the social elements during the design partner meeting, including taking steps to integrate with Google+.
Examples of how to build on social
Pearson developersshowed off some nifty innovations created during a previously held two-day internal hackathon. While these innovations may or may not make it into the formal OpenClass product roadmap, a few were notable and showed the potential of platform: 1) An integration of Google+ Hangouts to create video office hours from within OpenClass (very slick) 2) a collaborative multiple-choice test-taking tool that requires students to work in teams to answer questions 3) a badge system that gives rewards for a variety of activities (e.g. % of people you have interacted with in the class).
The other major feature is still in the works and is currently called the Exchange. An over-simplified view is to think of the Exchange as an app store for learning content. As design partners, we got to see some Exchange wireframe mockups. Creating a one-stop-shop for learning content is far more complex than creating an app store for a monolithic software platform. The vision is that it will provide a simple interface across open source and paid repositories of content. As faculty build their courses using content from the Exchange, they will see a running tally of what students would have to pay (if they select any paid resources). Students will have options on whether to pay for content when they login (e.g. I own the paper text and do not want the digital one in the course).
Pearson knows that gaining and maintaining trust in the Exchange means that they must be egalitarian and transparent in how content is listed. This is a tricky line to walk because, unlike Apple and iTunes, they also own a content business. Faculty ratings of content and open discussion forums will help build trust but attempts to highlight content (like most other digital stores do) will be difficult to navigate while avoiding the appearance of bias. Other design-related challenges include how much information to include for each offering (peer-review status, device compatibility info, evaluation data, etc.), what types of media to include (e.g. video file formats, proprietary players/readers, Flash), and rights management.
Beyond the technical and design questions, there are also potential institutional challenges. The long-term vision of the Exchange includes the ability to accept content submissions from any individual. Similar to the Apple App Store, each person can determine whether he or she will charge for the materials on a per student basis. I suspect this will bring many long-simmering questions about digital course ownership to the fore – especially the first time a faculty member creates a 99¢ math video that a giant community college system decides is a part of their core curriculum.
I think OpenClass is a bold product. In an area where innovation has been very slow and incremental, it offers a chance to rethink the LMS. The challenges are immense and there are no guarantees they can all be overcome. In these two brief posts, I did not touch on the possibilities of global scale and analytics, the host of open APIs, and the deep integration with Google (and soon other providers) but the social features and Exchange lead me to believe that investing time in a robust pilot is worth it to see where this goes.
Note: I do not promote or endorse any product on behalf of my employer. These are my own opinions.
Last week I was fortunate to participate in the design partner meeting for Pearson’s OpenClass LMS. At the University of Wisconsin-Extension, we are early in our OpenClass pilot but I was interested to hear what others had experienced.
It was a remarkable couple of days. Putting more than 20 people from different types of institutions in the same room to have in-depth conversations about what next generation learning technology infrastructure should look like was worth the trip to Denver. Conversations ranged from high-level technical (what should the SIS API enable?) to more broad philosophical issues (should the system encourage a move away from rigid course structures?).
I was impressed with the candor from everyone about the potential and the challenges of building a globally-scalable learning technology platform. OpenClass is available but still in beta and has some kinks to be worked out. Everyone agreed that the basics needed to “just work” before a more substantial rollout could happen at their institutions. What constitutes the basics, however, was different depending on partner needs.
I believe Pearson is facing a classic “Innovators Dilemma” (Christensen) as they launch OpenClass into a mature market. Mature markets have developed expectations about how products should function. The power users of mature technologies expect products that offer rich features that have grown over time. As these products add more features, they also become more expensive and harder for novices to use. This is generally the case in the LMS/CMS market. A disruptive innovation often offers less or different functionality but can be significantly cheaper than the more mature products. In the case of OpenClass, the cost drops to zero (at least in terms of licensing and hosting).
OpenClass does not have the feature depth of more mature learning management systems (at least the features we have come to expect). For example, there are fewer quiz options, the forums are not as robust, and the ability to customize roles is limited. This is not to say that the OpenClass features are not capable but, if you are used to being able to configure each role in 100 different ways, OpenClass does not have that kind of flexibility out of the box. The key is to look at how OpenClass is different and where it is better than current LMSs. What does it offer that other LMSs do not? It uses a much more social approach to learning, has a fantastic interface, and the potential for content sharing on a global scale (I will talk a bit about the Exchange in Part 2).
The big question is whether Pearson can capture enough of the mature market while pushing into new directions. Given that 3000 institutions/organizations are at least kicking the tires, it seems like they have a good shot at getting a solid user base.
We are continuing to move forward with our pilot at UWEX and are challenging ourselves to think different about course design and structure to take advantages of the platform’s strengths.
I split this reflection into two parts and I will talk more specifically about the current and future capabilities that are reasons we are moving forward in Part 2.
Welcome to the new version of my blog. After more than five years of blogging with Movable Type, I decided to switch to WordPress. MT is a great product but the functionality of WP is a more natural fit to how I like to post, write, and experiment with web technologies. I have also pulled the plug on my Feedburner feed and now have a combined feed using FriendFeed. For those who would like ALL of my tweets, pics, Youtube posts, Facebook entries, LinkedIn, and more, subscribe to the FriendFeed RSS. If that is too much of me, you can subscribe just to this blog.
The old version of the blog is still available. If you are looking for some of my older posts, you can find them here. Some links from archives back to the homepage of that site might be broken.