Learnlets

Secondary

Clark Quinn’s Learnings about Learning

The ‘Least Assistance’ Principle

20 February 2009 by Clark 9 Comments

While I agree vehemently with most of a post by Lars Hyland, he said one thing I slightly disagree with, and I want to elaborate on it.   He was disagreeing with   “buying rapid development tools to bash out ill formed ‘e-learning’ to an audience that will not only be unimpressed but also none the wiser – or more productive”, a point I want to nuance.   I agree with not using rapid elearning to create courses for novices, but there is a role for bashing out courses for another audience, the practitioner.   And there’s something deeper here to tease out.

I want to bring up John Carroll’s minimalist instruction, and highly recommend it to you. He focused on a) meaningful tasks, b) active learning quickly, c) including error recogition & recovery, and d) making learning activities self-contained (a lot like games, actually).   In The Nurnberg Funnel, he documented how this design led to 25 cards, 1 per learning goal, that beat a 94 page traditionally designed manual hands-down in outcomes.

Another way to think about it is something Jim Spohrer mentioned to me once. Now, Jim’s been an Apple Fellow, and is leading research at IBM’s Almaden Research Center.   He really cares and likes to help people, but he’s very busy.   So he adopted a ‘least assistance’ principle, where he would ask himself what’s the least he can do to get this person going, because there was more to do and more people to help than he was able to keep up with.   And I think it is a useful way to think about supporting learning.

This sounds a lot like performance support, and that’s definitely a mind-set we need to adopt. When Harold Jarche and Jay Cross talk about the death of the training department, they’re talking about not focusing on courses, and instead taking a broader, performance perspective.   Obviously, we want to talk about portals of resources, but we also need to recognize that there are formal learning situations that don’t require the full formality.

We develop full courses to incorporate motivation, practice, all the things non-self-directed learners need.   But there are times when we need to provide new information and skills to self-directed learners.   When we’re talking to practitioners who are good at their job, know what they’re doing and why, and know that they need to know this information and how they’ll apply it, we can strip away a lot of the window dressing. We can just provide support to a SME so that their talk presents the relevant bits   in a streamlined and effective way, and let them loose.     That, to me, is the role of rapid elearning.

It’s not for novices, but it’s effective, and more efficient.   In this economic climate, we don’t have the luxury of full development of courses for every need.   Moreover, in any climate, we shouldn’t give people what they don’t need, instead we need to focus on what the ‘least assistance’ we can give them is.

In many cases, the least assistance we can give is self-help, which is why I believe social learning tools are one of the best investments that can be made.   The answer may well be ‘out there’, and rather than for learning designers to try to track it down and capture it, the learner can send out the need   and there’s a good chance an answer will come back!   There’s a lot to making such an environment work; it’s not the case that ‘if you build it, they will learn’, but it’s still going to fill a sweet spot in the performance ecosystem that may not be being hit as of now.

Don’t look for everything you can do in one situation, unless you’re flush with too much time and resources (in which case, watch out!), instead look for the least you can do that will get the job done so you can do more for everybody. It’s likely that’s more to their taste, anyway. And that’s enough from me on that!

