No items found.

Easy Agile Podcast Ep.7 Sarah Hajipour, Agile Coach

Listen on
Subscribe to our newsletter
Caitlin Mackie

"I absolutely loved my conversation with Sarah, she shared some amazing advice that I can't wait to put into practice!"

We spoke about the agile mindset beyond IT & development teams, how teams such as marketing and finance are starting to adopt the methodology and the benefits of doing so.

In celebration of international women's day, we discussed the future of women in agile, and steps we should be taking to support one another towards an inclusive and enabling environment.

Be sure to subscribe, enjoy the episode 🎧

Transcript

Caitlin Mackie:

Hello everyone and welcome back to the Easy Agile Podcast for 2021. Each episode, we talk with some of the most interesting people in tech, in agile, and in leading businesses around the world to share fresh perspectives and learn from the wealth of knowledge each guest has to share. I'm Caitlin and I'm the Graduate Marketing Coordinator at Easy Agile and your host for this episode. We are thrilled to be back and have some amazing guests lined up this season. So to kick us off, I'm really excited to be talking with Sarah Hajipour.

Caitlin Mackie:

Sarah has so much rich and diverse experience in the agile space. She's an agile coach, a business transformation leader, a project and program manager, and more recently a podcast host and author. She's the jack of all trades and has been in the business agility space for over 10 years. In this episode, Sarah and I chat about the significance of goal setting and in particular goal setting in unpredictable times. We chat about her most recent projects, the Agility Podcast with Sarah Hajipour and her book on Agile Case Studies.

Caitlin Mackie:

And of course with International Women's Day coming up, Sarah shared some amazing advice and her thoughts on the way forward for women in agile. She highlighted the importance of raising your hand and asking for help when you need it, as well as embracing qualities that aren't always traditionally thought of in leaders. It was such a thoughtful and insightful discussion. I got a lot of value out of our conversation and received some great advice, and I'm really looking forward to putting into practice. I know those listening will feel the same. Let's jump in.

Caitlin Mackie:

Sarah, thank you so much for joining us and spending some time with me today.

Sarah Hajipour:

Sure. Thanks for having me.

Caitlin Mackie:

So being our first guest for the year, I wanted to ask you about any new year's resolutions. Are you on track? Are you a believer in them or do you have a different type of goal setting process?

Sarah Hajipour:

That's a great question because we discussed this with a couple of friends and we realized new year's resolution is always going to be some kind of like a huge goal that we don't know if we're going to meet it or not. And thinking agile business agility and as an agile coach, I believe in the fact that let's have smaller goals and review them every three months, every six months and see where we at. Instead of looking into huge goals that we don't know what's going to happen because there's always a lot of uncertainties, even in our personal lives regarding the goals that we set up for ourselves. So yeah, that's how I look at it. Quarterly, quarterly personal goals. Let's say that.

Caitlin Mackie:

Yeah. Yeah. I love that. Yeah, I think if the last year has taught us anything, I think we can all agree how unpredictable things can become. So those original goals.

Sarah Hajipour:

That's true.

Caitlin Mackie:

Yeah. The original goals might have to take a couple of detours. So what would be your advice for setting career goals in uncertain times?

Sarah Hajipour:

That's a great question. For career goals I believe it really matters that you do something that you're interested in at least. If you still haven't found your passion, that's fine especially people like young professionals. It's okay if you haven't found your passion yet, but you can still follow a basically career path starting with things that you like to do, kind of you enjoy and you learn through the way.

Sarah Hajipour:

I was listening to one of the fashion icons on YouTube a couple of days ago and the interviewer was asking her, "What was your career path? How did you get to this place you are now?" And I loved what she told everybody, the students, and that was go and find a career, find a job and learn. You first need to learn a lot of skills before you decide what you're actually good at. You decide, you understand what's your weaknesses and your strengths, right? Because not all of us have these amazing ideas all the time and that's fine.

Sarah Hajipour:

I'm not very much pro-everybody has to be a visionary and everybody has to have like big, shiny goals and ideas. I think that's perfectly fine to just find the kind of job that or the kind of career path that you're comfortable with and then sometimes get out of your comfort zone and then discover as you go. Life is to explore, not to just push yourself on the corner all the time and just compare yourself with everybody else.

Caitlin Mackie:

Yeah. I love that. That's great advice. So you've recently added podcast host and author to your resume. Were they always career goals of yours?

Sarah Hajipour:

No, absolutely not. Well, I'm a little bit of an introverted person. So kind of sit in front of a camera even talking and having people hear me was always like, "Oh my God, I know I need to talk about this even with my teams and stuff," but I will do it only if it's necessary. What got me into podcasting was that I figured there's a lot of questions that I'm finding answers when I'm having conversations and meetups and in different groups, professional groups that I'm in. And I wanted other people to hear those as well. I talked to people who have great insights and have been way longer than me in the career. So I'm learning at the same time. And I wanted to share that learning with everybody else. That's the reason I'm doing the podcast.

Caitlin Mackie:

Yeah, that's great. Yeah, I love that. And I think you kind of touched on this earlier, but I think being in the agile space, sometimes it can be a nice reminder for you to have a bit of a focus, but then reflect and understand sort of where to be more effective and adjust accordingly. I know you mentioned that with your career goals, do you think that those agile principles can be applied beyond the usual use case?

Sarah Hajipour:

I do. I believe that it's a very intuitive like agile is a very intuitive way of working and a way of thinking. That's why now it's expanded to other industries. They didn't stay with DevOps and IT and development. It is now a lot of different industries adopting this because it's a mindset change. And just not just using scrum. It's not just using Kanban. It is about understanding how to be able to reflect on and adapt to the faster changes that are happening in the world. And that also applies to our personal lives as well.

Sarah Hajipour:

I mean, I used to have set goals when I was 18-years-old, I'm going to be this at 30, but did they happen? No. In some aspects I achieved much, much more. And in some aspects I just changed my goal. I think the changes that are happening in the world that are more rapid, it demands us to change as well. Yeah.

Caitlin Mackie:

Yeah. Awesome. So just to circle back a little bit there for your podcast just for our audience listening, what platforms can they access your podcast on?

Sarah Hajipour:

I'm on all of the main platforms. I'm in Apple podcasts. I'm in Spotify, I'm in Amazon. Most of the prominent podcast platforms.

Caitlin Mackie:

Awesome. And then just again, for our audience, your podcast is called the Agility Podcast with Sarah Hajipour.

Sarah Hajipour:

That's correct. Yes.

Caitlin Mackie:

Awesome. That's great. What do you think has been the most valuable lesson you've learned from your podcast so far? Is it something a guest has shared or something you've learned along the way?

Sarah Hajipour:

What I have learned, I have learned a lot from the people that I interview because I make sure that I talk to people who know more than me and have been in this field more than me, and in different industries. The main thing I would say is that agile business agility is about mindset rather than the tools and processes. And the fact that the world overall is moving towards a more human-centric way of working.So basically that's why I say agile is more intuitive rather than just following ABCD. Yeah. This is the core, the main thing that that I have learned from my interviewees.

Caitlin Mackie:

Yeah, amazing. You've also started writing a book at the moment. Can you tell us a little bit more about that? How did that project begin?

Sarah Hajipour:

I actually love this project. In this book, the way I actually started writing the book was the book came first and then the podcast happened. I attend a lot of meetups. So for young professionals and even for professionals who are very much skilled in what they do, meetups are great place to meet and expand your network and learn from your peers. So I was attending all of these and I was learning from people. And then I decided I really want to have one-on-one conversations with them. And eventually I figured that a lot of the agile coaches, a lot of executive levels and a lot of consultants, they have a lot to share, but I didn't see any platform that kind of unifies that.

Sarah Hajipour:

I said, "Okay what are the learnings that we can share?" A lot of the mistakes because of the meetups groups, people feel safe to share and be vulnerable. And I was in multiple meetups so I heard very similar stories from people, the mistakes that have been repeated by a coach somewhere else. So I thought that'd be a great idea to put these in agile cases. So it's going to be Agile Case Studies and share it with everyone so. Especially the young coaches or stepping into the business, there's a lot of unknowns. I don't want them to be afraid. I don't want them to think, "Okay, this is a huge task." There's always going to be a lot of unknowns.

Sarah Hajipour:

Yes, I just see that. I kind of want to give that visibility that everybody else is experiencing the same, even if they have 25 years of experience, which is amazing, right?

Caitlin Mackie:

Yeah.

Sarah Hajipour:

And that's the reason I started writing the book. So I interview with agile coaches and agile consultants that have been around at least five to 10 years and led agile transformation projects. And then from there, one of my interviewers once said, "You should do a podcast. I like to talk about this too." I'm like, "This is great" and that was like the week after I was like running around looking for tools to start my podcast.

Caitlin Mackie:

Oh, amazing. Sounds so good. What's the process been like? How have you found from ideation to where you are now, and then eventually when you're publishing it?

Sarah Hajipour:

For the podcast?

Caitlin Mackie:

For the book.

Sarah Hajipour:

For the book, so I go to these meetups and I listen to what's the coaches and the executives are sharing. The ones that are exciting for me are kind of a new for me, I will ask them, I connect with them over in LinkedIn and people are so open to sharing their experience with you. I've never had even one person said to tell me, "No, I don't want to talk about this or anything." People want to share. So I approach and I say, "Hey, I have a book outline or guideline. It's a two pager." I send it to them and I asked them if they are interested to talk to me about this and they let me know and then I'll select a time.

Sarah Hajipour:

And first session, it's like a half an hour. It's a kind of a brainstorming session. What are the key cases that they feel they want to share? Then we pick one and the session after that, they'll actually go through the case with me. I record it, draft it and then share it on Google Drive back and forth until we're happy with the outcome.

Caitlin Mackie:

Yeah. Awesome. Do you have a timeline at the moment? When can we expect to be able to read it?

Sarah Hajipour:

I'm looking forward to around the end of 2021, because it's 100 cases and I think that I'll have that.

Caitlin Mackie:

Yeah. Awesome. It's so exciting. Lots to look forward too.

Sarah Hajipour:

Thank you.

Caitlin Mackie:

Now, I also wanted to touch on International Women's Day is coming up and you've been in the agile space for a few years now. I assume you've probably witnessed a bit of change in this space. Have there been any pivotal moments that have sort of led to where you are today?

Sarah Hajipour:

Well, I think that a lot of women are being attracted to the agile practice, the different agile roles. And I have seen a lot more women as scrum masters, as product owners and as agile managers or agile project managers. A lot of different roles are being kind of flourishing in this area. And I've seen a lot of women contribute. One my goals actually in my book and on my podcast is to be able to find these women and talk to them regardless of where they are in the world. Yeah, I just feel that women can grow really in this area in the agile mindset, because women are more the collaboration piece.

Sarah Hajipour:

I can't tell we're less competitive. I haven't done research on that, but I have discussed it with people. Do you think that women are more collaborative rather than competitive? Because competition is great, but you need a lot of collaboration in agile and a lot of nurturing. You need to have that nurturing feeling, the nurturing mindset, that's what a scrum master does. One of the key characteristics of a scrum master has to be they have to have this nurturing perspective to bring it to the team.

Caitlin Mackie:

It's funny you mentioned because I actually have read some stuff myself about women typically possessing more of that open leadership style and that open leadership seems to complement the agile space really nicely so.

Sarah Hajipour:

That's exactly, yeah.

Caitlin Mackie:

Yeah. Yeah. That's great and I think there's lots that we can take from that, open leadership and the direct leadership. So men and women coming forward and finding that middle ground and yeah, I feel like agile is a great space to do that in?

Sarah Hajipour:

Yeah, I totally agree. Yeah.

Caitlin Mackie:

Yeah, yeah. So what drove your passion? I guess what made you want to pursue a career in this space?

Sarah Hajipour:

