It is already two weeks ago now… the 2017 LeSS Conference in London. I’m still missing the discussion, my team, the wine, the people, the weather. Well… not the weather. It was wonderful, I enjoyed it thoroughly and hope and think the other people did too!
One thing I considered very successful this time was the team-based conference idea. This idea started in the previous 2016 Amsterdam conference. In that conference we experimented with this. The origin is in a discussion the organizing group had, which is that in LeSS we focus on teams… but most conferences are done individually. That felt like not following our own principles… so we thought about how we can make the conference experience more of a team experience. In Amsterdam we tried the first iteration, which was rough but good enough to keep trying. The second iteration was much better.
The essence is to make the conference experience a team experience where you learn together with your team, have a place to return to, people you got to know better, and can create a shared output.
The structure is like this:
In this blog post, I’d like to share the teams that were creates, in a future post we’ll share the outcome from each of the teams.
If you were in one of the team and want to share something about your team or experience, drop me an email and we’ll put it in this blog post which we’ll keep updating regularly.
If your team is missing, lemme know and I’ll add them.
A 1m30 team self-design workshop at #less2017 pic.twitter.com/bV5JtE3Fln
— Jurgen De Smet (@JurgenLACoach) September 13, 2017