Robert16:45
And the workshop went so well that at the end you decided to introduce the 'du' — in principle. What else did we do?
We practiced radical transparency. We organized evening events where we voluntarily invited people and said, 'We're having an event tonight, whoever wants can come.' Then we showed all the results from the workshops, surveys, and so on — completely unvarnished. We presented everything: what problems there were, what employees were complaining about, and so on. We displayed everything — which might be normal for many of you, but in such a culture, openly sharing anything that doesn't function was highly risky.
Because in principle, everyone had always performed great work, and great work always came with great results. Oh God, if someone made a mistake — mistakes were terrible. What else did we do? We ran some simulations, like the Ubongo game, to give people a feeling for how things could work differently than they were accustomed to. We simulated agility and different working methods to show how things could function differently.
Then the organization gained its own momentum. Experiments were conducted, new things were tried — not mandated, just from the desire to try something. 'Let's try this out, let's create a Scrum Lab here, let's run some experiments and test things.' Exactly. Maybe about LION — why LION? It stands for Leifheit Einmalige Offen Mega geile Neuigkeiten.
In development, they really jumped on agility and tried to experiment themselves. Some things went well, others not so well, and some went completely wrong. But that's what it's there for — to learn. And this was something entirely new: the goals worked on in OKR, developed with a cross-functional group from the organization, were simply posted publicly — visible to everyone — the strategic objectives in that area.
And you also made the weekly meeting public. Anyone from the organization could attend — it was the same with the Scrum Lab, an open space where anyone interested in seeing the experiments and what was being done could come. And the same here with the OKR weekly — everyone was allowed to participate and listen.
These are insights that emerged from an OKR retrospective: analog boards are quite good, but when you work a bit more distributed, as Leifheit does, you need something digital where remote participants can view it. Cross-functional teams proved very effective, and there was strong motivation to keep moving in that direction. The topic of setting objectives came up quickly too — it's not as simple as it seems.
Finding the right altitude for objectives — we discussed this in yesterday's workshop. And that objectives shouldn't be too detailed. Most importantly, an objective is an outcome description, not a work instruction. We rediscovered these principles quickly.
This was just about a week before we had to deal with Corona. And we said: okay, digital OKR — yes, that makes sense, we can imagine that. It was important because we have multiple locations and needed to include the other sites. We had no idea how important that would suddenly become.