Friday, December 29, 2006

Making Pie Crust

In his comments to my post You Just Had to Be There.... Kevin McCluskey writes:

I hear what you are saying but it kind of indicates that learning is always the same. synchronous learning is better because of context and the give and take between participants. Others might say that Asynchronous learning is better because you have time to think over ideas before you react. Neither answer is complete because learning is more than either synchronous or Asynchronous methods. To me it depends on the situation. Some times one works better; other times not

All learning and tool choices are situational.

Personally, when I have to design a course, I ask 2 questions:

- What is the ideal way to present this material to ensure optimum learning outcomes for my audience?

- Given the resources at my disposal (time, money, people, space, tools) - how do I need to modify the answer to question #1.

To demonstrate: let's say I have to learn how to make a pie crust.

Optimum learning scenario: I go see Mom and we spend time making pie crust. I can see what she does, feel textures, smell the pie baking and eat the pie - looking for texture and flavor. Dragging a recipe and notes back to my small apartment kitchen, I attempt to replicate the pie crust (practice). The result is then brought back to Mom for critique and we try again. At some point during the process, Mom shows up in my small kitchen to see the environment in which the learning takes place. With enough practice - I make good pie crust.

This process is synchronous. The takeaway (the recipe and notes) allow me to repeat the process asynchronosly at a later date.

Mom lives far away: Mom sends me a recipe via e-mail (I managed to drag her kicking and screaming into the 21st century). I call her while I make the pie crust to ask questions. If both parties had the resources, I would send her mobile pics of the various stages for her to critique. I feed the pie to my friends for feedback. I repeat the process until I find a pie crust I like. What's lost - there is no way to truly communicate appropriate textures without getting your hand in it. You are also missing the feedback loop from an expert on the process.

The initial process is asynchronous (the e-mail) with a synchronous component ("Hi Mom!")

Mom is a terrible cook and everyone you know buys pie crust at the store: I find a recipe for pie crust, follow the directions, and hope for the best. I can also watch a cooking show which will give me more visual information on how pie crust is made and what I should look for. I keep finding recipies and making notes until I find a pie crust technique I like and that my friends will eat. Disadvantage - requires a HUGE amount of self-motivation. And if I tried to tackle this without knowing some basics (like how to turn on the oven) - it might be trickier.

