I write this in my hotel room after having traveled back from Stoos to Zürich airport. The Stoos Gathering just ended and I’m feeling very tired. I had just 6 hours of sleep in the last 2 nights, and tomorrow I have to get up early, again, to catch my plane to Cleveland, US. My report about the proceedings of the Stoos Gathering will have to wait for a day or two.
But there’s one thing I wish to clear up before I tuck in.
A number of people have been waiting (in vain) for feedback from the Stoos Gathering over Twitter during the event. It seems they expected it to be like a regular conference, with a continuous stream of ideas emitted to the outside world.
Apparently, it wasn’t.
The purpose of the Stoos Gathering was to try and reach consensus on how to accelerate management transformation. We decided that, for us to be able to achieve consensus it would be necessary to have a high level of trust, respect and safety among the participants in the room. Many of us didn’t even know each other. But we wanted the participants to share their personal stories, and their stories from their organizations and customers, in order to get to the core of the problem we tried to solve. And this required a high comfort level among all participants.
And so, at the start of the event, we asked ourselves, “What about Twitter?”
Then a long discussion started. We identified two problems with publishing half-baked ideas on a #stoos Twitter stream, while the event was running:
Some of the participants had non-disclosure agreements with their organizations and/or customers. They could not say anything if there was a possibility that others would tweet identifiable comments about what was happening.
And some of the participants said they would not feel comfortable opening up and expressing their inner thoughts in a group of strangers if there was a chance that comments would turn up on Twitter and the whole world was listening.
The outcome of our 30-minute discussion was that we would only tweet personal opinions (if we felt like it) with the #myview tag appended. And we would ask permission if we wanted to tweet someone else’s contribution before the end of the event. This was the best compromise we could come up with, at a time when many people didn’t know each other.
Personally, I would not have minded more openness to the outside world during the event itself. But the fact was that in this particular case trust was in conflict with transparency. And, in order to achieve our goal, internal trust was of higher priority than external transparency. I had to accept the fact we wouldn’t get much done if we didn’t respect the diverse opinions, feelings and backgrounds of the people in the room.
Yes, we decided at that moment to favor respect people over openness. Sometimes you have to choose…
We went a long way collecting input from many people before the event, via several blog posts. We shared that input and even pasted all the feedback as information radiators on the wall in our room. But, as far a I remember, we never promised anyone to have real-time discussions over Twitter with the whole world during the event. It turned out that, with the participants in the room, that novel concept was simply not going to work. We would have real-time transparency of achieving nothing, instead of transparency-after-the-event about achieving something.
We preferred the last option.
I apologize to anyone if we have given the impression that we were going to have real-time updates, or on-line discussions. We did not intend to organize a conference. We intended to organize a focused discussion with a brand new team. And every newly formed team needs a bit of time to get to know each other, and work on a first sprint without being disturbed all the time.
Well, we finished our first sprint.
We’re delivering the results right now (see: here and here) and next week I’m sure several blog posts and announcements will follow (when we had some sleep). We welcome all the feedback we can get. And please help us do better in the next sprint. Yes, I’m sure we can do better! But interacting with the world while trying to build a new team was something we couldn’t do at the same time. At least not in Stoos.
Sorry, we're not superheroes. But at least now we are a team!
p.s. There were two other reasons for the lack of tweets. 1) The hotel wi-fi worked badly in our room. We often needed to go outside to get online. 2) Most of the discussions were so engaging, time simply flew past.