Tuesday, November 02, 2010

#DL10 Building High Impact Learning Communities

Presenters: Josh Little and Nemo Chu
Goal: How to become an internal marketer to your learners. Ongoing engagement.

(interesting - 2 people in the room looking to learn more about "community learning" but it struck me that they are still thinking of learning as a one-shot event deal.)

- Identify the pain
- talk the talk
- overcome objections
- make a business case
- launch a community

Reason to launch a community - to make the business (and people) better

What is collaborative learning?
- 2 or more people attempt to learn something together. (Wikipedia)

Wikipedia as accurate as Britannica (even more so since errors fixed in minutes rather than years)

Who wants to be a millionaire
50/50 - 50% right
phone a friend - 65% right
ask the audience - 91% right

Crowdsourcing - use wisdom of crowd to find right answer. Folks who don't know will cancel each other out. Because the folks who know will be louder and together.
- Outsourcing of tasks, traditionally performed by a single person performed by a group
- Benefits
+ Do more with less
+ Wisdom of crowd
+ Expand the talent pool
- Wikipedia
- Examples: Digg, Netflix - crowdsourcing the development of a decision engine.

None of us is as smart as all of us.

Can you crowdsource your training?
- Yes

The Pain
- Corporate Trainers
+ Lots to do. No budget.
- Small Businesses
+ Pass on tribal knowledge. Very inconsistent. No training infrastructure.
- Thought Leaders
+ On the road a lot. Need to "duplicate self."
- Brand Marketers
+ Products very technical. Novices need to learn from experts.

Need to move from traditions - top down. Things not trickling down fast enough (or at all)

Move to collaborative - leadership at center.

This is a big step. NOT re-doing the org chart. Redoing the learning map.
- How you get and archive knowledge.

Long Tail - niche content, something for everyone. Often applied to markets.
- Think about frequency of use.
- Most organizations don't create the specific information that may be needed down the road.
- Just in case v. Just in time.
+ 80-90% of what you need to do your job is in the long tail (specifics)
- Also helps to convince clients to slim down the course if the specifics are still being addressed. Not want to dump everything in the course.
- Amazon an example of the long tail. Can find anything no matter how esoteric.

Your training program - why can't you have it all?
- For most, the long tail doesn't exist. More because they can't get to it.

Principles of Collaborative Learning
- Learn or Die
- We all learn and teach every day
- Great teachers rule the universe
+ truly great managers, leaders etc also great teachers
+ Help people recognize that they can actually share too!
- Learning is about sharing and collaboration
+ Everything we learn is afforded or created by someone else
- People learn best from their peers
- Great learning experiences
+ Has nothing to do with the bells and whistles of elearning
+ Everything to do with creativity, humor, diversity, timing, passion, individualization
- good enough is good enough
+ Great learning experiences REAL and in the trenches
- people learn when they are ready to learn
+ not when WE are ready to teach them (please see comment in my prior post as a reminder)
+learning does not have to be about time and place.
- empower, not enroll
- There is energy and potential in the crowd.
+they have expertise you need
+ got to agree on "good enough is good enough"
+ think about the alternative (usually nothing)

Trying to move towards community.
- If it is OK in a training room to say something wrong, why is it not ok in a learning community?
+ we could use it as a teachable moment.
+ part of it is framework
+ part of it is rewarding pro-activity,
+ good gardening to help mitigate the fear of "documenting my stupidity"

Trying to build a community for the ENTIRE org - next to impossible.
- Unless really trying to flatten communication

Think in term of communities of practice
- group of like-minded, like-tasked professional.
- Content related
- Job role, team, project (GW examples: help desk, Banner (tool)

Business Case - 3 questions
- What would my organization gain if we made 1 momre sale.
- What would my organization save by avoiding one adverse event
- Is the sum of #1 or #2 greater than the cost of launching a learning community (cost + human cost)

Case studies
- Spinweb, Michael Reynolds
+learning center - help augment support center
+ Goal: Better customer service to clients
+ Org roadblocks - "sounds hard", populate with lots of content.
+ resolve - populate as you go.
+ to launch - put content in, tell clients and promote. Gradually build following.
+ launch received - positive feedback.
+ challenges - sometimes people not familiar with how to interact. Find a specific question, send link, encourage folks to register and explore with the initial link as an intro
+ successful practices - mention to EVERYONE. When help desk call, meet people, during training, etc

- eLearning - 2 minute tutorials help
- Just post content. Make the knowledge available as quickly as possible.

- learning community for software developers of front end.
- Wanting to document and preserve institutional knowledge. make it available to those who need it.
- need to have incentives to contribute. Otherwise, get the 85 watch / 15 post.
- learning curve for new hires dramatically reduced. Get them up to speed fast because can just give them one link.
- don't make your community TOO specific and closed. Learn from others outside the team too.


1 comment:

Unknown said...

Loving the summary of our workshop here. Thanks for taking the time to publish this!