The majority of the process is asynchronous (text and video.

All 3 processes will ultimately result in me being able to make decent pie crust with enough motivation, money (for ingredients) and time.

In other situations - a dominantly asynchronous learning process will provide better results. From what I've observed - asynchronous techniques work best with an audience with prior experience and well-designed tools.

For example, I find software applications easier to learn and teach through well-written text and interactive online tutorials. The student is able to learn at his or her own pace without feeling rushed. A synchronous component for individual questions (such as a chat room or a phone call) allow the student to get past stuck places and gain needed reassurance. It also provides some accountability.

Rick Lillie writes:

Think tools. To me a blog is a tool. Elgg is a tool. Microsoft Office is a tool. Google Docs and Spreadsheets is a tool. The question to ask at any moment is which tool is the right tool for the need at the moment? Which tool will enable the learning need at the moment to be met?

I'm a big fan of using tools - physical, virtual, and intellectual. Who says we have to use them in the prescribed manner?


End notes:
- Mom makes GREAT pie crust. Me - not so much......

- Dr. Lille's blog has some interesting ideas and tools for developing hybrid technology methods. Thanks for the link Dr. Lille!

- Commenters:
If you are a blogger or have a web page, please send me a link at the end of your comments. I get so much valuable information from your comments and I want to share your sites.

Thursday, December 28, 2006

You just had to be there....

Sandra Dickenson, in her post What does an e-learning community look like, describes an experience where she and a group of online learners collaborate on an image modeling how learning works. The group used a combination of chat and the collaboration tool to create the image above.

I’ve shared this image with a few other people - they don’t even think its interesting, let alone feel the powerful emotions and insights expressed in this image. Now that its static and preserved - so much of what it really means is gone - and we can only get that back if/when we do it again. When we got done making this picture — I absolutely had to preserve it — I was on such a euphoric high over what we had just made together.

If Sandra showed this picture to one of the participants of the class, the picture will have meaning and context. Looking at it as an outsider, the picture looks like a colorful collection of scribbles.

This had me thinking about the difference between synchronous and asynchronous eLearning communities.

In a synchronous learning community, in many instances, the process is the point. As Sandra points out, a tremendous amount of learning occurs in the push-pull of conversation. The downside is that these communities, by their nature, are exclusive. The objects that the community leaves behind oftentimes make no sense to anyone outside that community. They are missing the context.

Asynchronous learning communities, such as the blogosphere, generate objects that are meant to be referred to in the future. These objects can be used by the members of the community or by outsiders. The disadvantage is that the community members miss the instantaneous feedback loop. At certain points in any creative or learning process, the push-pull of others ideas in a rapid-fire fashion is necessary for progress.

I will admit that I prefer asychronous eLearning over synchronous eLearning, both as a teacher and a student. I like being able to mull over content and think through responses. I have found in chats, interactive video, teleconferences, and classrooms that the loudest person / fastest typist wins. Synchronous learning, to me, rewards the least introspective. I've always felt that some level of introspection is necessary for me to absorb new material. Of course, I'm a bit of a navel-gazer by nature.

My opinion - the best eLearning experiences , and the strongest online communities, provide both asynchronous and synchronous experiences. Looking at the number of people on the eLearning blogs who are grappling with changes to the field, Brent's Corporate eLearning Talkcast could prove to be the perfect synchronous forum for strengthening the community and providing the synchronous push-pull that helps synthesize and make sense of these changes.

Wednesday, December 27, 2006

Gearing Up for the Big Project

Over the next few months, I will be putting the Moodle install, my training strategy, my presentation skills and my stamina through its paces. I hope to document our Electronic Medical Record upgrade over the next few months.

The main reason for the Moodle install is to help us with a major upgrade to our Electronic Medical Record. This upgrade is, essentially, a brand new program. If we don't get people into training of one sort or another - the entire organization stalls.

To complicate the picture, our organization (the CEO) wants to go live with this new program 60 days after the program is put in our test server. No change management time.

Oh, and did I mention that this program is in controlled release for Beta testing.

And that we are one of the first organizations to even SEE the program.

And there is little documentation...

And the vendor's trainers haven't seen a working version of the entire upgrade yet....

And there are only half-finished movies available for online tutorials.....

You see where this is going.

The training challenge on my plate is to train this new upgrade to 2000 people in 10 business days.

The vendor's recommended "Basic" level for the upgrade is 7 hours of material. We need to add more of the functionality beyond "Basic" to match what we are currently using.

My tentative estimate of training time per person - 5.5 hours. This includes chopping out stuff I hope our end-users figure out for themselves and NO practice time.

We are fortunate that the vendor wants us to be successful and is providing 3 trainers. This will allow the in-house folks (i.e. Arlene the Medicine trainer, Gesine, and me) to continue building training materials, provide support, and finish configuring the system (the trainers also do some system administration).

Our biggest problem is training space. We have 1 12 seat classroom. Our current space strategy - try to get classroom space from the affiliated university during midterms. Those of you who work for universities can stop laughing now....

So below is my first draft of our training / change management plan.

Week 1 - Project Team Training and Preliminary Configuration
- Project Team Training for the IT department from the vendor. Start configuration of system.

- Moodle. I have already opened up a course with vendor-provided information to the rest of the organization. I can't start developing our customized materials until we get the upgrade into our test servers and finish the preliminary configuration.

Week 2 - Change Management
- Start of weekly 2 hour SuperUser trainings. Because we have so many people, the departments are being forced to take more responsibility for getting through the upgrade. Each department (with some browbeating) gave us 2 people who will be the first line support for the upgrade and will provide training for any stragglers. Since we will have about 50 SuperUsers, we are going to place the SuperUsers into 4 cohorts. I will train 2 and Arlene will train 2.

These trainings will give the SuperUsers practice time with the system and give the IT department feedback on the configuration.

- Town Meetings. We are planning a series of 5 town meetings so that the providers and staff can see the system for the first time. We are asking the vendor to be there so they can answer questions (and take the heat) about the changes to the system.

- Moodle. I will be trying to crank out new tutorials. Moodle will be used in parallel throughout this upgrade in an attempt to get everyone their preferred mode of training.

Weeks 3 - 5 - Change Management
- SuperUser trainings continue

- Moodle. I will still be cranking out tutorials for Moodle and encouraging people to take a look.

- Departmental Meetings. The IT department will hold a series of Departmental meetings so that the individual departments can see Moodle and decide as a group how they want to use it. We hope to get workflows out of these meetings as well.

Week 6 - the calm before the storm
- SuperUser Training
- Moodle. I hope to have the tutorials for the upgrade finished.

Weeks 7-8 - Upgrade training!!!!
- SuperUser Training. The SuperUsers will do the final test of the live system with the IT Department.

- Face-to-face. The vendor's trainers will be teaching this course. For week 7 we hope to get 2 computer rooms from the university. Week 8 - 3 computer rooms. I did this knowing that our students will procrastinate. It is mid semester for the university at this point so I'm not feeling nearly as optimistic as the boss about getting the space for 2 weeks running. I'm still working on a plan B.....

- Moodle. I'll be opening a chat function within Moodle for the online users for 4 hours per day outside of business hours each day those weeks. I'll be running daily reports from Moodle to see who has done what on the system.

I'm hoping that lots of people take advantage of the online option. Mostly to keep the pressure off.

Week 9 - Go Live
- Face-to-face. I am teaching 1 Upgrade training per day during Go Live week to catch some of the stragglers who insist on IT-led training. The SuperUsers will be responsible for most of the training and support in their department.

- Moodle. I'll still be running reports on Moodle and offering chat for 4 hours per day outside of business hours within the online class.

- Advanced training. I'm going to offer an advanced class for the more ambitious providers towards the end of that week.

Week 10 - Winding Down
- SuperUsers. The SuperUser training turns into a 1 hour standing meeting to address issues and questions.

- Moodle. I am going to build some advanced tutorials and reorganize the existing training to mirror the changes to our system. All of the tutorials for the old version are archived.

Week 11 - I go far far away for a long vacation.

Friday, December 22, 2006

Adding a Google Analytics Feed to your Blogger

Techie notes (my apologies for the lack of pictures).

Step 1: Open a Google Analytics account. Having a Google account makes this step much easier.

Step 2: Click Add a Website Profile. This link is found in the Website Profiles header on the right side of the screen.

Step 3: Add your site's URL, your country, and your time zone. Click Finish

Step 4: You will be given a box with some Javascript to copy and paste into your blog code. I copied and pasted this into a Word document for safe keeping.

Step 5: Open a new window and log into your blogger account.

Step 6: (I am using Old Blogger), Go to Template > Edit Current

Step 7: Scroll to the bottom of the code. Paste the new code between /div and /body. It should look something like this:

Step 8 : Save the template.

Step 9: Go back to Google Analytics. You should see a message stating that Google Analytics is now receiving data.

I find that it takes about 24 hours to start receiving reports.

Hope this helps.

Becoming an Egotistical Narcissist

Sandra Dickinson, in her comment to my Fear of Blogging post notes:

...the responses to what I have to say are NOT showing up as comments on my own blog. They are showing up in other people's blogs. VERY hard for me to find out about and keep track of and keep going with. So its not just fear in the first place, but some discouragement after awhile, if you can't figure out how to see what the response is.

I'll admit that my reasons for starting and continuing to write the blog are purely selfish. I do this to clear my head. I never anticipated anyone caring enough to read this, much less comment, link, and blog about anything I have to say.

That said, to my surprise and delight, I find myself tapped into a robust community of like-minded souls. This has made me curious. And more narcissistic than necessary.

Strategies I've discovered so far....

The blog reader (currently using Google Reader).... it always surprises me when I find my name in the post. I think it is some other Wendy, until I follow the link and it takes me to my site. BTW: Googling yourself is quite an education, if you are one of the few who have not done so yet.

Technorati - From this, I can tell that Tony Karrer has linked to my blog a lot. :' )

Google Analytics - I started playing with this tool this past week. Very informative and eye-opening (who knew that people from China, Turkey and Burnsville, Minnesota were looking?). Downside - it doesn't keep track of RSS subscriptions. For the curious, I'll add techie notes in another post.

Bloglines - I just started playing with this tool today - hoping to answer Paul Fender's question about my RSS feed. Very cool that it keeps track of how many people have RSS subscriptions to your blog within Bloglines. Wish Google Reader had that features....

I also noticed the BlogRoll feature in Bloglines. Aesthetically, I'm not a huge fan of buttons and links and other stuff on the sides of my blog. I'd rather shout about (and link to) someone's cool idea from the rooftops. But that's just me. I'll probably play with Blogroll over the next couple of weeks.

In my ideal universe, everyone would make their blogs feed-reader friendly, with full posts, so I don't have to click on the site at all unless the blog owner points out an interesting comment stream or I want to link to their post on my own blog. I am lazy.

Speaking of keeping track....anyone out there have any other suggestions for keeping track of what is going on with your blog?

An Open Apology to Brent Schlenker

I just finished participating in Brent's new Talkcast Corporate e-Learning Weekly.

With enough participation - this could prove to be a very active discussion space. Especially since we don't get enough chances to synchronously chat with each other.

And we can only type so fast....

Brent - my apologies for lack of audio. I've been having sound input problems on my laptop and had no mic. I also had a cell phone with a dead battery.

For anyone else who wants to join his talkcast - do the poor man a favor and give him some audio. Call in or Audio Skype. It will make for a more interesting podcast.

Brent - thank you so much for allowing me to participate and for your patience. You handled that with incredible grace.

Have a great holiday.

RSS Feeds

For those who are interested...

On Bloglines and Google Reader I've been successful copying my home page URL and pasting it into the subscribe area of the appropriate reader.

My home page:

I just tested this on Bloglines (dang - who knew I had 19 subscribers...)

At some point I'll getting around to putting in a formal RSS feed thing.

For those of you reading this directly off of my site - thanks for reading.

Recommendation: DEFINITELY try Google Reader or Bloglines. I've been using Google Reader. Blog reading is more efficient this way. The only downside is that you don't get to read the comments or see some of the pretty graphics.

Hope this helps.

Thursday, December 21, 2006

Playing Games

For our department's holiday party, the boss took us all to Dave and Buster's. For those of you not familiar with this chain, imagine a large restaraunt filled with video games, some billiards tables, and skeeball.

As I've admitted before, I'm not much of a gamer. Since gaming is the next big thing in instructional technology, I figured it was time to start playing.

During my explorations, I found the following (please excuse my lack of memory for names, it was late and there was alcohol involved).

The Snowmobile game: You sit on a snowmobile with similar controls and race down a hill against other people sitting next to you. This was one of the two games my boyfriend and I kept coming back to. Why? There was a goal(i.e. get down the hill faster than everyone else). The controls were intuitive. I didn't have to do anything fancy if I just wanted to get down the hill. If I wanted to punch people, I had to push 1 bright red flashing button. Mr. Flaky has a mean right hook.

Air Strike: Dave and Busters has you walk into a jungle bunker with 6 seats of this game. You are a gunner on a battleship (Why the restaraunt has you walking into a jungle bunker is a question I didn't think of until now...). You and the other people in the game shoot down as many planes and enemy battleships as possible. I found myself recruiting co-workers so we can shoot planes down together. One of the best team-building exercises I've seen in a long time. I found that my colleagues and I would start developing strategies for getting the enemy. "You take this quadrant and I'll go after this boat..."

The Zombie Shooter game: I think this was based on a movie. You and your friend are 2 teenagers who have to defend themselves from zombies. My boyfriend and I hated this game for 2 reasons: 1) There was no way to turn around and the zombies would attack from behind. 2) The controls were not intuitive. You have to point away from the screen, shoot, then shoot the screen. There were also a lot of buttons on the gun you had to push to do simple things like duck and jump. I panic when I am being attacked by zombies and forget which button controls which action.

