So I want to take a step back and look at a bigger picture for a moment. The previous diagram I created was meant as more of a “learner design” perspective, in the sense that the dual paths would be the two main possibilities for learners. This was meant to look at the course from the eyes of a learner. But, the diagram breaks down in many ways since this will not be a traditional course. This course will attempt to deconstruct what it is to learn, be a learner, and to move through a course.
There has been a lot of really good feedback on the diagrams. Mike Caufield makes a great suggestion for considering the idea of federation in this course. I’ll have to figure that one out some more and unpack that in another post. I want to zero in on a few big design considerations first.
Stephen Downes asked “But is that really distributed, the way a cMOOC would be? At a certain point, the movement to collect people into single-site courses collides with the movement toward things like indieweb and reclaim your domain.” Good questions, and very true. The main idea behind this dual design is to be distributed, and that is where my diagram starts to break down if you examine it closely enough. At some point, we probably will need to look at several things and decide between collected and distributed. Not that we will want to, but there will be time and technology constraints to consider, and then on top of that many thousands of people that are used to the collected, silo approach to learning will need scaffolding to get out of that mindset.
But the goal is to dismantle, deconstruct, and distribute as much as possible. Unfortunately, I did not capture that well in the diagram.
So let me look at this based on some other questions. Many have asked good questions about how competencies will work across xMOOCs and cMOOCs, as well as how the software for cMOOCs and xMOOCs can be connected in ways that connects designs that don’t fit together. All of these are good questions, and reveal how we will have to look at design in a vastly different way than we do in traditional classes and even many MOOCs.
Most of our design methods follow an ADDIE-ish structure that focuses on defining learner paths, pre-set competencies/objectives, pre-defined outcomes, and collected silo approaches. For this class, my goal is to transition from learner design to learning design. Instead of looking at what each path will look like, what content students will consume, what artifacts they will create, etc, we will need to plop the learner down at the middle of a fluid diagram and then place all of the parts around the learner. Instead of equal and opposite paths with xMOOCs and cMOOCs and instructors and books, we see a learner surrounded with many tools that they can choose as they so desire. Like this:
These parts are all possibilities that the learner can choose from to meet their chosen competencies – but what they use is up to them at any given point (I only put a few examples above – there are many others). Therefore, the design for the class could be more along the lines of giving the learner freedom to choose how they prove they learned what they claim to have learned.
Think of this in the sense of objectives. To have a good objectives, one model is to write a sentence with conditions, behaviors, and criteria. For example:
Using Tableau (CN), the learner will analyze the sample data (B) with at least 90% accuracy (CR).
This is how we typically create objectives in traditional learning. However, the sample data might be meaningless to most learners, and some learners may think 90% is too low while others might be new and think it is too high. To deconstruct this approach to writing objectives, you would start to put in many more blanks:
Using Tableau (CN), the learner will __________________ (B) by ___________________ (CR).
Those blanks would be filled in by students during class. This is the basic idea behind the assignment bank that ds106 uses very effectively. Let the learner set their own objectives and competencies and then let the learner choose how to demonstrate mastery. To do so, the learner might focus heavily on more instructivist resources to meet their objectives, like this:
Or, the learner may focus more on cMOOC resources to meet their objectives, like this:
Notice that not all of the aspect available are used, and even those that are used are not equally utilized. Additionally, these diagrams would not stay static through the whole course – they would morph over time to meet different objectives and competencies as they morph over time. If I had time, this would be better demonstrated by an animation that morphs through several versions as the class progresses. Keep in mind, this is in conjunction with the tubing metaphor of group formation (for those students that choose to have groups) as well as the dual pathways diagram. This is just another abstraction of different aspects.
This would also mean that the various software solutions would only need to be able to connect user accounts across systems and then export artifacts as needed. In other words, we don’t have to worry about how a paper submitted for “Week 1″ to EdX can be connected with a blog post for “Week 1″ on WordPress or how a discussion response on Facebook can be connected to a Tweet that also responds to the question. We just need to connect the user accounts from EdX and WordPress and Twitter and Tumblr with an account on a central profile (on something like ProSolo). These connected accounts would just need to be able to send out what ever artifact the student wants to use to prove they know the topic. This central profile would not necessarily collect and silo these artifacts, but would link to distributed artifacts. This could be then used for portfolios, badges, certifications, etc. All of this work could be individual or group based (as long as groups come together around shared objectives).
Again, none of this is new stuff – these are all ideas that others have explored. The main goal is to keep this all distributed and open. Anywhere where it doesn’t sound like that is probably just a break down in my explanation. But I need people pointing that out to help clarify and improve the design before we move into production. And I apologize where I had to gloss over some detailed complexities in order to just get to the point. But this is an idea in progress, and I have a bad habit of explaining something and then blowing it up the next day because I found a problem with it :)