What We Learned From Running Open Spaces
30 June, 2020
Problem
The fast-paced tech environment and product development focus create a culture in which little or no time is left for learning and development. A learning and development culture requires the free and open exchange of ideas between people from across the engineering domain. Despite having dedicated â10% timeâ to focus on learning and development, people still focused on individual learning and development, rather than using the skills around the department to learn and grow.
Â
Actions taken
We introduced an open space session for engineering to share information around the division. An open space is a conference where the agenda is completely driven by the participants. This is a scary thing; what if no-one turns up? What if no-one suggests any topics?
Â
Each open space starts with a blank timetable, with a number of meeting rooms each sliced into 45-minute chunks. We ask participants to define the agenda by inviting them to give a brief Tweet sized introduction on the topic they want to present/share and placing it in the timetable. This sounds chaotic but itâs worked!
Â
Open spaces sessions are governed by four principles and one rule. The principles (it starts when it starts, it ends when it ends, whatever happens happens, whoever is here are the right people) help participants. For example, if I run a session on Erlang and only one other person turns up, I shouldnât be disappointed! This is a great chance for both of us to learn Erlang in more detail. Similarly, if Iâm running a session and it morphs into a different topic, thatâs because that topic is more valuable for those in the room. These principles help lower the barrier to entry. encouraging people to share. The one rule (the law of two feet!) supports this, with a simple mantra - if youâre not going value from a session, leave!
Â
Over time, weâve had a huge number of topics shared. For example, when the K8S operator framework was launched we ran early sessions on this and from this generated new ideas around how we could harness that technology in the business. Topics havenât just been technical; weâve seen sessions on leadership, emotional intelligence and psychological safety. Weâve also had some fun sessions too, from understanding sorting algorithms using bells to human simulations of message buses. Â
Keeping open spaces running hasnât always been easy. Some open spaces have fewer sessions than others, but one lesson weâve learned is that by regularly scheduling them you increase the likelihood of engineers engaging with it. Itâs important to also remind engineers (through their line managers).
Â
Lessons learned
- Over the last few decades, a concerted effort has been made to create spaces and tools that will provide opportunities to share and hopefully generate innovation.
- While open spaces received huge prominence in the tech world, they arenât silver bullets and their magical appeal doesnât work for each and every organization.
- Whatever method or tool you opt for giving a platform for people in your organization to share and collaborate increases engagement, and most immediately productivity and innovation.
Discover Plato
Scale your coaching effort for your engineering and product teams
Develop yourself to become a stronger engineering / product leader
Related stories
Cody Kurz, Director of Engineering at 7shifts, details how he managed to secure buy-in for new metrics from a team that was largely skeptical and distrusted the management.

Cody Kurz
Director of Engineering at 7shifts: Restaurant Scheduling
Paras Doshi, Engineering Manager (BI & Data) at Amazon, discusses how to unlock the potential of an average-performing engineer and encourage them to be more proactive and autonomous.

Paras Doshi
Engineering Manager (BI & Data) at Amazon
Benjamin De Point, Sr. Director of Engineering at Coupa Software, outlines what to do -- and what not to do -- when acquired and going through challenging times.

Benjamin De Point
Sr. Director of Engineering at Coupa Software
Bhavini Soneji, VP of Engineering at Headspace, describes how she successfully led a not-yet-mature engineering team through a colossal and massively impactful change.

Bhavini Soneji
VP of Engineering at Headspace
Jadon Naas, Product Development Lead at InMotion Hosting, talks of his failed attempts to integrate a junior engineer into a new team with a culture of its own.

Jadon Naas
Product Development Lead at InMotion Hosting
You're a great engineer.
Become a great engineering leader.
Plato (platohq.com) is the world's biggest mentorship platform for engineering managers & product managers. We've curated a community of mentors who are the tech industry's best engineering & product leaders from companies like Facebook, Lyft, Slack, Airbnb, Gusto, and more.