Thinking about the experience...I've discovered 3 characteristics that make games engaging for me.

1) There is a concrete goal. You get down the hill faster than anyone else. You shoot all the planes.

2) The time for each exercise is reasonably short. Gameplay for each level of the games I liked took about 3 minutes. You then move on to something else or a greater challenge (depending on the type of game / goal). If I want to stop, I can.

3) Intuitive controls. If I have to think hard about what button to push while I'm playing, I get frustrated. If I have to finesse the controls on top of it, I get even more frustrated. This may be why Xbox, Playstation, and many PC-based games hold little appeal to me. I can't keep track of what button I'm supposed to push when and find myself mashing buttons at random hoping to get the thing on the screen to do something useful. Posessing bad small-motor skills doesn't help.

So if I'm going to design a training game for our organization, I'll want it to have these 3 features. If it won't engage me, it sure won't engage my audience of technophobes.

Wednesday, December 20, 2006

Five Things Meme

I'll admit I am not a huge fan of chain letters or tagging games.

Since I have not met most of you in person, I think this is a good opportunity to get to know each other.

Thanks Karyn. I am incredibly flattered you though of me.

So here it goes...5 things you may or may not know about me...

1) I worked at Stone Mountain Park as a laser show technician between '92 and '94. I got to play with powerful lasers and large fireworks. A very cool job - if not terribly renumerative....

