The Serendipity Engine

A somewhat serendipitous post about serendipity and designing for it.

A few years ago a colleague and I were working on a tool to enable better organisation of groups for learning. The tool ended up being a combination of a simple survey and a couple of unique sorting mechanisms that we developed.

In many cases, we aimed to group 'like' students together based on their answers - their location, area of study interests, etc. But during our discussions, we asked ourselves - what if we wanted to do the opposite? What if instead of grouping like students, we want to go the other way and group students together based on differences? A simple example might be grouping students by their preference for roles in a team, in that instance you would want a variety of roles in each group, not all of the same grouped together. But in other instances, you might group different students to create friction and possibility. That kind of sorting became known as the serendipity engine.

The serendipity engine groups learners in ways that increase the chances of serendipity - of sharing, discovery, connection, conflict - and learning together.

It wasn't a guarantee that anything would happen, but it increased the odds that something unplanned and unstructured would occur.

We aimed to enable group learning to be different and to create engagement by creating opportunities for collaboration, cooperation, sharing, and discussion and for differences to arise through the co-mingling of people and ideas.

By pushing different people towards each other with a shared purpose to produce something, we could create a whole variety of different learning opportunities.

Sometimes, it is through conflict and the creativity required to move past that which is where the real learning opportunity arises. Sometimes, it's in not dealing with the conflict and having to experience some level of disagreement and failure. There are so few real opportunities for us to delve into that process because conflict is one of those things where you have to be in it to learn from it and learn how to cope with it. It's not something you can just read about – it's experiential.


This all came up over the last week as I've been thinking about how serendipity relates to my current work on learning design. I've been developing my ideas around learning types and patterns and planning on running a few workshops on using them for learning design. I aim to get people to think about learning experiences more holistically and to think about moving between different types of learning as ways of engaging with different types of learners.

In many ways, a marker of the success of the learning experience is the variation of learning offered to students because each of these creates opportunities to learn - to engage with different types of students and connect with different ideas, concepts and experiences in their schema.

The aim of our design is to increase the conditions for serendipity.

And rather than fumbling through it, the concepts of learning types and patterns allow us to design for it. Rather than seeking to template everything by defaulting to the specific formats and structures that are so ubiquitous and forced on us by the technology and tools we use, what if we designed for serendipity instead?


In what seems like a serendipitous occurrence - Doug Belshaw mentioned his idea of Serendipity Surface in his latest Weeknote. He outlined the term to describe cultivating an attitude of curiosity and increasing the chance encounters we have by putting ourselves out there. On this podcast on YouTube Doug describes coining the term Serendipity Surface to describe cultivating curiosity, increasing random encounters and possibilities by putting ourselves out there. He sees it as the opposite of reducing the "attack surface" in security; it's about expanding opportunities.

I like that term, so perhaps the aim is to use the serendipity engine to increase the serendipity surface of our learners.