From mid-April to mid-May, we collaborated with our friends at the Open Knowledge Foundation to launch the “Data Explorer Mission” using the Mechanical MOOC platform. The Mechanical MOOC was built to form more intimate small learning groups around open educational resources. This was the first time we had used it for team-based projects with synchronous meetings. Here are our findings from the experiment.

Overview

• The “Data Explorer Mission” was designed as an introduction to working with data.
• Learning outcomes were: data cleaning, data analysis, facilitation, visualization and storytelling.
• 151 “Data Agents” signed up.
• Group formation: teams were put together based on time zone: we formed 13 cohorts of 10 learners each (more or less).
• Communication: teams received 2 emails per week–1 with an assignment, and 1 with a script for their synchronous meeting.
• Tools: teams were prompted to schedule their own weekly Google hangout.
• 5 Badges were designed for learners to apply for feedback on their projects.
• Support team (a.k.a “Mission Control”) comprised of one subject-matter expert (Neil Ashton) one data community manager (Lucy Chambers) and one learning designer (Vanessa Gennarelli)

Results

Our findings consist of 3 main datasets:

• Logs of emails from Data Agents to each other (we’ll call this set “Intergroup Emails”)
• Content of email conversations amongst participants
• Qualitative post-course survey results

Intergroup Emails:

In our 13 groups, we tracked how many emails Agents sent to each other. The results were quite surprising:

The full dataset for this chart can be found here: http://ow.ly/m1YCp

You’ll notice that most groups emailed each other around 30 times.  Two groups, Group 1 and Group 10 emailed each other more than 220 times over the trajectory of the course. What made these groups different?

Content of Email Conversations:

Since this was our first collaborative, project-based Mechanical MOOC project, we approached it as a pilot. As such, the 3 support folks behind Mission Control masqueraded in all of the groups as they evolved. To find out what set Groups 1 and 10 apart, we combed through the content of those conversations. This is what we found:

Team 1

Upon closer inspection, many of these emails discussed trying to find a time to meet. After the first 10 days, the conversation dropped off, so these results are inflated.

Team 10

In looking at the conversations from the most successful Team, several fascinating trends emerged that led to Team 10 to build social presence and cohere as a group.

• Core team: 4 of the 10 original members were active, encouraging each other to keep up with the Mission.
• Spontaneous prompts to check in: Members sent short messages to each other to keep the course alive, i.e. “Are you doing alright? Haven’t heard from you in ages” “Just making some noise.”
• Familiarity: Agents referred to each other by name (as opposed to “Team 10”) and shared bits of contextual information about their lives, such as when they found time to do the assignments, where they were traveling, etc.
• Building upon shared interest: Team 10 shared content related to the subject matter of the course that others might find interesting–such as other Data MOOCs, White House open data, etc.
• Tried new tools together: Agents tried out new tools like Google Fusion Tables together, and shared their frustrations, setbacks and successes. 
• Summaries of Hangouts: In a brilliant move, Agents sent a summary of the synchronous Hangout to the whole group, which kept the folks who couldn’t make it in the loop.

What’s notable about Team 10’s interactions is that all four of the core group members were about equally active–this is an example of true group facilitation. We’ll recommend using Team 10’s interactions as a model or a roadmap for future Mechanical MOOC projects.

Overall Team Activity

It’s also worth noting that 3 groups continued to email each other after the course officially ended. Even if they had not finished the project, they had built a community around data, and continued to share resources and review each other’s work.

This made us realize that perhaps we should experiment with time, or folks should be able to progress at their own pace. Another realization was that we should keep the small listservs up so that people can continue to tap their small learning community.

Survey Data:

After the Mission ended, we surveyed Agents about what they felt they learned in the Mission, which tools were most valuable, and about their level of satisfaction with the experience. In the results, we found that many respondents were looking for a more traditional, direct instruction MOOC experience. We need to make the peer learning approach clearer–that Agents were in charge of directing their own learning, that expertise would emerge from working together as a group, and not from an Instructor or a series of Teaching Assistants. This is important, because the Teams that embraced the peer learning approach fared far better in the Data Mission:

• “Apart from learning the basics of working with Google Spreadsheets (including some cleaning, formatting and visualising) and some other tools, I got my first and very impressive experience of P2P-learning.”
• “I would recommend the Data Explorer Mission, because it is a good starting platform, to my mind. What is also important, it’s one of the formats that fosters p2p networking for potential future cooperation, which is very important.”
• “It’s a great learning opportunity, but you take out only as much as you give. The amount of learning depends largely on the work each individual is willing to do.”

As mentioned above, participants who had yet to be “onboarded” to peer learning expressed frustration at the lack of structure and direction in the experience:

• “After reading more about p2p learning and its various methods, I can only say that the my experience would probably be less frustrating if I knew something about its specific in advance.”
• “Make it clear to to ‘beginners’ that there is no right or wrong answers involved in this Mission, but any exploration of the data given is acceptable.”
• “Before the team became interactive, it took quite a bit of effort to organise its cooperation. When people of different cultural backgrounds come together for the first time, they might feel shy and don’t know how to behave. For instance, the team had been keeping silent for more than a week and everybody, as it turned out before, felt frustrated, because there was no visible team or work at all. In fact, it was not because people weren’t doing anything. It was because they were trying to do, failed and didn’t share their negative experience. They thought they only could communicate when they had some positive results. Later we decided that in order to keep our teamwork we’ve got to stick together an share not only our achievements, but also concerns, problems or even just write a few words like ‘hi, I’m in’. That’s not all that obvious.” (Our italics).

Findings & Recommendations

• Google Hangouts. These worked well as a tool. 12/13 groups held at least one hangout. But we should schedule these beforehand, so the path is clearer.
• Onboarding to Peer Learning. Some scaffolding is needed here to prime learners about what to expect. The first exercise should be to examine peer learning and define it for yourself. We’ve updated our Create a Course content to reflect these findings.
• Facilitation. We should use Team 10’s framework to support distributed facilitation. It is our hope that a stronger onboarding process to peer learning will progress in that direction.
• A Sense of the Wider Learning Community. Lots of learners asked for a forum to go to with questions, how many people were in their group, and more of a meta sense of “what was going on.” We could solve this by visualizing group data to learners and contrasting it with the wider community in a weekly message or blog post. And in the future, we could leverage Open Knowledge Foundation’s Q&A engine for questions that the groups cannot answer themselves.
• Timing. We broadcasted the content, instead of working with the context of each individual group, and some folks needed more time. Design a more flexible flow where learners *ask* for the next unit or module. That way they don’t feel like the course has left them behind and they have to drop out if they aren’t “keeping pace.”
• Integrate Badges. We developed a series of Badges for this experience on our platform, but they weren’t used. We need to integrate these better and show learners the value of submitting a project for feedback.

Validity and Limitations

Data collection. We’ll admit candidly: we were learning along with the Data Agents. This was one of Peer 2 Peer University’s first attempts at using Mailgun to track engagement, and there are a few things we could do better. In the future, we will use the “Campaigns” feature to drill down into per group and per user opens / click throughs / replies to the group.  We also struggled to get an export of the engagement data on a more regular basis, which would have helped us support groups that were flagging.

Sample size. With a pilot of 150 folks, Teams of Data Agents were spread thin across the world. Some groups, like those in Fiji or Australia, got placed with the nearest-by folks–sometimes 3-4 hours away. With a larger group, Teams will have more local folks in their Mission.

Avenues for Future Projects

From our pilot experience and lessons learned, we’ll be running another iteration of the Data Explorer Mission in August that will include a clear onboarding process for peer learning, stronger support for facilitation, and integrating the “Ask School of Data” to support Agents who have questions their Team cannot answer. Stay tuned for more details.

This post comes to you from Anna Sakoyan, who participated as a “Data Agent” the Data Explorer Mission, a partnership between Peer 2 Peer University and the Open Knowledge Foundation. The course ran from mid-April to mid-May, and primed Agents to analyze, clean, visualize data, tell a story with it, and facilitate their group. Here is her story. The original post can be found at her blog, Self Made University.

I can hardly believe it, but my assignment at School of Data seems to be completed. The last step was to produce some output, that is to tell the story. Now I think I should somehow summarize my experience.

Now, first off, what is Data Expedition at School of Data? It can be very flexible in terms of organisation. Here are the links to the general description and also to the Guide for Guides, which is revealing. In this post, I’ll be talking about this particular expedition. Also, a great account of it can be found on one of my team mates’ blog. So, this expedition was technically very similar to the principle of Python Mechanical MOOC. All the instructions were sent by a robot via our mailing list and then we had to collaborate with our team mates to find solutions.

(Image CC-By-SA J Brew on Flickr)

First of all, we were given a dataset on CO2 emissions by country and CO2 emissions per capita. Our task was to look at the data and try to think about what can be done about it. As a background, we were also given the Guardian article based on this very dataset so that we could have a look at a possible approach. Well, I can’t say I was able to do the task right away. Without any experience of working

with data or any tools to deal with it, I felt absolutely frustrated by the very look of a spreadsheet. And at that stage peers could hardly provide any considerable technical support, because we all were newbies.