2) I am new, avid, golf hacker. Best score to date - 118. And that includes only 1 use of the infamous "overhand wedge" (i.e. throwing the ball out of an inconvient spot - like a bunker). Best legitimate (rules of golf) score - 125.

3) My personal goal for this winter - learn how to snowboard without spending time in the hospital. When I ski, I am the snowplow queen - so I can't be much worse at snowboarding....

4) I am a brand new auntie. Matthew Allen Wickham was born on November 30, 2006 at 9lbs and 7 oz. I look forward to hearing about my brother's hands-on learning experience...

5) My History MA thesis was on the cultural use of Ilex Vomitoria in Georgia.

Tag, you're it!!!! (apologies to those who have already been tagged)

Brent Schlenker
Mark Oehlert
Tony Karrer
Karl Kapp
Alvaro Fernandez

Fear of Success

Brent Schlenker sent me another nice comment on my post Playing in the Digital Sandbox that I'd thought I'd share for those of us who read blogs on feeds:

I think Paul touches on something a little deeper and may not even realize it. Much of that fear is NOT based on what if nobody comes, or what if it's a fad. The fear for many is that people WILL come, and people WILL begin to create their own content and make their own connections with the covetted SMEs. Then where will the value add be for those practicing old school ISD? Its the fear of success for many, not the fear of failure.