Comments

  1. sflowers says

    23 February 2009 at 4:16 AM

    Wow! This discussion is so cogent and timely. We have been having the EXACT conversations within our workgroup. We reallize that something isn’t right with our current models, some of us have recognized this for quite some time.

    The ideas that Lars and yourself are talking about are things I’ve been attempting (often unsuccessfully and unskillfully:)) to articulate to every organization that I’ve been a part of.

    There are a lot of reasons why I think that alternative delivery methods fail to live up to potential:

    1. They are often thought of as isolated interventions. This makes me a sad panda and goes back to the ‘spray and pray’ solution mentality. This is a tough nut to crack with so many stakeholders and owners (each with an expectation of traditional packaging.)

    2. We support the product assembly with an array of theories. The ‘pick what you want, flavor of the day’ theory support makes it pretty difficult for us to self diagnose what’s wrong with the typical package. Try to bring a pragmatic argument to the table and you are met with ‘but, so and so says’. I don’t care as much about what so and so says as I do about meeting the needs of my peeps. Truth is a solution is about more than what a slew of theories ‘can’ support. It’s about doing what you can when you can to deliver the right solution. Minimalist ideas fit the bill.

    3. Our design folks often get hung up on what’s been done before. We are model driven and breaking out of a pattern of packaging is a really difficult task. Changing that expectation with exemplory cases and following that up with comparative studies is likely the only way we are going to win the expectations battle.

    4. When something new comes along (rapid eLearning, for example) decision makers tend not to fully qualify it for what ‘part’ of the need it will meet and how it will meet that need. Ooh, a new paintbrush. Order a bunch of these and we’ll have everyone paint everything with this brush. It’s far too easy for folks with a limited imagination to evaluate a solution path for what it is instead of listening to bits of pundit around the table and concluding with narrow focus.

    5. Our design folks are limited in their skillsets by many years of learning what we think they need to know to DO what they need to do. The traditional education focuses a tremendous amount of energy on theory and practice to support the theory. As a result, it’s a little unfair to expect most designers to be able to fill multitude of skill roles that it takes to make a successful product. Knowing how to write is a rare skill. Of those that know how to write, even fewer can write well for their audience. I’ve seen far too much of what I call androidgogy. Programmed instruction…

    6. We bend to the will of the SME. We bend to the will of the designer. We bend to the will of the stakeholders. We bend to the will of the developer. So many wills. The SME wants to fill it with his passion. The designer wants to do everything they can to apply each theory appropriately (structuring the product by these rules). The stakeholders want their piece, often adjusting the design during development as they see what can be done or ask others what they think since ‘this stuff isn’t their business’. The developer wants to contribute, this often results in overcomplication of the solution. We need less forces of will. Particularly when we try to keep these forces equal.

    So we have come to a point where we now expect that we can toss aside our developers and one-stop-shop a soup to nuts product with a small staff of designers. Unless we change what our folks know, we are destined to experience the same level of fail we have been for quite some time.

  2. Clark says

    23 February 2009 at 7:01 AM

    Steve, you point out some real issues that I suspect many will resonate with. I will immodestly point you to my Monday Broken ID series of blog posts which tries to point out some underlying principles that cross theories, argues that you can’t bend to the will of the SMEs, etc. More to come. I wish you the best of luck!

