No items found.

Easy Agile Podcast Ep.11 Dave Elkan & Nick Muldoon on building Easy Agile

Listen on
Subscribe to our newsletter

On this episode of The Easy Agile Podcast, join Nick Muldoon and Dave Elkan, Co-CEO's and Co Founders of Easy Agile. As they look forward to the next phase of growth for the company, they wanted to take this opportunity to reflect on their journey so far.

Nick and Dave talk growing a start-up in regional Australia, finding the right people, sustaining a positive team culture and the importance of having values driven teams.

"Our purpose is to help teams be agile and in doing that, we're doing that for ourselves, we're constantly trying to learn and adapt and experiment with new things. I hope that was a useful little tidbit and journey from Dave and I on how we got Easy Agile to this point."

- Nick Muldoon, Co-CEO, Easy Agile

"There's these funny little hacks and analogies and I think that's a longterm vision thing. If you are running a business which doesn't have that longterm vision and purpose, then you can go actually in multiple directions at once, and you're not going to make any progress."

- Dave Elkan, Co-CEO, Easy Agile

Be sure to subscribe, enjoy the episode 🎧

Transcript

Nick Muldoon:

Good day, folks. Nick Muldoon with co-founder, co-CEO of Easy Agile, Dave Elkan. Before we kick off, we'd just like to do an acknowledgement to the traditional custodians of the land on which we broadcast and record today, the Wodiwodi people of the Dharawal Nation. We pay our respects to elders, past and present, and extend that same respect to any of our aboriginal folks that are listening today.

Nick Muldoon:

Dave, just a bit of a reflection on five and a half years of business?

Dave Elkan:

Business? Yeah, a rollercoaster. It's been great fun.

Nick Muldoon:

It is a rollercoaster, isn't it? I guess, where's the best place to start? The best place to start is at the start.

Dave Elkan:

Yeah, I mean we can go before the start. There's always a good prequel. We can do a prequel episode later, I guess. But I guess the earliest I remember working with you, Nick, was at Level 15 at Kent Street, at Atlassian. There was this redheaded guy down the one end of the building, working on Atlassian GreenHopper and I was busy working on the Kick-Ass team at the time, building the new issue navigator, which is now the old issue navigator, back in 2011. And then you screwed off to San Francisco and I followed eventually, and then we hung out there for a while, didn't we?

Nick Muldoon:

Yeah, I remember that because we sat down, I was back to get married, and we sat down and had a coffee and a yarn about you and Rin relocating to San Francisco and how it had been for Liz and I, and what the process was like and all that sort of stuff.

Dave Elkan:

That's a great opportunity to acknowledge our lives in this amazing journey as well and if it wasn't for those, we probably wouldn't have gone to San Francisco in the first place, because a large part of the promotion of going overseas and doing that for me anyway, and for yourself, I'm pretty sure.

Nick Muldoon:

Yeah. Well, Liz was this big conversation of go overseas and experience something new and I was quite comfortable in Sydney and enjoying my role with product management at Atlassian, but it was really a push to try and experience and do something a bit different.

Dave Elkan:

Absolutely, same here. And you were there for over four years, in San Francisco, and I was there for three. But you came home, you got married, and I just grabbed you for a coffee and we sat there in Martin Place and had a chat, and you said, "Yeah, it's great. Come over, you can stay with me for two weeks." And I'm like, "Oh, I barely know you."


Nick Muldoon:

Yeah, but it was so much. I mean, even not knowing Liz or I, it was way better than the alternative. So for folks listening in, the Atlassian apartment, at the time, was in a fairly rough part of The Tenderloin in San Francisco, and it probably wasn't the greatest introduction if someone was relocating to San Francisco.

Dave Elkan:

No. But to cut a long story, there's a lot of good stories here I'm sure we can tell one day, but eventually, we both had daughters in San Francisco and we wanted to be home and closer to family. Then we came home to Sydney and found that the traffic is 20% worse or 50% worse than when we left and we were uprooted. So once you've been uprooted, you've got to plant yourself back somewhere and it's quite easy to change at that point, and you've chosen to go outside of Sydney.

Nick Muldoon:

Yeah, this Wollongong regional lifestyle.

Dave Elkan:

Yeah, where you can have a full block of land to yourself without breaking the bank and you can, relatively speaking, like times have changed a bit in that space, but since then, that's what we were chasing, wasn't it? And we looked at Newcastle, and-

Nick Muldoon:

Looked at Newcastle, looked at Brisbane, Adelaide, we even went through Wagga Wagga. We had the most amazing Indian meal in Wagga Wagga, we were almost like, "This is the place. If we can get food like this in Wagga, we're sweet." Bit too cold, but we ended up settling on Wollongong, in large part because of the proximity to the beach and the Early Start Discovery Space for the kids and just a pretty cool, chill place to raise a family. There are aspects of it as well, I think, that really reminded Liz and I of San Francisco. We used to go to the farmers market down at the Ferry Building a lot on a Saturday morning, and we found the farmers market on a Friday in Wollongong on Crown Street North, so there were these similarities to kind of enable us to transfer from one city to the other fairly easily.

Dave Elkan:

Yeah. It's a pretty easy place to live and to be. The way I like turn it, is it's just far enough away from Sydney.

Nick Muldoon:

Yeah, a nice little national park in between.

Dave Elkan:

That's right, it can't really encroach on us, it's not allowed. You can't build there so you're always going to have that buffer. But I do remember going back to Sydney for a niece's birthday and having been charged $9 an hour for parking at the beach, considering you don't even have a parking sticker anymore because I wasn't a resident, and I was like, "Wow, it's really expensive." But for anyone coming to Wollongong or the other way, you can park for free at the beach. That's just kind of like a good litmus test of the difference that we're talking about here.

Nick Muldoon:

Mm-hmm (affirmative). Yeah, I guess this regional life, like we didn't really have a tech industry here. We come from Sydney where, 10 years ago, there was this emerging tech scene and SydJS, SydCSS, other meetups up there, and in San Francisco we were thrust right in the middle of it. I remember, we were chatting the other week about a meetup where we met, the Ruby Creator at a Heroku meetup, I think it was, and a session on [detrace 00:06:17] at that company that's gone bust now, whose name I can't even remember, but we were in the heart of all the meetups in San Francisco. Then in Wollongong, there was none of it, and so it was like a question of what could we do to build a community here as well, try and meet other like minded folks?

Dave Elkan:

Yeah, it was definitely that desire, wasn't there? And we set out to do that, and I think it was Rin who termed it Siligong. I remember we were actually talking about Siligong Valley before we actually left, and we just decided to make that the name of the community. I was actually looking back on my old emails the other day and I was like, "Oh, we actually talked about Siligong before being in Wollongong," so that's pretty cool.

Nick Muldoon:

I remember early days because I think you and Rin returned on flight with [Umi 00:07:08], and Umi was six or eight weeks old.

Dave Elkan:

Yeah, October.

Nick Muldoon:

If I'm not mistaken, I dropped you at your mom's place so that you could catch up with your mom and Ken and that was kind of like home base. And it was a couple of months after that or something, where we finally had you down here. I think you stayed with Liz and I when you came down here-

Dave Elkan:

Yeah, again for two weeks.

Nick Muldoon:

... for another couple of weeks, and we were really talking about the genesis of what was, at the time, what was termed Arijea Products, and a brand that we never ended up sticking with. What do you remember about those early days and trying to get the business off the ground?

Dave Elkan:

Actually, come to think of it, you were staying in, not Coniston, [Carmila 00:07:59], it was actually less than two weeks because we all had little kids and it was just a bit crazy. So I think Rin and I organized... we came down and did inspections and we stayed with you whilst we're doing that, and then we were able to secure a place in Fairy Meadow and we moved down, so we were going back and forth a bit at that point. And then it was this six months of just literally... I didn't have a bike, I just walked to work, which is super new to me. I've always caught the bus or ridden my bike.

Dave Elkan:

Some of you may know I've never commuted to work and I hopefully will never have to do that, and we've engineered our lives around that kind of concept. But I think that it was really great, I was just living within two kilometers' walk of work, and that was for at least the first six months until I moved to Balgownie, but it was great time of my life and we had a brand new baby and just concentrating on the business, trying to [crosstalk 00:09:00]-

Nick Muldoon:

I remember, we really didn't have much of an idea of what we were doing in early days. We chased down one area and we said, "No, that's not appropriate," and then we kind of turned our attention to something else.

Dave Elkan:

Yeah. We were chasing our tails a little bit. We, at one point, had five products with two people.

Nick Muldoon:

That's right.

Dave Elkan:

I think that, that's too much, but with good conversations with the fellows around us at IXI, that we were able to have... like they were asking good questions and I remember Rob and Nathan asking us, "What is it you're good at?" And I think it was Rin, was like, "Okay, you've got this app idea, who're you going to market it to? Look at your networks." And it was, all those arrows started pointing towards Agile.

Nick Muldoon:

Yeah, I think it was this idea that Rin had like, "You can build it and they will come, or you can figure out your go-to market and your distribution piece, and what's the audience that you've already got, and how do you leverage the audience that you've already got in Agile Software Development to kind of seed and build that audience, and get some momentum?" And that's what really kicked us along and got us going. If I'm not mistaken, I think we'd actually... not that we had a lot of outgoings, but I think we were actually break-even by June of 2016, and it was kind of like this, "Hurray," moment because we were not going to have to get on the train and commute to Sydney for working at Atlassian or something like that. We'd found product-market fit and we could kind of pursue and go to the next stage.

Dave Elkan:

That's right, yeah. There's a lot in that story as well, like how we found product-market fit and the steps towards that and lots of learnings from that time as well, which is great to share eventually, I guess, but we might go down a rabbit hole if we jump into that one. But I certainly do remember good considered conversations that were held by lamingtons and tea in the Mike Codd building at the Innovation Campus at University of Wollongong, where we started. And that was really just a time to... it felt different to my prior, at the time 15 years of experience, where you actually, it's okay to stop and talk and think about what you're doing, whereas in the past, it's just been, "Go, go, go, build this thing." And it's like, "Oh, okay," so that was really refreshing for me and I think that, that was a really good step in opening up what became the story map, which was our first really successful product.

Nick Muldoon:

Mm-hmm (affirmative). You mentioned the lamingtons and tea, it was probably at least 50% of our time getting the business off the ground, was lamingtons and tea. It was chatting about stuff, it wasn't writing code, we didn't have customers to speak of. It was really trying to figure out what sort of market did we want to pursue, what solutions did we want to provide and what sort of business did we want to create? That was a large part of our time getting it off the ground.

Dave Elkan:

Absolutely. And for those listeners out there who don't know what a lamington is, it's actually a delicious piece of sponge cake dipped in chocolate sauce and then coconut, shredded coconut, so I know you can buy them in US, we actually did that at Atlassian and they were a huge success, especially because they had cream inside them as well, so real good for a cup of tea or coffee, whatever you take. But the thing is that it's a good idea to sit down with a co-founder and talk a lot more than you type, that's the kind of rule I took out of that.

Nick Muldoon:

It's interesting because it was kind of like that approach to talking instead of typing that was kind of like the genesis of one of our values, this engaged system, too. And I don't think you'd read Kahneman's book at that time, and that was something that came later, but even just this idea of, "Now, let's just take the time to think and process this sort of stuff," and the context [crosstalk 00:13:09]-

Dave Elkan:

No, I do remember. Sorry, yeah. I did a presentation at Lansing Summit in 2017 on Engaged System too.

Nick Muldoon:

16 or 17?

Dave Elkan:

16 or 17, I can't remember which one it is.

Nick Muldoon:

'16 because you went to Barcelona in '16.

Dave Elkan:

Barcelona, and that's what I did there, wasn't it? Yeah, so that was early on that I read Thinking, Fast and Slow, which I highly recommend.

Nick Muldoon:

And the context around this, for folks listening; in mid 2016, Dave had a nine month old daughter. My daughter was two years old and I had a newborn and you were to have... your number two was on the way, right? So we were building a business as we were starting and establishing our families as well, so it was, "Let's do it all," in a new city. Like, "Let's do it all at once."

Dave Elkan:

Yeah, you might as well, right? Just bite it all off and rip the Band-Aid off and get it done. I mean, my daughters were only 18 months apart, so that kind of... just get it over and done with. Get the hard part done and then you can go and enjoy yourself afterwards, just kidding. It's great to have lots of kids at a young age, like I really do miss that time. But yeah, we were pretty crazy, but we got through.

Nick Muldoon:

It gave us a constraint as well, didn't it? Because we couldn't burn the midnight oil, we couldn't flog ourselves from 05:00 AM to midnight because we simply did not have the energy and we had to get kids fed and bathed and off to bed and all that sort of stuff. So it brought a cadence and now that I reflect on that, there was another value that was kind of coming out of that, which was with respect to our balance and establishing balance in our lives.

Dave Elkan:

Yeah I do remember, sorry to interrupt, a tweet idea, I can probably dig it up, which was me hanging out cloth nappies or diapers on... it must've been, it was in Balgownie so that must've been after six months. But I was hanging out nappies and I must've been working from home that day or something like that, but that was just like me balancing life like that, with work. And I think it came back with like work, life, family balance or something like that. We would expand that to work life, family, community balance, is what we try and chase.

Nick Muldoon:

Mm-hmm (affirmative). How did we get on this journey around the values and kind of establishing the values? When was that in the life of the business?

Dave Elkan:

I can remember the place we were in, we were actually in our Crown Street office when we really sat down and really hunkered down into that, so that would've been 2018.

Nick Muldoon:

I think in November 2018, we held our first advanced Easy Agile, and that's where you ran the session, "What got us here won't get us there." And so at that point in time, we had the two products, we had Easy Agile User Story Maps and Easy Agile Roadmaps, and we had changed our brand from Arijea Products to Easy Agile, to kind of focus our energy on the Agile space. We divested the other three products that weren't focused on Agile, so we'd sold those off to another Atlassian Solution marketplace partner. I think that's where we started having these conversations around the next evolution of the growth of the business. Then it was in 2019 where we were back in Crown Street, back in the office, where we were having that conversation about codifying, establishing, writing down our values.