It takes a lot of courage, both on the individual instructional designer level and on the organizational level, to allow individuals to create content.

If we're serious about being educators, that's the way it should be.

Think about it:

- People learn more if they are forced to put concepts into practice - through teaching, applying the information in other contexts, creating things for public consumption, etc.

- As educators, we are about helping people learn more (right?).

So why are we so afraid?

I'm seeing a growing consensus in our little corner of the blogosphere that our job, as it evolves, is to create environments that motivate people to learn things, rather than content.

This change in emphasis is long overdue.

Tuesday, December 19, 2006

A Badly Needed Conversation

Mark Oehlert and Karl Kapp are having a badly needed conversation between a practitioner (Mark) and an academic (Karl) within the blog comments for Mark's post If You Believe It's Broken - How Do You Change Our Industry/Models/etc.

Read the comments from bottom to top.

Personally, I've noticed that our little corner of the blogosphere makes these conversations much easier. Practitioners get new models and ideas to develop learning. Academics get a better understanding of their models in practice.

I think we've been missing the feedback loop.

Playing in the Digital Sandbox

Paul Fender hints that it's not just the desire for control that prevents us from adopting web 2.0 tools, but fear of failure...

The fear that we’ll stick up a wiki and no one will use it. The fear that we’ll learn how to podcast and it will turn out to just be a fad. The fear that we’ll start blogging and run out of things to say (not a problem for me ). And, as illustrated by the too lengthy story above… the fear that we’ll go out on a limb and others will think we’re not perfect; that we some times make mistakes; that people will think we’re really just full of bu!!sh@#.

What if you put up a social software tool and no one comes......

In my Moodle install, I've put in some forums. I've been asked about wikis, blogs, and chat spaces. And Paul is right, we can't control how our end-user choose to use these tools...or how others feel about us.

If we listen to the end-user, we may ultimately find a more effective use for all of these tools. Or find that the tools aren't worth using. Isn't that the point of this whole "2.0" exercise?

I am fortunate that I work a space where I feel safe taking huge risks - both my work environment and the blogosphere.

So what big risk have you taken recently?

Monday, December 18, 2006

Update: Talk vs. Action

Soon after I wrote my post Talk vs. Action, I received a phone call from the Neurosurgery Manager.

"Wendy, I'm in this Moodle thing! This is really neat!!! Do you mind if I share this with some of the other staff? I have some people who have been trained and forgot how to scan."

This is the entire point behind this project!!!!!

I also noticed that 3 more managers have logged in since that post and looked at things in the system.

Every person who logs in on their own, with no further prodding on my part, is a victory. If they share with their staff - further victory. I want this thing to be one of those "word-of-mouth" tools that people use because it is useful and works for them, not because it is mandated from higher up.

I've been involved in too many implementations where I had to browbeat people into using new software. Having spent the past 5 years serving as the main punisher, the last thing I wanted to do with this project was spend my time pounding on people when I could be helping them. It will be a nice change of pace if I can pull this off.

Physician Reaction

Friday, I presented Moodle to our Pilot Clinicians group. This group consists of the more tech-savvy doctors in the organization. These are the people who help make decisions about the configuration of our Electronic Medical record, make decisions about workflows and point out problems with our system.

I wish there were more than 5 people at the meeting this week, but I got excellent feedback from the group. Even better, they seemed excited.

What made them happy:

- They liked the reporting mechanisms.

- They liked that all of the tutorials were available under specific job titles. (This is the 3rd group that has looked at this form of tutorial organization and liked it, so I am keeping the course categories)

- They liked that I encouraged them to use the system for training their residents and offered to help.

Other questions/comments they had:

- Does this thing have chat capabilities? Yes. And we can sit down and play with the tools to see how best to use them.

- Does this thing have forums? Yes. All of my EMR courses have 2 forums, 1 for questions (and an encouragement for others to answer questions), and 1 for improvement recommendations for the course. These are not gradeable, but can be. The docs thought this was very cool.

- Does this thing have wikis? Yes. I demonstrated one I put together for a project planning area for our upgrade. The wiki capability generated the most discussion.
+ What is a wiki? (This from the doc that is supposed to be the most tech-savvy in the organization. Eeek.)
+ Why can't we see who makes which change right on the page? My answer - It's in the history. The wiki is a living document. Once a wiki is deemed "final", I can help them convert it to documentation.

The exciting thing about these meetings is that people see what I am trying to do. Even better, the "behind-the-back" noise is just as positive. If something wasn't right, I would know about it.

