Learnlets

Secondary

Clark Quinn’s Learnings about Learning

Evolutionary versus revolutionary prototyping

26 May 2015 by Clark 2 Comments

At a recent meeting, one of my colleagues mentioned that increasingly people weren’t throwing away prototypes.  Which prompted reflection, since I have been a staunch advocate for revolutionary prototyping (and here I’m  not talking about “the”  Revolution ;).

When I used to teach user-centered  design, the tools for  creating interfaces were complex. The mantras were test early, test often, and I advocated  Double Double P’s (Postpone Programming, Prefer Paper; an idea I first grabbed from Rob Phillips then at Curtin).  The reason was that if you  started building too early in the design phase, you’d have too much invested to throw things away if they weren’t working.

These days, with agile programming, we see sprints producing working code, which then gets elaborated in subsequent sprints.  And the tools make it fairly easy to work at a high level, so it doesn’t take too much effort to produce something. So maybe we can make things that we can throw out if they’re wrong.

Ok, confession time, I have to say that I don’t quite see how this maps to elearning.  We have sprints, but how do you have a workable learning experience and then elaborate it?  On the other hand, I know Michael Allen’s doing it with SAM and Megan Torrance just had an article on it, but I’m not clear whether they’re talking storyboard, and then coded prototype, or…

Now that I think about it, I think it’d be good to document the core practice mechanic, and perhaps the core animation, and maybe the spread of examples.  I’m big on interim representations, and perhaps we’re talking the same thing. And if not, well, please educate me!

I guess the point is that I’m still keen on being willing to change course if we’ve somehow gotten it wrong.  Small representations is good, and increasing fidelity is fine, and so I suppose it’s okay if we don’t throw out prototypes  often as long as we do when we  need to.  Am I making sense, or what am I missing?

Comments

  1. Sky says

    26 May 2015 at 10:48 PM

    I’ll point out additionally that the cost of making a software prototype has come down so far that it can actually be cheaper to prototype in software than on paper. That’s because when you prototype in software you get something that runs, not something that you have to -imagine- would run. The thing unsaid is that usually when we talk about prototypes (of products) we are talking about prototypes of software systems. So prototyping in other areas can still suffer the fate you describe — when you embody something physically, then you may have invested so much you don’t want to throw it away.

    Now, that said, in learning, one of the things you want to do is check your knowledge, or check your proficiency, early and often. So taking in information is like the “sprint” phase, then you try applying that knowledge, then you revise your models or you seek new information, and so forth. So the principle that makes most sense is to take small steps when learning — small ingestion of knowledge, small practice, small application, small corrective steps, and cycle frequently.

    Ah, the other thing is you talk about “increasing fidelity” — this presupposes there is a correct way, or a correct model of a real situation. That idee fixe view of the world doesn’t work as well as it used to. Most of the time when we’re learning in real life, business, science (etc.) we are trying to understand systems that are constantly evolving, so there may not be as much of this “increasing fidelity” as there was 20 or 30 years ago. That’s certainly a core reason that -agile- works when it comes to software development — we don’t have a good idea what we want, and the prototyping and development helps us understand that.

  2. Chris Riesbeck says

    28 May 2015 at 2:08 PM

    Let me be more radical and push for more than just elaboration of working designs in sprints. Following lean startup ideas, every release should be a viable product on its own.

    In a Prezi I did a few years back (https://prezi.com/c75ncmsqv8m9/3-transformative-agile-ideas-for-education/ — Dramamine recommended), I pushed for assessment-first experiences focused on small but standalone useful skills, e.g., “can build a web page to do simple calculations” not “can write a FOR loop.” (Before would have come a module on “can build a web page” etc.)

    A lean startup approach to developing such things would begin with building assessments for the skills we’d like to teach, and testing their viability. Can experts pass our assessments? Do they accept them as valid? Do target learners fail these assessments in the way we expect? Do they also accept them as valid? Can we generate instance of these assessments ad infinitum? If the answer to any of these questions is no, already we have a problem. We have failed fast, as they say. Otherwise, these assessments are in themselves a viable useful deliverable.

    The second release would be developing the simplest activities that could possibly work to help students learn how to pass the test. Drill and practice, challenge and defend, construct and measure, etc. The test of course is how well students do on the assessments from the first release.

    Rinse and repeat.

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.