Dave Elkan:

That's right, and it's a highly valuable process to go through and to really just pause on the day to day, and really focus on it. That's something I've always had trouble with, like I've always got things to do, but once you just extract yourself from that process and zoom out and look at the company and what you've come up and what you hold dear, that's when you can really start having those conversations, but making it an actual thing. I think that you can't just do it on the side, you can't just do it as well as other things, it's really got to be like the priority as I like to say. Priority is not a plural, it doesn't make any sense if it's pluralized, but that should be the one thing you do in an ideal circumstance, like you just do it and really focus on it, because it's really hard.

Dave Elkan:

And it shouldn't, I guess not in one sitting, but at least when you do it, make it a serious thing because if they're real values and you live them, like they just are pretty immutable, they just keep moving forward with you. If you found you're not living them, then you should absolutely revisit them, but we've been lucky enough in that the values we put forward have stayed true and I really feel like, of all the companies I've worked at, even Atlassian, like these ones I've lived every day in very distinct ways.

Nick Muldoon:

Mm-hmm (affirmative). So what are the values we've got? We've talked about better with balance, and we talked about that a little bit. We also talked about engaged System 2 like this System 2 thinking. What are our values?

Dave Elkan:

Be the customer, give back, and [crosstalk 00:18:30]-

Nick Muldoon:

[crosstalk 00:18:30] was a big one, and commit to team. So better with balance, give back, be the customer, punch above our weight, Engaged System 2 and commit as a team. Go back to the conversation that we were having in 2017 around give back, that was something that was really System 2. How did we think about giving back to the community and what that meant to us as a company?

Dave Elkan:

I think it goes back to what you said before about the community in San Francisco we experienced and what we did here with Siligon and just making that a focal point for us to give back to the community. It doesn't build itself, like the community has to be actively built by somebody has to put their hand up and start it, and I think we did that. Since then, like we've enabled heaps of other people to be able to give back in a really easy kind of way like, "Let's host a meetup," "That's fine, here's our framework to go build that on." And also just the daily communication we have amongst each other on our Siligon Slack, which is just super valuable.

Nick Muldoon:


Super active, too.

Dave Elkan:

Oh, super active, especially in lockdown, lots of people on there talking about all sorts of things.

Nick Muldoon:

I think maybe one of the other things, so Dave and I experienced this at Atlassian, which was this idea of the Pledge 1%, but in our first or second year of Easy Agile, Atlassian along with Salesforce and a bunch of other companies came together to actually codify and build the foundation around Pledge 1% and ask other companies to commit to that. And we made that commitment in 2017 if I'm not mistaken, to do Pledge 1% donations and now, where I guess we're kind of doing Pledge 2% donations, but what was the drive behind our Pledge 1% to Room to Read?

Dave Elkan:

It's in part laziness, because I really want a system to these kinds of things and unfortunately, when you're starting a business it's hard to dedicate the time and to think about that. So I took the easy System 1 option, which is to go with what we experienced at Atlassian, which was to back Room to Read, which is a great initiative to help ensure that young ladies, specifically in third world countries, get at least a higher education, get out of primary school, get into high school, and once they've gotten to that point, it's far more likely they're going to be independent. And with that kind of thing, like that investment, it's like restarting at the beginning and enabling countries and people to help themselves. If they're educated, that's a huge step in the right direction to both fighting overpopulation, climate change, all these things which benefit from those people doing well in life.

Nick Muldoon:

Mm-hmm (affirmative). Yeah, continually improving their lot in life, right? Like raising standards of living through education.

Dave Elkan:

That's right.

Nick Muldoon:

And if we think about punching above our weight as one of these other things, I mean I remember that was something that we talked about before we wrote down our values, that was something that we really did focus a lot of energy on. You mentioned before, there were two of us and we had five products in the marketplace. I'm not exactly sure that was a great example of punching above our weight, because we might've struggled a bit, but what are some examples of where we've punched above our weight as a small team from regional Australia?

Dave Elkan:

One of our products that we built initially was really a bit of a thorn in my side, it was continually breaking and it wasn't playing to my strengths, which is traditionally front end development. So after that and getting burned by that and having to stay up all night and fix it, I opted towards apps which are more front end focused, and so we've built Easy Agile User Story Maps and Easy Agile programs and Easy Agile Roadmaps primarily as front end apps. As a matter of fact, Easy Agile Roadmaps, for the first two years, didn't even have a server, it was just a static file in a bucket in CloudFront. That's the way Atlassian Connect works, it allows you to host apps that way, and that really can't break, it's just providing a different view on Jira in essence, but architecturally, it's quite simple. So therefore, we could easily... that was a way of punching above our weight, which also allows better rebalance, so they're kind of complimentary in that respect. What other ideas [crosstalk 00:23:24]-

Nick Muldoon:

Yeah, if not much can go wrong, then you don't have to be on call, and you don't have to fix things out of hours, so you don't wake up blurry eyed and fat finger and have a bug the next day that compounds the problem.

Dave Elkan:

And if you take the analogy too far, like you could think punch above your weight is like being able to punch someone really hard and then knock them over, but this is more like just definitely, you're running around the big [fur 00:23:44]. You're not even engaging in babble, you're just sidestepping it. That's why we've run those products, and until recently, we actually do have servers now for them, and once again, it's still very simple, but they're very well monitored so if something does go wrong, that we're on top of that.

Nick Muldoon:

I think one of the other aspects with respect to technology in punch above our weight, is we've quite often... I think maybe you mentioned before, with respect to Room to Read and the give back, the laziness, but we are lazy in certain respects and we just want to automate things. And I remember the XKCD comic that you share, with what is the right time to automate something and when do you automate it to get the return on investment that you want? But I feel like we've made some fairly good decisions around when to automate things and even around how we provide customer support or the old test and deploy, toying around with products, we've done these things at pretty good times so that we can deliver products to a global audience of a couple of thousand customers, from Wollongong out of timezone with those customers.

Dave Elkan:

Yeah. It's also being ahead of the curve as well, so I think Inception Week, which is something we do every fifth week now, we give up one week to provide the team with the space to explore new things. Amazing things have come out of that, which otherwise, if you would just week to week, week to week, you would never actually realize, but when it comes to mind is our dev container, which is a docket container which contains all of the parts which are required to develop our apps. So you just check out this one repository, run a script and it sets up your entire develop environment. It's a great way for the team to share the tools that help them punch above their weight, so it's a huge punch above our weight thing and that came out of Inception Week. So I think Inception Week's a punch above thing, and also the dev container's a huge punch above thing.

Dave Elkan:


We used to have so many problems with individual versions of this or that on everyone's computer, and now that's just all gone, it's never happening again, it's never come back to bite us since, and I think it's an overwhelming success. Sure, it does need an all new RAM and all new CPU, but it does... we'll get there, like it's going to get better.

Nick Muldoon:

RAM and CPU are cheap, it's okay.

Dave Elkan:

You can never get time back, right?

Nick Muldoon:

Yeah, absolutely. So when we think about these things, how intentional do you think we were around the values in our approach to building and scaling a company versus things that just kind of happened?

Dave Elkan:

For a large part of the starting of the business, there was a lot of, "Just get it done," kind of mentality stuff, which has to happen. However, I want to hop back to when we started, everything was chaos. I remember this, early 2018, mid 2018, we'd come in on Monday, go, "What are we doing today? What's this week? Let's look at the backlog and have a look." And there was no forethought whatsoever.

Nick Muldoon:

And we'd kick a couple of things off the backlog and we'd just work through on that weekend. That was it, right?

Dave Elkan:

Yeah, pretty much. And so you proposed the idea, it was at the beginning of the year, it must've been 2018. Was it 2019? Either way, let's just do one week on clarity, which is our internal CI room, essentially, and just knock out a bunch of products and problems. That was the first time we started really focusing, because since we had so many products, I think we actually might've sold them by now at this point. Yeah, I think we definitely had. However [crosstalk 00:27:28]-

Nick Muldoon:

But we still had Roadmaps, Story Maps, Clarity Week, EACS, like we had other internal systems that we used and the team was actually growing beyond Dave and me, and it was growing. There was Jared and Satvik and Rob, and so the team was growing at that point in time as well. So it gave us the opportunity to put a number of people onto one problem for a period of time, like a week.

Dave Elkan:

That's right, and from that came this idea of focus, and we started doing focused sprints, so product focus sprints, which highlighted another terrible problem of run over, if you did run over in your estimates, then you would have to come back like in nine weeks or something and it was just [diabolical 00:28:12].


Nick Muldoon:

That's right.

Dave Elkan:

So we dropped [crosstalk 00:28:14]-

Nick Muldoon:

What did we do? We did two weeks on Story Maps, two weeks on Roadmaps, two weeks on internal systems, two weeks on something and then one week on Inception Week?

Dave Elkan:

Inception Week. Yeah, I think [crosstalk 00:28:26]-

Nick Muldoon:

I can't even remember now, what that other thing was.

Dave Elkan:

It was nine weeks in total, wasn't it?

Nick Muldoon:

Yeah.

Dave Elkan:

[crosstalk 00:28:31] Roadmaps-

Nick Muldoon:

If you missed it and you didn't ship it, then we went onto the next product and moved that forward, and then we'd come back to it.

Dave Elkan:

In ages away. And it was super stressful for the team and we quickly destroyed that, the week we went with a more flexible approach to it, where we dropped the hard mandate of you have to exchange products now, we let them run over a bit and then we'd adjust the story points to the next one, blah, blah, blah. And then eventually, I'm scratching my memory, but essentially, we got to a point where we introduced opportunities, which was based loosely on Shape Up by Basecamp and we took a bunch of things from that, but most things of that didn't really gel with our way of working and our values.

Nick Muldoon:

I mean that whole opportunity cycle, we've evolved three or four times now.

Dave Elkan:


And they were ideally just two or four weeks of work, and then we'd do Inception Week and Tech Debt week, and we have a dedicated Tech Debt week as a mandate. We dropped that since, and we've got to now we have four weeks of work, which includes Tech Debt and then we have Inception Week, and that's kind of cool, right? Like we still have this mandate of Inception week, not Tech Debt week. That's the last thing; I feel like the mandates... because it's like kick starting your motorbike, you've got to really give a good kick and that's essentially what we've been trying to do over the last three years, is like get this thing running. I think we've-

Nick Muldoon:

Built momentum.

Dave Elkan:

The engine is now running... yeah. The engine is now running and we're pulling the clutch out. It's just that the mandates slowly fall away and the team finds their own way, but I still feel that, that cycle is the most important thing, that five weeks where we stop, everyone knows what's happening. Because if it just runs off into the future forever, you can't compute that in your mind, but you can see forward five weeks and go, "I'm going to plan this work, it's not going to be done to a Nth degree because that's kind of a bit weird," it's just like, "Let's try and achieve this and let's bite off one bit at a time." Then we have a break with Inception Week, let our creative juices flow and then we'll come back to it the next round.

Nick Muldoon:

Right, so I have to call timeout here. So this is a sidebar for everyone listening at home; Dave just used this analogy of kick starting the motorcycle and then pulling the clutch out. So one of the things that Dave does tremendously well, is he grabs these analogies and he uses these analogies to simplify what I otherwise feel can be fairly complex kind of concepts, and simplify them and communicate them really nicely. That's not one I've heard before but there's a new one we can add to the repertoire, Dave. I love it.

Dave Elkan:

Thanks, mate.

Nick Muldoon:

What other sorts of things? Because I guess we're charting this journey over five and a half years, where it's gone from Dave and Nick and the addition of Satvik and Teagan and Jared and Rob and Brad, and a few people over time, to the point today where we are 27, 28 people. What are some of the other markers along the way, that we've kind of gone through, that have shifted or evolved how we operate? Like the Easy Agile operating system that we've talked about in the past.

Dave Elkan:

Well, it's something that we've just discussed in the execution kind of level. Obviously, every six months, everything just goes and explodes and you have to fix it, like there's always some major thing that happens every six months, and I feel like that's good and that's healthy, and that continue to run into those things. Either they're internal or external and I feel like we're dealing with an external one right now, which I don't really want to touch in this podcast, but I think that they're healthy for the business to adapt to. But certainly, I think in that time, like really understanding that it's the people that count, right?

Dave Elkan:

The business is in there, like it's a thing, but it's nothing without the people who worked for it, and it's in service of the people who work here, as well as the customers. And so that's something we've come out of it. What do you think, Nick? Like the cultural aspects of what we've built, what do you think stands out to you?

Nick Muldoon:

I certainly think there's these inflection points. I mean, I remember a conversation with Jared when we were in Crown Street Mall, and it was in 2019 and we were talking with the team around the kitchen table there, and we could get eight people around this kitchen table and we were talking about growing the team to take advantage of the opportunity and responding to requests from customers and all that sort of stuff. I think Jared said, "Well, I quite like it the way it is."

Nick Muldoon:

And then I fast forward to an interview with Jared, which went into the five year video that we saw just before Christmas and that was around his trajectory and how he's evolved and adapted professionally and personally along with the company. I think that's the story for all of us as team members, we've all kind of been on a journey together and we're all learning and adapting together. We do live, in many respects, we do live this Agile approach where we do reflect and we take the time and we think and we experiment with new approaches to getting work done.

Nick Muldoon:

Even, I think... and we've been talking about this a bit recently with respect to pace, that first version of our learning and development program, where we wanted to provide funding for people to go and pursue something that they wanted to learn about. But we got that out, "Hey, that was a morning's worth of work," we put out an L&D, people started using the L&D program, and we called it our Version one of our L&D program, and today we're on Version, I don't know, 1.4 or whatever it is, of our L&D program. There's a lot of things that have gone out and we tweak and we improve them over time to make them ever better and better suited, perhaps, to the current state of play within the team. Is that fair?

Dave Elkan:

Yeah, it is. It is, and I think that; A, I've never worked at a business who has anything like that, and where they actively encourage you to use it, spend the money, make yourself better. If you make yourself better, the team will get better, if the team gets better, the customers get better outcomes, and the company continues to improve, and it will be probably a better place for you to work in the future. So it's really a holistic kind of perspective, rather than, not narrow minded, but myopic or focused on just output. It's outcomes of output and I think that could be another value of ours, if we were to have seven, it'd be outcomes over output. So really stopping, having that permission to stop and think, and system to it and think about what it is you're trying to achieve, rather than just blindly doing stuff.


Dave Elkan:

So from a developer's perspective, the fastest code is the code that doesn't exist, and so if you can do something differently, which doesn't require 100 steps or just decide, "Hey, this is really tricky right now, this bit of code we're trying to work on or this feature is really hard. Can we just delete the feature?" And we did it on notice, I know that sounds pretty bold, but quite honestly, that kind of discussion is really healthy to have. I want to encourage the team to think that way and I think that learning development is also something you can do to bring people into it, look at their trajectory as a way of gauging their abilities, and giving them really... throwing fuel on the fire in that respect and seeing them ramp up in their ability, and help those around them.

Nick Muldoon:

Yeah, so take us through that, because that's something that we definitely talked about a few times, like when we've been looking at candidates and in a hiring huddle around candidates, we've talked about those that are on a certain trajectory and that we think that we can accelerate that trajectory. Where did that come from?

Dave Elkan:

Where do thoughts come from? I'm not sure, that's a good question. I couldn't tell you, but I think it's pretty obvious when you look at someone's CV and you see... now, there's nothing wrong with people who have long tenured positions, but if you talk to someone and they can't really say what they've done in the last 10 years and they've donned that one position for 10 years and they haven't really got anything striking they can tell about how they've made that better, that kind of says a lot about that person. Maybe they would come in and they'd just coast... they're a coaster, right? If they're coasting, that's fine, it's their call, but at the same time, we look for people who are actively trying to make their impact bigger through their work, help those around them. And you can see that, you can see, "Oh, look. They've been at the same company, that's fine, but they've gone and done these different roles or they've seen this kind of improvement in their approach."

Nick Muldoon:

This comes back down to that article, that Financial Review article, the mid-career annuity, so this was an article that we must've been kicking around in 2016, 2017, and it was around a Japanese term, mid-career annuity. You could have 20 years of experience in a role or you could have 20 first years of experience, and I think early on, and maybe it still occurs these days, I think it probably does, but it felt like we were getting 20 quarters of experience. Over that five year period, there was always some big, new challenge that we needed to learn and adapt and incorporate into the business over the first five years. So we were always learning and adapting, and we wanted folks that were on a similar journey and they were learning and incorporating and adapting and experimenting themselves.

Dave Elkan:

Yeah, it's something definitely, that can be learned, and I think that if you bring on new stars, they can just get that, this is what they do by default because you've put them into that environment. But some environments, especially older companies, can be fairly stagnant and static, so that just reflects on people's CVs. Either there's some kind of reason why the company won't give them a promotion or give them opportunities to chase, how we have a different approach where we throw too many opportunities at people, I think sometimes, and I've seen people using their L&D so much, it is actually impinging on their better with balance value. I'm like, "Whoa, this is fantastic but don't forget you've got kids and you've got to help look after them," and [crosstalk 00:39:41]-

Nick Muldoon:

Temper your enthusiasm, yeah.

Dave Elkan:

Yeah. So that's something to look for.

Nick Muldoon:

Stopping and reflecting on five and a half years, what's the purpose of the business, what's the goal over the next couple of years?

Dave Elkan:

Have fun, learn, what about you?

Nick Muldoon:

Definitely learning.

Dave Elkan:

Stay in business.

Nick Muldoon:

Oh, yeah. Stay in business, sustainable growth is always a good one. I think that's important. Yeah, I don't know, it's interesting. I feel like some days, it can be really fun and other days, it's not fun at all. That's probably due in large part, like when we started this, we were not in service of anyone but ourselves and one another, and now I feel like we are in service of a team of people that are themselves in service of the customer because we've got a couple of thousand of them. So it's the responsibility and the accountability's changed, and the way that fun comes about is, these days... it used to be fun to have lamingtons and chat, and these days, typically, there's someone else in the crew that is organizing the event that often participate in that I find fun and enjoyable with the rest of the team, rather than being able to carve out that time and do that.

Nick Muldoon:

I remember when we roped in a bunch of folks from iAccelerate and we went into town and we'd go into town and we'd go and we'd get a Laksa in town and we'd get a bowl of Laksa. It's been harder to do that in the past 12 months, given the global environment and all that sort of stuff, so hopefully we can find a bit more of that in 2022.

Dave Elkan:

And maybe ramen. There's ramen now.


Nick Muldoon:

Oh, and it's great, you know it.

Dave Elkan:

Yeah. I think refining what we do and continuing to think more about that, so specifically with the engineers, I like to use a goal based... goals are big at Easy Agile, I think you should talk a bit about goals, but we use them to help guide people in chasing down things they want to achieve, and we can align those things with what the business does to an extent. Then, you can actually go and achieve your professional and goals through the business and the business is the vehicle to do that, rather than having to it outside. That's really cool, like find that harmony there so both Easy Agile can succeed and the people who work here can succeed.

Dave Elkan:

I think it actually is quite difficult, like you go, "Hey, take a step back, think about what you want to achieve, give that to me, and then I'll see what I can do to change the course of the business to help you accomplish that. What can we do? Maybe there's a middle ground we can chase down together." And that's something new to me and I'm kind of using that instead of performance reviews so make sure you do your goals, people. [crosstalk 00:42:44]

Dave Elkan:

But yeah, also you've made sure, you want to look back in time and you want to see yourself in the future, reflecting with the team. When they've gone and moved on, [crosstalk 00:42:56]-

Nick Muldoon:

Oh, yeah. Absolutely. I was even chatting with Elizabeth Cranston this week and I was saying, "I can picture in the future, you're living down at Narooma down the coast and I can come down and have a cheese and biccies with the families and you're looking over the bay at Narooma or something, and we're reminiscing on this period of time at Easy Agile." I can totally see that. Yeah, I think it's great and I think just on the goals, the goals are important personally, and we've talked a lot about goals in the past, with respect to tenure vision for the families and that sort of stuff.

Nick Muldoon:

But it's also for the business, I remember we had okay hours in place from getting the business off the ground, we've revised them every year, we've learned and adapted a lot over the last couple of years in how we think about our objectives and our key results. And the fact that we write them on a quarterly basis and we review them on a quarterly basis, but we've got these objectives that align with a business goal that's three years out, and it all kind of flows. I mean, I think we're a lot more mature around that aspect of our... I don't know, would I say strategic planning? Vision goal setting over an extended time period? We're a lot more mature around that today than we were two or three years ago. That's really exciting as well. [crosstalk 00:44:33]

Nick Muldoon:


Come back to what you were saying before about the backlog. We'd come in on a Monday morning, and we go, "What are we going to work on this week?" And we kind of worked over a couple years, we worked it out so that, "Ah, here's the vision for the product." It was a longer term thing, and we've elevated that and it's not like, "Hey, what are we doing for the business this month?" It's now, "Here's our longterm trajectory for the business." We've been elevating that, that's pretty exciting, I think.

Dave Elkan:

And at the same time, trying to get the team to lift their line of sight as well.

Nick Muldoon:

Mm-hmm (affirmative), mm-hmm (affirmative).

Dave Elkan:

And look out further afield, but not too far. You want them to be looking at what's happening next week and next month as well, but also what's the goal, what are we chasing down? What's the bigger picture? And I think that's starting to happen.

Nick Muldoon:

What's the analogy there about golf, Dave?

Dave Elkan:

Oh. No, can you tell me? I can't remember.

Nick Muldoon:

It was this analogy about golf, like you've got to look where you're going to hit the ball and you've got to look up. You don't want to look at the tee, you want to look beyond the tee so that you... not beyond the tee, beyond the hole, sorry. You want to look beyond the hole.

Dave Elkan:

That wasn't my analogy, that's why I don't remember, but I do remember someone telling us that one. But it's a good one, like it wasn't even an analogy, isn't that the literal thing that the golf tutor would do? It's like, "Where are you looking?" And then they go, "Oh, I'm looking at the hole." "No, no, you've got to look further than the hole. Look up where you want the ball to go, and then away it goes."

Nick Muldoon:

Yeah, raise your sights.

Dave Elkan:

Raise your sights, yeah. And if you are looking at your feet, then you're probably not going to go far, but if you do look up and take stock, you can probably... that's actually a soccer analogy I can give you, like from my soccer coach, like you've got to point your toe where you want the ball to go. And that's just the magic thing, it just works. You just put your foot next to the ball with the pointing at the corner of the goal you want it to go in and you kick it, and then it just happens.


Dave Elkan:

There's these funny little hacks like that and I think that's a longterm vision thing. If you are running a business which doesn't have that longterm vision and purpose, then you can go actually in multiple directions at once, and you're not going to make any progress. I think a good analogy I read was like with a team, if you imagine all the team members are tied to a pole with a rubber band and they're all heading in different directions, the pole's not going to move because everyone's just... and the company's going to stay static and still. But if everyone just goes in the same direction, then it's going to move along.

Nick Muldoon:

Shift it, yeah.

Dave Elkan:

Yeah. And that's something that we've bitten off recently, is our purpose.

Nick Muldoon:

Mm-hmm (affirmative), to help teams be agile.

Dave Elkan:

Yeah. It's one of those funny moments when we we're talking about, and we talked about it, we set ourselves a deadline for the sake of a better word, like we had our planning session coming up in a couple of weeks, so we sat down and talked about it. And we went around and around in circles, trying to discover what it is, not to be agile, but just, what is Agile? And we know [inaudible 00:47:45], but we were trying to codify that in words. And when you said that, like it's being agile, it was kind of one of those... the way I like to describe it is, an upside down A-moment, which is our logo as you can see on Nick's jacket there.

Dave Elkan:

So when that was proposed to me, I was like, "No, that's so silly." But I was like, "Oh, but I love it." And I'm not saying that being agile is silly, but the fact that it's so simple, that's what I like about it, it's easy, it's simple, and there's a lot there if you dive into it.

Nick Muldoon:

Mm-hmm (affirmative). Yeah. Well, why don't we wrap it there? I think that's a good place to end.

Dave Elkan:

Yeah.

Nick Muldoon:

Our purpose is to help teams be agile and doing that, we're doing that for ourselves, we're constantly trying to learn and adapt and experiment with new things, being Easy Agile and as our team members here. So I hope that was a useful little tidbit and journey from Dave and I on how we got Easy Agile to this point, and some of the things that have been on our mind.

Dave Elkan:

Yeah.

Nick Muldoon:

Thank you, Dave.

Dave Elkan:

Thank you, Nick. That was fun.

Nick Muldoon:

That was fun. Oh, goody.

