Episode Transcript
Transcripts are displayed as originally observed. Some content, including advertisements may have changed.
Use Ctrl + F to search
0:00
Hi, I'm your host Vasco Duarte. Welcome
0:03
to the Scrum Master Toolbox Podcast, where
0:05
we share tips and tricks from Scrum
0:07
Masters around the world. Every
0:10
day we bring you inspiring answers
0:12
to important questions that all Scrum
0:14
Masters face day after day. Hello
0:22
everybody, welcome to our Wednesday the
0:24
Leading Change episode this week with
0:26
Milica Lubinich. Hey Milica, welcome back. Hello,
0:29
thank you for having me again. Absolutely,
0:32
we still have two more episodes to
0:34
go after this one, so people stick
0:36
around. There's a lot of lessons to
0:38
come still, but today
0:40
we dive into change, which is something
0:42
we very often work with as Scrum
0:44
Masters and Agile Coaches. So
0:47
we want to learn about one of those
0:49
processes, Milica, and how you went about it.
0:51
What were the steps that happened in that
0:53
process? And as you go through the steps
0:55
and tell us the story of that change,
0:58
highlight for us the tools, the tips, the
1:00
tricks and the techniques you learned back then
1:02
that you still apply today. So
1:07
in one of my
1:09
previous companies, I think, so
1:11
when they started transformation, it was long
1:13
before I came there. And
1:16
when I came, what I witnessed, and I think
1:18
it's also a very common thing, is that things
1:20
are moving very slowly. And
1:22
I think one of the
1:24
reasons that things are very often
1:27
moving very slowly is because we
1:29
are jumping into a bit more agile
1:32
ways of working, but the ways that
1:34
we're doing decision making is still not
1:37
aligned with that. So for a lot of
1:39
things, we're still in the
1:41
consensus mode of making decisions, and
1:44
that is taking a lot of time. And
1:47
behind consensus kind of decision making
1:49
is also our ability or inability
1:51
to let go of certain things,
1:53
to trust others to be able
1:55
to do their job properly. So
1:58
it's a kind of very complex. topic. But
2:02
sometimes changing the way that we're
2:04
doing decision making is also helping
2:07
let go of certain things, right? Something
2:09
sometimes it's kind of a building on
2:12
that brain muscle from, you know,
2:14
starting the tooling before, you know, diving
2:17
deeper into the into the issue. So
2:19
what I did, what I did then
2:23
was kind of first reflected with the leadership
2:25
team on how are we as a leadership
2:27
team doing decision making? So what are the
2:29
things that we are
2:31
willing or not willing to
2:34
let go of? And can
2:36
we move to a consent
2:38
based decision making? And just
2:40
for the reference, the difference is that for
2:42
consensus, we need everyone being on board 100%.
2:45
And when we talk
2:47
about consensus, we are focusing more on having
2:49
that 60 70% agreement, which means
2:53
I'm not super happy with this decision, maybe
2:55
it could be better, but I'm
2:57
not objecting it. So when
3:00
you get into that kind of thinking, it's
3:02
kind of starting with what is
3:04
the best thing that we can figure out
3:06
right now so that we can get started
3:08
and we'll align on the go. It's the
3:10
most agile kind of way of doing decisions
3:12
and kind of moving things forward, right? So
3:16
and once we aligned in
3:19
leadership team that this is something that we
3:21
want to try out. And once I went
3:23
through the kind of teaching and mentoring process
3:25
with with them, we said, okay, let's create
3:27
something that will work
3:29
as a guide for everyone within the
3:31
company to understand what is that exactly?
3:34
How does you know, what is the
3:36
difference? And how do you even make
3:38
a conscious decision? Maybe for certain decisions,
3:40
we have to have a consensus. And
3:43
that's fine, right? It's too
3:45
big. It's super important. I don't know, it's involving a
3:47
lot of people. There is a lot of risk. I
3:49
don't know. It could be that for some decisions, you
3:51
need to have consensus. But how
3:54
about we start or try out being,
3:56
you know, getting into the default with
4:00
consent-based decision-making so that we
4:02
can unravel and push things
4:05
a bit faster. I
4:12
created a bit of a guide so that people
4:14
understand the difference and know how they can use
4:16
it. Then I did a lot
4:18
of workshops with teams, again, going
4:20
through the process, going through different
4:23
what-if scenarios with them. Because
4:25
once you introduce consent-based
4:28
decision-making, it's creating
4:31
a lot of anxiety with people. That means,
4:33
oh, what if someone makes a decision that is
4:35
bad? Then you have to go
4:38
through all these conversations and ask, what is
4:40
a bad decision? How will you know if
4:42
it's a bad decision? What are the means
4:44
that you have as an individual to object
4:47
it? If you think it will
4:49
create a risk, it will create a huge
4:51
cost. It will do this and that. Then
4:53
it's something that we need to stop. But
4:56
if not, if it's just about, oh,
4:58
I might have a better idea, but
5:00
I don't have it now and I'll
5:03
work on it, yada, yada, then it's
5:05
not an objection. It's an opinion, which
5:07
is fair and you can share it,
5:09
but it's not something that is going
5:11
to stop us from progressing. Then I
5:13
did a lot of one-on-ones
5:17
with people. I did a lot of team sessions.
5:19
I did a lot of Q&As. But
5:22
I think the core for all these conversations
5:26
was this guide
5:28
that I created. It
5:30
was more pretty much just understanding, how
5:32
do you go with consent-based decision-making? How
5:34
that can help you? What are the
5:36
differences? How
5:38
you can put it in practice with big decisions,
5:41
but also on a daily basis. The
5:45
biggest thing that
5:47
I noticed from
5:49
the whole process
5:52
is how much of
5:54
what I would call leg work is needed. How many
5:56
of these things are needed? How many of these things
5:58
are needed? these one-on-ones
6:00
and team sessions you have to have. So
6:02
it's not a straightforward thing.
6:05
You often see this in organizations
6:07
like HR launches something, and then
6:09
they share it and they have
6:11
one Zoom session and they think
6:13
it's going to be implemented. I
6:15
think for me, it was more like, okay,
6:18
this is just a
6:20
thing that we will have in the background, but what
6:23
we actually need to do is go through a lot
6:25
of these scenarios, a lot of these one-on-ones,
6:27
a lot of what I also
6:29
did was offering to people, okay, if you
6:32
want to create a proposal,
6:34
how about I help you? You can pull
6:36
me in, let's do it together. Let me
6:38
help you, coach you through the process. So
6:42
I think when
6:44
trying to introduce
6:47
a change, at
6:50
least from my perspective, as big as this one, it
6:53
will take a lot of legwork. I
6:57
think that needs to be taken into account.
6:59
I was expecting that, but it took a
7:01
lot more than I initially- It's
7:03
funny you call it legwork, and I
7:06
imagine that the metaphor is about going
7:08
and talking, going and meeting, going and
7:10
being present. Is that what you're referring
7:12
to? Exactly. I
7:16
remember the work by
7:18
Esco Gilpi, who's an organizational,
7:20
who was, he passed away some
7:22
time ago, an organizational philosopher,
7:25
so he talked a lot about
7:27
how organizations develop, grow, become better
7:29
or not. And he had this
7:32
metaphor that he used a lot,
7:34
and he called it the ongoing
7:38
co-creation. And
7:40
he used this process of conversation
7:42
as the, we
7:44
could call it the mechanism right behind
7:47
this ongoing co-creation. And
7:49
when you talked about legwork, it immediately
7:51
sparked in my mind this idea that
7:53
what you were doing was keeping the
7:55
conversation alive, because
7:58
you understood that the change- would have
8:00
to be implemented by others and
8:03
you were just the catalyst. And
8:05
therefore, as a catalyst, you need to
8:07
keep the reaction going, right? Like if
8:10
we talk about chemical terms. And
8:13
one very practical way to do that
8:15
is to become part of the conversation
8:17
and keep the conversation alive. Is that
8:19
how you see it? Am
8:21
I characterizing it well? Absolutely.
8:23
Loved how you reflected
8:26
on this one. Exactly. What
8:29
I'm trying to say is that for
8:32
a lot of these things, you cannot just
8:34
create a beautiful workshop and expect that things
8:36
will change. You have to be present in
8:39
the team meetings, in these one-on-ones, in
8:41
the team sessions. You have
8:43
to create a lot of different opportunities. I
8:45
think also a variety of
8:48
different places and times,
8:50
like culture follow structure.
8:52
You have to have different kinds
8:54
of structure to help
8:58
and keep the conversation going so that it's
9:00
a regular team meeting where you can just
9:03
jump in and they're talking about certain things
9:05
and you just quickly can ask what kind
9:07
of decision making would make sense for you
9:09
right now. And then it's
9:12
a sparkle and it keeps happening on the
9:14
go with different conversations. As I said, it
9:16
doesn't have to be, oh, I have this
9:18
idea and then I want to push it
9:20
through. It's more about changing the way that
9:22
we're thinking about decision making on a daily
9:24
basis. And for that, it's
9:26
absolutely necessary to just be present
9:29
and do a lot of this
9:31
legwork. Yeah. I like how you
9:33
call it the legwork because it really requires
9:35
us to go and meet people. Very
9:38
often in the Kanban community, we talk about meet
9:40
the people where they are, right? Like don't push stuff
9:42
onto them, meet them where they are. And I think
9:45
that's a very graphical
9:47
way to describe it. These
9:49
days it's easy to do the legwork. We can just sit
9:52
on a Zoom call, although it is
9:54
not as humane as being face to
9:56
face. It still is one way to go
9:58
and meet people where
Podchaser is the ultimate destination for podcast data, search, and discovery. Learn More