Back
Igor Munduate
Chief Operating Officer (COO), Management Board member, Leifheit AG

In Krisenzeiten auf den "unfair advantage" fokussieren (Robert Gies, Igor Iraeta Munduate)

🎥 Nov 01, 2023 📺 projektmagazin ⏱ 45m 👁 139 views
„Wirtschaftlichkeit ist die Basis unsere Existenz, aber nicht der Sinn unseres Handelns“ – Bodo Janssen (Unternehmer, Hotelier und Buchautor) In einer turbulenten und unsicheren Umwelt stoßen wir an unsere Grenzen, wenn es um Wissen und Vorhersagen geht. Glauben Sie, dass eine Produktionsverlagerung von Asien nach Deutschland gleichzeitig günstiger, schneller, hochwertiger, wertschöpfender und nachhaltiger sein kann? Glauben Sie, dass der Einsatz von umweltfreundlichen Materialien besser, billiger und langlebiger sein kann? Wird die Unternehmensstrategie von wenigen Managern bestimmt, die ei...
Watch on YouTube
Transcript (74 segments)
M
Moderator0:00
Today we have Igor here. I actually haven't asked how to correctly pronounce your last name. We're on a first-name basis with Igor in the program. Igor is a board member at Leifheit AG — you probably know them from household items like drying racks or dusters. He has a very demanding role as COO, overseeing purchasing, production, logistics, and development. To balance that demanding role, he turns to sport. And as Robert revealed to me, before Corona he did something I consider relatively crazy: he regularly went swimming at the Standort Nassau in the river. You can do that and then run back upstream — practically, you don't have much further to go after that.
He's also the kind of triathlete that appeals to me most. The ISA, I can recommend it too — maybe you can jump in later. It's the name of the program, so to speak. Four years ago, Robert and Igor crossed paths and introduced the topic of OKR at Leifheit AG. Beyond this introduction, they also share a love of good food and meaningful work in general.
When it comes to triathlon, Robert is truly the perfect partner. With over 30 years of experience in agile project work and 15 years in agile leadership, he brings tremendous know-how to the organization. He has trained agile and OKR coaches since 2018 — over 400 coaches in total, which I think is an impressive number. But what's particularly special about Robert — and perhaps you can see some photos during the break — is that he has converted a van into a mobile workspace. I was allowed to see some photos at the last conference. If you're curious, ask him to show you. With that said, enough from my side. I wish us all an exciting presentation.
R
Robert2:58
We won't just be sharing success stories today but also some pitfalls — showing things where we really got stuck and couldn't move forward. But first, I'd like to talk about the unfair advantage, which features prominently in our title. Who knows where this term comes from? Ah, interesting — one person got it exactly right. To clear up misunderstandings: ChatGPT says unfair advantage means a benefit a company or person obtains through unethical or unfair means. That's not what we mean. It comes from Ash Maurya's lean canvas: it's something that cannot be easily copied or purchased. It means making yourself unique through a special strategy — leveraging individual skills, experience, or specific situations to your advantage.
Today we'll also report a bit on how Leifheit has used intelligent strategies — for example, leveraging Corona as an advantage in certain areas. Igor, shall we say much more about Leifheit? We probably don't need to say much. Leifheit is one of the leading household product manufacturers in Europe, known for durability, high-quality products, and products that make consumers' lives easier and more comfortable at home.
Many consumer surveys confirm that our brand Soehnle, which also belongs to the Leifheit Group, is top-rated in product quality, durability, and sustainability. This is also confirmed by many consumer opinions. We stand for 'Made in Germany' — manufactured in Germany. This is actually something that emerged from the OKR teams, who gave the impetus in that direction. Igor, when we crossed paths — what were you looking for at that point?
I
Igor Munduate6:00
Perhaps as a starting point: in 2019, a new management board came to Leifheit AG, and I'm part of it. We found a very hierarchical culture where board members and board chairs strongly governed what ideas got approved. Work across different areas within the board was slow and heavily dependent on the opinions of superiors. With the new board team, we realized we needed a new strategy. But it was clear to us, as Peter Drucker said, that 'culture eats strategy for breakfast' — we wouldn't implement even the best strategy without changing our culture.
Our strategy is called 'Access' — taking what we're good at and multiplying it, making it bigger. Advertising is important for this, as are good products that are better than the competition. But the most important pillar for implementing this strategy is what we call the winning culture — our VIVE culture. That stands for Fun, which is crucial since we spend so much time at work, and if it's no fun at all, that's already not good. It also means Fast — adapting to changes in the environment. Friendly — treating each other with respect and meeting on equal footing, like at this congress. And Bold — being courageous, not afraid of superiors, but letting the best ideas win. We should also argue respectfully, always listening to what the other person means.
This desire to install such a culture led me to the topic of agility. Our advisory board member, Georg Hesse, who was CEO of HolidayCheck at the time — that's probably a term familiar to everyone here — introduced me to Robert.
R
Robert9:13
Those who were in the OKR course yesterday can probably still remember that I spoke about dead and living artifacts. Such a beautiful picture is naturally first a dead artifact — it looks nice, but it must be brought to life. You have to live it, embed it into the organization, and be able to implement it — not just look at the beautiful picture. How we did that is what we want to tell you today.
The very first thing we did was survey the organization about what wishes and topics they had — what gave them stomach aches or what problems existed. We received a very long list of different things that actually annoyed the organization — things many employees wanted to change. Then we also looked at the current workload: how many topics were being worked on simultaneously? We were shocked to find that many topics were running in parallel — a real scattered focus.
To prioritize and bring focus, we came up with the idea that OKR might help. The call was to 'stop starting and start finishing.' The question is whether we've actually become significantly better after four years — I ask myself that every day. But I can definitely say we've learned a lot in four years about what works and what doesn't.
We started a journey. We gave the organization some initial impulses. This is an organization that had essentially been operating the same way for many years — at Leifheit, employees often have long tenure, many only know this one organization, and perhaps had no ideas about how things could be done differently. So we conducted impulse workshops, did a situational assessment, ran exercises to experience agile work, and in September 2019 we did our first OKR planning.
As you can see at the top, next week we'll have our twelfth cycle change — impressive, four years. We've experienced a lot and will share more today. One thing was pretty clear to us from the start: we didn't need to repaint everything — we needed real, genuine change. A pattern break where we truly rethink.
The strategy was that we needed to make more of the organization's intelligence usable. The intelligence of a single individual isn't enough — we need the collective intelligence of many. So we invited people into the organization, asked who was interested, who had fun working on something new. That's when the workshop took place, which was very impressive for me.
Maybe I can add: when I first came to Leifheit and sat with the leadership team, I experienced something totally strange for me personally — people who had worked closely together for a long time, who knew each other well, were sitting with physical distance between them. You could sense a certain distance. And throughout the organization, people sat apart from each other — everything was kept at arm's length.
I
Igor Munduate14:06
Yes, I think it's great that I came to this congress. When Robert showed the slides and this journey, I realized where we actually stood. I only look at cycles 12 and 11, but this was really interesting. When I saw the photo, I thought: oh God, where were we actually back then? Perhaps you had to experience it. Not so long ago, the board members at Leifheit had their own chauffeur. There was a separate executive floor — that old-fashioned thing you see in films. We had all of that.
In that environment — good old industry, which probably doesn't exist for you all — oh yes, it does. In that environment, the topic of 'du' — I came from igus, which might be familiar to some here. There they already used 'du,' but I quickly had to switch to 'Sie' because it was shocking — a board member addressing me with 'du'? That doesn't happen. It was even advised not to offer the 'du.' And accordingly, that's how it was.
In 2019, we still addressed each other with 'Sie.' Then we did the workshop, and there was a pattern break because you went into the workshop as a board member with cross-functional people from completely different levels and departments, and you offered the 'du.' And it wasn't in Leifheit's rooms — it was in a restaurant, deliberately chosen outside the company.
Perhaps an interesting story: about a year or two later, I went to dinner with some employees. They recalled this workshop and said it was one of the biggest real changes in the organization — that we started using 'du' with each other. It's quite impressive what such a small thing can actually trigger in terms of change.
R
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.
I
Igor Munduate21:46
And then it happened — Corona arrived and the world was different. From one day to the next. And what did we do? We started working remotely, everyone at once. Robert was an enormous support — he brought great tools and ultimately enabled so many people to participate at once. It was unimaginable. Just two weeks before, we held the workshop like that.
When Corona came, there was also — let's call it — an extreme challenge and contradiction. Something I always noticed very clearly, and it's still the case today: the fight between innovation and cost savings in the OKR cycles. Driven by certain conditions: rising transport costs at Leifheit were a huge problem. But on the other hand, disruption — a more strongly changing market and changing business models.
Energy costs, supply shortages, lockdowns, raw material prices that skyrocketed. These were topics that triggered either savings or innovation. Many people from development said: we need innovation, we must remain viable for the future. But then the finance people said: we need to manage with rising prices. There was a real battle.
Absolutely. We saw in the keynotes how the mood of people fluctuated. At the beginning of Corona, the mood was briefly very good, then it went rapidly into the negative. And then came the big topics: savings and supply shortages. Where we had previously focused on innovation and where things were going, we were now in a very changed environment.
R
Robert24:12
There were strong fights that at least one objective on the board wasn't about savings but actually about innovative development for the future.
Exactly. Then you also had a TV campaign planned for 2021, and it actually wasn't going badly. The problem was just that nothing was deliverable. That was the big challenge. We had about 20,000 GP points — that's the unit for advertising pressure — that's a lot for our scale. The challenge was: when demand was there, with these supply shortages, to be able to deliver. And OKR certainly helped us a lot with that.
Now we have some examples where OKR was a significant driver in pushing forward certain innovations. First, the topic of Made in Germany. About 60% of our revenue we produce ourselves. But there are also products and components we bring from China, mainly anything with batteries or electronics. It was very important for us to better manage our supply chain — bringing it back to Europe as much as possible. And everything we produce ourselves, to make independent of external factors.
I
Igor Munduate25:58
There were also big surprises. I remember specifically the joint for the clothes horse — we discovered that recycled material was actually cheaper and better to produce. Even the durability was actually better with recycled plastic. That's a topic of sustainability. Sustainability was one of big objectives — our goal is to be climate-neutral by 2030. We reduce our CO2 footprint, and where it can't be reduced further, we compensate. Durability, quality, and reusability of our products are our understanding of our contribution to sustainability.
In these products, we want to reduce resources and our CO2 footprint. Recycled material is a big topic. We've had many attempts, many setbacks, but also positive surprises — like the unexpected finding that recycled materials had better properties for certain products than original materials.
Another big OKR topic was consumer needs — quality understood as making our consumers happy. Not just 'very good quality,' but our customers are enthusiastic about our products and services.
For example, the vacuum cleaner issue: 99.99% bacteria-killing, I believe. Our development team, together with our brand management, engaged deeply with what bothers consumers. Vacuum cleaners exist in many varieties, but through the housing design, dirt always collects at the edges. How do you solve this small but important problem? Hygiene was a particularly big theme during Corona — the steam cleaner that reaches 100°C, which can kill viruses. But we had to prove this through testing and verification, so we wouldn't advertise with nonsense. And we drove that forward with OKR.
OKR was a help there. Similarly, other topics like having our own webshop — selling our products directly. There was a theme of reducing dependency on Amazon, standing on our own feet, and distributing products ourselves. That also emerged from OKR — the energy to move in that direction.
R
Robert29:43
Perhaps a small note: the green posts we see here are actual objectives from the various cycles we've had. With OKR, we went from under 1% revenue in D2C in Germany in 2018-19 to today reaching a double-digit percentage of our revenue in Germany and other European markets where we're strong. And the synchronized, cross-functional work was crucial because there are many facets necessary in the enterprise — order-to-cash process, all the way to delivery, everything interlinked and functioning well.
Because in the end, we all as consumers want that when we order, within 24, 48, or 72 hours — 72 is already pushing it — the products arrive.
Then we also had the logistics topic — scaling logistics more broadly. In the group, we have different companies, some in France, each with their own warehouse. We developed these warehouses into logistics centers. The difference is the ability to deliver to end customers with proper performance, and that different brands and companies can use these services. This means integrating many IT systems.
That was the challenge we're still working on — getting our last logistics center online in September. What started partly as a cost-saving program became a revenue booster because we could deliver directly to many more European countries. OKR helped us broaden our perspective there.
I
Igor Munduate32:09
The wording of the objectives is very important because it allows different people to take different approaches. But the common understanding of what really helps and what the true value is — that's essential.
Then you mentioned it's about being able to react quickly. In the animal kingdom, as Darwin illustrated: not the strongest or most intelligent survives, but the one who adapts to the conditions. Applied to a company, that means we adapt our ideas to external conditions we can't influence and turn them into a strength — an unfair advantage.
And as you can see, you didn't do badly in the difficult times. But there were setbacks. I'll quickly go through them.
The perception that OKR takes too much time — that's a constant battle in the organization. The real value is questioned relative to the time invested. We quickly won many multipliers early on, but at some point we hit a saturation point where it unfortunately didn't continue. You often hear that initiatives and projects simply can't be broken down into three-month cycles. The perception that the ideas from OKR aren't really new, aren't mature enough, not well-developed enough.
And we still haven't managed to implement OKR across the entire Leifheit organization. It's mainly done in our area. These are the things we can learn from the most — from what didn't go well.
Strategic goals with a certain appeal to people somehow work better. That might have to do with meaning — understanding the meaning behind something. It can be helpful to define goals as simple, innovative, useful, and sustainable.
R
Robert35:08
And your takeaways at the end: keep groups small. We once did very large big room plannings, and the communication complexity was personally very challenging for me. We've made changes. The composition of the various OKR levels should always be carefully checked and selected. Participants should be able to really grasp the impact of their decisions for the entire company. Necessary information is important for good decisions. Challenge people beforehand on whether they're truly ready to work differently.
Participants who understand OKR as just another form of conventional project tracking harm the whole effort. Don't underestimate the demands on the quality of objectives and key results — it's very hard work but decisive for success.
I
Igor Munduate36:05
The two points are closely connected. In an old industry company, people partly understand key results as to-dos and as planning. Robert always challenges us: 'No, no, no — you need to have something where you can create value, a benefit.' That's still not fully resolved. We keep returning to it. And when it gets tight, when there are problems, we always fall back into old patterns.
R
Robert36:48
Mm, that's a learning process. It's like how people react in fear situations — without thinking.
I
Igor Munduate37:03
It's the same with mistakes. Error culture as a chance — not error culture, but a learning culture. That's another aspect where we still have a way to go.
R
Robert37:21
Maybe about key results — what seems so simple. It's exhausting. That's one of the negative feedbacks we get: we invest too much time. Why are we fighting over the words? But ultimately, that's exactly what matters — the shared understanding and a clear formulation of what it's about.
M
Moderator37:55
Many thanks. Let me thank you both again for this incredibly exciting presentation. Who in the room is currently implementing OKR? Raise your hand. Think about it for the future. A question often asked is: who does OKR work for? Now you can name Google and Leifheit. And every time you're at home and walk past your drying rack, ironing board, or duster, you can think: at their place it worked too. We can do this as well.
In that spirit, we have time for two or three questions. Who has a question? Let's go — ah, you have one too.
S
Simon39:03
Thank you. What I'd be interested in: you mentioned the difficulties in your process. How did you deal with those, or how are you dealing with them currently? You said it works well in your area but in others you haven't been able to introduce it yet. Are you planning to, and what obstacles are you facing?
I
Igor Munduate39:26
Very good question. Your name was Simon? Simon, great question. It starts with differing opinions within the board itself. Some board members say it's too much effort, too many people to bring together. 'I don't want it yet for myself.' The status quo is still there despite four years. There are always good reasons for that. You have to respect that.
How do you deal with it? Openly and transparently. You can't sugarcoat things. I'll say it quite openly: Industry 4.0 is a big topic, and things are always tangled there. The IT realm — we work with it and not everything always works well. We deal with it transparently. We say: we set these objectives, but these key results — for these and these reasons, primarily their own fault — we're not making progress.
R
Robert40:35
It's a challenge. No one claims they did a bad job. The difficulty is when many people in the company did everything right, but the result is poor. That's tough. How do you get past that? You have to address the topic. What do we learn from this?
I
Igor Munduate41:10
It's like life — it's not simple. Like a relationship. You always stumble over the same stones, always make the same mistakes. You can only say: okay, now let's try to do it even better. I think it's important not to talk about OKR but about what's happening — what's harmful for the organization, because collaboration isn't working, because people aren't cooperating, because things don't run hand-in-hand, because there are too many unmet dependencies where you constantly get stuck.
It's important to talk about these things. OKR is just a means to an end. The goal is to help the organization function well and be value-creating.
M
Moderator41:57
And we have a second question from Georg.
G
Georg41:59
Thanks for the talk. I have two questions. First, you said it was very hierarchical and siloed at the start, with topics driven from the top. Do you still have a division of responsibilities as a board? Do you still have your silos that you drive? What has changed there? And the second question follows from that: we saw the dead artifact of your culture change, which I find totally exciting. But we all know how difficult and how much work culture change actually is. From your gut feeling, where do you stand? What have you achieved so far? What do you do daily to actually set accents there?
I
Igor Munduate42:44
Very good questions. To the first question: we have a division of responsibilities — yes, we do. There's a simple reason: it's legally required. As a publicly traded company, we have legal requirements — personal liability, etc. Clear responsibilities must be defined.
How do we approach it? By talking to each other. Sometimes multiple times. And appearing as a team in several meetings, addressing things openly and expressing different perspectives — because the board doesn't always agree. But it's very important to us to express ourselves with fun, with fairness. Always with respect, always on equal footing. And when we don't succeed — because I can also become emotional — then I say sorry, I crossed the line there, I'm trying to do better.
The second question was: where do we stand in our culture change? We asked our employees: how do you find the atmosphere? Where do you see us? How do you view Leifheit as an employer? And we received amazingly positive feedback: 96% of employees say yes, I enjoy working here. In other companies I've been at, where there were feedbacks saying the boss is dumb and so on — we didn't have that.
That doesn't mean it's peace, joy, and pancakes. But self-critically, on a scale of 1 to 10, where 10 is very good and 1 is very poor, we're somewhere around a 5. So there's still significant room for improvement.
M
Moderator44:52
Thank you very much for the detailed answers. Anyone with further questions can find both of them at the topic table in the back — they'll be there for at least 10 minutes before the next presentation. Are you both here all day? Yes? Very good. Otherwise, there were small postcards on your chairs. Whoever wants can briefly reflect after the presentation: what did I take away, where can I apply it? Invitations — whoever doesn't want them can just leave them there. And with that, we're done with the first presentation from OKR. Many, many thanks.
R
Robert45:26
Thank you.
I
Igor Munduate45:28
Thank you.