Related Episodes

  • Text Link

    Easy Agile Podcast Ep.19 Combining Ikigai and OKRs to help agile teams achieve great results

    In this episode, I was joined by Leandro Barreto - Lead Software Engineer at Miro.

    Leandro is responsible for helping engineering and product teams to be more productive through metrics and KPIs with a focus on increasing their operational efficiency. Before moving to Europe, Leandro worked for an Atlassian partner company in Brazil as Head of Technical Sales.

    In this episode, we spoke about;

    • Ikigai - what is it and how do you achieve it?
    • The benefits of OKRs
    • How can we combine agile, Ikigai and OKRs?
    • How Ikigai can help agile teams achieve great results and stay motivated

    I hope you enjoy today's episode as much as I did recording it.

    Transcript

    Robert O’Farrell:

    Welcome, everyone, to the Easy Agile Podcast. We have an episode today with Leandro Barreto who is a lead software engineer at Miro. I'm your host for today, Robert O'Farrel. I'm the Growth tech lead at Easy Agile. Before we kick off this podcast, I'd like to acknowledge the traditional custodians of the land from which we broadcast today, the people of the Duruwa-speaking country. We pay our respects to Elders past, present, and emerging and extend the same respect to all Aboriginal and Torres Islander, and First Nations people joining us today on the podcast.

    Robert O’Farrell:

    Leandro currently works as a lead software engineer at Miro where his responsibility is to help engineering and product teams to be more productive through metrics and KPIs with a focus on increasing their operational efficiency. Before moving to Europe, he worked for an Atlassian partner company in Brazil and acted as a head of technical sales with the mission to increase the service offers in Latin America. Welcome, Leandro. It's great to have you here today.

    Leandro Barreto:

    Yeah. Thanks, Rob. Thanks also for the Easy Agile for the invite. It's a pleasure to be here today.

    Robert O’Farrell:

    Fantastic. You're here to talk about Ikigai, objectives and key results or OKRs in Agile, so let's kick it off. Ikigai, what is it? Can you give us a brief or a long explanation of what it is?

    Leandro Barreto:

    Yeah, of course, of course. So, Ikigai I use it to say is a philosophy of life that means like a reason for being or the meaning of life. So, the world Ikigai originates from a village in Southern Japan, where the average life expectancy of people is over 100 years old. So, Ikigai is basically divided in four components. The first, things you love. Second, something that you are good at, then something that pays you well. And finally, something that the worlds need. So, when you put it all together, then you have the Ikigai, but this is not easy. So, let me explain a little bit of each of these companies.

    Leandro Barreto:

    So, the first thing is something that you love, something that makes you be present, something that you must ask yourself what do you really enjoy in doing? What makes you happy? What holds your intention that makes you lose time and forget about time? So, for example, reading, dancing, singing, painting, learning, teaching, et cetera. So, maybe it's a little bit difficult to answer right now, but understanding and seeking what you love must is fundamental so that you can have a healthy balance between learning, putting it in practice, testing, failing, trying again, and keep the circle repeating itself.

    Leandro Barreto:

    So, an example that I can give you is, for example, I had a jujitsu teacher that no matter the day, he was always training. And one day, I remember I got my arm hurt. And in the next day, I had a message from him like 6:00 in the morning, he was asking if I was okay. And I was waking up and he was texting me like, "Hey, are you okay? Are you going to be able to train today?" And I was like, "Whoa, take it easy, man." This is very funny because our class is 6:00 p.m. And he was punctually at the tatami or dojo. I don't know the English word for that.

    Robert O’Farrell:

    Yeah, dojo. We have dojo. Yeah.

    Leandro Barreto:

    Dojo. Awesome. Yeah. And he was always punctual. And after the classes, he always said that he wants to get home earlier after the classes because he has private classes. So, from morning to night, he always keeps training and you can see the passion in his eyes when he talks about jujitsu. "It's a passion for me". A little bit exaggerated.

    Robert O’Farrell:

    Something that definitely got him up in the morning and kept him going throughout the day to the late evening, by the sounds of it.

    Leandro Barreto:

    Exactly. Yes. And then, you have the second component, which is something that you are good at. Something that you can always improve with yourself. So, for example, what you are really good at. It's quite hard to answer, but what the people say is that I'm do... something correct or what they say something positive that what I do. So, for example, I remember the book Outliers by Malcolm Gladwell that says that usually, you have to spend 10,000 hours in something practicing to be good at.

    Leandro Barreto:

    So, don't take it as an obstacle but as a motivation to keep going, and understand this part of what you are good at. It's a good way to improve. And the third part is what pays you well? So, money is what... Some people say that "Hey, money don't bring... It's not... how can I say that?

    Robert O’Farrell:

    Money doesn't bring happiness?

    Leandro Barreto:

    Yeah, exactly. But it puts a roof in your head. It makes you provide a good life for your family. It makes you travel. It makes you have a hobby. So, according to Maslow, for example, one of the bases of human beings is to start thinking about security. So, we have to have this security in order we can improve as a person. So, money helps you to achieve it. Yeah. So, find something that makes your life as comfortable as you desire to, as you wish to. So, otherwise, you'll always be looking for something that you never had. So, for example, time.

    Leandro Barreto:

    So, you will spend so much time thinking how can you have more money? And here's the glitch, you will never be paid because you will be stuck on your daily basis thinking on how to get money instead of how to improve your skills to get money. Right? And then, you have the what the world needs. So, here, the idea is to find a proposal for what do you do and what is value to the society, your proposal. And sometimes it's quite difficult to find precisely because of the plurality of positions and responsibilities that we have nowadays. And even more today with the full expansion of technology that every month we have new positions to be filled by companies that needs different type of skills, soft skills and hard skills.

    Leandro Barreto:

    And here, the keyword is to serve. So, I will give a personal example. For example, one of the things that I missed most when I was a young teenager was having someone who could help me to explore the technology so I can get a job. So, it was in the early 2000 and it was quite hard.

    Robert O’Farrell:

    Yes, very much so.

    Leandro Barreto:

    The internet is starting, everything is new.

    Robert O’Farrell:

    People on dial-up, internet was slow.

    Leandro Barreto:

    Do you remember that sound like prshh?

    Robert O’Farrell:

    Oh, yeah. It comes to me in my dreams I think. I heard it so many times in that era.

    Leandro Barreto:

    My family and my friends, they wasn't in the IT field. So, there is no one to help me that. So, I had to learn it by myself. Seems impossible. But it took me time to learn it and enter in a company with a good position let's say that gives me money and the possibility to learn much more faster. So, since 2013, I dedicate part of my time to teach young people, acting as a mentor to help them enter in this market so they can learn new skills. I can open paths for them, put in contact with the right people, people which is going to be important for them, and all aiming to accelerate their dev development and giving them the opportunity.

    Leandro Barreto:

    And this for me is very meaningful because I'm helping those who don't have any references also, and sometimes don't have a chance. And the more I serve them, the more I earn and I grow with them. So, I came across like when I was introduced to Ikigai for example, another personal example.

    Robert O’Farrell:

    Sorry. Before we get to that, just reiterating. So, the four components, so there's something that you really lose time in doing, something that you get into the flow of doing very easily. And then, the second component is the thing that you are very confident in doing, something that you do quite well. The third one, being something that pays you well, and the fourth one, being something where there's a need for it. So, just reiterating that. That's correct?

    Leandro Barreto:

    Correct. Correct.

    Robert O’Farrell:

    So, I guess getting to that, our second question that like for yourself, you can apply obviously in a business sense, but in a personal sense, what's been your journey there, and do you believe you've achieved Ikigai, I guess, would be my next question?

    Leandro Barreto:

    Yeah. Well, actually personally, I have some things that's very clear in my life. I'm still not there, but let's say that I'm in the process.

    Robert O’Farrell:

    Work in progress

    Leandro Barreto:

    Exactly. Work in progress. So, I have clear goals and I have clear in my mind where I want to go in a few years, so I don't get disencouraged if the weather is cold or warm, if the stock market goes up or down. And the only thing that I focus is to be 1% better than I was yesterday. And this provides me a security that prevents me to wasting time and things that doesn't make any sense or simply doesn't matter for me in the future. So, I take my career very, and also my personal life very serious on that point. So, yeah, let's say that work in progress.

    Robert O’Farrell:

    I love that word security that you use there. It draws a parallel, I think, to a word that we also use when it comes to that plan that we have, which is that focus element, making sure that we do the things that matter. Do you think that it's also given you a sense of focus too on what you take on and what you say yes to and what you say no to with regards to your personal and professional development?

    Leandro Barreto:

    Yeah, absolutely. Absolutely. When you know where you want to go, it's more easy to say yes or no to something that came up to you. Another personal example that I remember was something like 12 years ago, 12 to 13 years ago, my focus was to learn Java, for example, Java programming. Because I know in the midterm, I would like to be a Java architect. So, I have to improve my skills on that programming language.

    Leandro Barreto:

    So, during that time, the company that I was working was making some changes and then they asked me, "Hey, I know you are good at Java. You are learning, but we need you to start learning this another language, Ruby on Rails during that time. But you have to at least for the moment, forget Java." And then, I was like, "Mm-mm. No, no."

    Robert O’Farrell:

    It's not what I want to do.

    Leandro Barreto:

    Exactly. I totally understand that was a company's decision. But during that point, it begins to separate my focus on what I want to achieve from the company's purpose. So, it doesn't make any sense to continue on that company. I asked to leave. And again, best decision ever, because then I entered in another company that I learned so much. And then, in three years I became a Java architect.

    Robert O’Farrell:

    Yeah. That's a fantastic example of that focus. I'm quite curious out of those four components that you mentioned before, what have you found quite easy, I guess, to achieve or to at least get clarity around personally? And what have you found more challenging?

    Leandro Barreto:

    Good question. Good question. Yeah. So, learning something that you don't know, it's always a challenge but when you have a desire or a clear focus where you want to go in a few years, things start to be clarified for you. For example, in 2014, I did extension of my MBA in United States to learn about entrepreneurship and things that for me was really, really important. But totally new field, I have no idea what to expect but it provides me the vision to... I always had the idea to have my own company in other words. So, I know that in short term, not in short term, but in midterm at least five years to four years, during that period of time, I would like to have my company.

    Leandro Barreto:

    So, after I did this MBA, I came back to Brazil, and then I started to put myself in situations that makes me learn these new things. And in 2016, I open up our restaurant in Brazil. So, when you have an objective, things, and it's quite funny because the universe starts to help you.

    Robert O’Farrell:

    You make your own luck in a lot of regards too, I think.

    Leandro Barreto:

    Yeah.

    Robert O’Farrell:

    So, if you had somebody who was looking to learn about Ikigai and came to you for some, for your experience and your advice in how to apply it to their lives, what do you think your advice to someone would be who doesn't know much about it?

    Leandro Barreto:

    Good question. Great question. So, one tip that I, or advice that I can give is, and I think that this is fantastic and I apply it in my daily basis. Don't waste time in small decisions on a daily basis because every day we have thousands of decisions to make and our brain capacity is limited daily, at least daily. So, there are some times that we feel like mentally exhausted after, for example, you have six meetings in a row in a day. In the end of the day, you were totally tired. Right? And I once read that the greatest minds don't waste time thinking on small things, for example, Steve Jobs always wore the same jeans and t-shirt every day. And he didn't need to think to use it. He just took it and reuse it.

    Leandro Barreto:

    So, during that time, what I did in 2018, more or less when I was presented to Ikigai. So, what I did, I lived alone in an apartment in Brazil. So, I decided to change it, my life. What I did, I donated my entire wardrobe of clothes with things that I almost never used. And I was only wear eight t-shirts and two jeans.

    Robert O’Farrell:

    Quite a collection.

    Leandro Barreto:

    So, I avoid making those small decisions, especially in the morning, because in the morning, you have a clear mind and you don't have to spend those in small things, because if you think on small things, probably it'll grow during the day. So, for example, another thing that helped me a lot is plan the week. So, Google Calendar exists to be used, right?

    Robert O’Farrell:

    Yeah. Yes.

    Leandro Barreto:

    So, everything that is very important for you, events or plans that need to be done, put on the calendar. And also, talking about the clothes, separate your clothes a day earlier before you go into bed. So, you wake up more calmly, you drink your coffee calmly, and you focus your efforts on what really matters. And once you have freed your mind from thinking about these small things, you can focus your time and energy on learning new things or getting things done the way it should be. And whether it's learning a new language or a new skill, or you can also read a book in the morning because you have free time, let's say. You can focus on what matters to you exactly.

    Robert O’Farrell:

    Yeah. I'm quite curious about this aspect of finding something that you really get consumed by. And I think in this digital age, we have so many things that distract us. Our phone has a lot of notifications where we have a lot of information at our beck and call and sometimes it can be overwhelming to know what we should focus on, and I guess what we can really get passionate about. I'm curious, do you have any insight into that as to how people can find that thing that they just lose themselves in and that they're super passionate about?

    Leandro Barreto:

    Yeah, absolutely. Absolutely. Another thing that worked very well for me is to turn off all the notifications.

    Robert O’Farrell:

    Get a dumb phone just so you don't have that level of notifications coming through. Yeah.

    Leandro Barreto:

    Yeah. Because I read... I don't remember where exactly, but your brain took something like 15 minutes to focus on something. So, if you don't spend 15 minutes of your time, focus on what needs to be done. You cannot focus at all. So, what I usually do, I turn off all of the notifications from my phone. So, the principal one, I just took it off and I don't care about notifications. Also, one thing that I noticed is that when I, for example, when I had Apple Watch. In the Apple Watch, even if you turn the notifications on or off, the iPhone, it keeps doing on the phone. Oh, my God. So, this is one simple device that I can say, because otherwise, you will enter in a black hole in a community and social media and news, and then you'll lose yourself.

    Robert O’Farrell:

    Yeah. I found that personally with the Apple Watch, having something on your wrist that vibrates is incredibly distracting. And I was always very big champion of technology, but that was one area where I just moved away from it, went back to a mechanical watch, just didn't want that level of interruption when I was trying to focus on things. So, I think it's a really key insight to focus.

    Leandro Barreto:

    Yeah. In addition to that, when you, for example, when you are in a meeting with someone and you are actually expecting a message for, I don't know, maybe your family, and then it pops up on your phone and you are in a meeting, and then you take a look into the watch and the people notice that you are not paying attention because you are looking into watch. No matter why you are looking, if it's a message or et cetera, you do provide a psychology... How can I say that in English? Oh, my God. Psychology interference. Let's say it.

    Robert O’Farrell:

    Yep. Psychological interference.

    Leandro Barreto:

    Interference. Yeah. Thank you. That will provide a negative influence to other people. So, yeah, that's why you made the right choice to move into the-

    Robert O’Farrell:

    Yeah. I've heard some people that will actually ask people to leave their phones outside when they go into meetings or leave their laptop outside so that you're present and that you are engaged in the conversation. Because I think even the mere fact that you have your phone near you is a distraction. Even if there's no notifications, its presence is enough to ensure that you're not 100% present in the conversation, which I think is quite interesting from how we focus and our dependency on that rush that we get or that endorphin rush of getting that ping on the phone or that notification.

    Leandro Barreto:

    Exactly.

    Robert O’Farrell:

    I thought we could move on to talk about objective and key results. Or for those people that may not have come across this term before, OKRs are collaborative goal-setting methodology and used by teams and individuals to set challenging and ambitious goals with measurable results. So, to break that down further, the objective part of the OKR is simply what is to be achieved and the KR part of it, which is key results, benchmark and monitor how we get to the objective. So, getting to the heart of setting successful OKR is establishing it clear and compelling why. Is there a secret formula to creating a powerful why to get everyone on board?

    Leandro Barreto:

    Yeah. Great question. So, OKRs, it's all about action and execution. And I think the secret formula, let's say it's having a well-defined proposal and also everyone engaged in seeking the result as the main objective. So, companies in my opinion are made of living ecosystem called human beings. And every human being has its own desires, proposals, goals. And en suite, unite all of the objectives of both the companies and all the people together. That's when we can achieve best results. And that's why some companies are focused on the cultural fit.

    Leandro Barreto:

    And this is one thing that I see growing a lot in the HR area, companies and persons that must, which the cultural fit must match. It basically means that the person has the same values and desires to achieve results as most of the people in the company or what the company understand as their force that they need to keep growing as a company. And I have seen many technically good people failing in selection, in process selection, simply because they don't adhere to cultural fit. And this is much more than a psychological issue because you don't know how to say like people that cannot work as a group.

    Leandro Barreto:

    So, it's better for the company to hire someone who can play as a team instead of someone who is like the lonely wolf that keeps working alone. And the results is for only him and not for the entire company. So, yeah, this is the classic example that I can see. And also, one thing that is good for that is nowadays, our fault tolerance is quite good because today at least serious companies don't punish failures. So, they even encourage you to learn.

    Leandro Barreto:

    And the Spotify models, I remember they say like, "Fail fast and learn fast." So, that was the fail wall was born. So, where everyone shared their failures and they can learn as a team, as a clan, guild. And this is quite beautiful because you can create such an environment where everyone can learn and grow together because humans can fail. And this is normal.

    Robert O’Farrell:

    Do you think that-

    Leandro Barreto:

    And-

    Robert O’Farrell:

    Sorry, I'm just curious. Do you think that companies are more focused around the why these days, or that why has become more important in their measure of success? And you mentioned cultural fit and I love this idea that more companies are much more sensitive to what is their company culture and how does this person work within, or are they going to fit into this company culture? Because the existing people in that company are aligned around their why. And if someone is coming in and doesn't align with that, they understand the impact on their success. So, do you think that company's becoming more and more aware of this and more sensitive to this?

    Leandro Barreto:

    Yes. I think they are. So, as far as they have the right people in the right environment with the right proposal, no matter the why they will find it blindly, let's say. I think it's like a sense of behavior for the people. Because if you see someone from, as your peer, let's say, that's running to an objective that was defined by the company. And you are aligned with your values and goals. You will follow it.

    Leandro Barreto:

    So, this is good for both persons as human beings and also for the company because they show the proposal, they show what is the why we must be, for example, the first selling company for our product in the market, why, and then people who is working on it, they will take it as a personal objective. And this is when you make the connection between the company's objective and the people's objective because when the company grows with this why, with this north star, the people will grow together with you.

    Robert O’Farrell:

    I completely agree. I'm quite curious too from the opposite point of view. Do you think that employees are becoming more aware of understanding the company's why before they join the company? Because we've seen with the pandemic that a lot of companies are now moving to this remote recruitment. And so, the possibilities for employees to work for a much broader range of companies now have increased. And do you think that employees are now finding better wire alignment when they're looking for new jobs because they do have a broader pool to play in per se?

    Leandro Barreto:

    Absolutely. Absolutely. I think that's why Glassdoor is so popular. So, when you are invited for a meeting or for an interview, you can see everything from the company. Like from salary to feedbacks from the people who works there or is not working anymore. And then, you can see if there's a match. And this is quite funny because like 10 years ago, which is not so popular, we are blindly thinking to work, let's say, in a position like software development. So, I have to be a software developer. I have to be a...

    Leandro Barreto:

    So, it was more focused on the position instead of the purpose. And now we are seeing the opposite. Now, the people are looking for the purpose, what the company can help me achieve. And it's more like a win-win-

    Robert O’Farrell:

    Situation.

    Leandro Barreto:

    ... situation let's say, situation. Exactly.

    Robert O’Farrell:

    Yeah, I couldn't agree more. And I think also a lot of people are really focused on how the company takes care of them as a person. They're very sensitive to the fact that they are committing their time to that company. So, there has to be that alignment around professional goals and personal goals. And I think that it's a great shift to see, to come back to the OKR side of things. I'm curious about what benefits do setting OKRs within an organization give or provide?

    Leandro Barreto:

    Yeah. I think OKRs, they are very, very simple. They do not require a specific knowledge to implement it. So, when you have the people committed and engaged to the goal and the why they want to achieve, then the implementation and using of OKRs became naturally. So, company can benefit because he's straight to the point. He's like, "Objective, it's the direction. And the key results are yes or no." So, keep it simple. That's the main benefit of the companies.

    Robert O’Farrell:

    Yeah. I love that. The fact that there's no gray area. You either succeed or you don't, and there's a lot of clarity around that as well.

    Leandro Barreto:

    Exactly.

    Robert O’Farrell:

    I think that with that aspect of OKRs, in your experience, have you seen OKRs set that tend to stretch the team further than they normally would be stretched in terms of what they attempt to achieve than companies that don't set OKRs from your experience?

    Leandro Barreto:

    Yes, but I think it matters on what the company, what's the culture of the company, because I have seen companies that is setting OKRS in the good way, but I have seen companies that is setting OKRS because it's fancy. When it's fancy, you don't have a clear objective. You don't have a clear vision. You don't have the right people. And then, it's very tricky and you will never achieve what you are proposing.

    Robert O’Farrell:

    I'm curious to dig into that a bit more to get your insight on that. Because as somebody who would come into a company that might be setting OKRs, how would you determine that the OKRs are probably not as clearly defined or that they're implementing a process that don't necessarily have the depth or the belief in doing? So, how would somebody come in and determine that?

    Leandro Barreto:

    Good question. Good question. So, the idea to have a objective is like to have something that can be... How can I say that, can provide you like a, not a fear, but it's going to be like, provides you a direction for, but the people who sees it, they think like, "Hey, this is quite hard to achieve I think." So, one example for Google, for example. So, Google in 2008, they tend to launch the Google Chrome. And as I remember, the first year was like, "Hey, this is the objective." Like, "Hey, we want to launch the best browser in the world." And the key result is the number of users because the users will tell you if the browser is good or not.

    Leandro Barreto:

    In the first year, they didn't achieve the key result. But the second year, they rise at the bar again, like, "Hey, now we are much than double the objective." And the second year, they still didn't achieve it. But it was very, very close to it. And the third year, they pass it. So, keep in mind that the objectives must be something that seems like a challenge, a huge challenge, but at the same time, it's very inspirational.

    Robert O’Farrell:

    Inspirational.

    Leandro Barreto:

    Inspirational. Thank you so much. For those who are working on it. So, I think this is most of the point.

    Robert O’Farrell:

    Yes. And what do you see as some of the pitfalls when setting OKRs for an organization?

    Leandro Barreto:

    Awesome. Awesome. So, the pitfalls from my perspective, there are some common mistakes when implementing OKR. So, for example, as I said, not having a clear vision of the goal, so people cannot engage. And especially when you have senior engineers because they don't want to work in something that don't bring purpose for them. Right? So, this is the first one, for example. The second one could be like a system that supports the monitoring of the results. So, you cannot follow up, which is quite important to keep following it if you are, we are close to achieve it. Yes or no? So, a good point.

    Leandro Barreto:

    And one thing that seems quite strange, but it's very, very common in the market is that your product is not finished yet. One personal example that I faced not quite recently, but do you play video games?

    Robert O’Farrell:

    When I get the time. I have two young boys, so I get very little time to do that these days. But yeah, I do.

    Leandro Barreto:

    Yeah. I love doing, I don't have also time, but when I have a litle bit of time, I can spend. So, this little time I try to spend in the best game that I found in the market. And here is the point because some years ago, there was a game that was released and before released, there was several gaming platforms, new sites, and et cetera, that was telling us that, "Here is the game challen... no, the game changing for the gaming market, because it's going to be very good. The marketing for this game was really, really good. And the game was like highest expectations for that. It was always in the top. "Hey, you have to play this because it's going to be very great. You are going to be having a great experience on that."

    Leandro Barreto:

    And the funny thing is that after they launch it, a few hours later, I notice some YouTubers who start testing the game. They began to post videos about so much bugs that they are facing. And within a week, the game had to stop selling because that was a disaster.

    Robert O’Farrell:

    Yeah.

    Leandro Barreto:

    And... Yeah.

    Robert O’Farrell:

    I was just going to say, I can think of a few games that come to mind that fit that criteria.

    Leandro Barreto:

    Yeah. Probably we are thinking the same, but I can say it, so.

    Robert O’Farrell:

    Yeah. Yeah. Do you find that people get OKRs and KPIs confused within an organization? Or have you ever come across any examples of that, where people misunderstand the purpose of between the two of them?

    Leandro Barreto:

    Yes. One thing that came up to my mind is the key result is a simple measure to understand if you are going in the right direction to your objective or not, but KPIs is it's more a performance index for performing for your team. For example, if they are performing in a good way, if we have the right resources for delivering something. And so, I think this is mainly the difference is the KPI, it's a measure for you to, maybe to bonus, to create a bonus for your team or et cetera. And the KR must be not linked to bonus or salary, et cetera. Must be like a direction. Something that, yes, we are achieving it or not. Or if not, what we have to do to correct the direction.

    Robert O’Farrell:

    Yeah. Fantastic. So, coming around to Agile, I'm curious about this marrying of the two, of OKRs and Agile together. How can we combine Agile and OKRs in your experience and your understanding to achieve results that drive high performance?

    Leandro Barreto:

    Awesome. So, as the Agile manifesto says, "People over process," so I believe whenever you maintain a fail-safe environment along with a good leadership, you can get the most of your team. So, connecting what I said earlier regarding the Ikigai and when you have a good leader, for example, in a safe environment and colleagues or peers who shares the same values and goals as you, then you can extract maximum efficiency because high-efficiency teams are teams that are focused and committed with the company results, and that will achieve great business results. Sorry.

    Robert O’Farrell:

    I also love that aspect with the OKRs, with that clear definition, too, that Agile, that processes is that sprint by sprint activity where you're going back and you're looping around and looking at the results of that sprint and going back to the customer and getting customer feedback and that real alignment around what you're trying to achieve as well, to give you that clarity of focus that when you are going through that sprint process, you're coming back and saying, "Okay, are we acting on the initiatives that have come out of these key results that contribute to that OKR?"

    Leandro Barreto:

    Exactly. And also, adding to that, that's why we have the goal for the sprint, right? So, we have the direction for the sprint. So, every sprint you can measure if you are achieving this goal or not.

    Robert O’Farrell:

    And I love it as a mechanism, too, to link back to that, that why piece to really give a clarity around why, which I think a lot of software development sometimes doesn't focus as much as they can on. So, I'm curious, so how can Ikigai mix into this? So, we've talked about that at the start and we talked about the components of it and it was a great framework about understanding a purpose, but how can we use that to achieve better results and stay motivated as a team?

    Leandro Barreto:

    Great question and also quite difficult. But yeah, I believe there are two thin lines that eventually met in the future. For example, the first one is like the individual as a person. So, how he seems himself in, within the organization and how can benefit, how this relationship can benefit from this win-win relationship. And also, the second one is like the individual as a professional. So, based on the skills that he already has. How can he help the company achieve the results more efficiently?

    Leandro Barreto:

    So, in a given timeline, these two lines will cross and then you will be able to extract excellent results because you will have a person with excellent internal knowledge, internal as a person, and also engaged with the companies is seeking as a greater objective, as a north star, and also helping your peers to grow all together.

    Leandro Barreto:

    And I think this is quite like a smile. When you smile at someone unconsciously, you make the other people smile too. So, when you have someone who is genuinely working with a proposal, that person will contaminate other in a good way. And then, you have a continuous string of people delivering consistent results. And I think this is the most important.

    Robert O’Farrell:

    Have you experienced that yourself where you see someone working with purpose and contaminate or infect how you... infect is again, not a great word, but inspired is probably the best word there, inspired the people around them to work in a similar fashion. Has that something that you've witnessed yourself?

    Leandro Barreto:

    Yes, yes. I remember back in the company that I was working in Brazil, that was my first day. I was like, "Hmm, there's something strange here," because everyone is so passionate on delivering their best results for their customer, that this thought influenced me in a positive way to start being like hungry for good results, not only for the company but for me as an individual, as someone who have to learn and teach others. And nowadays, I see these companies, it's achieving a great results with a great leader because even if we have a good team, we have to get someone who is a servant leader, who you can follow and maybe follow blindly in a good way. But yeah, I experience it.

    Robert O’Farrell:

    That's fantastic. But I'm interested, is there anything that you wanted to talk about personally with regards to either of those three topics or even outside of that, that has been inspirational, I think, in your professional development, in your personal life?

    Leandro Barreto:

    Yeah, absolutely. Absolutely. I think Leandro five years ago was totally different person. And when I started looking, not only by myself inside me, but also outside and the opportunities that the world can give me and how can I serve back this, or how can I provide this back to the world? This is very funny because good things start to happen. For example, I never imagined to be working here in Amsterdam. And now, I'm here in Amsterdam, working in a great company with great people, delivering such great results, which is giving me a lot of knowledge to keep learning and keep the wheel turning on, keep the cycle.

    Leandro Barreto:

    And I think today, like performing the best Leandro's version ever, maybe tomorrow, a little bit more, and I can provide this knowledge to other person and I can also learn from other persons, from other people. And that's very exciting. I think that's what motivates me to wake up in the morning, do my sport things like running and jujitsu, and then let's do the work.

    Robert O’Farrell:

    That's fantastic. I love that, that reflection on the past five years, how far you've come. It sounds like you've had a lot of inspiration from a number of different sources, but is there something in there that you think was key to that? Or was it just a general progression over that time?

    Leandro Barreto:

    Yeah. Yeah. Actually, I tried to focus on people who have positive influence on others. So, I try to be more not equal because if you are equal, so you are the same person, so it doesn't provide value to the others, but try to be quite different in your own way. So, yeah, basically, that's what motivates me to get different sources of references and trying to be the best version of myself.

    Robert O’Farrell:

    That's fantastic. I love this mix of the philosophical, which is for me, the Ikigai, and the concrete, well, not concrete, but the workflow aspect of the Agile side of things coming together. Have you traditionally worked in Agile methodologies or did you transition between that may be starting, because if you're from the 2000s, so you probably touched on Waterfall at some point in the past and then came into Agile. Was that your professional progression over that time?

    Leandro Barreto:

    Yeah. Yeah. Actually, I worked a lot with the Waterfall methodology in 2008, when I was introduced to the Agile methodology with Scrum... no, actually 2009, then I saw. "Hey, this is very, very interesting." Let's learn more about it. And then, during this time, I keep working both with the Waterfall methodology and the Agile methodology. And the more I work it with the Waterfall, the more value I saw in the [inaudible 00:54:24]-

    Robert O’Farrell:

    In Agile. Yeah.

    Leandro Barreto:

    Yeah. And that was quite fantastic because then I also learn about SAFe and how to scale it, and yeah.

    Robert O’Farrell:

    I'm quite curious, like because we had a similar path in that regard and I reflect on where we are with OKRs and Agile, and it's interesting that Agile brought us closer to our customer and we speak to our customer on a more regular basis, which I thought was a massive win over Waterfall where you might have months and months of development, and you've got a requirement that you're trying to put into code, and then suddenly, you have this big delivery and that's when you talk to the customer. And usually, the customer comes back and says, "We want all these things changed." And it's a real pain.

    Robert O’Farrell:

    Agile was instrumental in that, but then going up from there and putting that layer of why on top of that, which I think is, again, one of those big fundamental shifts on how we focus on what we are doing. Do you see anything emerging from your experience, your professional experience that is tackling another key challenge with regards to, I guess, how we work and how we deliver value?

    Leandro Barreto:

    Yes. And for example, the customer, they want to see value on what is going to be delivered. They don't want to spend six months to wait something to be delivered. So, I think that's why cloud start being so popular, like SaaS companies, because when you are working on something that is on cloud, for example, you always have the last version. And no matter the day or the hour of the day, there will come new features. And usually, it's transparent for you. And internally from the engineering perspective, the more you deliver, the more quickly you can correct and the more you can understand the market.

    Leandro Barreto:

    And also, that's why some strategies, some release strategies came up so popular like Canary release. So, you deliver a few things to a particular person, and then you can test it. And if they provides you good or bad feedback, you have time to correct it. So, that's why it became so popular. So, I think during this time from now on, we must see a lot of SaaS companies starting to growing because things are in real life now, real time now, so I think it's natural.

    Leandro Barreto:

    By the way, there's a good strategy that was implemented by Spot 5 if I'm not mistaken that was like, but this is more for engineering perspective. They have some robots that keeps doing bad things to the servers.

    Robert O’Farrell:

    Oh, that's the Chaos Monkey.

    Leandro Barreto:

    The Chaos Monkey.

    Robert O’Farrell:

    That was Netflix. Yeah. Yeah.

    Leandro Barreto:

    Netflix, yeah.

    Robert O’Farrell:

    Netflix. And it would take down bits of their infrastructure and break things. Yeah, yeah.

    Leandro Barreto:

    Exactly. It's quite hard to see in some companies, but I think this has become to be more popular during the next couple of months or years, because it will teach the engineers how to deal with that because no one wants to stay working in the weekend. You stay with your family.

    Robert O’Farrell:

    Yeah. I completely agree. I remember when I first heard about the idea of the Chaos Monkey, that it shocked me that someone would inflict that upon their business and upon, I guess, their systems, but then it only takes a production incident to realize that if you had something like that, that you would've built in some provision should that eventuate. And I think that there's a lot of wisdom to it. And so, I absolutely love the idea. I love this, what you were saying about real-time delivery of value to customers.

    Robert O’Farrell:

    And I think back to how Agile has really been fundamental in pioneering that, well, not pioneering it per se, but with the release cadence that you get from one to two-week sprints, you're putting yourself in a position where you are delivering more often. And you mentioned Canary deploys, I think within that. Is there any other deployment strategies that you've come across that also support, I guess, that immediate delivery of value to customers?

    Leandro Barreto:

    Yes. There is another strategy which is called the Blue-Green release, but the difference between it is like the Canary release, you deliver something in the small portions, but the Blue-Green, you, like a switch that you turn on and off.

    Robert O’Farrell:

    Yes. Yes. Right.

    Leandro Barreto:

    Yeah, you can test it. You can deliver new version of your environment or your tool, and then everyone can use it. And if something goes failed, then you have the plan B, where you can just turn on and off, and then you can rearrange the traffic to your tool. But this is very technical.

    Robert O’Farrell:

    Yeah. Very interesting to me, but we might lose a few of our podcast listeners. One last question from me, just within your current professional engagement, were they implementing OKRs before you joined the company? Or was that something that you've seen introduced over that period of time?

    Leandro Barreto:

    From my current company, they are currently working with OKRs, so I didn't participate and implemented it. So, I'm just more focused on helping the teams in implementing the KRs. There were some companies that I worked in the PEs that I helped to build it, and also to build not only the objective but also the KRs. And the objective, it's you spend so much time because you have to understand where the company wants to be in the future.

    Leandro Barreto:

    So, you have to know inside what we have, what we can improve, where we can improve, and then we can base it on that, base it on the objective. We can build up to four key results to be more precise in achieving this. Yeah. But it's quite challenging, but at the same time, very exciting.

    Robert O’Farrell:

    I think that was going to be my question in your experience in seeing a company go from not doing that to then implementing it, what were the real challenges in doing that? And how long did you see that process take before they really got good at doing that? Because it is not only setting the meaningful objectives and obviously measurable key results but also then getting the alignment from the teams around that. What were the big challenges there and how long did you see that process take?

    Leandro Barreto:

    Yeah. I think it depends from company to company. I remember back in Brazil, I had to work with companies that spent months on deciding, but at the same time, I remember my own company took three months to start implementing it. So, I think it depends on the commitment of the people who is responsible for this objective. So, yeah, depends on the maturity also of the company, the people who is working, and yeah. Because the OKRs are quite old, but at the same time are quite new for people, for the companies. Right? So, this is like very challenging. And how do you balance it?

    Leandro Barreto:

    There are some people who doesn't know how to set the correct objective. And then, we came up with the same thing that we are discussing earlier. Like if you don't know where you're going to go, if the objective is not clear enough, no matter if you have good people or bad people, the people will not see value on that.

    Robert O’Farrell:

    Yeah. And you won't get your alignment because people don't either understand or don't believe in the objective.

    Leandro Barreto:

    Exactly.

    Robert O’Farrell:

    That's fantastic insight, Leandro. And I really appreciate your time today. Again, is there anything that you'd like to chat about before we wrap it up? I'm just conscious that we have been chatting for about an hour now and gone off script a little bit too.

    Leandro Barreto:

    Yeah, absolutely. Absolutely. No, actually I'd like to thank you, Rob. Thank you, Agile team, everyone. I don't want to spend much time talking also. It was a pleasure and thanks for invite again. And I hope we can think good things in the future. Like, "Hey, I hope I can provide good insights on this."

    Robert O’Farrell:

    That's fantastic. You certainly have. I've learned a fair bit today as well. So, I'll be going back to revisit some of the talking points from this chat. So, thank you very much again for your time, Leandro. I really appreciate it. And, yes, have a great day. It's kicking off for you and it's ending for us. So, yeah, really appreciate it, mate.

    Leandro Barreto:

    Thank you. Thank you. I really appreciate it too. Thanks again. See you. Have a great day.

    Robert O’Farrell:

    You too. Cheers.

    Leandro Barreto:

    Cheers.

  • Text Link

    Easy Agile Podcast Ep.2 John Turley, Digital Transformation Consultant, Adaptavist

    Transcript:

    Sean Blake:

    Hello, everybody. I'm Sean Blake, the host of this episode of the Easy Agile podcast. I'm also Head of Marketing at Easy Agile, where our mission is to help teams around the world work better together. We have a fascinating guest with us today. It's John Turley from Adaptavist. John is a pragmatic Agile leader with 25 years experience working in companies at all levels, from teams to C suite, always bringing real value, adding change to the way organizations work. Dissatisfied with the standard discourse around transformation and agility, he is passionate about applying cutting edge knowledge from fields as diverse as sociology and psychology. We're really excited to have John on the podcast today. So John, thanks so much for being on the Easy Agile podcast.

    John Turley:

    You're welcome, Sean. Pleasure to be here.

    Sean Blake:

    Thank you so much. So John, you've got a lot of experience in the Agile space, in the tech space. And I'm not trying to call you old. But I'd love to get a sense of what's changed over 25 years. It must just be night and day from where you started to what you see now.

    John Turley:

    There's a lot of change. And I'm pretty comfortable with old. I'm 48 now, and it's closest to 30 years now. That tells you when I first wrote that bit in the bio. So the technology has changed. That's mind blowing. I started off in ops, and then infrastructure and project management and stuff and 1999, 2000, it would take us three months and 50,000 quid to build a couple of web servers with a pair of load balancers and firewalls and a database at the back. And now we spin them up in seconds.

    John Turley:

    This is profound. Platform technology is profound slack or I mean platform technologies, that makes a massive difference to the way we interact. Scale is a massive issue. I would say that the world is sort of dichotomized into very large and quite small organizations. There seem to be less in the middle. It's just a gut feeling. We see, I think trust is collapsed. We see that in Edelman Trust Barometer. We see the complexity has increased. That's deeply problematic for us. [inaudible 00:02:23] has been measuring that one.

    John Turley:

    And we see that workforce engagement is at all time lows through the Gallup World Poll. Those things are big, big changes. What's the same though is the people, the way the people think, the way we construct our reality, our mindset, if you like, the way we make sense of the world around us is very, very similar. So although we now talk a lot more about Agile, the waterfall and waterfall for many is a bit of a dirty word, not for me and same with command and control. People are taking the same mindsets. This is measurable and provable. People are taking the same mindset that they had around waterfall and command and control using different language of Agile and behaving in the same way. That hasn't changed.

    Sean Blake:

    Very interesting. So you touched on trust, and how basically we've seen this breakdown of trust across the board. And I've just watched a documentary that's come out on Netflix around the Social Dilemma, and how the trust that we have in these big social media platforms is eroding. And we're getting a little bit skeptical around what these big companies are doing to us as the customer. Do you find that that's a hard balance with the people that you work with around being customer focused, but still building a profitable and growing business?

    John Turley:

    Yeah, I do. Yes, and the way I think it manifests itself, which again maybe we'll get into the sort of the psychology and the sociology as well as the complexity science, I'm into it later. But there's a very clear way that that lack of trust manifests itself. I'm not sure it's the lack of trust that manifests itself. But there's a very clear thing that's happening is people, there's repeated patterns of behavior I see all over the place in a lot of the work I do, which is one on one and with groups, that people hold on to this idea that their view is right and anything that doesn't comply with that is wrong.

    John Turley:

    This is a view that comes from the predominant mindset from what [inaudible 00:04:33] call the sort of expert or the achiever mindset, and it becomes a barrier to us collaborating and learning together and innovating. If somebody with a different point of view is dismissed as wrong, then there's no common ground to start to build trust. Trust is eroded from the outset, and that means that we can't collaborate, and in a complex world where we need to collaborate ever more closely and learn together and innovate, that's a deep, deep problem.

    John Turley:

    And the response seems to be that people actually withdraw, they withdraw into groups, we might call them cliques or echo chambers. The sociologists call this process homophily. This is a function like many say of platforms like Twitter, we retreat into groups that echo the opinions that we already hold that then reinforce those opinions, and separate us from the opinions of others and reinforce the opinions we have. So the gaps between the cliques grow wider, and particularly in times of COVID and the lockdown that we've had here, and that we seem to be maybe heading back into the isolation perhaps adds to that, and we see it more and more. So at a time where we need to be getting our act cliques and talking with understanding with others with different views, we're actually psychologically in a difficult position to be able to do that. And so that's what we might generically call the lack of trust manifests itself in the work that I'm doing. And that's how I see it with almost everybody that I work with, including myself, by the way. It's not an easy thing to conquer.

    Sean Blake:

    So what does your day to day look like, John? I think your official job title is Digital Transformation Consultant. You work for Adaptivist as one of the most well known Agile consulting practices in the world, I would say. What does that mean for you day to day? What does your nine to five look like?

    John Turley:

    So we're really involved in three things. I'm really involved in three things. And it's all about learning, collective learning, organization learning. So we're involved in a lot of original research. We do that original research with a number of academic partners in a program that we're putting together. We've been doing a lot of the research on our own. But as it gets bigger and more credible, other partners are coming to join us and they're very credible partners.

    John Turley:

    And the research is uncovering new learning. And that new learning points us to new consulting practices where we can take that learning and embed it into a workshop, say or how we might use the research instruments that we've borrowed from academia in the real world to measure social networks or psychological complexity or the amount of autonomy in the environment. So we can then use that to work with teams to help them shift from a sort of functionally oriented way of working to a cross functional way of working, which whether we're talking about safe and Agile release chains, or whether we're talking about Lean software management and value streams, whether we're talking at a team level or an organizational level, the challenge is essentially the same. We need to orientate ourselves around the creation of customer value in cross functional teams that are focused on delivering that value, not just delivering on their function. And that switch brings with it some deep, complex, deep psychological challenges that we're just not really equipped to meet. So we bring sort of the people and culture element, the tools and the Agile methodology simultaneously to bear in teams to help them make that shift. So that's really what my day to day work looks like, so the research and the practice.

    Sean Blake:

    Okay, research and practice. And when it comes to the practice side and encouraging that cross functional collaboration, how hard is it for people to get on board with that recommendation or get on board with what the company is trying to do?

    John Turley:

    For most people, it's really hard. So my experience before doing the research that I guess we started a couple of years ago I was just referring to, was something like this recently. We'd often get, so I've worked in the Agile space for a long time, I don't quite know when I started working in that space, in other words, full space, but a decade or two, let's say, and now bumped into a repeated problem, we get our, let's say, thinking of a specific example with a specific client about three years ago, very functionally orientated, trying to make that shift into cross functional teams. So we got a group of five people together from different functions, so designers, testers, developers, a couple of ops people, and between them, they should be able to obviously, launch some working code within 10 days or whatever. We were probably trying to spring into the real world.

    John Turley:

    And they were all great people. I knew them all personally. I spent time working with them all. They were very sort of Agile in the way they approached the development of the software that they did, and we put them in a room virtually to begin with and we asked them to produce a piece of code that works across functions, produce a piece of code and release it at the end of the week. And they didn't. And we thought what on earth happened there? We didn't really understand this, so we tried it again. But we assumed that the problem is because we'd done it virtually.

    John Turley:

    So this time, we got everybody together in Poland, as it happened in a room, we set it all up, we talked to them at the beginning, then people like me sort of left the room and let them get on with it, got to the end of the week, same outcome, nothing has happened. And if you talk to them, while they say, "Yeah, my phone pinged and there was a support incident, and you just couldn't.", and they had lots of very plausible reasons why they couldn't come together as a cross functional team. But the fact remains twice in a row, the most capable people haven't done it.

    John Turley:

    So we had a really long think about it, one of the senior leader in the business and myself. And we realized that the only thing that could be happening, the only thing that could be going wrong here is that there must be some sort of breakdown in the dialogue between the group in the room. So we ran it, we ran the workshop, let's call it for a third time. And this time, we had somebody else in the room just watching what was going on.

    John Turley:

    And they spotted something happened really early on. One of the people from the UK said to one of the Polish developers, they said, "Look, think of us like consultants. We're here to help you, to transfer knowledge to you so that you develop a capability so that you can do this on your own." And at that moment, the person who was in the room said that the dynamic in the room seemed to change. People glazed over. And I think what it was is that that word consultant that the English person had used had a different meaning for a colleague in Krakow. I think that meaning, the meaning of consultant meant, we're just here to tell you what to do and not actually do anything and put ourselves on the hook for any work, just kind of watch you do it.

    John Turley:

    And I think at that point, they kind of went, "Okay, well, all right, I get it, same old, same old. We'll do the work you English guys talk about it, because it's an English company.", and that breakdown started to occur. So the question we started is, I've seen that all over the place. So the question we started to wrestle with in our research is what's happening in those moments when that dialogue breaks down what's happening?

    John Turley:

    And what we've discovered is that there is a number of research studies, the biggest is about 10,000 people, that shows that around about 50% of people are at a level, and this is 50% of leaders in a study of 10,000, so for middle management, senior management, so it's a skewed number. So in reality, in software teams, it's probably more than 50% of people have reached a level of psychological complexity that suits the environment as it was, but has some limitations in cross functional working.

    John Turley:

    So they have a mindset, a way of making their reality that works well in a functional environment, but it's challenged in a cross functional environment. And that mindset, this way of thinking, which is very prevalent, is a way of thinking where individuals draw their self esteem from their expertise, just to put it very short, simple as an oversimplification. And the thing is, if you're drawing your self esteem from your expertise, when your expertise is challenged, it feels personal.

    John Turley:

    If it feels personal, people are likely to get defensive. And it's not because they're stupid, or they're not interested or they don't want to, the psychologists can show it's a level of psychological complexity, where that's just how our minds work. That's just how our meaning making works. Now, if that's the stage you're at, if we imagine me as a developer sitting down with a tester, and the tester's saying to me, "Look, the way you've written the code isn't the best way to do it for me, because I can't test it."

    John Turley:

    If I'm drawing my self esteem from my expertise as a developer, I'm likely to reject that, and might even start to think thoughts like, "Well, I think what really needs to happen here is that you need to be a better tester." I think that's the problem. And then we get this separation. Now at the next stage is psychological complexity. And these stages are in a framework that we do move through these stages. Again, it's an oversimplification, but it's observable and measurable. At slightly later stage of psychological complexity, things start to change. People start to recognize that the world is much more complex, that it's not black and white. And actually, there are multiple ways of doing things.

    John Turley:

    So to go back to my example as a developer, the tester might say to me, "This isn't the best way to write the code as far as I'm concerned." And what I'll hear is the, "Oh, as far as I'm concerned." It might be as far as I'm concerned, it's not fair enough. How can we change the way I'm writing the code to make it easier to test? But I can't do that if I respond like it's a personal criticism, you know what I mean? So what we started to uncover in the research is a correlation between how successful cross functional teams can be, and the level of psychological complexity in the leaders and the individuals in that team.

    Sean Blake:

    Interesting. So there's a book that we've been reading at Easy Agile recently called Radical Candor. And really, it comes down to giving constructive feedback to each other, not in a way where you're attacking them personally but you're trying to be honest around how we can work more collaboratively. And like you said with that example, how can a developer write code in a way that the QA tester can actually perform the tests on it? For someone who's new to cross functional ways of working, what advice does the research have around preparing that mindset to receive some of that radical candor, to receive that feedback in a way that you don't take it personally?

    John Turley:

    Well, so it's a great question, you put it really well, because radical candor is fine. We have, I work in a team that is very candid. We have some difficult conversations, and we don't even really dress our words up. And nobody gets offended. We just know that it's a shortcut. We might get our words wrong, but it's a shortcut to unlocking value to finding out how to work together. But it's not about the words that each of us picks to express. It's about how the other chooses to react to the words landing, as much as now that's a dialogue, it's a two way thing, it takes two to tango.

    John Turley:

    And the way we can develop a mindset that's more suitable to cross functional work is interesting. First of all, we've got to get out of comfort zone. We've got to be prepared to get out of our comfort zone, not far necessarily, and not for very long necessarily, and not without support and understanding from the colleagues around us. But we do need to get out our comfort zone. Otherwise, psychological growth can't occur. This is what I'm talking to about now is the work really of Robert Kegan and Lisa Lahey, who do a lot of work in dialogue on radical candor.

    John Turley:

    So we've got to get out of our comfort zone. But we've also got to be addressing a complex problem with a group of people when we're outside of our comfort zone. And that complex problem has to be meaningful, and it has to be salient, it has to be something that we care about, it has to be something relevant to our day to day work. And if we've got those characteristics in the environment that we working in, then there is an opportunity for individuals to choose to develop their own psychological complexity.

    John Turley:

    So that environment that has those characteristics, we would call in Kegan's word a deliberately developmental environment, because we can't separate the development of individual mindsets from the environment that that mindset functions in. The reason most of us have got the mindset that draws self esteem from expertise is because that's actually what most environments that we work in or not. That works in a functional environment. It's where you get promoted, it's where you get hired. It's where you get your Scrum Master badge and all that other stuff that gives you status and makes you feel good.

    John Turley:

    The world that we work in for many of us honors that expert way of making meaning. It doesn't honor learning and admission that yours might not be the best way to do things in the same way. So we have to shift the environment to support the individual to choose to take that developmental step because it can't be something that's done to them. You can't make people develop a more complex psychology. You can't train them to do it. You can only give them an environment that supports that step if they want to take it and if they don't, fair enough, that's okay. But maybe cross functional teams for them, if they don't want to because the hard place is to work.

    Sean Blake:

    Is it a problem that people find their expertise or find their self esteem from expertise? Is part of it encouraging men to find their confidence in things outside of their work or is expertise an honorable pursuit?

    John Turley:

    I wouldn't say it's a problem at all. Expertise, and the development of expertise is an honorable pursuit. Drawing your self esteem from your expertise is a very necessary part of our psychological development is a stage that can't be skipped really. I said to you before that I don't like to say things like that without the research base, but the psychology certainly imply that it's a stage that can't be skipped. So we've got to do it. We've got to go through this stage. The stage before we're drawing our self esteem from our expertise is where we draw our self esteem from our membership of the group.

    John Turley:

    And that's very important too, if you think of us as children or being part of a group is essential for our survival, so ingratiating yourself into that group, not rocking the boat, so we don't jeopardize our group membership is critical. But at some point, people start to realize, well, actually, I have to rock the boat a little bit if we want some direction. So separating your meaning making from drawing your self esteem from the group to drawing your self esteem from your expertise is a development in that sense. Drawing your self esteem from your expertise means the best way to write this code is let me train somebody to do it.

    John Turley:

    It's critical. But like all developmental stages, it has its limitations. So it's not problematic in any way, unless the individual is in a complex environment in which that expert way of making meaning isn't well suited. And then you got a mismatch between psychological complexity and environmental complexity. And when you've got a mismatch like that, the individual's anxiety will go up probably, employee engagement goes down, certainly wellbeing goes down, people revert to an earlier way of making their meaning that's more embedded in their expertise or the group, just to the point, they need to get more sophisticated.

    John Turley:

    So the problem is the mismatch between psychological complexity and environmental complexity. That's why we need to support, as the world gets more complex, that's why we need to get all get better at supporting the development of individuals into a level of psychological complexity that suits the more complex environment. That's kind of the nub of the problem. Nothing wrong with being an expert in drawing your self esteem from your expertise. People have done it forever, and will continue to do so. Every time you get in a flash car and you feel good, because you're in a car, you're drawing your self esteem from the status symbol, which is very similar to your expertise. As a young man, I put on my sharp suit and I feel a million dollars. Nothing wrong with that at all, but it's limited. That's the problem.

    Sean Blake:

    Understood, understood. So you've spoken about research and measurement and having an evidence based way of making decisions. When it comes to this cross functional way of working or digital transformation or teams moving from the old way of working to an Agile way of working, do we have evidence to say one way of working is superior to another way of working? And when you're talking to these clients or these customers, can you guarantee that if they work in this way, it's going to lead to better outcomes for the business? How do you approach that conversation?

    John Turley:

    No, I can't do either of those things. So I would never go anywhere near nor would I research saying that one way of working is better than another way of working or we can say like the mindset and the environment that there are ways of working that will work better depending on the problem that you're trying to solve. But it's very unlikely that one could be considered right and the other wrong in all sorts of circumstances, but more than that, I would say that doesn't matter what your way of working is or a team's way of working is. If the mindset is the way of making sense, if the reality doesn't also shift, then you're just following a new process, a new way of working with the old way of thinking, and you're going to get the same results just with different words.

    John Turley:

    So for me, that isn't entirely true, I'm quite biased. I guess in the work I do, I've got quite a perspective. If you shift mindset, then everything else will drop into place. If you change everything else, but don't shift mindset, nothing else will drop into place. What we can say however, is that there are three things, let's call them the three elements of a cross functional team that are hidden to people in organizations at the moment.

    John Turley:

    So generally, we think if we've got people with the right experience and skills working suitably hard, then they're going to work as a successful cross functional team. And if they're not, they're either not working hard, they're not the right type of person, or they haven't got the right set of skills, so fire them and hire somebody else or give them or put them on a training course, and that solves the problem, which of course it doesn't.

    John Turley:

    We would say that there are three other elements that remain hidden parts of the cross functional team that are more critical than that, and we're beginning to be able to demonstrate that there is a correlation between these three things that I'm going to tell you about on both employee engagement and team performance.

    John Turley:

    And these three hidden elements are the structure of the social networks that underpin the way people work. So if we think about how we as groups of human beings organize ourselves, we might think about hierarchies and hierarchy diagrams and old charts and bosses and stuff. That's not really very important for a cross functional team. What's much more important is the social network that develops across that team, who works with whom and when and how, right? Do the developers and the testers and the testers and the ops guys and the designers and the technical architects, do they all work together in a cross functional team?

    John Turley:

    Now that's a social network. That's a network that's formed through individual autonomy because they want to get the job done not because the boss says you've got to go and do it. In fact, it can't be done because the boss says go and do it. So we have worked with some friends in academia with actually an Australian company called Polinode to measure their various ways we can get the data, what those social networks look like. And the structure of those social networks is key.

    John Turley:

    As we look at the structure of social networks, we can see whether those teams look like their function, sorry, organized hierarchically, or were they organized for cross functional working because of the network structure. So network structure is one element. The other is psychological complexity. So we've worked with a gentleman called David Rook, who did the original research and developed a psychometric instrument that can measure an individual's stage of psychological complexity, both the structure and the substructure. And that mindset complexity is also linked along with network structure to where the teams can function cross functionally.

    John Turley:

    The third thing that was the hardest bit, the last bit of the jigsaw that we sort of put into our hypothesis is we need to have adequate degrees of autonomy. We needed to develop a much better understanding of what it means for teams to be autonomous than we had, and how that autonomy relates to control and how control undermines autonomy and how we all tend to be orientated, to taking the cues in the environment either as instructions, which we must comply with or invitations to be autonomous. And we now have another psychometric instrument. So the third instrument that we use, we call the motivation orientation scale, excuse me, that can measure an individual's likelihood to interpret inbound information as an instruction or an invitation to be autonomous.

    John Turley:

    And once we know that, we can start to challenge this common perception within product teams, software teams that the team is autonomous, because everybody thinks they are autonomous. And in fact, everybody is, research shows mostly autonomous, but we might be almost entirely autonomous, or we might be 60% autonomous. We can measure this. And then we can say to teams, "Look, you are autonomous as a bunch of individuals. But you also have this control thing going on where you're responding to inbound requests."

    John Turley:

    And we need to be more autonomous. So once we can start to measure it, we can start to challenge their ideas of how autonomous they are. And we can start to examine where the teams are choosing to respond from that control orientation or their autonomy. So they're the three things, autonomy and control, complexity of mindset and network structure, equal employee engagement and team performance. That's what our research says. So what we can say is, to your question in the beginning, there is a network structure, a level of psychological complexity and the amount of autonomy that correlates to successfully working as a cross functional team. And in that sense, we might think that those levels are right, in some sense.

    Sean Blake:

    Okay. So what does a 100% autonomous team look like? And do they still have interaction with, say the executive team on a day to day basis? Or are they at odds, those two concepts?

    John Turley:

    No, they're not at odds. They do have, they might have day to day, I suppose they would, they will have either directly or indirectly interactions with the executive team. So the first thing we need to bear in mind here is that the research that we're leaning on is something called self determination theory, which is a theory of motivation. And it has quite a specific definition of autonomy, which is not what we might normally think. Often autonomy is taken to mean as sort of the general use of independence. So if we buy a company, we might leave it to run autonomously, which would mean we just left it alone for a while. And autonomy in this context doesn't mean that. It means individuals acting of their own volition, individuals deciding how to act towards a common purpose. So the team has to have the vision which they can self organize around. You can't self organize without autonomy. If you don't got autonomy, you have to wait to be told what to do. And then it's not self organization.

    John Turley:

    So autonomy leads to self organization, and self organization can be around a common vision or a set of goals or an OKR is quite a sophisticated way to do instead of management by objective, then we can self organize in a way that sort of honors the need to be part of an organization, doing some coordinated work, but that doesn't rely on a manager telling the individual what to do.

    John Turley:

    That's what an autonomous team looks like. An autonomous team, you need the autonomy is really a self organizing team. And the self organizing team is deciding what the team ought to do in order to achieve a wider objective, which could be integrating with other self organizing teams. And obviously, the direction is set often by the executive. So all these things sort of come into play. It's not a question of control on the one hand or autonomy on the other or Agile on one hand or waterfall on the other.

    John Turley:

    So we're going to blend the two. We're going to balance them. And that balance needs to shift not only across teams, but also depending on the level that the organization is, that the team is working in the organization. And what I mean by that is the need for control and measurement increases in many ways as you go higher up the organization. So we want high degrees of autonomy at a team level where we're creating customer value. But we need to recognize that that self organizing team has a legitimate requirement to integrate with some elements of controlling the organization, because if we have some elements of control, then we can't do the accounting and be accountable for where we spend investors' or shareholders' money, you know what I mean? So it's much more complex in the sort of the dichotomized world that people tend to look at, which is very black and white. Is it Agile or is it waterfall? Are we autonomous or are we control orientated where you're both and the blend of which needs to shift depending on the environment here.

    Sean Blake:

    Okay, okay. So there's always a need for a bit of control on top of the autonomy.

    John Turley:

    It's a balance, right? We're all comfortable with control, aren't we? We all comply with speed limits, for example. We're perfectly okay with that. Control is not a dirty word. Some will do things that we're told to do sometimes, and we're happy to do it. Sometimes we do it begrudgingly. We're not happy to do it. Sometimes we reject it. There's nothing wrong with control in itself. It's the overuse of control to coerce people to do things that they don't want to do. That's when it becomes problematic because it undermines an individual's autonomy, which is a basic, universal psychological need. We all need to have a sufficient degree of autonomy to feel well.

    Sean Blake:

    Okay. Okay. So we know that Agile's had a good run, it's been decades now. So do you still find that you come across the same objections when you're speaking to these executive teams or these companies perhaps from more traditional industries? Do they still have the same objections to change as they did in the past? And how do you try and overcome them?

    John Turley:

    Yes, they do. So one of my strange experiences as a young project or program manager, whatever I was, is that when I would end up in a room full of software developers who were Agile, probably the language they would have used at the time and a bunch of infrastructure engineers who followed waterfall, and the distaste for one group for the other, it was almost visceral, and you could see it in them. There would be a bunch in, I don't know, Linux t-shirts and jeans, and then the infrastructure waterfall people would probably be wearing suits.

    John Turley:

    I mean, it was really obvious, and it was hard to bring these groups together. That was my experience in let's say, around about 2000, I sat with a client yesterday, who said exactly the same thing. They said that in their organization, which is going through a very large, Agile transformation at the moment, they said, "These are their ways. We kind of got people at the two extremes. We can sort of bookend it. We've got the waterfall people who think their way is best and we got the Agile people who are totally on board with Agile transformation."

    John Turley:

    And what I heard when the individual said that is quite senior leaders, the Agile people are on board with the Agile transformation brackets because they think their way of working is best. And what I tried to point out to that senior manager was that that was one group, there were perceptions anyway, that one group was into Agile and got cross functional working, all that got cross functional working and the other group didn't, actually the two groups were operating in the same way.

    John Turley:

    They both thought their way of working was right, and one was espousing the virtues of waterfall and the other Agile, but the fact was they both thought that they were right, and the other was wrong. And they were both wrong in that. Waterfall works really, really well in a lot of scenarios. And full on Agile works really, really well in some environments. In some environments, it's quite limited by the way, in my opinion.

    John Turley:

    My friend and colleague, John Kern, who was a co author of the Agile Manifesto in 2001 or 2004, whatever it was, I can't remember. He says, "I love waterfall. I do loads of waterfall, I just do it in very small chunks." And because the fact is we've got to do work sequentially in some manner. I can't work on an infinite number of things in parallel. There has to be a sequence.

    John Turley:

    And that really, when I heard him say that, it sort of filled my heart with joy in a way because for somebody with a waterfall background, I used to say, "Look, I don't get this. In waterfall project management, we're talking about stages. And in Agile, we're talking about sprints." And they've both got an end. One's got a definition of done. And one's got some acceptance criteria, and they both got a beginning. The only difference is the language and the duration.

    John Turley:

    So what if we make sprints, sorry, stages 10 days long? What's the difference now? And yet people would say, "Well, we're Agile, and we do sprints, and that would still be a stage." Come on, we've got to find some common ground right to build a common meaning making between large groups of people. Otherwise, only the Agile listeners amongst us can work for Agile organizations, and everybody else is doomed. And that's not true, is it? That's nonsense, right? So we've got to come together and find these ways of working as my friend John Kern points out so eloquently.

    Sean Blake:

    Okay, that's good advice. So for these, some people that you meet, there's still this resistance that has been around for many years. How do you go about encouraging people to get out of their comfort zone to try this cross functional way of working and be more transparent, I guess with contributing to the team and not necessarily pushing towards being just an individual contributor?

    John Turley:

    Another great question, Sean. So there are a couple of ways we can do it. The psychometric instrument that I mentioned earlier, that can sort of measure I kind of always put that in inverted commas, because it doesn't really measure anything, it assesses, I suppose, is a really, really powerful tool. Off the back of that measurement, the psychologists that we work with can create a report that explains lots of this sort of meaning making stuff, adult developmental psychology to the individual. And it tends to be mind blowing. It really shifts people's perspective about what they are and how they're operating in the world.

    John Turley:

    Once people start to understand that there are these developmental stages, and we all move through them potentially to the last days of our life, we can start to see the disagreements. They just start to fall away. Disagreements start to fall away, because they cease to be seen as opposing views that can't be reconciled, because I'm this type of person and they're that type of person.

    John Turley:

    And they start to be seen as incompatibilities in meaning making. So people start to go, "Okay, well, I think this and you think that. How are we both making our meaning around this, that means we can see other's perspective?" And immediately, then you've started to find a mechanism to find some common ground.

    John Turley:

    So the leadership development profile report, which is the report that comes from the psychometric instrument really sheds a lot of light on for the individual, both on how they're working and what development looks like, what psychological development looks like for them. So that's a powerful tool. We have another service that we call dialogue partnering, which we're piloting, which is sort of what over an eight or 10 week program, it's a one on one collaborative inquiry into how an individual is making their meaning, and what the strengths of their meaning making and the limitations of their meaning making are.

    John Turley:

    And once people start to realize that the way, the reason they feel defensive because the way they code has just been criticized is because they're drawing their meaning from being the best coder on the planet. But there is a development path that leaves that behind, which is where many, many people get to. It's kind of like an a-ha moment, people just realize that reality is different to what they thought and it can be adjusted.

    John Turley:

    So the LDP, the Leadership Development Profile reports, dialogue partnering, and working with senior management to create a deliberately developmental environment, which does those things I mentioned before, they're the critical tools that we use to help individuals unlock their own psychological development. And the question is, of course, why would they be motivated to do this? Why would they care? And they care, because 80% of people have got a very low level of engagement in their work. Most people are treading water, killing time. It's not a joyous place to be. Once people start to work in cross functional teams and get involved in joyous work with their colleagues to create things they couldn't, which is a basic human instinct, that's a buzz, then you come into work and enjoying yourself.

    John Turley:

    That's what I said to you at the beginning of that call, right? I'm having a great time, I'm working with some brilliant people unlocking new knowledge that we believe humankind doesn't have. That's a buzz. I'm not treading water in my role, you know what I mean? And this isn't unique to me. In my view, the whole world could be like that. We could all work in roles like that, maybe that's got a bit far. But certainly, many more of this could then currently do to get on board with the psychological development and enjoy your role more, enjoy your work. There's a lot of time.

    Sean Blake:

    Yeah, I really resonate with what you said about the buzz. And I've seen that happen when the light bulb comes on in people, and it's no longer this factory line of work getting passed down to you. But you realize you're now part of a team, everyone's there to support you, you're working towards a common goal. And it's transparent, you can see what other people are working on, and you're helping each other build something together. It's actually fun. For the first time in a lot of people's careers, it's a fun and enjoyable experience to come to work. So that must make you feel really good about doing what you do.

    John Turley:

    Yeah, it does. It's why I get out of bed, and it's what I've been about for 20 years trying to unlock this, really help other people unlock this. I got a phone call from a colleague the other day who said they were doing some exercise, and they were thinking about their new role. And they thought to themselves, this is what it feels like to do joyous work.

    John Turley:

    I mean, that [inaudible 00:42:51] job done, because this is a very capable individual. Once they're feeling like that, you know that they're going to do great things. When they're feeling like they're other people feeling, that people are clot watching, or there's this culture of busyness, where we can't admit that we don't know things. And then we've got to be in a meeting doing something, in the transparent world that you're just talking about, if I've got any work to do, I can just sit and say, "I'm going to work today, I'm waiting for more stuff to write." And it's not a bad thing. It's like, great, you're working at a sustainable pace. That's a good thing. I worked for a Swiss bank for years and years, working at a sustainable pace but nobody was interested, you need to work at a full on flat out unsustainable pace. And when you're burned out, you can go and we'll get somebody else to come in and do it. That's how it works. That's miserable.

    Sean Blake:

    It's not what we want, Sean, is it? It's not what we want. And unfortunately, a lot of people have been there before and they've experienced it. And once they see the light, they never want to go back to it, which I guess is a good thing once you recognize that there's a better way.

    John Turley:

    Yeah, agreed.

    Sean Blake:

    Yeah. Okay, well, I think we're going to wrap up shortly. I do have two more questions for you before we call an end.

    John Turley:

    I'll try and keep the answers brief.

    Sean Blake:

    No, that's fine. I'm really enjoying it. I could probably go for another hour but I know we've got other things to do. So in the research, I've read some of your blog posts, and I watched some of the talks that you've done and events in the past, and you speak about this concept of hidden commitments. And I just like to learn a bit more, what is a hidden commitment? And what's the implication?

    John Turley:

    Great question. So Robert Kegan and Lisa Lahey, developmental psychologists, wrote a book called Immunity to Change. This is a book that I read here a few years ago. And in there, Bob and Lisa talk about hidden commitments. And so they start by pointing out that we all make New Year's resolutions and they all fail. We really mean them when we make them. And when I was in my late teens, maybe I really did mean them when I made them. But I could never keep them.

    John Turley:

    In another book, Kegan points out, I think it's in the book called The Evolving Self. He points out that a large majority of men, after they've had heart attacks, I think it's a study in America. But it's been a while since I read it, I think it's six out of seven, don't change either their diet or their exercise regime after they've had a heart attack. And the reason he uses that as a case study in the book, because he's pointing out that it's not that these people don't know what to do, you need less calories in, more out. And it's not that they're not motivated to do it. They've had a near death experience. They'd like to stay alive, we presume.

    John Turley:

    Yet still, they don't make any meaningful change to their diet, their exercise regime, why not? And what Bob and Lisa say in the book from their research is that it's down to hidden commitments. We all have our way of making meaning. We have our values and our assumptions that we absorb from society as if by osmosis. And we don't question them. We can't question all of the assumptions that we absorb as we grow up. It's just not possible. So we have these hidden assumptions that we're committed to hidden commitments. And sometimes, these hidden commitments conflict with our stated objectives. And when the hidden commitment conflicts with our stated objective, the result is that we get very confused about the fact that the stated objective sort of falls by the wayside, and we don't really understand why. We might think, I would think a common out, because I just need to try harder, I just need more willpower. I just need to stay the course. And it's not true very often. There is something else in your meaning making this conflicted with our stated objective. And once you can surface it, then you can start to examine that hidden commitment, and you can play around with it.

    John Turley:

    And when you can play around with it, then you're adjusting your meaning making. And the technique that we use in dialogue partnering comes from Bob and Lisa's book, where we're essentially uncovering those hidden commitments and seeing how they conflict with commitment. So that's sort of, and then once you can see it, and you can experiment with it, you can start to unlock change in yourself. Peter Senge, I think he's director of innovation. He's very famous, director of innovation for MIT. And he has a beautiful little quote, something like, "What folly it is to think of transforming our organizations without transforming ourselves?"

    John Turley:

    We need to change our relationship with power in order to change the way power is distributed across our organizations. And that's an example of a hidden commitment that we don't normally think about. We just think we can empower people magically, whilst retaining all the power for the senior manager. And that just doesn't work. There's a hidden commitment, conflicting with the idea that we want to empower our teams, which is a quite flawed idea.

    Sean Blake:

    Wow. Okay. Well, I really like the approach to work and looking at the social structure, the social networks, and the psychology behind it all. It's really fascinating and it's not something I've really come across before, especially in the Agile space. So that's really unique. Thanks for sharing that, John. Last question for you. 2020 has been interesting to say the least. We've talked about some things that have stayed the same over your career, some things that have change. What do you think is going to come next, looking forward to the next five, 10 years? What are some of those trends that you think are really going to stand out and maybe change the way that your work, it changes the way that that your nine to five looks or changes the way that you interact with your clients?

    John Turley:

    I think that this won't just change the way my nine to five looks. It will change like everybody's nine to five looks. I think that the world is in a difficult place. A lot of us are upset, and it looks like a bit of a mess, and we're all anxious, I think. A lot of us are anxious. But as a friend said to me, he was quoting somebody else, never let a good crisis go to waste. The amount of changes, a lot of energy in the system, the amount of changes in the system is palpably changing things.

    John Turley:

    Many of us recognize there must be a better way of doing things because our ways of organizing ourselves as society, including our organizations is collapsing. It doesn't work anymore. People are realizing through work that people like the names I've mentioned, and through our original research, I hope will sort of contribute in an original way to this, that there is a better way of organizing ourselves that humankind does have the knowledge and the experience to do what we need to do.

    John Turley:

    It just isn't in IT. We need to look outside of it to what the psychologists say about mindset, not what the Agile people say about mindset. That's a radical idea. And as we import this learning and this knowledge, we have a framework that helps us understand to a much greater degree what's really going on, and how we can unlock real change. So everything that I talked about today, very little of it is original. We have some original work I can't really talk about. Does it matter? The knowledge is out there. If we do the people and culture bit and the tools and the methodology together, then it scales, then we change the way organizations work, which is going to change everybody's nine to five.

    Sean Blake:

    That's great. It's bringing it back to basics, isn't it? What we know about human beings, and now let's apply that to what we know about work. So that's really eye opening. And I've learned a lot from our conversation, John. I've got a few books and a few research papers to go and look at after this. So thank you so much for appearing on the Easy Agile podcast, and we really appreciate your time.

    John Turley:

    Sure, my pleasure. I mean, I love and we love at Adaptavist to sharing what we're doing. So we can all engage in more joyous work, man. So thanks for helping us get the message out there.

  • Text Link

    Easy Agile Podcast Ep.7 Sarah Hajipour, Agile Coach

    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.