Trackbacks

  1. » OLDaily per Stephen Downes, 21 de febrer de 2009 TIC, E/A, REF / PER…: says:
    22 February 2009 at 6:42 PM

    […] auxiliars del mètode.” Clark Quinn, Learnlets (glops o glopets d’aprenentatge) [L’enllaç] [etiquetes: aprenentatge en […]

  2. What’s the least you can do? | Workplace Learning Today says:
    23 February 2009 at 5:02 AM

    […] The ‘Least Assistance’ Principle | Clark Quinn | Learnlets | 20 February 2009 […]

  3. So many thoughts, so little time — Internet Time Blog says:
    6 July 2009 at 2:42 PM

    […] The ‘Least Assistance’ Principle, February 20, 2009 […]

  4. Internet Time Blog : Informal learning hot list for February 2009 says:
    13 February 2013 at 11:48 AM

    […] The ‘Least Assistance’ Principle […]

  5. The Least and the Lazy – Learning Emergencies says:
    5 March 2016 at 7:53 AM

    […] “Least Assistance Principle” struck me. It isn’t a new concept in the design world, but does a better job of describing how […]

  6. The future role of the enterprise’s learning and development department says:
    10 January 2017 at 11:51 AM

    […] should listen to Clark Quinn and do as little as possible to be useful – what he calls the Least Assistance Principle. It’s not being rude or lazy, it’s ensuring the optimum use of […]

  7. The future role of the enterprise’s learning and development department - Human Capital Management UKI-Benelux-Nordics says:
    15 June 2017 at 1:13 AM

    […] should listen to Clark Quinn and do as little as possible to be useful – what he calls the Least Assistance Principle. It’s not being rude or lazy, it’s ensuring the optimum use of […]

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Clark Quinn

The Company

Search

Feedblitz (email) signup

Never miss a post
Your email address:*
Please wait...
Please enter all required fields Click to hide
Correct invalid entries Click to hide

Pages

  • About Learnlets and Quinnovation

The Serious eLearning Manifesto

Manifesto badge

Categories

  • design
  • games
  • meta-learning
  • mindmap
  • mobile
  • social
  • strategy
  • technology
  • Uncategorized
  • virtual worlds

Blogroll

  • Charles Jennings
  • Christy Tucker
  • Connie Malamed
  • Dave's Whiteboard
  • Donald Clark's Plan B
  • Donald Taylor
  • Harold Jarche
  • Julie Dirksen
  • Kevin Thorn
  • Mark Britz
  • Mirjam Neelen & Paul Kirschner
  • Stephen Downes' Half an Hour

License

Previous Posts

  • March 2023
  • February 2023
  • January 2023
  • December 2022
  • November 2022
  • October 2022
  • September 2022
  • August 2022
  • July 2022
  • June 2022
  • May 2022
  • April 2022
  • March 2022
  • February 2022
  • January 2022
  • December 2021
  • November 2021
  • October 2021
  • September 2021
  • August 2021
  • July 2021
  • June 2021
  • May 2021
  • April 2021
  • March 2021
  • February 2021
  • January 2021
  • December 2020
  • November 2020
  • October 2020
  • September 2020
  • August 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • March 2020
  • February 2020
  • January 2020
  • December 2019
  • November 2019
  • October 2019
  • September 2019
  • August 2019
  • July 2019
  • June 2019
  • May 2019
  • April 2019
  • March 2019
  • February 2019
  • January 2019
  • December 2018
  • November 2018
  • October 2018
  • September 2018
  • August 2018
  • July 2018
  • June 2018
  • May 2018
  • April 2018
  • March 2018
  • February 2018
  • January 2018
  • December 2017
  • November 2017
  • October 2017
  • September 2017
  • August 2017
  • July 2017
  • June 2017
  • May 2017
  • April 2017
  • March 2017
  • February 2017
  • January 2017
  • December 2016
  • November 2016
  • October 2016
  • September 2016
  • August 2016
  • July 2016
  • June 2016
  • May 2016
  • April 2016
  • March 2016
  • February 2016
  • January 2016
  • December 2015
  • November 2015
  • October 2015
  • September 2015
  • August 2015
  • July 2015
  • June 2015
  • May 2015
  • April 2015
  • March 2015
  • February 2015
  • January 2015
  • December 2014
  • November 2014
  • October 2014
  • September 2014
  • August 2014
  • July 2014
  • June 2014
  • May 2014
  • April 2014
  • March 2014
  • February 2014
  • January 2014
  • December 2013
  • November 2013
  • October 2013
  • September 2013
  • August 2013
  • July 2013
  • June 2013
  • May 2013
  • April 2013
  • March 2013
  • February 2013
  • January 2013
  • December 2012
  • November 2012
  • October 2012
  • September 2012
  • August 2012
  • July 2012
  • June 2012
  • May 2012
  • April 2012
  • March 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • October 2011
  • September 2011
  • August 2011
  • July 2011
  • June 2011
  • May 2011
  • April 2011
  • March 2011
  • February 2011
  • January 2011
  • December 2010
  • November 2010
  • October 2010
  • September 2010
  • August 2010
  • July 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • January 2010
  • December 2009
  • November 2009
  • October 2009
  • September 2009
  • August 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • March 2009
  • February 2009
  • January 2009
  • December 2008
  • November 2008
  • October 2008
  • September 2008
  • August 2008
  • July 2008
  • June 2008
  • May 2008
  • April 2008
  • March 2008
  • February 2008
  • January 2008
  • December 2007
  • November 2007
  • October 2007
  • September 2007
  • August 2007
  • July 2007
  • June 2007
  • May 2007
  • April 2007
  • March 2007
  • February 2007
  • January 2007
  • December 2006
  • November 2006
  • October 2006
  • September 2006
  • August 2006
  • July 2006
  • June 2006
  • May 2006
  • April 2006
  • March 2006
  • February 2006
  • January 2006

Amazon Affiliate

Required to announce that, as an Amazon Associate, I earn from qualifying purchases. Mostly book links. Full disclosure.