Learnlets

Secondary

Clark Quinn’s Learnings about Learning

Revisiting the Ecosystem

28 February 2017 by Clark 6 Comments

One of the keys to the L&D  revolution is recognizing the full performance ecosystem and the ways technology can support performance and development.  I’ve tried to represent and share  my thinking via diagrams (including here, here, and here).  Prompted by a recent conversation, it was time to revisit the representation.

the performance ecosystemHere, I’m layering on several different ways to think about the goals, elements, etc.  (Given that this is an initial version, I’m kind of haphazard about labels like mechanisms, components, etc.)  To start, as I continually argue, at the bottom it’s about coupling optimal execution with continual innovation.  We need to do well those things we know we need to do, and then we need to continually improve.  I think that more and more of the optimal execution is getting automated.

On top of that, we have components – content and people  – and the tactics to leverage them. We create or curate content (curation over creation!), and we develop relationships through community or find appropriate expertise through recommendations or search.   The goal is to have the right content and the right people ‘to hand’ to work with.

We develop content elements like performance support to support performing in the moment, and learning resources for self-directed learning over time.  We also use courses, whether individual or collaborative, to develop people (particularly when they’re novices). I’d  put courses to the left and performance support to the right (above content) if we were talking about developing people (as I have here). So,  for novices we first use courses, then  practitioners need resources and coaching, and experts need interaction.   However, performance support is on  one side on a continuum of mechanisms from performing, to developing, to innovation.  That’s what I’ve captured here.

Similarly, we use social elements like coaching, mentoring, and informal learning to develop ourselves and our organizations over time.  We use  processes  like consuming and completing to execute. Then we  develop our ability to execute and the continue to learn through  communicating and collaborating.

There are lots of ways to represent the ecosystem, and given that elaboration theory tells us multiple representations help, here’s another stab. There are lots of elements to consider and fine tune, but I like to share my thinking to help it develop!  Overall, however, the opportunity is the chance to be contributing to organizational success in systematic and valuable ways. And that, I’ll suggest, is valuable. I welcome your thoughts.

Comments

  1. James McKim says

    6 March 2017 at 6:52 AM

    Interesting depiction. I agree that multiple representations from different perspectives bring a more comprehensive, clearer picture of the ecosystem.

    I wonder where you see Competency Modeling (defining skills, knowledge, behavior for a specific role) in this picture?

  2. Clark says

    6 March 2017 at 9:29 AM

    James, I see competency modeling falling under formal learning. That is, we use such models to define what we should be curating or creating. Increasingly, however, I think it’s more work than makes sense (see an old/new picture of L&D activities here). Pretty soon, I reckon, anything that can be so well described in a competency model will be automated. And other stuff will be too fluid to define before it’s out of date.

    Two other thoughts: competency modeling needs to design backwards to separate out what’s in the head versus what’s in the world. I’d also like to devolve responsibility to the communities that are around those roles and skills to maintain their own competency definitions. Thanks for the inquiry.

  3. Henrik Svensson says

    7 March 2017 at 12:23 AM

    Nice model! Where would you put the necessary evil of compliance training? I can’t place it since it’s not performance and not development. It’s more of “we have your skills/knowledge documented for when FDA comes to visit”.

    Or maybe we’re thinking about it from the wrong perspective? If one were to analyze compliance training from a design thinking perspective, maybe there shouldn’t be anything called “compliance training” but rather “Our Service Reps aren’t allowed to service our machines unless we have documented proof of their knowledge and skills. How do we solve that the most efficiently?” The solution might be something completely different than “train them and document the fact”.

  4. Clark says

    7 March 2017 at 8:20 AM

    Henrik, thanks for the question. I think when compliance training is CYA for legality (e.g. “we gave him sexual harassment training, so when he did it he’s a bad person, we’re a good company”), it’s not on this diagram. When you truly want to ensure new responses are there, then it fits under courses and performance. And your rethink is spot on: see the ‘design backwards’ reply I wrote to James’ comment.

Trackbacks

  1. Learning in a High Performance Ecosystem – Design4Performance says:
    5 February 2018 at 4:21 PM

    […] Clark also shared one of his diagrams around conceptualising an ecosystem here, which I found fascinating, particular for its consideration on tactics people engage with content or people. […]

  2. Learning in a High Performance Ecosystem - :: arun pradhan :: says:
    21 September 2019 at 7:53 PM

    […] Clark also shared one of his diagrams around conceptualising an ecosystem here, which I found fascinating, particular for its consideration on tactics people engage with content or people. […]

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.