The next trick is to get other people in the organization to take some ownership and help shape the system so that it works for them. A much harder task.

Friday, December 15, 2006

Talk vs. Action

I have been introducing Moodle to the Manager level over the past couple of weeks and watched to see who uses it and who doesn't.

As anticipated, the gap between talk and action is huge. The challenge - figuring out ways to bridge it.

My change management timeframe for this tool has shrunk dramatically since we moved up our major upgrade to January and reduced the time from installation in our test servers to live from the recommended 20 weeks to 60 days (don't ask).

The system has been positively received verbally. I've received some enthusiastic comments during these meetings. Thus far, I have seen only 2 people outside of the IT department log in and play with the system. This includes the senior management (with a whopping total of 0 logins).

Within IT, I've noticed that the new employees are the ones most enthusiastically using the system. Particularly the network folks. This is encouraging.

The applications team looks at it, likes it, and ignores it. They see it as my baby and a distraction to the "real work" - administering our existing applications. They are also incredibly fixated on the idea that we (I) need to have face time with every student. I suspect that their fixation with classroom training is going to diminish significantly as we find that we don't have the classroom space, bodies, and time to train 2500 people in 2 weeks with what appears to be over 4 hours of material just to prevent our organization from grinding to a stop. I may have to leave that particular issue to the fates.

Looking back, I should have involved the applications team more while I was building the site.

Thus far, I have come up with 2 strategies for bridging this gap.

1) All of the upgrade documentation and materials will appear on this site. No more sending stuff via e-mail. They will get the link. Period.

2) People who want to put training material on our intranet will have to put it on Moodle. I'm having this argument now with one of the other trainers as we speak. I always find it interesting that the educators (the ones who lead the change whether they want to or not) are always the most resistant.

I'm surprised by this since an unexpected side benefit to this system is that it has made it easier for me to organize and rearrange my materials. Furthermore, the people who have worked through the tutorials have liked how the information is organized and how they can stop and start as needed.

I'm gearing up to show the Pilot Clinicians (our more tech-savvy MDs) this new system. I will keep you informed......

Further adventures in Customer Service

In a previous post, Adventures in Customer Service, I have complained about software vendors who place critical bug fixes in new versions. Upgrading is a major project that requires significant resources that we don't have. We are going to be doing a MAJOR upgrade starting January 9th and the resources are in the middle of planning and preparing for that project.

OK - it's one thing to break something that makes it easier to work. We can work around that. It's a whole 'nother thing when you break something that, by breaking it, puts your client at legal risk.


Our organization has not made a decision on what to do yet. Current thinking - hope that nothing happens between now and March, when we go live on the new major upgrade.

Thursday, December 14, 2006

Welcome to Wendy's Blog - The Current First Time Visitor's Guide

Thank you for spending your valuable time reading my blog. I've been at this (more sporatically than I would like) since September and find that my blog is an ever-evolving beast.

Who I am (the professional self)

I am a corporate software trainer / instructional designer / eLearning specialist / LMS administrator / implementation bully in a health care group in Washington DC.

What I write about...

The blog started as a way to journal my experience implementing Moodle and make sense of changes occuring in technology, education, and business.

If I find an interesting article, video, podcast, book or blog post, I'll write about it. Most of my interests these days are in education, change management, brain science (particularly research on how people learn), productivity, and new technologies. I am always looking for recommendations.

Within the blog, you will also find a diary of my attempts to apply these new ideas and theories into my work as a corporate trainer. As you'll see, I'm not always successful.....

So why the strange title?

The title is based on the Technology Adoption curve. I find that, by nature, I tend not to be an early adopter. Instead, I am usually adopting a technology when it starts becoming popular...and after many of the bugs have been beaten out.

Dirty little secret: my home network is still wired, I don't have a MySpace or Facebook or Flickr page, my cell phone only does "phone", and I don't own a BlackBerry.

These are not the characteristics of an early adopter.

When I started the blog, I thought the blog would focus on technology adoption. It's turned into something much more than that.


I do read them before I post them. I'm a little paranoid that way....

To date, I have rejected 1 comment post for content that was completely irrelevant to the blog and not suitable for public consumption.

Like other bloggers, I blog in an attempt to get feedback from people smarter and more experienced than myself. I am incredibly fortunate for having attracted a group of readers that I carry tremendous respect for.

Why I don't have a tidy list of topics and appropriate posts in this First Time Visitor's Guide....

A combination of lack of time and excess of laziness. At some point, I'll read through what I've written to see if there are any trends.

Besides, I'll probably have another First Time Visitor's Guide in 3 months. This blog will continue to change and it should.

