Transcript
Vasco Duart (0:00)
Hi, I'm your host, Vasco Duart. Welcome to the Scrum Master Toolbox podcast where we share tips and tricks from Scrum Masters around the world. Every day we bring you inspiring answers to important questions that all Scrum Masters.
Host (0:14)
Face day after day. Hello everybody. Welcome to our Wednesday the Change Leadership episode. This week with Gosia Smolenska. Hey Gosia, welcome back.
Gosia Smolenska (0:31)
Hello. Thank you for having me here again.
Host (0:34)
Absolutely. So today's change day here on the podcast. I like to call it change leadership rather than change management because I do feel a lot of what we do is about helping others make decisions, helping others move on, rather than telling them what to do and keeping them accountable for what they are supposed to do. But coming back to the story of change, what we want you to share with us, Koshia. It's a story of change and how it went from beginning to end. And as you go through that process, highlight for us the tools, the tips, the tricks and the techniques you learned back then that you still apply today.
Gosia Smolenska (1:15)
So I have experience in few different startups, but actually experience I will share with you is from one startup which I went the furthest. And also this was first time opportunity for me to work actually with the founders and with C level and the whole process, how the company worked with me, working with the founders, then working with the business people and the whole company on this is how we want to work, this is how we will try. And because it was a startup environment, founders were really cautious on naming everything experiments. So we did a lot of small experiments and we left only those which worked. I think this is information that you need to know before going to the experience. And where we started is that the company wanted to have goals. The company wanted to have some goal framework to actually look, are we achieving? We were in the series B and we wanted to hit the series C in the startup. So how we went to that was okay. This is what we discussed with the board members. This is what we think that we supposed to deliver till the end of this year. This is the strategy. How can we actually split it? And one important information is that one of the founders from Free was not really keen on OKRs. So he was like, whatever we do, I don't want to have okrs. I did that. This was a shaky process. Don't do it. So we started, we started with thinking, okay, so let's do some goals. And every quarter we were reviewing this process. So it was not like we set it in the stone. It was every quarter reviewed. We started with Having three goals for a year and each team in the company had to contribute to those three goals. It didn't work well. People didn't know what to do. People didn't understand how to actually approach those goals. Especially there was no Scrum masters. I was the only person in the company from other environment. The company wasn't also that big, so it didn't work. Teams didn't know how to connect their goals with other teams. They were collaborating like development teams were collaborating with business teams. They had no idea how to actually do it. So we said, okay, stop, we need to sit and think about it again. And actually after three months, so after first quarter, the person was like, no, no, we are not doing OK. So we're like, I think those OKRs could help us. We were like, yes, well, that's a change. Exactly. And we were like, finally, so let's start implementing okrs. So we rewrite our goals in the OKR manner. The company goals we started, the first of all was rewriting the okrs. Second step was actually for each team to do the product canvas. This is the small exercise with why your team was created or what, what is your mission, who is your customer, what needs you will be fulfilling, what are your goals as a team and who is your partner? So we added this part. This is your customer, but you also have partners in the company. Because we had the flow. Like there was a development teams but very closely connected to business teams who were then connected with the customers. So we actually did this with every single team so they will understand, okay, this is my partner in crime, but this is my stakeholder. And after that we started actually doing okrs. So we had OKR framework in place. We had company goals, which were yearly goals, but KRS were quarterly, so objectives were yearly. The keyers were quarterly. And we started to ask each team to contribute to key results. And because they already knew, okay, this is my partner, so we can together contribute to okr, they started to thinking about that this was the first quarter when we did okrs and when we figure out how to do it. And after. And we used Excel for that, we had no idea what to use, so we used Excel.