I love the collaboration piece and I love the vulnerability because like people are allowed to be vulnerable and in the teams that they work in. And it is a culture that is more human rather than super strict. We're not allowed to make mistakes. We're not allowed to be wrong. Leaders are supposed to know everything right off the bat. But in reality, that's not the case. Leaders have to feel comfortable not knowing a lot of things that are not even known. But a lot of times I always say we're in the unknown unknown zone. And in that zone, even leaders are not supposed to know everything.

Sarah Hajipour:

So a lot of it starts with what are the other things that I learned from my interviewees is that it all starts with the leadership. So the agile transformations, the leaders have to first create that atmosphere of collaboration and of trust and psychological safety among themselves. And then only then they can help with teams to be able to thrive in those kinds of atmospheres as well.

Sarah Hajipour:

Women in agile and women in leadership. I like to say and what I see is a lot of men and women both that are changing their perspective from process of tool-centric to people-centric because it works better for everyone. And I see change really happening in all industries. I see it in retail. I see it in construction, obviously in IT, in finance system. And there's men and women like hand-in-hand trying to kind of embrace this way of thinking and this way of working.

Sarah Hajipour:

And women are being more comfortable to grow and kind of raise their hand and say, "Hey, I can make each page. I can take this role" because they understand because they bring that psychological safety that women for ages, it has been a workplace has been something that was mostly men and we're gradually getting into the workforce or the business world as females. So that psychological safety has allowed women to raise their hand and grow in different roles and leadership roles obviously.

Caitlin Mackie:

Yeah, yeah. I couldn't agree more. Has there been any resources or networks, things like that that have helped you along your journey?

Sarah Hajipour:

Learning from everybody else like creating a network, expanding my network to kind of coming in and saying, "Hey, I don't know. I want to know." There is all of these amazing things that are happening. I like to understand how this works and I remember it was one of these founders. Who's the founder of Apple? Oh my God. Don't tell me.

Caitlin Mackie:

Steve Jobs.

Sarah Hajipour:

I love this quote from Steve Jobs that says, "There has never been a time where I asked for help and people didn't help me." So just raise your hand and say, "I need help." And what does that help that I need? I need to know about this. What does it mean? What does scrum mean to you? How does it work in your industry? How does it work? And really I think that was the key for me up until now to connect with people and just be vulnerable and let them teach me.

Caitlin Mackie:

Yeah. I think my next question would be about how do we amplify that diverse and empowered community of women and our job in increasing the representation of women in agile? And yeah, what do you think is key to achieve a supportive and enabling environment?

Sarah Hajipour:

What I have seen and realized is that women really need to be and are being more supportive of each other. There was a study in HBR, Harvard Business Review in 2016 that said, "If there is only one woman in the pool of the interviewees, there's a zero chance for that woman to get the job, even if she's the best." So this calls for not which women are actually working great on that. Not being the queen bee, but also engaging and including other women. Because the more women in different roles, the more we are going to be receptive in those communities. That I think is a key that we understand that and support each other, help each other, build the communities around it.

Sarah Hajipour:

There is a community Women in Agile that is in different cities and different parts of the world that I'm a member of as well doing a great job. It's not just women actually in those groups. I see men participating as well, but it's predominantly women are trying to give each other insights from all aspects of the agile practices, the agile ways of working and stuff. Yeah.

Caitlin Mackie:

Yeah. So I think what's the way forward? I guess what's your prediction for women in agile? What do we need to do to continue that momentum?

Sarah Hajipour:

I think women will do great in anything and everything they put their minds in, regardless. We're human bottom line and we all have this potential to be able to grow in whatever we put our mind and heart on, regardless of our gender. So I would love for women to kind of be able to get that holistic perspective that regardless of their gender, they can do anything and they are, we are.

Sarah Hajipour:

We read about other women who have been successful in the fields of business that you felt that probably women can't do like women astronauts. There are women physicists. Women engineering leads and all of these that have been less common. The world is changing for the better and that's great.

Caitlin Mackie:

Yeah, yeah. I absolutely love that

Sarah Hajipour:

It's a great time to be alive.

Caitlin Mackie:

Yeah. That's exciting. Yeah, exactly.

Sarah Hajipour:

Yes.

Caitlin Mackie:

Yeah. I definitely think that we are beginning to see a huge increase and the visibility of female role models across so many industries. So it's great to have that. But Sarah, this has been such a great conversation. I wanted to finish with a final question for you and that was if you could give one piece of advice to women just starting their career in their industry, what would it be?

Sarah Hajipour:

I would say maybe the best advice that I can give is that we do have the power. And we need to look, number one, beyond gender and kind of have that belief that we can do anything that we want. And second is don't be shy to open up and build your community like build a community, join a community of agile practitioners of agile coaches, even people, specifically people who know more than you.

Sarah Hajipour:

And don't be afraid to ask help. Don't be afraid to say, "Hey, I'm new to this and I love to learn from you guys." Don't be afraid to put yourself out there and you're going to learn a lot that you wouldn't even expect. Just like you're going to get the result so you're going to hear things beyond what you've expected. There's a lot to human potential that could be unleashed when you just put yourself out there and let others contribute to your growth.

Caitlin Mackie:

That's amazing. That's great advice, Sarah. Loved every minute of our conversation. So thank you so much for joining me today. I really appreciate it.

Sarah Hajipour:

My pleasure. Thank you so much for having me.