Thank you to Dr. Tony Karrer for giving my blog so much press and for being such a thoughtful cheerleader.

Tuesday, December 12, 2006

Educators vs. Subject Matter Experts

Recently, I've sat through a discussion with one of our subject matter experts as he attempted to teach me how to perform credit card batch maintenance on one of our systems.

The system itself is quite simple - look at the credit card transactions and make sure they are correct. If they are, click the Submit button. If not, click the Edit button next to the incorrect transaction. Correct the transaction and click OK. When everything is correct in the batch, click Submit. A yes/no decision tree within an intuitive user interface.

I happen to like this subject matter expert. He is knowledgeable about the systems he works with and possesses almost saintly patience. Sadly, by the time the subject matter expert finished explaining how the batch maintenace system worked - I was thoroughly confused.

The "training" went something like this:
- The system is on Internet explorer at X address
- Log into the system
- "If you don't know your user name or password, people generally call me, but they really need to talk to their practice administrator. You know, I really need to enforce this....."
- This is the main screen. (He then provides a detailed explanation of what each button does - whether we use the button or not.)
- 30 minutes later......
- Click Batch Maintenance
- "You really should only have 1 batch, but lots of people have multiple batches so you really need to make sure you have the right batch. I try to tell them to only open one batch, but they don't listen to me. If you have the wrong batch...."

How many "trainings" given by a subject matter expert have you sat through like this?

The majority of the subject matter experts I know approach training as an evil akin to getting a root canal with no anesthesia. As a result, many provide training in the following manner:

1) The expert assumes you come in with a certain level of prior knowledge, either about the system or the process. That assumed level of prior knowledge varies based on the subject matter expert's mood and personality.

2) If the subject matter expert likes you, has time to talk, and/or thinks you are a moron and is taking pity on you (again, depending upon the subject matter expert's mood), they assume that you need to know EVERYTHING about the system, including the location of interesting lines of code or strange factoids about the evolution of the system across versions.

3) The subject matter expert is not concerned with the context in which you are going to be using the system. That is YOUR problem.

From my perspective, an educator's JOB is to make a topic understandable, thereby encouraging behavior change. When we approach training, we:
- Determine the student's actual prior knowledge of the topic
- Figure out what the student needs to know. This includes eliminating the unnecessary from our courses.
- Place that knowledge in a context that makes sense to the STUDENT. Not the developer or the administrator or the expert.

These important steps differentiate an educator's training vs. a subject matter expert's training. These steps are the ones that are lost when someone without an educator's mentality designs and delivers training.

Monday, December 11, 2006

Big Question - Dec 2007

I do a variant of this exercise 3-4 times per year.

This iteration of the Big Question allows me to think about past, present, and future on a more professional and public level.

What will I remember most about 2006?

1) Finally bringing up the last department on the Electronic Medical Record. 5 years of paper to computer conversions in 2 different institutions comes to a close. Not a moment too soon.....

2) Bribing my boss into letting me attend eLearning 2006 and NOT another health care vendor conference. As a result, I managed to escape my isolation from the eLearning industry. More importantly, I found a group of like-minded people both at the conference and in the "blogosphere." It's still nice to have your ideas validated and to know that others sense the same tsunami approaching.

What are the biggest challenges for me as I head into 2007

1) Personal: Implement and train a new program to 2500 people in 90 days. Including configuration and planning. Training time provided: 2 weeks. I hate this trend towards speed with "training" as another part of the implementation checklist. But this is my world...

2) Professional: Brent Schlenker (again) is dead-on. Change management. Not just among the students, but among our fellow professionals. As I've watched and participated in the conversation over the past few months, I think we are circling closer towards workable theories and techniques for incorporating this new paradigm.

What are my predictions for 2007?

1) The sun will rise and set for the next 365 days

2) There will be at least 1 more post from a blogger on blogging

3) There will be at least 1 more podcast from a podcaster on podcasting

4) Educators will continue to fret about how their profession is changing.

To those of you who read my blog, lurkers and commenters, thank you for making 2006 a life-changing year.

Correction: The conference I went to that was so life-changing was eLearnDev 2006 in Utah. I hope next year to make both this conference AND eLearning 2006....if the boss will let me out of my cubicle......

Tuesday, December 05, 2006

There's Gotta Be A Way To Do This......

Thinking about my post "Good Workflow Through Games" and my comments on Dr. Karrer's blog, I am disappointed to find that I am spending more time poking holes and no time fixing them. This griping phase may be part of the process.....

Still, there's gotta be a way to do this.....

Today's Washington Post includes an article on how Madden NFL teaches people the nuances of football strategy.

I'm thinking aloud, please humor me for the following.....

Football, to me, is all about predicting what the other side will do. How will this action cause the other to react.