Then we had tasks to clean and format the data in order to analyze certain angles. Here our cooperation began and became really helpful. Although nobody among us was an expert here, we were all looking for the solutions and shared our experience, even when it was little more than ‘I DON’T UNDERSTAND ANYTHING!!11!!1!’.

Our chief weapons were:

• the members’ supportive and encouraging attitude to each other
• our mailing list
• Google Docs to record our progress
• Google Spreadsheets to work with our data and share the results
• Google Hangout for our weekly meet-ups (really helpful, to my mind)
• Google Fusion Tables for visualisation (alongside with Google Spreadsheets)

And that is it actually. I’m not mentioning more individual choices, because I’m not sure I even know about them all.

Now some credits.

Irina, you’ve been a source of wonderful links that really broadened my understanding of what’s going on. And above all, you’re extremely encouraging.

Jakes, you’ve contributed a huge amount of effort to get the things going and I think it paid off. You have also always been very supportive, generous and helpful even beyond the immediate team agenda.

Ketty, you were the first among us who was brave enough to face the spreadsheet as it is and proved that it is actually possible to work with. I was really inspired by this and tried to follow suit. Same was in the case of Google Fusion Tables.

Randah, I wish you had had more time at your disposal to participate in the teamwork. And judging by your brief inputs, you would make a great team mate. You were also the person who coined the term dataphobia and in this way located the problem I resolved to overcome. I hope to get in touch with you again when you have more spare time.

Zoltan, you were also an upsettingly rare contributor, due to your heavy and unpredictable workload. But nevertheless, you managed to provide an example of a very cool approach to overcoming big problems just by mechanically splitting them into smaller and less scary pieces.

Vanessa Gennarelli and Lucy Chambers, thanks for organising this wonderful MOOC!

So, as a result, I

• seem to have overcome my general dataphobia
• learnt a number of basic techniques
• got an idea of what p2p learning is (it’s a cool thing, really)
• got to know great people and hope to keep collaborating with them in the future

Well, this is kind of more than I expected.

Next, I’m going to learn more about data processing, Python, P2P-learning and other awesome things.

We provide multiple pathways to learning here at P2PU–if visual is your thing, here’s the walkthrough of Data Explorer Missions on our Community Call (start around minute 19:00):

Last year Peer 2 Peer University and the Open Knowledge Foundation launched an initiative to to meet the global demand for data-wrangling skills–enter the School of Data. Over the course of the past few months, Lucy Chambers, Neil Ashton and I designed a pilot “Data Explorer Mission” that we just launched on April 15th. We’re in the third week of that project now, and here’s a window into how it works.

Fast Facts

• Four-week long course, running from April 15 to mid-May

• 130 signups for our initial pilot

• Our Mechanical MOOC email grouping mechanism formed 13 groups by time zone

• The course features 5 Badges on our new platform (http://badges.p2pu.org) and it’s our first time implementing Badges for a Mechanical MOOC project

Learning Design

• Mechanical MOOC put together 13 groups of 10 learners (or team of “Data Agents”) based on time zone.

• Each week Data Agents receive 2 emails from “Mission Control”–one email with a project and resources on Tuesday, and one email with directions for their Google Hangout on Friday.

• The learning project asks Agents to examine a CO2 dataset, ask a question, and then clean, refine, visualize and tell a story about their exploration.

• We designed Badges that directly correspond to those learning goals.

• During the weekly hangout, Agents share their projects, help each other, and reflect on their projects. Data agents take notes on etherpad.
• Facilitation duties change from week-to-week, with folks opting-in to facilitate.

Who is “Mission Control”?

• Mission Control is our persona for the School of Data Mechanical MOOC–think a mix of 007/Bond’s “M” and “Charlie” from “Charlie’s Angels.”
• We’ve been giving a lot of thought to the affective dimension of learning, or how positive feelings in learning situations increase a sense of curiosity or play. Mission Control comes out of recent research on affective learning and engagement through Universal Design for Learning.
• Behind the curtain it’s me, Vanessa, Lucy Chambers with Open Knowledge Foundation and our rockstar data wranger Neil Ashton.

Preliminary Results

• We’ve been using Mailgun to track opens, clicks and replies to the emails we send from [email protected]

• We’ve sent 4 emails so far, so we’re about halfway into the course. 
• 131 participants have sent approximately 50 emails to their small groups per day since the start of the course, or 675 emails total.
• Almost every group has had at least one synchronous Google Hangout.

Lessons Learned (Already!)

• Find a clearer way to represent that Data Agents are already in a small group by the time they are contacted. Learners seem unclear about how their small group functions. We need to a.) visualize to the teams who is in their group and b.) give them a sense of “people in the room.”
• We should consider moving Data Agents whose teams don’t take off–maybe these folks form their own team?
• We haven’t mastered Mailgun analytics yet, so Dirk and Vanessa need to thrash around with it a bit longer before we are truly confident in the reliability of the data.