Related Episodes

  • Podcast

    Easy Agile Podcast Ep.4 Em Campbell-Pretty, CEO & Managing Director at Pretty Agile

    "We spoke in detail about scaling agile, being a SAFe fellow, discipline, the traits of effective leaders and how to trust your people."

    Transcript

    Nick Muldoon:

    Good day, folks. Thanks for joining us for another Easy Agile Podcast. This morning, I'm joined by Em Campbell-Pretty of Pretty Agile. Em is one of 22 SAFe fellows globally and she's been doing agile transformations at scale for over a decade now. She's also the author of two books, The Art of Avoiding a Train Wreck and Tribal Unity. So, all about culture and psychological safety here, and all about obviously scaling agile release trains, tips and tricks.

    Nick Muldoon:

    My key takeaways that I was really jazzed about, the traits of effective leaders for scaling agile transformations and being an effective organization, trust, as in trusting their people, an openness to learning and a willingness to learn, the ability to experiment and treat things as failures if they are failures, and discipline. Em and I talked a bit about discipline today as a trait of leaders. It's a really great episode and I took a lot from it, and you'll hear my takeaways at the end and what I need to go and learn after some time with Em this morning. So, let's get started. How many weeks a year are you typically on the road?

    Em Campbell-Pretty:

    How many weeks a year am I typically on the road? A lot, most. It would be unusual for me to spend four weeks without going somewhere. That would be unusual. I don't travel every week, but I travel most weeks, and I travel in big blocks. Right? So, I'll go and do ... Like I said, just before the lockdown, we did three weeks in Auckland, so that was in February-March.

    Em Campbell-Pretty:

    We went to Auckland, we had a client in Auckland, we just stayed there. So, three weeks in Auckland, came back here, and did not return to Auckland. Returned to support that client virtually over Teams and Zoom was how that one went. But yeah. Normally between running around Australia, Southeast Asia, Hong Kong, Singapore, Manila, the US, New Zealand, yeah, not home that often, normally. This has been truly bizarre.

    Nick Muldoon:

    So, this is a very unusual year for someone like yourself that's flying around visiting clients all over the world.

    Em Campbell-Pretty:

    Absolutely. Absolutely. It's been a very strange year. It's an interesting difference on energy as well. Not flying all the time I think is good for my body. I feel the difference. I also feel the difference sitting in a chair all the time. So, I was traveling a lot, but I was on my feet most days when I was working. Now if I'm working, I'm sitting a lot.

    Nick Muldoon:

    You're sitting down. Yeah.

    Em Campbell-Pretty:

    So, that's interesting. But I don't miss the jet lag at all. I don't miss the amount of time the travel consumes at all. In fact, it's been nice. I've had a little bit of head space. I've probably blogged more this year than I have in a few years because I've just had some head space and being able to think. But I don't get to see the world either, and all my holidays got canceled. So, nevermind work. I had trips to Europe. Four weeks from now, I was supposed to be in Canada seeing polar bears.

    Nick Muldoon:

    Aw.

    Em Campbell-Pretty:

    Tell me about it!

    Nick Muldoon:

    I would love to see polar bears. They look so cuddly on TV. I'm not sure that that would actually be the circumstance if I was to try to approach one and give one a cuddle.

    Em Campbell-Pretty:

    Yeah. I don't think cuddling was involved. I was told I could bring a camera and a tripod, which means obviously I'm going to stand some distance away from this polar bear and take photos. But that will not be happening either. So, no holidays and no travel for work, and of course, being in Melbourne, not even any, let's just go to [crosstalk 00:04:15].

    Nick Muldoon:

    Coffee or anything like that.

    Em Campbell-Pretty:

    Just nothing.

    Nick Muldoon:

    Nothing.

    Em Campbell-Pretty:

    Nothing.

    Nick Muldoon:

    Yeah, because you've been on legit lockdown.

    Em Campbell-Pretty:

    Yep.

    Nick Muldoon:

    So, tell me then about the shift over the last 10 or 15 years in these scaled, agile transformations. Obviously today, like you described with this client in Auckland, everything's got to be remote. Presumably, not as effective. But I'd love to get a sense of what the evolution is from the transformations 10 years ago, banking, telcos, that sort of environment to the clients that you're working with today. Describe what it was like 10 years ago.

    Em Campbell-Pretty:

    So, 10 years ago, and it's so interesting to reflect on this now, I read Scaling Software Agility, which is a book that Dean published in 2007. Then I discovered that wasn't the latest book, so then I read Agile Software Requirements. This was 2011. I'm this crazy, angry business sponsor with this program of work I'd been sponsoring for five years that's never delivered anything, and in this cra-

    Nick Muldoon:

    You were the crazy, angry business sponsor?

    Em Campbell-Pretty:

    Yeah. Yeah, yeah. I was the crazy [inaudible 00:05:26]. I was very angry. You would be angry too if you were me. I refer to it now as the money fire. So, basically, here's my job. Right? Go to the CFO, ask for money. Give the money to IT. IT lights a match, sets it on fire. Comes back, asks me for money. I get to go back to the CFO and say I need more money. Five years. Five years. That's all I did. Ask for money and try to explain where the other money went.

    Em Campbell-Pretty:

    Anyway, in the strangest restructure ever, I end up the technology GM for the same group I had been the business sponsor of for the past five years. Apparently, they couldn't find anybody appropriately qualified. So, you can do it, Em. Sure. So, I'm a bit of a geek, so I read books, and I'm reading these books by Leffingwell because I'd been doing some agile ... So, I'd been doing something I'd been calling agile. Let's just go with that.

    Em Campbell-Pretty:

    It was interesting to me because I could see little rays of light. But it still wasn't really making anything happen, so hence the reading. These books talk about this agile release train [inaudible 00:06:46] that sounds cool. We should so do this thing. So, I set about launching this train at a Telstra in early 2012. It wasn't called SAFe, right? It was just the books and these things called an agile release train.

    Em Campbell-Pretty:

    Now, to look back 10 years ago, it wasn't called SAFe. People weren't running around doing this. I was not actually really qualified for the job I was in. Well, I wasn't a technology leader by any stretch of the imagination, and I decide that I'm just going to launch an agile release train. So, there were rare and unusual beasts, and I'm not sure I really understood that when I went down the path of doing it.

    Em Campbell-Pretty:

    I'm big on the, I read it in a book, I read it in a blog, I heard it at a conference, I'll just try it. That's very much always been my mental model. So, I read it in a book and I just tried it. Then we discover that actually, literally nobody is doing this, so it becomes Australia's first agile release train and Australia's first SAFe implementation. Oh, boy, have I learned a lot since then.

    Nick Muldoon:

    Well, yeah. I was reflecting on that because I dug out The Art of Avoiding a Train Wreck, right? This is one of the ones that you signed for Tegan. But obviously, you've learned a ton since then because you've managed to put together a tome of tips and tricks and things to avoid as you are pursuing these transformations. As an industry, though, well, as an industry, I guess this spans many industries, but as a practice these days, are we actually getting better at these transformations? Are there companies out there today, Em, that are still taking piles of money and setting it on fire?

    Em Campbell-Pretty:

    So, I think I meet people every day who hear my story and go, "Oh, my god. You used to work here?" So, I think there's still many, many organizations that have an experience that is like the experience I had back in 2010 and what have you. So, it seems to be something that really resonates with people. I guess so many of the businesses we go into now either are not agile at all or, I guess like my world was, doing something they call agile. What we find is the something that they call agile, I wouldn't say it's not agile. But it leaves a lot to be desired.

    Nick Muldoon:

    They're on a journey, right?

    Em Campbell-Pretty:

    Yeah. Yeah. Well, I guess so because they end up having a conversation with us. So, they understand that what they're doing is not enough. They understand that what they're doing isn't getting them the results that they want. I don't know that they understand why. It's interesting to me sometimes that they look to SAFe because you asked me about how's the client base changed? One of the things that's really interesting in Australia is we get far more of the small to medium sized companies now than the big ones.

    Em Campbell-Pretty:

    So, they're companies that consider themselves agile. But what we're calling them, the startups that are no longer startups, right? These are organizations that they're generally old 10, 20 year old startups and they're scaling and they see their problem as a scaling problem. So, that's what leads them to a conversation around the scaled agile framework.

    Em Campbell-Pretty:

    When we look at them through a SAFe lens, we go, "Gee, you're tiny. But okay. I can see that you can have an agile release train and it won't do you any harm. In fact, it would probably help you a lot in terms of mid-range planning," because mid-range planning just seems to be nonexistent for a lot of these organizations. Prioritization. A lot of these small organizations, very knee-jerky in terms of how they prioritize, bouncing from one thing to the other.

    Nick Muldoon:

    Are they reacting to the market, or are they reacting to the leaders, maybe the lack of discipline in the leadership?

    Em Campbell-Pretty:

    You know what? They would say they're reacting to the market. I would say they've got a discipline issue.

    Nick Muldoon:

    Yeah. [crosstalk 00:11:23].

    Em Campbell-Pretty:

    So, I read, obviously, big reader, last summer, obviously Australian summer, US winter, I read Melissa Perry's The Build Trap. Interesting book and your well respected thought leader in product management. Not a big fan of SAFe. Probably not a big fan of agile either was the takeaway I had from her book. But the thing that she does talk about that I really thought was valuable was the lunacy in chasing your competitors. So, building features because your competitors-

    Nick Muldoon:

    Your competitors [crosstalk 00:12:06].

    Em Campbell-Pretty:

    ... build them, or building features to land a contract or retain a customer. So, I thought she sees all of that as lunacy, and I tend to agree. So, that was my ... I think that's quite interesting. Her perspective is you don't know if the competitor's actually having any luck with that thing that they've built. So, if you build it because they built it, you don't know. You have no idea. So, don't just build it because they've built it. It might not be doing them any favors either.

    Em Campbell-Pretty:

    Of course, once you start just doing random stuff for this big customer or this big client, you start to lose your way as an organization. People end up with completely different versions of their products, branches that they can't integrate anymore. It's interesting. So, when I look at that, I go, "I feel like there's a discipline issue in some of these organizations at the leadership level."

    Em Campbell-Pretty:

    What is it we're trying to do? What is our vision? What is our mission? What is our market? What are we doing to test and learn in that market, as opposed to just get a gun, let's do everything, grab everything? Oh, my goodness. They were doing that over there. Stop this, start this, stop this. Of course, if you're stopping and starting all the time, you're not delivering anything, and that seems to be something that we see a lot with these organizations. They're not delivering.

    Em Campbell-Pretty:

    I'm not saying their delivery mechanism is perfect. There's challenges there too. But some part of the problem is the inability to stay a course. Pick a course and stay a course. I'm not saying don't pivot, because that's stupid too. But being more deliberate in your choices to pivot, perhaps. Yeah.

    Nick Muldoon:

    Do you get a sense, Em, that there are leadership teams in various geographic regions that are more effective at this and more effective at that longterm planning and having that discipline and that methodical approach to delivery over an extended time period?

    Em Campbell-Pretty:

    I think regions and cultures and nationalities certainly play a role in the leadership, I don't know, persona, personality. I don't know that I could say when I've worked in this country or this part of the world that their leaders are better at forethought. I think some cultures lend themselves to lean and agile more than others. Hierarchical cultures are really, really challenging.

    Em Campbell-Pretty:

    That can be both a geographic thing, but it can also just be an industry thing, right? So, government can be very hierarchical. The banks can be very hierarchical. Some of the Asian cultures are very hierarchical. But some companies are just very hierarchical as well. So, who owns the company, who leads the company, all of that can play a big role in what's acceptable because so much of success in this scaled agile journey comes down to a leadership that is willing to trust the teams, a leadership that is willing to learn, a leadership that's willing to experiment, and a leadership that's prepared to be disciplined.

    Nick Muldoon:

    So, leadership with trusting the teams, willing to learn, willing to experiment, and with discipline. They're those four things that you-

    Em Campbell-Pretty:

    Yep.

    Nick Muldoon:

    Yeah, okay. I'll make a note of those, Em. I'll come back to those. Trust, learn, experiment, and discipline. I'm interested, I guess, this year being a very interesting, a very unique year for doing remote transformation work and coaching and consulting, 10 years ago, what was the percentage of remote team members distributed teams? Now, you've basically, I think the big banks in Australia aren't even going back to the office until 2021. Atlassian is not going back to the office until 2021. Twitter, Jack Dorsey, my old CEO, said, "Work from home forever," sort of thing. What's the takeaway for this year and what do you expect for 2021 and beyond?

    Em Campbell-Pretty:

    So, look. This year has been eyeopening, and look, some things are, as I would have anticipated, some things have been different. So, obviously, we're seeing entire organizations going online. We're seeing the teams are online, the PI planning's online, everything's online. That's actually in some ways opened up opportunity. So, where we've had clients who have had the most odd setups in terms of distribution, and you can make a train work where you've got teams across two locations. But we're big fans of the entire team is in Sydney or the entire team is in India. We don't have half the team in Sydney and half the team in India.

    Em Campbell-Pretty:

    But organizations really struggle with that because perhaps all the testers are in India and then you want a tester on every team and now you've got a problem. How do you create a complete team and not cross the time zones? So, the opportunity becomes if I can find teams that are not physically co-located but time zone friendly, I have a little bit more option. So, I can have a train that operates between, I don't know, Sydney and India. Or I can find a four hour overlap in their day, and I can insist that that team works 100% online.

    Em Campbell-Pretty:

    So, the big thing that we'd advise against is I don't want that team hybrid. Right? I don't want three people sitting in the office in Sydney and three people sitting in their homes in India. I want everybody online. I want an even playing field, and I think we can do that now in a way that is more acceptable than before. Because the same advice I was giving, gee, back when I wrote Tribal Unity, same advice. Right?

    Em Campbell-Pretty:

    So, 2016, everybody, equal playing field. If you're going to be distributed, everyone has to be online, as opposed to some people online and some people in a room. So, that's a more acceptable answer now than it was prior to this year. So, that's good. I think that's good.

    Nick Muldoon:

    In 2021, then, Em, you mean this is just going to play forward. I guess there's going to be a reversion of some of these companies back to the office because they've got huge real estate and workplace infrastructure already.

    Em Campbell-Pretty:

    Yeah. So, look. We're seeing clients closing offices the same way that you see some of the companies in the US doing that. We're also seeing parts of Australia and New Zealand with no particular COVID impact at this point actually going back into the office, and having created that example of teams that are crossing time zones, and then going back into the office and going back to that hybrid space. So, that's interesting and [crosstalk 00:20:08].

    Nick Muldoon:

    So, where you're back into that environment where you might have some people working together in an office that can get a cup of coffee together and then some that are stuck still at home. I guess there's not just even regional differences, right? If you've got a team member that's got a particular health situation, they're not going to feel comfortable necessarily coming back into the office, regardless of the situation, until there's a vaccine or something.

    Em Campbell-Pretty:

    Absolutely.

    Nick Muldoon:

    Yeah, okay.

    Em Campbell-Pretty:

    So, yeah. Look, I think it's going to be interesting. I would strongly advocate that organizations have teams that are either in person teams or online teams, and the team just either operates 100% online or the team operates 100%-

    Nick Muldoon:

    In the office.

    Em Campbell-Pretty:

    ... in person and in the office, and if you have a train that has both in any train level ceremony, everybody goes to a desk and-

    Nick Muldoon:

    And do it online.

    Em Campbell-Pretty:

    ... a video camera and we do it that way. I think the thing that seems to be most sticky about the physical environment and SAFe is PI planning. Nobody needs to beat. Right? That was cool. Nobody needs to beat, no one's PI planning slipped, everybody just went. They were all online. So, we'll just PI plan online. It'll be fine. We saw people use whatever infrastructure they had available to them.

    Nick Muldoon:

    Yeah. [crosstalk 00:21:30].

    Em Campbell-Pretty:

    So, I'm sure a number of people called you folks and said, "We need a tool." But some just went, "We have Google Suite, we have Microsoft whatever it is, we have this, we have that. We're just going to make it work," and no matter what they used, they made it work and they ran the events and their events were effective and they got the outcomes. The big thing that is missing is that energy. You can't get the energy of 100, 200 people in a room from an online event. But mechanically-

    Nick Muldoon:

    We can achieve it.

    Em Campbell-Pretty:

    ... we can achieve it. So, we hear everybody wants to go back to PI planning in person because of the social, because of the energy, which I think is awesome. I absolutely think that is awesome, and I can see this world in which people do a lot more work from home, work remote, whatever that looks like, and then the PI planning events are the things that we do to bring ourselves together and reconnect on that eight, 10, 12 week basis. That's my feeling. Could be wrong.

    Nick Muldoon:

    I guess I'll be really interested to see how it plays out, and I think we should return to this conversation in 12 months, Em.

    Em Campbell-Pretty:

    Yeah. Oh, no.

    Nick Muldoon:

    I'm just thinking, what's going through my mind is one of our customers in New York, financial services company, and for one of their arts, it was 150,000 US exercised to bring their people together once a quarter.

    Em Campbell-Pretty:

    Yeah. Wow.

    Nick Muldoon:

    I'm now going, I'm like, "Okay, yes, they're doing it digitally now." That's fine. They're going to miss out on things. But if they lose the budget, do they have to fight to get the budget back? Or does the budget sit there? There's these other unknown ramifications of this shift over the course of 2020 that we're yet to see play out, I guess.

    Em Campbell-Pretty:

    I think you're right, and I think it would be particularly interesting for the trains that have been launched remotely. So, if the train has been launched remotely, do you ev-

    Nick Muldoon:

    So, not existing trains that have been working together for six to 12, 18 months. But you want to get a brand new train started. Have you done that remotely this year with some of your clients?

    Em Campbell-Pretty:

    Oh, we're in the process of doing it now.

    Nick Muldoon:

    Cool. Tell me.

    Em Campbell-Pretty:

    We had one, though, literally just before the lockdown. So, they did their first PI planning face to face and then immediately moved to remote working and, yeah, now working on remotely launching a train. For us, we have a playbook. It's a bunch of workshops. It's a bunch of classes. We just use online collaboration tools. We've found things that replicate the sort of tools that we would have in a physical room, and the joy of being able to read people's Post-it notes, right? This has been the absolute highlight for me, the joy of being able to read people's Post-it notes.

    Nick Muldoon:

    No more hieroglyphics.

    Em Campbell-Pretty:

    Yeah. Absolutely.

    Nick Muldoon:

    What is that that you wrote, Sally? Yeah.

    Em Campbell-Pretty:

    Everyone can say everything at once, right? So, you think about the classroom and the workshop where there's a group of people huddled around Post-its and a flip chart paper and they're still huddled in a way in their virtual huddle, but everybody can read, right? It's not that I'm not close enough, I can't read, I can't read your handwriting. There's this great equalizer is the online world. So, I think that's great. I think the challenge for the trains launched remotely is going to be do you ever get the face to face experience?

    Em Campbell-Pretty:

    Because if I go back over the years, one of the things we know is your first PI planning event sets the standard. So, people get this imprint in their heads of what is possible. For example, if you skip something in your first PI planning event, you just decide to, I don't know, skip the confidence vote or something weird like that, you don't do the roam of the risks or you just skip something, you never do it because you're successful without it.

    Nick Muldoon:

    It never gets picked up. Yeah, okay.

    Em Campbell-Pretty:

    You're successful without it. So, every compromise you make, and you make a series of compromises, and then you're successful despite those compromises, and that becomes a false positive feasibility. It tells you, yes, I was right. I was right.

    Nick Muldoon:

    I don't need to do that.

    Em Campbell-Pretty:

    I didn't need to do those things because I was awesomely successful and I didn't do these things. So, it's the learning [crosstalk 00:26:15]-

    Nick Muldoon:

    That's confirmation bias, is it?

    Em Campbell-Pretty:

    Yeah, that's it. That's the one. Confirmation bias. That's exactly it. Yep. Yeah, and I think there's going to be a bunch of confirmation bias in these remotely launched trains, and unless they're inside organizations where there's enough knowledge of SAFe and the physical PI planning to know that there's going to be value in bringing them together, but I can see that being a real challenge. I think trains that are launched online may never go into a physical PI planning event because of that confirmation bias.

    Nick Muldoon:

    All right.

    Em Campbell-Pretty:

    That makes me really sad.

    Nick Muldoon:

    I want to come back to something you said before about the leaders, and you mentioned the trust, the openness to learning and experimentation, and the discipline. I was going back over your SAFe Global 2018 talk about the seven traits of highly effective servant leaders.

    Em Campbell-Pretty:

    Yep.

    Nick Muldoon:

    Yeah?

    Em Campbell-Pretty:

    Yep.

    Nick Muldoon:

    I guess I had some questions about this, and obviously, these are four of the traits. What are the other three traits that I'm missing? Then I've got a followup question about some of the actual things that you talked about that you picked up in your trip.

    Em Campbell-Pretty:

    [inaudible 00:27:29] one of those four on the list I had in 2018.

    Nick Muldoon:

    I'll quiz you on it.

    Em Campbell-Pretty:

    How awkward. So, in 2018, the answer was people first, a respect for people, that sort of lens, lean thinking, manager, teacher, learner. So, we had that one. Yeah. Learner. [inaudible 00:28:00] crazy. What else did I have? [inaudible 00:28:10].

    Nick Muldoon:

    Yeah. Okay. I wanted to talk about that one, actually. I made a note about that. What is that, and are there examples of that in the West?

    Em Campbell-Pretty:

    A lot of people talk about true north.

    Nick Muldoon:

    [inaudible 00:28:28]. True north.

    Em Campbell-Pretty:

    Yeah. True north. The translation I got, which I got from Mr. [inaudible 00:28:39], who partnered with Katie Anderson for the lean study tour I did in, I don't know, '18, '17, '18, 2018, I think, so the translation he gave was direction and management sort of things. So, it's mission, right? It's strategic mission. It's that sort of thing.

    Nick Muldoon:

    So, just a sidebar here for anyone that hasn't seen Em's talk on this, there's a woman by the name of Katie Anderson. She runs an annual, I think, I guess not this year, but she runs an annual-

    Em Campbell-Pretty:

    No, not this year. She did not go this year.

    Nick Muldoon:

    ... not this year, runs an annual lean, Kanban, kaizen study tour to Japan and visits ... Who did you visit, Em? You visited with Katie. How many were in the crew that you went over there with?

    Em Campbell-Pretty:

    So, I think it was a group of about 20 from memory. Katie lived in Japan for two years and then went back to the US. She lives in San Francisco, I think. While she was there, she really liked the idea of putting together these lean study tours. She was already a lean practitioner more in the healthcare side of things. So, she got the opportunity to ... We actually were on a test run tour.

    Nick Muldoon:

    Oh, cool.

    Em Campbell-Pretty:

    So, this was her experiment. She had a relationship with Ohio State University and they brought some people to the table and she brought some people to the table and they made it happen. She also had an existing relationship with Mr. [inaudible 00:30:24], who was John [inaudible 00:30:26] first manager at Toyota. So, he's a 40 year Toyota veteran.

    Nick Muldoon:

    Veteran.

    Em Campbell-Pretty:

    He came with us for the week. So, we of course went to Toyota, but we went to a bunch of Toyota suppliers as well. Isuzu, [inaudible 00:30:43]. Then we also went to Japan Post, which was fascinating. We went to a city which name escapes me right now, but they called it 5S City because all the companies in that city practice the 5S, the manufacturing 5S.

    Nick Muldoon:

    Tell me about it. It's not coming to mind. I don't feel comfortable or familiar.

    Em Campbell-Pretty:

    You don't feel good about 5S?

    Nick Muldoon:

    No.

    Em Campbell-Pretty:

    No. That's not good. So, how would I ... The 5S is five Japanese words, which I'm going to go ... Yeah. My Japanese, nothing. But it's about standardized work. So, for example, when you go into the 5S factories, you'll see the floors marked up where you need to stand to do a particular job.

    Nick Muldoon:

    [crosstalk 00:31:41] This is what Paul Aikas picked up for his-

    Em Campbell-Pretty:

    Oh, no.

    Nick Muldoon:

    I feel like I've seen Paul Aikas' videos of their manufacturing in the US that everything's marked up.

    Em Campbell-Pretty:

    Yeah.

    Nick Muldoon:

    Okay.

    Em Campbell-Pretty:

    Probably. That would be my guess. We should ask Teddy.

    Nick Muldoon:

    We can ask Paul, and we can ask all these people. There's time.

    Em Campbell-Pretty:

    Well, yeah.

    Nick Muldoon:

    Okay.

    Em Campbell-Pretty:

    Okay.

    Nick Muldoon:

    So, that lean tour, the Japan study tour, that was a super effective and motivating thing for you?

    Em Campbell-Pretty:

    Yeah. For me, it was very reinforcing. So, I had I guess my own lens on what lean leadership meant, and I found that particular tour to be very reinforcing around the value set that I believe is part of that. Katie [inaudible 00:32:43] created [inaudible 00:32:44] that is designed to show you that. So, she's often very clear that says this is not Japan, right? This is not a reorganization into Japan. This is not every leader in Japan.

    Em Campbell-Pretty:

    This is, I've hand picked a series of lean leaders to show you it being practiced. But it was certainly very reinforcing for me. So, very similar messages I picked up in terms of how I like to head, how I coach others to lead was built into the messages that she delivered. So, it was very cool. It was very cool. Some of those leaders, just so inspiring, particular kaizen. I think the thing that just really hits you in the face as you're talking to these folks is kaizen, this drive to get better.

    Nick Muldoon:

    All the time.

    Em Campbell-Pretty:

    All the time. Absolutely. It's these folks looking for, they're looking for the one second, right?

    Nick Muldoon:

    Yeah.

    Em Campbell-Pretty:

    The one second improvements. There's a video that floats around. Have you seen the Formula 1 video-

    Nick Muldoon:

    Yeah.

    Em Campbell-Pretty:

    ... where they do, yeah, the changeover in 63 and it takes them over a minute and they do the changeover in 90-something in Melbourne and it takes them six seconds or whatever it is. It's like that, right? It's that how do I find one more second, half a second? They're just so driven. If I can remove a step that someone has to take, can I move something closer to somebody?

    Nick Muldoon:

    Yeah. There was some comment in the presentation that you gave. There was some comment about if I have to take another five steps, that's an extra 10 seconds. Then that's an extra 10 seconds every time I do this activity every day, and that all adds up. So, how do we shave these seconds off and be more effective and deliberate about how we do this?

    Em Campbell-Pretty:

    That was just huge, right? I called it kaizen crazy in the presentation. I'm just so, so driven to improve, and just tiny, small improvements every day.

    Nick Muldoon:

    So, one of the other practices that I didn't grok out of that talk was about the Bus Stop. What was the Bus Stop about?

    Em Campbell-Pretty:

    Was that in that talk? Really?

    Nick Muldoon:

    I'm forcing you to stretch your mind [crosstalk 00:34:57].

    Em Campbell-Pretty:

    You are. You are. You are. You are quite right. It really was [inaudible 00:35:01]. Okay. Oh, you're awful.

    Nick Muldoon:

    Yes.

    Em Campbell-Pretty:

    Yes. Yes, you are. Okay. So, effective leaders are human was the tagline on that one. It was really about leaders being down to Earth and being one with the teams. So, things I saw in Japan, this factory run by a woman, [inaudible 00:35:42], I think it was, so very unusual. Not a lot of women leaders in Japan. Her husband took her name because [inaudible 00:35:52]. It's a really interesting character.

    Em Campbell-Pretty:

    But her company has a bunch of morning rituals. You always say good morning and thank you and how they talk every day and everybody talks and everyone interacts. Then one of the other places we went to, they all had their uniforms they wore in the factory. But everybody wore the uniform, right? The CEO, the office workers, and everybody wore the uniform. Everyone was one.

    Em Campbell-Pretty:

    Then I was thinking about my experience leading teams, and a lifetime ago, I was working with a team that decided to enter a corporate competition. This competition was about showing your colors and showing the corporate values, which were things like better together and courage, and then [inaudible 00:36:49] a rainbow thing. So, this team decides what they're going to do, is it an address up in the rainbow colors, and they're going to be better together and show their courage and they're going to do the Macarena and they're going to video it and that's going to be how they're going to win this competition.

    Em Campbell-Pretty:

    I did not participate in this Macarena because someone has to take photos and stuff, right? How else are they going to enter the competition? So, had to do my bit. Anyway, we also had this ritual, which was about teams bringing challenges to leadership to resolve, and they did at the end of every spring. So, they do this Macarena and they film it and they enter the competition and at the end of the spring, they bring their challenges to leadership.

    Em Campbell-Pretty:

    Their challenge is Em did not do the Macarena. You are our leader, you did not do the Macarena. We are feeling very challenged by that, and we're bringing this to you to resolve. So, I went and spoke to the team that raised and said, "Look. I got to tell you. I don't know the Macarena. So, sorry." I still remember this so clearly. One of the guys said to me, "I read this blog about the importance of leaders being vulnerable." You know who wrote that blog post, don't you?

    Nick Muldoon:

    Oh, Em. Oh. You have it.

    Em Campbell-Pretty:

    So, we negotiated. I said, "Look. I think I can manage the Bus Stop." For those not from Australia, we grow up doing this in high school dances. In my part of the world, anyway. So, I grabbed my leadership team and we did do the Bus Stop and it was part of proving that we too were the same as everybody else and doing our bit and responding to the team's feedback. So, yes. That is where the Bus Stop fits in. Thanks so much for that, Nick.

    Nick Muldoon:

    Okay. No, I appreciate that. Now, I'm glad that I got that context. I try and do similar things. Typically, it's a karaoke or something, or that we haven't done that in a while. Yeah, okay. So, I guess the thrust of that talk was really about to leaders to serve, and it was all about being in service of. It sounds like what you took from the Japan study tour was these leaders there were very much in service of their people.

    Em Campbell-Pretty:

    Absolutely.

    Nick Muldoon:

    Do you see that as a trait that is prevalent in the best performing companies that you deal with, and how likely are they over a five, 10 year horizon, whatever that happens to be, to outperform their competitors or to be more successful in their market? Or I guess however they define success?

    Em Campbell-Pretty:

    I certainly see a correlation between leaders that like to serve and/or choose to serve and success with scaled agile, and business, because I guess we have seen over, it's close to 10 years, is those who practice together, your framework with discipline get results, and they get significant results. They improve their ability to deliver products and services, their cost base goes down, their quality goes up, their people are happier, their attrition goes down. We see it every single time.

    Em Campbell-Pretty:

    What we also see is when the leaders don't walk the talk, when the leaders are paying lip service to the transformation, it doesn't stick. They don't get the results. People don't find it a better place to work. People aren't bought into the change. So, there is definitely a correlation there. You can get pockets of wonderfulness inside an organization.

    Em Campbell-Pretty:

    We often observe that the organization that's transformation is as successful is the most bought in leader. Most senior bought in leader. So, if you're the leader of a train and you show the right behaviors, your train will be really great.

    Nick Muldoon:

    Successful.

    Em Campbell-Pretty:

    But that means nothing for the broader organization, solution train, the business unit, what have you. You see this thing that goes from the leader. If the leader's showing the right behaviors, you get within that space, you get the behaviors, you get the change, you get the results. But leaders who say one thing and do another, people don't buy it, right?

    Nick Muldoon:

    I guess this is true of any organizational change, isn't it?

    Em Campbell-Pretty:

    Yeah.

    Nick Muldoon:

    You hit the boundaries of your pocket, as you said, within the organization and then you meet the real world, the rest of the organization. People, maybe they don't have enough energy or they don't feel that they can influence and change that, and so they just live within their bubble because they don't feel that they can exert the pressure outside of that.

    Em Campbell-Pretty:

    Yeah. Look. I've certainly, I've seen successful bubble influence organizations. Successful bubbles can become interesting. Chip and Dan Heath's book, which one was it, Switch.

    Nick Muldoon:

    Oh, yeah. Switch. Yeah.

    Em Campbell-Pretty:

    [inaudible 00:42:02]. Shine a light on bright spot or something like that. So, bright spots inspire, and if you can create a bubble in an organization that outperforms the rest of the organization, or even if it performs better than it has previously, then everybody looks. Right? How did the organization that goes from poor delivery to great deliveries is what is going on here? That inspires others to get interested. One of the really interesting things we've seen in Australia, we can trace pretty much every SAFe implementation in Australia back to the one at Telstra.

    Nick Muldoon:

    Yeah, right. They all spun off from that, from the people that were part of it.

    Em Campbell-Pretty:

    Well, no. People who came and saw it. People who were inspired by it.

    Nick Muldoon:

    They're not necessarily directly involved in it.

    Em Campbell-Pretty:

    No. People came and got inspired by it, and then they went, did their thing, and then they inspired someone else. I haven't tried to do it recently, but there was a point in time we just could web together all of them because we could count them when we could see them. But we can web together most of them still. It says you saw someone who saw someone who saw someone who actually was someone who went to visit us at Telstra back in 2012, 2013 and got inspired.

    Em Campbell-Pretty:

    So, that bright spot can be really, really powerful, and that's what it takes, right? You get to add a little bit of noise, a little bit of difference, and people start to ask what's going on. I wouldn't say it's foolproof. I think it still requires, so someone's got to come, they've got to see, and then they've got to have the courage to do it for their part of the organization.

    Em Campbell-Pretty:

    That's the hard bit, right? I can come, I can see, I can get inspired. But am I prepared to put myself out there? There's a lot to be said for leaders who are prepared to take risks. That was one of the-

    Nick Muldoon:

    This was your lesson about the Bus Stop, right? You have to put yourself out there and be vulnerable.

    Em Campbell-Pretty:

    Yeah. Absolutely. Absolutely. This was actually, I was thinking, was the thing I was talking about at last year's SAFe Summit was be safe or be SAFe.

    Nick Muldoon:

    Be safe or be SAFe. Tell me about that.

    Em Campbell-Pretty:

    So, be safe, don't take a risk, or be SAFe, as in the scaled agile framework, and take that leap of faith. It comes back to, we started talking today about when I did this at Telstra, I didn't really understand that this wasn't a normal everyday, this is what everybody did sort of thing. It was a very new thing. So, I took a risk from a perspective that I was a business leader in a technology space and I really felt I had nothing to lose.

    Em Campbell-Pretty:

    So, I look back and that and go, "What on Earth possessed me?" And I go, "Well, I'm this business person leading this technology team. I wasn't supposed to succeed anyway."

    Nick Muldoon:

    Put it all on the line, right?

    Em Campbell-Pretty:

    I found out later they actually had a plan for when I did not succeed. I was supposed to fail.

    Nick Muldoon:

    Wait. How much waste is that? Why did they plan for something before it was ... Okay.

    Em Campbell-Pretty:

    Organizational policies. What can I tell you? Anyway, I did not fail. I did succeed, and because I took some crazy, calculated risks, and I've seen it time and time again, right? So many of these leaders in these companies that make this change are taking a leap of faith. I'm always saying I can't tell you exactly what's going to happen. I don't know whether you're going to get 10% cost out or 50% cost out. I don't know if your people are going to be 10% happier or 50% happier. I don't know that.

    Em Campbell-Pretty:

    What I do know is if you listen to what we're telling you and you follow the guidance and you behave in line with those lean and agile values, you will get results. You'll get results every single time. But you've got to be brave enough to buy in and take it on holistically and not do this thing where you manage to customize your way out of actually doing the thing-

    Nick Muldoon:

    Doing anything.

    Em Campbell-Pretty:

    ... that you wanted to do.

    Nick Muldoon:

    Yeah. Okay. Em, this was awesome. Before we finish up, I want to take two minutes. You've mentioned books a lot today and you reminded me of this quote, Verne Harnish, "Those who read and don't are only marginally better off than those who can't." So, today so far, you've mentioned Chip and Dan Heath with Switch, you've mentioned the Leffingwell series from the late noughties. There might have been a few others. But tell me, what are you reading today? You've been in lockdown. What are the two or three top books that you've read since you've been in lockdown in Melbourne?

    Em Campbell-Pretty:

    Oh, my goodness. It's very awkward. Every time someone asks me, "What did you just read?" I go, "I don't know."

    Nick Muldoon:

    I don't think I remember.

    Em Campbell-Pretty:

    Can't remember. It's terrible. What am I reading? I need to open my Kindle. I don't know what I'm reading. Geoffrey Moore, Zone to Win.

    Nick Muldoon:

    Zone to Win.

    Em Campbell-Pretty:

    Zone to Win. I think that's what it's called. It's a newer book. I know this year, because obviously, I've read The Build Trap this year-

    Nick Muldoon:

    Yep. Melissa Perry. You mentioned that one. Yeah.

    Em Campbell-Pretty:

    Yep. I've read the Project to Product, Mik Kersten.

    Nick Muldoon:

    What was that one, Project to Product?

    Em Campbell-Pretty:

    Yeah. Project to Product, Mik Kersten. One of the IT Revolution press books. So, released just over a year ago. Very tied up in the SAFe 5.0 [crosstalk 00:48:21]. The other book tied up in the SAFe 5.0 release is John Kotter's Accelerate. So, I picked that back up. I read it a number of years ago when it first came out. But I like to revisit stuff when SAFe puts it front and center. Seems to make some sense to do that at that point in time.

    Nick Muldoon:

    Yeah, okay. It's interesting that, thinking about Verne Harnish, the scaling up framework, no relation to-

    Em Campbell-Pretty:

    No.

    Nick Muldoon:

    ... scaled agile, for anyone that's not familiar. But so much of the scaling up framework about scaling businesses, they draw on so much content from existing offers, existing tomes, points of reference and experience, and it's super valuable, and I guess SAFe is no different, right? It draws on this wisdom of the collective wisdom.

    Em Campbell-Pretty:

    Absolutely. Absolutely. [inaudible 00:49:14] It was very fun to say in the early days, we stand on the shoulders of giants, a quote from somebody else whose name escapes me.

    Nick Muldoon:

    Yeah, okay. Well, Em, look. I wanted to thank you so much for your time this morning. This has been fantastic.

    Em Campbell-Pretty:

    No worries. It's great to catch up with you.

    Nick Muldoon:

    Yeah. I guess my takeaways from this, I like the be safe or be SAFe, like either be safe and don't take any risks, or be SAFe and actually put yourself out there and step into scaled agile. I definitely have to go and do a bit of research on the five S's as well and learn a bit more about that. But thank you so much for your time. I really appreciate it.

    Em Campbell-Pretty:

    No worries, Nick. Great to see you.

  • Podcast

    Easy Agile Podcast Ep.5 Andrew Malak, Chief Product Officer at Spaceship

    Teagan Harbridge

    "I really enjoyed my conversation with Andrew Malak. We talk integrating agile techniques and tips on how to achieve a culture of accountability"

    Andrew is a firm believer that the customer trusts your business by joining, and you have an obligation to repay that trust by helping them achieve their outcomes.

    Enjoy the episode!

    Transcript

    Teagan Harbridge:

    Welcome to another episode of the Easy Agile Podcast. I'm Teagan, head of product here at Easy Agile. And we've got a really exciting guest on the show today, Andrew Malak from Spaceship. He's the chief product officer. Andrew is a true believer in creating products and experiences that solve customer problems. He believes that the customer trusts your business by joining, and you have an obligation to repay that trust by helping them achieve their outcomes. In his current role, Andrew aims to help people take control of their wealth from a young age, educating good money habits and helping people invest where the world is going. Andrew is a family man who loves his time with his wife and children. And believe it or not, he uses agile techniques in his personal and professional life. Andrew is an economics geek. He plays and coaches soccer, football. He's a big Liverpool supporter, loves to travel, loves amazing architecture, and loves working with children.

    Teagan Harbridge:

    There were so many takeaways from my chat with Andrew that I really struggled to pair it down to three. But if you say tuned, here are some of the things that you're going to learn from our chat with Andrew. Why we should stop using the term agile transformation and start calling it an agile evolution. Why it's important to be open-minded to our own limitations so to break the old mindset of protecting original scope. And tips on how to achieve a culture of accountability. So I hope you enjoy. Andrew, can you tell me a little bit about Spaceship?

    Andrew Malak:

    Oh, fantastic. Well, thank you very much for, first of all, having me, Teagan. Spaceship is a business that's on a journey to make good money habits and investing accessible to all people. So what we look for is trends to do with industries or companies who are building the future of both industry or economies. We invest in them for the longterm, we break down barriers of entry for people, we give them a fee-free product under $5,000, no minimum investments. It's really easy to sign up. You simply download an app and you sign up and make one product selection decision, and you're done. You can start investing on autopilot. We allow you to also invest your superannuation in a not too dissimilar way.

    Teagan Harbridge:

    So tell me a little bit about who your target customer is, then. Because it seems like you're trying to make something quite complicated accessible for maybe first time investors.

    Andrew Malak:

    Well, you're absolutely right. There's a niche segment of people out there at the moment, millennials or even gen Zs, that we just don't think have been well serviced by the incumbents. And what we're trying to do is resonate with these young people as much as possible. We're trying to reduce industry jargon and really make things simple to them, because investing doesn't have to be complex. It's really about a lot of discipline around, if I can manage my personal P&L, or money in, money out, then I can create a cash buffer that can go into my assets column on my balance sheet. That's really what we're trying to do. And that kind of language, if we can get it right, can really simplify things that have typically been in the hands of financial advisors and accountants and give it back to everyday Australians who are starting out in their investment journey.

    Teagan Harbridge:

    Yeah, awesome. And you've been on quite a journey before landing in the FinTech space as the Spaceship CPO. So can you tell me and our audience a little bit about what that journey has looked like?

    Andrew Malak:

    Oh, where do I start? If you asked a graduate Andrew Malak what he'd be doing now, I don't think I would've been speaking about this because at that point in time in my career I didn't know this space would actually be around, if that makes sense. So I'll go back to my younger years, and I always thought I was going to be an architect. I had this fascination with bridges and I wanted to design things and see them come to life. And let's just say that I do that in different ways right now, but I started out working in CommSec on the trading floor. I moved on to work as a business analyst, and that's where I started my critical thinking into how businesses work and how things can be made more efficient.

    Andrew Malak:

    I dabbled in teaching for a little bit, I taught high school economics and religion for a little bit. And then I eventually landed in a product role at St. George Bank prior to the merger with Westpac. At that point in time, the light bulb really came on. I realized, "Hey, I like creating things. I like to change things. I don't like to just do things," if that makes sense. And that wondering mind that doesn't like the conform was finally let loose, if that makes sense. And I haven't stopped enjoying it. I loved my time at Westpac, made lots of friends, worked on really cool, successful projects, and implemented lots of things that had great results. Worked on lots of things that have failed miserably and learnt a lot out of that. And when the opportunity at Spaceship started to surface late last year, it was just too good an opportunity to not really come in and have a go. So yeah, it's been quite the journey.

    Teagan Harbridge:

    Yeah, wow. And I love a good failure story. And you said you've had lots. Can you think, just off the top of your head, what one of those big failures has been?

    Andrew Malak:

    Where do I start? I think our first attempt at taking a digital experience to allow customers to acquire a product online was quite a failure that taught us a lot. We basically took the systems that our back office staff used and just made it available to customers. And the real good learning out of that is there was a lot of traffic and a lot of demand, but not enough completion ever. And the best learning that came out of that... This is back in 2006, so internet speeds were just starting to pick up. Broadband was starting to go mainstream and customers' trust around doing more transactions that used personally identifiable data was starting to normalize at that point in time. Up until then, people quite reserved thinking, "I'm going to lose my personal data," et cetera. So when we decided to do that, we saw that there was a lot of demand but we quickly came to the realization that we used to train staff for four to six weeks on how to use the systems before they knew how to service customers using them.

    Andrew Malak:

    But then we've deployed it into production for customers to self-service and realized quite quickly that the experience for customers had to be much more guided than the experience for a staff member. This is where the evolution of usability or design thinking started to come in. We started thinking of, "Well, how do we make these things so easy that a first-time user can go end to end and not encounter friction?" And this is where our understanding of design principles, customer testing using verbatim and anguage that can resonate with a first-time user becomes critical to the execution. It's not just good systems but it's good user experience sitting on top of systems.

    Andrew Malak:

    That's probably the one that resonates with me the most because I've held that to a very high regard throughout my whole career. Now everything I do I think of, "Where's the friction? How do we make sure there's no friction? What's the customer going to feel throughout this experience? How are we creating unnecessary anxiety in that experience for the customer, and how do we move that away? How do we become more transparent but still be simple?" And yeah, that's probably the one that resonates the most.

    Teagan Harbridge:

    Seems like a tremendous learning opportunity early enough in that project and something that's stuck with you since, so great learning opportunity.

    Andrew Malak:

    Absolutely.

    Teagan Harbridge:

    We've got a ton of customers who are at all stages of their agile transformations, and I know that this is something that you've had experience with if we go back to your St. George, Westpac days. Can you give our audience any tips or stories that you encountered when you were going through those agile transformations? What lessons can you share with our audience?

    Andrew Malak:

    Oh, I have lots of lessons to share, actually.

    Teagan Harbridge:

    This is what I love.

    Andrew Malak:

    Look, I like to position it more as agile evolution more than agile transformation because no matter what you try to do, you're not just going to drop waterfall and become agile next morning. Honestly, I've seen so many attempts and every single time I see that the graduality of the change is a better predictability of the final outcome that you're going to land. So ultimately the Holy Grail that everyone's aspiring to is that, as a leader, you can rock up to a team stand up unexpected and then, without being told who is in what role, who the product owner is, who the engineer is, who the QC is, who the designer is, it becomes hard for you as the leader to work out who's who because at that point in time the team is so well converged on customer outcomes that they will self-organize themselves around what each person needs to do.

    Andrew Malak:

    And most of the language being used is really around, what are we trying to define the customer? What's the best thing to do within the capacity that we have to deliver this feature to market as quickly as possible, capture value for the customer and the business as much as possible? This takes a long time to get to, where you can start normalizing to a standardized, common set of goals, common cadence, and common ways of working. And I think it's ultimately about how much empowerment you can give people and how much as a leader you can relegate yourself in the background to allow them to work it out themselves as long as you're coming in and nudging things along the way and helping people course correct along the way. So the good news is that I actually think at Spaceship, we're pretty close to getting there.

    Andrew Malak:

    We have been running scrum and we have been running sprints for a long time, but it has been largely ceremonials. But over the last quarter, we've done a really good job at embedding more cross-functional people into these teams. But the goal for us is that now we feel like our throughput has actually increased and that the constant flow of information between the teams is becoming more natural and there is actually less ambiguity between the teams around, "All right, we built it this way. The API is no longer consumable. It doesn't fit what we're trying to do from our front-end and there's less back and forth." So we can really see that the amount of friction between persons in the team is really starting to reduce dramatically and we're starting to see that throughput really increase. Having said that, the best way to go about an agile transformation is just get started.

    Andrew Malak:

    You can sit and plan out things and plan towards utopia as much as you want or you can actually just get going. So when I say by get going, I say you have to start by getting buy-in from all the leaders of the different cross-functional teams, because if you don't have that buy-in at the leadership level, it's just not going to work because there's going to be blockers, there's going to be escalations. And if all these things result in conversations around, "Should we keep doing this?" Or, "Hey, maybe this is not the right thing to do." That needs to be off the table really early on and it needs to be a total commitment at the leadership level that we're going to make this work and whatever we encounter we're just going to fix forward. Once you have that commitment at the leadership level, you need to very clearly define the values that the team is going to be handed to work with, because agile itself, it's not a process, it's a set of values that the team needs to just take and start working with.

    Andrew Malak:

    So we could go and rattle individuals and interactions over processes and tools or working software over comprehensive documentation. Well, give these to the team and they're going to say to you at day one, "We can't go to all of that straight away." So they might actually say that day one, "We're still going to need some documentation because we're not comfortable yet. We don't understand the language of the other people in the scrum team well enough to be able to go and actually code off the back of a conversation." But by the 10th sprint, the 20th sprint, that misunderstanding of what the product owner wants or what the designer is trying to achieve in an experience starts to become embedded in the mind of the engineer.

    Andrew Malak:

    The engineer understands the customer a lot more, and then you can make do with less process and less documentation and less negotiated outcomes and more commonality across the team. The other thing that then starts to kick in at that stage is that ability of the team to pivot in response to a change and not see that as a threat to what they're trying to achieve. The old ways of working was, define that scope, protect that scope, and not let things disturb that scope, whereas if you're halfway through a project and you get some really good information that tells you that maybe you are not on track to achieve a good outcome, you should be welcoming that. And the team itself in the beginning is going to find that an irritation, but over time they'll become more comfortable with pivoting off the back of new information.

    Teagan Harbridge:

    Yeah. It's a big mindset shift. I was just having a discussion today about, where does being agile and being reactive, where's that line in the middle. And when does taking information and pivoting because you think something will be better, when can we break that mindset of, "Oh, we're just being reactive?" No, we're being responsive.

    Andrew Malak:

    Yeah, yeah. And look, I think the word reactive itself naturally has a negative connotation to it, but agility in mindset allows you to flip that on its head and say that no one can work things out in totality to 100% of what's possible, so being open-minded to our own limitations first and foremost allows us to acknowledge that when new information comes in, it is because we didn't think through the solution 100%, but let's also be okay with that because no one can. So I think it's flipping on its head and acknowledging it upfront and saying that this is going to happen, but when it comes we will assess the information we have with the capacity we have with how far progressive we are and make a decision that's right for us, for the customer, and for what's possible.

    Andrew Malak:

    So I take it as the more information you get along the way, the more reinforcement of, are you doing what's right or should you pivot and change at that point in time? The other thing that happens really early on is that if you as a leader can create a really clear vision around customer outcomes and establish your first cross-functional team and hand over that vision to the team, it becomes theirs. Don't hand over the backlog to the team. Don't give them a ready backlog, just give them the vision and then tell them, "You guys work out what your backlog looks like." When they come up with their own backlog, as long as you as a leader don't see that it's just a list of Hail Marys in it and there is a fair bit in there that is well spread out between hygiene things, strategic things, and a few moonshots and the balance is right, if the team has come up with their own backlog, the motivation they have to build their own ideas just goes through the roof.

    Andrew Malak:

    And that's what you want to achieve. You want to achieve clarity that the work fits with the vision and the motivation that you get out of the backlog being created by the team itself gets you that throughput enhancement. The other thing that you're going to struggle with really early on is chunking things down to fitting within the sprint cadence. I think that's one that's often been my biggest challenge when moving towards agile practices early on. Typically in the first few sprints, you always have overruns and things don't complete in the sprint because we end up thinking we can do more than we can and it takes us a while to work out, in wrapping up something that becomes shippable in a sprint, you probably take a little bit less in that sprint because you've got to test it or you've got to do a release in that sprint, or you're going to do a PIR in that sprint, or you're going to do a lot of retros in that sprint. Start to sort of formulate what you're going to take through the next planning cycle.

    Andrew Malak:

    So you've got to budget to that capacity, and I'll find that teams underestimate the magnitude of that work. So be okay with that. Overruns in the first few sprints don't mean you've failed, it means you're learning how to plan better. And then make sure your retros and your pivot off the back of that into your next planning sessions is taking information that is now new to you, and making sure you're working with it. I think as the leader, though, you have to set the expectations that teams can make mistakes and that it's a safe environment.

    Andrew Malak:

    And I've seen many agile... I was about to use the word transformation, even though I've just said I don't believe in transformation. Any teams that are adopting agile principles expecting that in their first few sprints they don't have any hiccups, and that if throughput falls in the first few sprints, then there's a bit of a, "Oh, well you told me this thing was going to increase our throughput." Yeah, but not straight away. So I think just being realistic with yourself and what's possible, and that shift in itself, until it normalizes, takes a bit of getting used to. The teams need to know it's a safe environment, that if their productivity suffers, if they make mistakes or if they break things, it's going to be okay. We'll fix forward.

    Andrew Malak:

    But then also there comes a point in time where we have to be very clear about the culture of accountability around using that capacity really well. So what I've found, that the best use of that is the showcase. And what we've done at Spaceship, because we're trying to reduce the amount of ceremonies, we've combined both the planning playback in a sprint as well as the showcase into the same ceremony. So what we do is we play back what we built last session using a demonstration of working software and comparing the amount of work we've executed versus what was planned in the previous sprint. We're saying we've got 80%, 90% through the work and this is what it looks and feels like, and this is what we're deploying to the customer. Then we actually showcase what we plan to do in the next sprint.

    Andrew Malak:

    And that's part of the showcase, is our hand on heart commitment to, "This is what we as a team are committed to doing in the next sprint." And then that accountability to the organization becomes something that keeps us on track throughout the sprint. As distractors or things that are not committed in the sprint come our way, we quickly think about, all right, can we accommodate these things? Do they need to be done? Are they going to take us off track with what is planned? Are they important enough? Is it a major defect of production, and can customers no longer access our app? Well, drop what you're doing and attend to that. Otherwise, if it's not material, keep focused on the work that you've committed to in front of the organization.

    Andrew Malak:

    After this you're going to start to experience some growing pain, and the growing pain is good because it means that agile is working and more teams or more feature opportunities become possible for the business. There's going to be a lot more hype around moving to agile. Other teams are going to come across and say, "Oh, how do we piggyback off what you're doing?" Et cetera. This is good. This is good, but what it means now is that some new risks are going to actually start to be introduced. Working with common code, common dependencies, or even common people being needed to be doing multiple things just means that you now need more coordination. I'd say to anyone who reaches this point in time, this is where people feel compelled to start introducing some new roles, coordination roles. And I'd just say, be careful because that can start add to your overhead really quickly.

    Andrew Malak:

    I find the best way to ensure that teams continue to be in sync is with the right dialogue at the right level with the right rhythm. And this is where I think keeping it simple to just the scrum of scrums works really well. I like the scrum of scrums to be balanced between both product owner and tech lead from each team being present, and a cadence of one to two times per week works really well. And as long as the product owners across the teams and the tech leads across the teams know what the other teams are working on, know what could impact their own work from a release perspective or scheduling perspective or an environment perspective, I think that tends to work really well as well.

    Teagan Harbridge:

    Yeah, wow. Lots of nuggets in there and certainly things that resonate with our experience here at Easy Agile, being a small company that's grown really quickly. So I can definitely relate. We've had conversations about, do we introduce new roles into this company? We've introduced a new cadence of meeting rhythms only the last couple of months, so we're going through these things too.

    Andrew Malak:

    Absolutely. Absolutely. What have been your biggest learnings so far?

    Teagan Harbridge:

    I think that you cannot underestimate communication, and it really does come back to that cadence and that rhythm with the team. And we're experimenting at the moment with a daily huddle where we're talking about, how do we embed showcases more regularly in our cycles? We've got a big demo at the end of the cycle. How can we make that a more ingrained part of our culture? And it really does come back to that culture of accountability as well. So yep, it's all resonating.

    Andrew Malak:

    Yeah, absolutely. Look, you can go to whatever industry you want but the problems are usually similar. And the great thing is that having these conversations is very important to fast-tracking your way forward, because your problem is not unique to you. Someone else has seen it in someone else has figured out a way. And I think what I like about the FinTech industry is that we compete on products and services, but there's a lot to learn from each other. And even if you just go outside of FinTech, there's a lot to learn from other industries who have adopted agile practices.

    Teagan Harbridge:

    If we take a bit of a flip, we've gone from your professional career and your experience into a more personal level. You mentioned that you use agile techniques outside of work. So I'm not sure if many others are in the same boat, but can you elaborate on this? What does that mean? What does that look like?

    Andrew Malak:

    Okay, I hope you don't think I'm extremely weird. We actually have a family campaign. So I guess if I go back to how we've come to actually doing this. Becoming parents, we would look at our children and see so many things that we want them to be better at. And in trying to give them constant feedback, which felt like the feedback was so much that it's all being drowned out because there's so much of it. In fact, my oldest son actually gave me that feedback. He goes, "Dad, why don't we focus on one thing at a time?"

    Andrew Malak:

    And I was like, "Wow, okay." For a ten-year-old to tell me that, that was amazing. So we came to realize that we needed to narrow and focus on one improvement area at a time, and we don't move on to the next one until we've actually closed out the first one. For example, my oldest son, very clever boy. We're trying to focus with him on the discipline of process over just getting the answer right, because he is clever and nine times out of 10, ask him a question, he's got the answer and he just wants to say it.

    Andrew Malak:

    But we've started to try to break down the question and work more on the process with him so that in following the process, coupled with his natural ability, we will get more answers right more often. And that's what we're working through at the moment. So our family's scrum wall at the moment has a mix of things on it. Everyone has their own swim lane, and in each swim lane there are a few tasks, some related work or study, some relating to household chores, some related to health or exercise, and some related to acts of kindness. And what we aim to do is make sure that we're moving things across in all four categories every single day. So yeah, you can use agility wherever you'd like but I think that mindset in general, that if I wake up every day and do things that make me better than I was yesterday, then I'll get to keep moving forward in my personal life as well as my professional life.

    Teagan Harbridge:

    And do you have WIP limits?

    Andrew Malak:

    We don't at the moment, and we're not doing showcases at the moment. We'll see how we can introduce them in the future.

    Teagan Harbridge:

    And how was the introduction of a Kanban board at home? How was that received by the family? Have they enjoyed it, has there been any feedback?

    Andrew Malak:

    Well, it wasn't actually planned. It started by just sticking some Post-its up on the fridge to remind us of stuff. And then one day I said to my wife, "You know what? This reminds me of what we do at work. Why don't we formalize it?" She had a bit of a chuckle but then one day she came back and then she found it there. So yeah, it wasn't really planned.

    Teagan Harbridge:

    Awesome. And you've already been super generous with your time so I'll close it out with one final question. What advice do you wish someone would have given you when you took the leap from product management into product leadership?

    Andrew Malak:

    Yeah, that's a really good question. I think first and foremost, that you've got to make sure that you drop your need for perfectionism, because first and foremost, you might have been the best product manager yourself. You might have been amazing. And I'm not saying I was, but if you were and you step up in leadership role, you're going to have people of different abilities working for you. And what you need to understand is that they're going to need some time learning their role and learning their trade. And just don't get in the way of them learn. So for example, you might see someone doing something that may not be the best or most optimal use of that capacity in that sprint. You might feel the urge to jump in and course correct. But if you let them go and just hear their feedback post the retro, they might've had that learning themselves, and a learning that they get for themselves rather than being told by their leader is going to be much more useful for them.

    Andrew Malak:

    You have to drop your need to make decisions and be in control because, again, the more you can relegate yourself to a servant leadership role and let the team make decisions, when they make decisions and now have to go back up that decision with execution, they're more likely to put their heart and soul into it. The more they feel like you are going to make the decisions, the less inclined they are to think through problems themselves, and then they'll keep bringing the problems back to you. So every time someone asks you a question that has a black and white answer, throw it back to them and ask them what they think, because that way you're coaching them to work it out themselves. And then the last thing that's really important is, I feel like it's really important to think through how your organization allows you to be different and take advantage of that differentiation.

    Andrew Malak:

    So for example, at Spaceship here, because we're small, we're not a large corporate, our customers are a little bit more forgiving. So you have a limited capacity to build experiences and you can't do all things at the same time. Understand that and take advantage of it, and get your team to also learn that. Because if you're trying to how the all edge cases, it will take a lot longer to get something to market and you might use a lot of the team's capacity to build edge cases. And you can't really afford that when you're in a start-up.

    Andrew Malak:

    So for example, we launched a new investment portfolio yesterday. We launched the Spaceship Earth portfolio, our first sustainable investment portfolio and it's a sign of more things to come hopefully in the sustainability space. But in launching that, we knew that we have a limitation in our experience or our product set today where each customer can only have one portfolio. We knew that existing customers would want to invest in sustainable investing, but our commitment to them is that it's in our backlog and it's actually the next feature that we're actually going to take to market.

    Andrew Malak:

    And in explaining that to our customers, they've been very understanding, that they know our throughput is limited but they also know that their voice is being heard and we are building the things that they're telling us about. So I would say that the best piece of advice to tell my young self is to make sure that you get the balance right between the voice of the customer. That's going to tell you all the hygiene things that your product lacks in terms of experience or gaps. And then get the balance between new strategic things that you can go after and new things that you can take to market, as well as a few Hail Marys every now and again. We call them moonshots. They may or may not work, but it's exciting, and if it works, can 10X your volume. And they are the things that are likely to go viral. So getting the balance right is very important.

    Teagan Harbridge:

    It's been wonderful, Andrew. I've definitely taken a lot away from our chat today, and I'm sure our audience will too. So thank you again so much for your time, and good luck.

    Andrew Malak:

    No Teagan, look, thank you very much. And it's been a pleasure speaking to yourself and Easy Agile, and I wish you guys all the best too.

    Teagan Harbridge:

    Awesome. Thanks Andrew.

    Andrew Malak:

    Have a good afternoon.

  • Podcast

    Easy Agile Podcast Ep.31 The Release Train Engineer + SAFe Summit 23

    "Lieschen's wealth of experience is absolutely incredible! Not only did she provide invaluable advice, but I thoroughly enjoyed our conversation."

    In this episode Caitlin Mackie is joined by Lieschen Gargano Sr, Release Train Engineer at Scaled Agile. They delve into the role of the Release Train Engineer, sharing tips and tricks, FLOW activities, lessons learned and how to get started in the role. With SAFe Summit 2023 just around the corner, Lieschen also takes some time to talk about what she’s most excited about for the event and shared some advice for first time attendees.

    If Lieschen's expertise and passion have piqued your interest, be sure to explore the Scaled Agile RTE course. It provides comprehensive training, equipping you with the necessary skills and knowledge to excel as an RTE.

    Scaled Agile RTE course

    We hope you enjoy the episode!

    Transcript:

    Caitlin Mackie:

    Hi there. Welcome to the Easy Agile Podcast. I'm Caitlin, your host for today's episode. At Easy Agile we specialize in developing apps for Atlassian Jira that help your team move from simply doing agile to truly being agile. Our apps have gained recognition and trust from over 160,000 users across top companies worldwide. With our products, teams can transform their flat Jira backlogs into something visually meaningful and easy to understand. Whether it's sprint planning, retrospectives, or PI planning, our apps are designed to foster seamless team alignment.

    Before we begin the episode, we would like to say an acknowledgement of country. This is part of our ongoing commitment towards reconciliation. Easy Agile would like to acknowledge the traditional custodians of the land from which we broadcast today. We pay our respects to elders past, present, and emerging, and extend that same respect to all Aboriginal Torres Strait Islander and First Nations people joining us today. Let's jump into today's episode. So today I'm joined by Lieschen Gargano, a senior release train engineer at Scaled Agile. Lieschen is a highly experienced professional when it comes to change management, system design and stakeholder engagement, and has a passion for developing teams and connecting strategy to execution. Lieschen welcome to the Easy Agile Podcast.

    Lieschen Gargano:

    Thank you. I'm happy to be here.

    Caitlin Mackie:

    So Lieschen, you are a release train engineer. For our listeners, can you explain a little bit about the role? For anyone that's not familiar, how would you describe a Release Train Engineer?

    Lieschen Gargano:

    Yeah. I think one of the easiest ways for people to think of a Release Train Engineer is kind of like a coach or scrum master for the art, for the Agile release train. A servant leader facilitating all of those art events, facilitating the processes and process improvements. And really measured in value delivery, and using flow metrics to measure those improvements and support of the arts.

    Caitlin Mackie:

    So you mentioned flow metrics there. I've heard a lot about this recently and optimizing flow. What are some of those flow activities that a RT is responsible for?

    Lieschen Gargano:

    I like to look at feature flow and cycle time. So really looking like are we bringing all of our features in progress at once or are we managing our WIP, not just at the team level but at the art level. Are we taking the whole PI to get a feature through the system, or are we able to finish something before we start the next thing? So I look at that a lot and also just are we making and meeting commitments. Those PI objectives that we set, are we in that 80-100% range? A lot of people want full credit, extra credit and to be in the 120, but for us, predictability really means you tried really hard and you stretched, but you also still made and met commitments. So I look at that really closely too.

    Caitlin Mackie:

    I love that. You mentioned just then quite a lot of different responsibilities that a RTE has. Do you think that there is one in particular that you really need to get right from the start?

    Lieschen Gargano:

    Oh, as an RTE, I think the biggest thing is building the relationships and intention. As a servant leader, we really are there to help make the art better, to make being on the art enjoyable and productive and flow. So building that trust and those relationships as a servant leader is the first thing. If you get that wrong, no one will help you do the rest.

    Caitlin Mackie:

    Yeah-

    Lieschen Gargano:

    And you need a lot of help. You're not doing anything alone as an RTE.

    Caitlin Mackie:

    Yes. Yeah, for sure. I can definitely imagine that. Let's go a little bit deeper on that servant leadership that you just mentioned. Can you share your approach and what servant leadership means to you?

    Lieschen Gargano:

    Servant leadership to me is helping people understand the direction, communicating early and often so that they know where you're going. And then not just saying, "how can I help you get there? What can I do?" But saying, "how can we go together?" A lot of coaching and understanding the problem to solve and connecting it to how it benefits the people. Just like we ask them to connect their work to how it benefits the customer. As the RT, they're my customer. How does what I'm asking you to change benefit you? Not changing is always easier than changing even if we don't like our current state. So why is it worth it?

    Caitlin Mackie:

    I love that. Yeah, always asking the why and being really clear on it. Yeah, I think that's great. I've done some LinkedIn digging of your profile, as you do, had a little bit of a stalk and noticed that you hosted a webinar recently on tips and tricks and lessons learned as an RTE. Can we start with maybe some tips and tricks? What can you share?

    Lieschen Gargano:

    The first thing I will say is lean on the Scrum master team, and if you're lucky enough to have an Agile coach or another RTE, lean on that team. Your lean Agile Center of Excellence, those people have the expertise. They're also building the relationships. They're there to help you. Don't try to just prove yourself or go it alone, it's not possible. That team is your team for success. So 100% go to them. They're a wealth of knowledge, a wealth of relationships, and the best support.

    Caitlin Mackie:

    Yeah, I know it's so important to have that support network around you. You just mentioned the Agile Center of Excellence. Maybe for some of our listeners aren't familiar, could you explain what that is?

    Lieschen Gargano:

    Yeah, so the Lean Agile Center of Excellence can look a few different ways depending on your organization. At our organization, it is the coach, release managers, RTEs and Scrum masters or team coaches. And some larger organizations than ours might have that hub and spoke model of a centralized change leader. And then RTEs and Scrum masters that are in different arts and around the org. And some even have separate laces in different parts of the organization if it's really big. But really they are that community of practice that holds your lean Agile practices and the standards of those practices and talks to each other and debates and evolves them to make sure that it's consistent throughout the org. That the org is getting consistent coaching, consistent guidance, and they're not being told five different things about how to transform. Because again, change and being lean is so hard. If you add too many voices into that coaching, it gets really overwhelming for folks.

    Caitlin Mackie:

    Yes, 100%. And an Agile transformation is already overwhelming as it is, so you can imagine that laid on top. I suppose speaking, if we explore a little bit around those on an agile transformation journey, at what point would you say it's important that that lean Agile Center of Excellence is formed?

    Lieschen Gargano:

    Oh, I think it should be in place pretty quick. I mean, we talk about training your leaders, training your experts and then doing safer teams and launching trains. You need that Center of Excellence there from the start so that they can go out to the rest of the org that they can do all that training and they can be there to support people through title changes, role changes. Launching an art can feel very scary to folks. If you don't have that in place beforehand, you're going to have a lot to reel in after the fact.

    Caitlin Mackie:

    Yeah, I really like that. It's almost having this really solid foundation and unified voice to sort of go forward and support the rest of the org.

    Lieschen Gargano:

    And it's so great to have consultants support, to have partners come in and help you and to have the right tools, but they need the help of people inside. They need that lean Agile Center of Excellence of employees inside the company to help you be successful. As an RTE, you need your team. Anybody, any tool, any people trying to do a change, a transformation are going to need that Center of Excellence because all those parts, that's what makes the whole.

    Caitlin Mackie:

    Yeah, yeah, definitely. So you mentioned as an RTE, a big tip or trick is to rely on that lean Agile Center of Excellence. What do you think has been your biggest lesson learned as an RT?

    Lieschen Gargano:

    There are a few things that have been particularly difficult for me. One of them is that I don't like to say no and not in that I take on too much or whatever, but more in that if someone has passion for something, I want them to be able to take it on. I want them to be able to move forward with it. And there are times where we really have to say it's too much change. It's too much for this group to manage. In particular, the Scrum Masters and RTEs people come to us for a lot of things and they need that consistency from us, and they need predictability in a change to feel like we know where they're going and if we introduce too many things or if we try to hold too many things at once, it's easy for us to forget about it later or drop something else. So learning when and how to say no, again not necessarily in that capacity way, but just in the width of change, if that makes sense.

    Caitlin Mackie:

    Yeah, definitely. I think that what you just said there, learning how and when to say no. I think that's not even exclusive to the RTE role as well. I think that's an amazing piece of advice for anyone listening and to share across our audiences, because I know it's definitely something I struggle with as well. So that's my takeaway from this is to, okay, I'm going to constantly imagine like 'no Lieschen told me to when and how to say no', and just focus on that. So yeah, I think that's a great piece of advice. What was your journey like to an RTE? I know we caught up last week and I got a little sneak preview into this, and I know it wasn't straightforward, so if you can share a little bit about that, that would be great.

    Lieschen Gargano:

    Yeah. I actually started in conflict resolution. I worked in public private reconciliation doing a lot of natural resources facilitation, so hundreds of people, governments, companies, private landowners, residents, trying to bring all those people together to get to consensus or at least to build relationships that allow them to move forward. So really strong foundation and facilitation in particular, and just day-to-day conflict. When we say conflict, we get so worried, 'oh, I don't do conflict', well conflict's everything all the time. It's all the disagreements we need to succeed in life. So that gave me a great foundation when I became a scrum master, and I did that for a few years working with development teams. One of my favorite teams was our infrastructure team, 10 foot pole because no one wanted to touch their work or the 10 foot pole, and I learned so much there and eventually became a coach and started doing more strategic planning and coaching parts of the organization that weren't used to being on arts. Marketing and other groups, which helped me transition to Scaled Agile, where I started working with our CMO and as he grew the marketing team, helping coach that marketing group into an agile way of working, a safe way of working, before actually becoming a product owner, because I loved organizing around value, and I loved those different topics that we were working on internally.

    And one of the people I work with at Scale Agile said, "well, help us develop the product then for everybody else". So I did that for a little while, which gave me so much power in that learning how to say no and prioritize and coaching people to decisions is one thing, but as the product owner, I had to practice being where the buck stopped. There are five right decisions, just make one so that people are unblocked, and that prepared me really well for transitioning into RT.

    Caitlin Mackie:

    Yeah. You have such a wealth of experience there across so many different roles, and you can really see that each of those key roles have taught you something valuable that you can take into this RTE role. So I think that's amazing. It's so cool to see that even though it's not this straightforward linear journey, there's all these parts that there's traits within each that ladder up to helping you succeed as an RT. So I think that's really cool.

    Lieschen Gargano:

    And I know people are afraid to make some of those lateral moves sometimes, but the skills that you can build might just be that thing that gets you other open doors that you didn't even think about.

    Caitlin Mackie:

    Yeah. Yeah. I absolutely love that. Yeah, just embrace every opportunity for what it may be, what it may not be. You don't know until you give it a shot. So I think, yeah, I love that. I think that's really great advice. So everything we've spoken about in regards to being a Release Train Engineer may have really hit the spot for some of our listeners. How does someone get there? Were there certifications, courses? What's the process that way?

    Lieschen Gargano:

    Another thing I probably did backwards. I started with a scrum master cert and then actually ended up getting a SPC certification through Scaled Agile when I was a coach. Because I was a coach before I was an RTE, and I learned about so many other parts of the business that way. But then to become an actual RTE, taking the safe RTE course, but then actually there's a community of RTEs... Which we didn't really talk about this, but being an RTE is a lonely thing. I said earlier, if you're lucky to have another RTE, this is a lonely role. You're really kind of on your own. So not just getting that cert, but being part of that community and being able to send people messages and ask them crazy questions was part of my certification process, but also just community building to where I could feel like I had the connections and competence. So yeah, I found all of them similar to holding each of the roles, also getting that certification, just another tool in the tool belt.

    Caitlin Mackie:

    Yeah, for sure. I don't want to touch on something you said there about an RTE being sometimes quite a lonely role. What do you think makes it lonely?

    Lieschen Gargano:

    It's a role that a lot of people have strong opinions about what they need and what success looks like based on where they are in the organization. And there are usually few of you, and even if you're in a large organization with many, you're with your art, you're very focused on your section, and so having all of those pulls and expectations and not having anyone who understands what that feels like just makes it kind of lonely. Now that we have two RTEs and a coach at Scaled Agile, it makes a big difference for me because they are right there in it with me and it's very helpful.

    Caitlin Mackie:

    Yeah. You can see in that scenario why that community of RTEs is like you said, so important to lean on them as well. Yeah.

    Lieschen Gargano:

    I find even just connecting to RT's outside our organization too. I grabbed beers with one a couple weeks ago. Those little things, even if you can find that person, meet them at a summit, meet them out in the wild, find them on LinkedIn and just say, "Hey, we live in the same area. We have the same role". It can go a long way because it may seem weird to reach out like that, but they probably are looking for that connection too.

    Caitlin Mackie:

    Thank you so much for sharing. And for any of our listeners, I might pop some links to any certifications and some scout Agile courses. I'll pop that in our episode notes, so feel free to check those out. You mentioned about connecting with other RTs and meeting at summits, which is a really nice segue to the next part of our conversation. Just around the corner is the 2023 Safe Summit and we're heading to Nashville Music City. What can we expect from Safe Summit? What are you looking forward to?

    Lieschen Gargano:

    Well, what I'm most looking forward to is that I am putting together an RTE breakfast. So all RTEs are welcome, or even if you're a solution train engineer or you do the role of an RTE with a different title. I'm really excited to meet with those folks over breakfast and just chat it out. And my goal with that really is to have people to connect with so that as we go through the rest of the summit, listening to the talks that we have people enroll, that we can check back in with over drinks and stuff on the later days and say, 'oh, what do you think? How might that work?' So that's what I'm most looking forward to.

    Caitlin Mackie:

    Amazing.

    Lieschen Gargano:

    But obviously there are going to be some great talks and the product labs are always really fun. We get to play with the product together.

    Caitlin Mackie:

    Yeah, cool. Tell me a little bit about the product labs, what's involved in that?

    Lieschen Gargano:

    The product team puts it together and they have computers set up and you can bring your own and they talk through some of the new releases or things they're working on and help you log into it and use it in your context, but also try to get some feedback on how it works or how you might use it in your organization. So it's a nice two-way street. It's sort of, 'I need this, how might I do it?' And then them saying, 'well, why don't you try and let me see how it works and how we should change it based on how you interact with it'. So it's just really fun. It feels really practical because it's so hands on.

    Caitlin Mackie:

    Yeah, amazing. I love that. I'm definitely going to have to try and come along and suss that out. It sounds really great. Where do you hope or where do you think we'll see a lot of conversations focused at this year's Safe Summit?

    Lieschen Gargano:

    At Safe Summit I think the conversations will be really focused on just the day-to-day of Safe. We have new topics that come up. We obviously have new ideas that are going to be presented. But every time I go to one of these, it really is the connecting one-on-one to say, here's where I'm stuck, here's what I'm trying to learn. So we'll hear a lot about Flow, we'll hear about Team Topologies, but we'll also hear those 'I'm just getting started and we're stuck, we have change fatigue. We don't know if our arts are set up correctly'. A lot of those classic conversations that are just really impactful and why people come together.

    Caitlin Mackie:

    Yeah, definitely. Yeah, I love that. Creating these spaces for people to bond over shared experiences and problems they're facing or wins they're seeing and sharing them. I think that's where these events are amazing for creating that kind of environment. Lieschen, this is my very first Safe Summit. I haven't been to one before and I'm really excited. What advice would you have for first time attendees, returning attendees, what's the way to get the most out of Safe Summit?

    Lieschen Gargano:

    If you're attending with other people from your organization, the best thing is to split up so you can cover more ground and then come back together and share. The second advice is find people with a similar role as you, because again, you can do that same thing with those folks and split up and then meet up again and try to talk about it in your context. It's great to do that at the parties too, because we throw great parties, but that's the best because no matter what room you end up in, what talk you end up at, you're going to get a great nugget. But where it really sinks in for me is talking with someone else about what I heard and then thinking about, 'okay what does that mean?', when I go home.

    Caitlin Mackie:

    Amazing, great advice Lieschen. If anyone listening happens to also be attending Safe Summit and they see Lieschen on the floor or myself, make sure you say hello, and if you've got any questions for Lieschen about the podcast episode, I'm sure she'll be more than happy to answer and engage in a great conversation. And anyone looking to get advice around the RTE role, make sure you find her and have a chat. Lieschen I'm really excited to meet in person. We've done this podcast with yourself in the States, myself in Australia, so I'm excited to connect over in your world. And yeah, really thank you so much for your time. I hope you enjoyed the episode. I know, I sure did.

    Lieschen Gargano:

    I did. Thank you.

    Caitlin Mackie:

    Thanks, Lieschen.