There are many strategies that a coach uses to achieve the desired result. From what I can tell, these are carefully scripted in advance.

During the game, there are 2 areas of improvisation: the coach who changes a planned strategy mid-game (manager) and the player who reacts during the play (implementation specialist). These actions fall within a range of possibilities determined by the rules of the game and the laws of physics.

Madden NFL has been around a since 1989. With each version, the programmers have added more plays and more variables as football evolves. I suspect the decision mechanism behind this game is incredibly sophisticated.

So what does Madden NFL have to do with developing a gaming program that will assist with business workflows?

I'm thinking that a successful workflow game would include the following characteristics:

- Focus on a workflow that stresses cause / effect. Customer service and sales are the obvious choices. In my context, maybe a game that focuses on the patient experience or whether a piece of information successfully makes it from one point to another. Many of the workflows that I deal with tend not to have an obvious predictive angle so I may have to stretch more than most.

- An easy way to add options as different variables and strategies become apparent. I haven't sat through a process meeting yet where they mapped the current process accurately on the first try.

- Development of limitations to the process. What are the limits of what you do without closing off options? Each piece of the game would have to be carefully defined.

Kids (including my friends) happily spend many hours on Madden NFL. Our employers won't give us that much time. Furthermore, we have to take the next step of taking the solutions learned in the game and implementing them to people. I know that some NFL players play Madden NFL, but I haven't found anyone admitting that it impacts the way they play the game. Yet.

The Middle Manager Meeting

Now that I have the blessing of the Sr. Managers, I am starting to meet with the departmental managers and providers. The first group consisted of the management staff for OB/GYN, IVF, Neurology, Neurosurgery, Orthopaedics, Emergency Medicine, and Psychiatry.

As anticipated, they were not nearly as excited as the Senior Managers. I am a bit nervous since they said very little during the meeting. Admittedly, I only had 15 minutes to present and the Senior Manager's introduction consisted of "You are doing this" rather than any advantages they will see from its use (most importantly, training access).

I've worked with many of these managers during various implementations, so I suspect that I will get more honest feedback later as I encounter them in the halls.

I have more meetings and presentations scheduled during December. As I meet with each group, I have offered to show the system to anyone else they may think would be interested. I'm hoping this subtle buzz-building will help with acceptance.

Monday, December 04, 2006

Good Workflow through Games

It's been awhile since I have run into an article that made me want to drop everything and write. Larry Dignan, in his article "Can game design make your company more efficient?", highlights the work of Edward Castronova, an expert on virtual worlds and economies from Indiana University. In his summary of Castronova's talk at the Terra Nova State of Play symposium, Dignan writes:

Given most technology implementations rely heavily on good processes, game design could enhance returns. Wouldn't it be nice to botch a technology project in a virtual world, fix the problems and then roll it out without millions of dollars being dropped on pricey consultants?

Yeah, that would be nice. However, the skeptic in me does not see this as the utopian process improvement solution Dignan claims (never mind that the "virtual world" solution will still require a full technology implementation project).

The group developing the workflow through the virtual environment will still have to perform their old processes in their "First Life" environment. Like real life process-improvement initiatives, you still need to take real people's time away from their regular tasks (or add on to those tasks), then hope that the members of the group can accurately describe their existing processes and predict how changes in any step will impact that process.

In the gaming environment, the folks doing the workflow adaptation will not only have to grapple with the usual political and change management issues, they will also have to fiddle with the technology. How many of your organizations have multiple unused copies of MS Project or Visio taking up space on hard drives because fiddling with the technology was too time consuming?

Even if things go smoothly, despite ample testing (and a few tears), the transition from virtual process to reality may prove to be just rockier than processes developed using crayons, stickers and butcher paper because it proves to be harder to incorporate new information as the process improvement project evolves.

My personal opinion: For a virtual world process improvement game to work, there has to be enough case studies to create a robust decision tree. The target process should be narrow and the game should be able to address special case exceptions. For example: the workflow questions "What is the best process for handing Rx refill requests?" Special cases include Schedule II controlled substances, short-term refills between appointments, prior authorizations requirement, and refill rejections. There also needs to be an easy way to incorporate new information.

If gaming will be used as part of technology implementation, the technology should be old enough so that there is a library of best, worst, and OK practices for each workflow decision that needs to be made with that technology. The game needs to incorporate both the technology and surrounding computer systems PLUS the human workflows. In my ideal universe, I should then be able to use the end product for implementation training with little editing.

I will admit I am not much of a gamer. I am not a game designer nor am I a programmer, but to my liberal-arts eye, this strikes me as a very tall order.

Are my initial impressions of this idea correct? Is there a better way to use virtual worlds for process improvement?