Next Steps

• We’re designing a post-course survey for our pilot teams of Data Agents.
• In another 2 weeks we’ll present summative data, including: number of messages per group, number of click throughs, number of Badges applied for, and number of reviews per application.
• We’re experimenting with the timeline for the course–our next iteration will be only two weeks long–watch out!

As a Data Agent, your first Mission, should you choose to accept it, would begin Monday, April 15. That gives you only 3 more days to sign up for this innovative partnership between the Open Knowledge Foundation and Peer to Peer University. Read on for more details.…

Image CC-By-SA J Brew on Flickr

At the School of Data, we teach in two ways.

1) By producing materials to help people tackle working with data and
2) By running Data Expeditions – where learners tackle a problem, answer a question or work on a project together, learning from one another as they get hands on with real data.

It’s come to our attention, that sometimes, it’s handy to combine the two – handing people materials to tackle the challenges they are likely to encounter along the way. The Data Explorer Mission is like a data expedition with one crucial difference: your guide is a robot…

Read on to learn more…

Your Mission: Tell Stories with Carbon Data

Learn how to tinker with, refine and tell a story with data in this 4-week course. Each week you’ll be commissioned to work with others on a project that will hone your data-wrangling skills. Lessons will be pulled from Open Knowledge Foundation and Tactical Tech with help from Peer 2 Peer University. At the end of the course, you will have finessed, wrangled, cleaned and visualized a data set and shared it with the world.

What to Expect

The course will run April 15 to May 3, and each week your team will receive weekly “Missions” from Mission Control over email. You’ll work together on those projects, including a 30-minute Google Hangout each week. Each “Mission” will lead up to your final project. For each skill you master in the course, you can earn a Badge to show your mastery and to get feedback to further your talents.

The Topic

Carbon Emissions. Don’t worry if you don’t know anything about them at the moment, you don’t need to be a topic expert and the data skills you will learn will be very transferrable to other areas!

The Level

No prior experience is required, we’ll cover spreadsheets and working with data. If you’re more advanced, you are also welcome to join us to hone your skills, and the only limit on what you can learn is your imagination – so if you’re prepared to push yourselves on the project front the data-skills-bucket is your oyster!

About Mission Control

Normally – Data Expeditions are guided by a human sherpa, in this course, we’re weaving School of Data course material with a robot sherpa to help guide participants through the phases of the expedition. You’ll need to listen out for Mission Control’s instructions to guide you through the phases, keep timing and look out for handy tips, but organising your team is up to your group…

Sign up by completing the form below!

Image CC-By-SA J Brew on Flickr

At the School of Data, we teach in two ways.

1) By producing materials to help people tackle working with data and
2) By running Data Expeditions – where learners tackle a problem, answer a question or work on a project together, learning from one another as they get hands on with real data.

It’s come to our attention, that sometimes, it’s handy to combine the two – handing people materials to tackle the challenges they are likely to encounter along the way. The Data Explorer Mission is like a data expedition with one crucial difference: your guide is a robot…

Read on to learn more…

Your Mission: Tell Stories with Carbon Data

Learn how to tinker with, refine and tell a story with data in this 4-week course. Each week you’ll be commissioned to work with others on a project that will hone your data-wrangling skills. Lessons will be pulled from Open Knowledge Foundation and Tactical Tech with help from Peer 2 Peer University. At the end of the course, you will have finessed, wrangled, cleaned and visualized a data set and shared it with the world.

What to Expect

The course will run April 15 to May 3, and each week your team will receive weekly “Missions” from Mission Control over email. You’ll work together on those projects, including a 30-minute Google Hangout each week. Each “Mission” will lead up to your final project. For each skill you master in the course, you can earn a Badge to show your mastery and to get feedback to further your talents.

The Topic

Carbon Emissions. Don’t worry if you don’t know anything about them at the moment, you don’t need to be a topic expert and the data skills you will learn will be very transferrable to other areas!

The Level

No prior experience is required, we’ll cover spreadsheets and working with data. If you’re more advanced, you are also welcome to join us to hone your skills, and the only limit on what you can learn is your imagination – so if you’re prepared to push yourselves on the project front the data-skills-bucket is your oyster!

About Mission Control

Normally – Data Expeditions are guided by a human sherpa, in this course, we’re weaving School of Data course material with a robot sherpa to help guide participants through the phases of the expedition. You’ll need to listen out for Mission Control’s instructions to guide you through the phases, keep timing and look out for handy tips, but organising your team is up to your group…

Sign up by completing the form below!