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

"I really enjoyed my conversation with Andrew Malak. We talk integrating agile techniques and tips on how to achieve a culture of accountability"
Andrew is a firm believer that the customer trusts your business by joining, and you have an obligation to repay that trust by helping them achieve their outcomes.
Enjoy the episode!
Transcript
Teagan Harbridge:
Welcome to another episode of the Easy Agile Podcast. I'm Teagan, head of product here at Easy Agile. And we've got a really exciting guest on the show today, Andrew Malak from Spaceship. He's the chief product officer. Andrew is a true believer in creating products and experiences that solve customer problems. He believes that the customer trusts your business by joining, and you have an obligation to repay that trust by helping them achieve their outcomes. In his current role, Andrew aims to help people take control of their wealth from a young age, educating good money habits and helping people invest where the world is going. Andrew is a family man who loves his time with his wife and children. And believe it or not, he uses agile techniques in his personal and professional life. Andrew is an economics geek. He plays and coaches soccer, football. He's a big Liverpool supporter, loves to travel, loves amazing architecture, and loves working with children.
Teagan Harbridge:
There were so many takeaways from my chat with Andrew that I really struggled to pair it down to three. But if you say tuned, here are some of the things that you're going to learn from our chat with Andrew. Why we should stop using the term agile transformation and start calling it an agile evolution. Why it's important to be open-minded to our own limitations so to break the old mindset of protecting original scope. And tips on how to achieve a culture of accountability. So I hope you enjoy. Andrew, can you tell me a little bit about Spaceship?
Andrew Malak:
Oh, fantastic. Well, thank you very much for, first of all, having me, Teagan. Spaceship is a business that's on a journey to make good money habits and investing accessible to all people. So what we look for is trends to do with industries or companies who are building the future of both industry or economies. We invest in them for the longterm, we break down barriers of entry for people, we give them a fee-free product under $5,000, no minimum investments. It's really easy to sign up. You simply download an app and you sign up and make one product selection decision, and you're done. You can start investing on autopilot. We allow you to also invest your superannuation in a not too dissimilar way.
Teagan Harbridge:
So tell me a little bit about who your target customer is, then. Because it seems like you're trying to make something quite complicated accessible for maybe first time investors.
Andrew Malak:
Well, you're absolutely right. There's a niche segment of people out there at the moment, millennials or even gen Zs, that we just don't think have been well serviced by the incumbents. And what we're trying to do is resonate with these young people as much as possible. We're trying to reduce industry jargon and really make things simple to them, because investing doesn't have to be complex. It's really about a lot of discipline around, if I can manage my personal P&L, or money in, money out, then I can create a cash buffer that can go into my assets column on my balance sheet. That's really what we're trying to do. And that kind of language, if we can get it right, can really simplify things that have typically been in the hands of financial advisors and accountants and give it back to everyday Australians who are starting out in their investment journey.
Teagan Harbridge:
Yeah, awesome. And you've been on quite a journey before landing in the FinTech space as the Spaceship CPO. So can you tell me and our audience a little bit about what that journey has looked like?
Andrew Malak:
Oh, where do I start? If you asked a graduate Andrew Malak what he'd be doing now, I don't think I would've been speaking about this because at that point in time in my career I didn't know this space would actually be around, if that makes sense. So I'll go back to my younger years, and I always thought I was going to be an architect. I had this fascination with bridges and I wanted to design things and see them come to life. And let's just say that I do that in different ways right now, but I started out working in CommSec on the trading floor. I moved on to work as a business analyst, and that's where I started my critical thinking into how businesses work and how things can be made more efficient.
Andrew Malak:
I dabbled in teaching for a little bit, I taught high school economics and religion for a little bit. And then I eventually landed in a product role at St. George Bank prior to the merger with Westpac. At that point in time, the light bulb really came on. I realized, "Hey, I like creating things. I like to change things. I don't like to just do things," if that makes sense. And that wondering mind that doesn't like the conform was finally let loose, if that makes sense. And I haven't stopped enjoying it. I loved my time at Westpac, made lots of friends, worked on really cool, successful projects, and implemented lots of things that had great results. Worked on lots of things that have failed miserably and learnt a lot out of that. And when the opportunity at Spaceship started to surface late last year, it was just too good an opportunity to not really come in and have a go. So yeah, it's been quite the journey.
Teagan Harbridge:
Yeah, wow. And I love a good failure story. And you said you've had lots. Can you think, just off the top of your head, what one of those big failures has been?
Andrew Malak:
Where do I start? I think our first attempt at taking a digital experience to allow customers to acquire a product online was quite a failure that taught us a lot. We basically took the systems that our back office staff used and just made it available to customers. And the real good learning out of that is there was a lot of traffic and a lot of demand, but not enough completion ever. And the best learning that came out of that... This is back in 2006, so internet speeds were just starting to pick up. Broadband was starting to go mainstream and customers' trust around doing more transactions that used personally identifiable data was starting to normalize at that point in time. Up until then, people quite reserved thinking, "I'm going to lose my personal data," et cetera. So when we decided to do that, we saw that there was a lot of demand but we quickly came to the realization that we used to train staff for four to six weeks on how to use the systems before they knew how to service customers using them.
Andrew Malak:
But then we've deployed it into production for customers to self-service and realized quite quickly that the experience for customers had to be much more guided than the experience for a staff member. This is where the evolution of usability or design thinking started to come in. We started thinking of, "Well, how do we make these things so easy that a first-time user can go end to end and not encounter friction?" And this is where our understanding of design principles, customer testing using verbatim and anguage that can resonate with a first-time user becomes critical to the execution. It's not just good systems but it's good user experience sitting on top of systems.
Andrew Malak:
That's probably the one that resonates with me the most because I've held that to a very high regard throughout my whole career. Now everything I do I think of, "Where's the friction? How do we make sure there's no friction? What's the customer going to feel throughout this experience? How are we creating unnecessary anxiety in that experience for the customer, and how do we move that away? How do we become more transparent but still be simple?" And yeah, that's probably the one that resonates the most.
Teagan Harbridge:
Seems like a tremendous learning opportunity early enough in that project and something that's stuck with you since, so great learning opportunity.
Andrew Malak:
Absolutely.
Teagan Harbridge:
We've got a ton of customers who are at all stages of their agile transformations, and I know that this is something that you've had experience with if we go back to your St. George, Westpac days. Can you give our audience any tips or stories that you encountered when you were going through those agile transformations? What lessons can you share with our audience?
Andrew Malak:
Oh, I have lots of lessons to share, actually.
Teagan Harbridge:
This is what I love.
Andrew Malak:
Look, I like to position it more as agile evolution more than agile transformation because no matter what you try to do, you're not just going to drop waterfall and become agile next morning. Honestly, I've seen so many attempts and every single time I see that the graduality of the change is a better predictability of the final outcome that you're going to land. So ultimately the Holy Grail that everyone's aspiring to is that, as a leader, you can rock up to a team stand up unexpected and then, without being told who is in what role, who the product owner is, who the engineer is, who the QC is, who the designer is, it becomes hard for you as the leader to work out who's who because at that point in time the team is so well converged on customer outcomes that they will self-organize themselves around what each person needs to do.
Andrew Malak:
And most of the language being used is really around, what are we trying to define the customer? What's the best thing to do within the capacity that we have to deliver this feature to market as quickly as possible, capture value for the customer and the business as much as possible? This takes a long time to get to, where you can start normalizing to a standardized, common set of goals, common cadence, and common ways of working. And I think it's ultimately about how much empowerment you can give people and how much as a leader you can relegate yourself in the background to allow them to work it out themselves as long as you're coming in and nudging things along the way and helping people course correct along the way. So the good news is that I actually think at Spaceship, we're pretty close to getting there.
Andrew Malak:
We have been running scrum and we have been running sprints for a long time, but it has been largely ceremonials. But over the last quarter, we've done a really good job at embedding more cross-functional people into these teams. But the goal for us is that now we feel like our throughput has actually increased and that the constant flow of information between the teams is becoming more natural and there is actually less ambiguity between the teams around, "All right, we built it this way. The API is no longer consumable. It doesn't fit what we're trying to do from our front-end and there's less back and forth." So we can really see that the amount of friction between persons in the team is really starting to reduce dramatically and we're starting to see that throughput really increase. Having said that, the best way to go about an agile transformation is just get started.
Andrew Malak:
You can sit and plan out things and plan towards utopia as much as you want or you can actually just get going. So when I say by get going, I say you have to start by getting buy-in from all the leaders of the different cross-functional teams, because if you don't have that buy-in at the leadership level, it's just not going to work because there's going to be blockers, there's going to be escalations. And if all these things result in conversations around, "Should we keep doing this?" Or, "Hey, maybe this is not the right thing to do." That needs to be off the table really early on and it needs to be a total commitment at the leadership level that we're going to make this work and whatever we encounter we're just going to fix forward. Once you have that commitment at the leadership level, you need to very clearly define the values that the team is going to be handed to work with, because agile itself, it's not a process, it's a set of values that the team needs to just take and start working with.
Andrew Malak:
So we could go and rattle individuals and interactions over processes and tools or working software over comprehensive documentation. Well, give these to the team and they're going to say to you at day one, "We can't go to all of that straight away." So they might actually say that day one, "We're still going to need some documentation because we're not comfortable yet. We don't understand the language of the other people in the scrum team well enough to be able to go and actually code off the back of a conversation." But by the 10th sprint, the 20th sprint, that misunderstanding of what the product owner wants or what the designer is trying to achieve in an experience starts to become embedded in the mind of the engineer.
Andrew Malak:
The engineer understands the customer a lot more, and then you can make do with less process and less documentation and less negotiated outcomes and more commonality across the team. The other thing that then starts to kick in at that stage is that ability of the team to pivot in response to a change and not see that as a threat to what they're trying to achieve. The old ways of working was, define that scope, protect that scope, and not let things disturb that scope, whereas if you're halfway through a project and you get some really good information that tells you that maybe you are not on track to achieve a good outcome, you should be welcoming that. And the team itself in the beginning is going to find that an irritation, but over time they'll become more comfortable with pivoting off the back of new information.
Teagan Harbridge:
Yeah. It's a big mindset shift. I was just having a discussion today about, where does being agile and being reactive, where's that line in the middle. And when does taking information and pivoting because you think something will be better, when can we break that mindset of, "Oh, we're just being reactive?" No, we're being responsive.
Andrew Malak:
Yeah, yeah. And look, I think the word reactive itself naturally has a negative connotation to it, but agility in mindset allows you to flip that on its head and say that no one can work things out in totality to 100% of what's possible, so being open-minded to our own limitations first and foremost allows us to acknowledge that when new information comes in, it is because we didn't think through the solution 100%, but let's also be okay with that because no one can. So I think it's flipping on its head and acknowledging it upfront and saying that this is going to happen, but when it comes we will assess the information we have with the capacity we have with how far progressive we are and make a decision that's right for us, for the customer, and for what's possible.
Andrew Malak:
So I take it as the more information you get along the way, the more reinforcement of, are you doing what's right or should you pivot and change at that point in time? The other thing that happens really early on is that if you as a leader can create a really clear vision around customer outcomes and establish your first cross-functional team and hand over that vision to the team, it becomes theirs. Don't hand over the backlog to the team. Don't give them a ready backlog, just give them the vision and then tell them, "You guys work out what your backlog looks like." When they come up with their own backlog, as long as you as a leader don't see that it's just a list of Hail Marys in it and there is a fair bit in there that is well spread out between hygiene things, strategic things, and a few moonshots and the balance is right, if the team has come up with their own backlog, the motivation they have to build their own ideas just goes through the roof.
Andrew Malak:
And that's what you want to achieve. You want to achieve clarity that the work fits with the vision and the motivation that you get out of the backlog being created by the team itself gets you that throughput enhancement. The other thing that you're going to struggle with really early on is chunking things down to fitting within the sprint cadence. I think that's one that's often been my biggest challenge when moving towards agile practices early on. Typically in the first few sprints, you always have overruns and things don't complete in the sprint because we end up thinking we can do more than we can and it takes us a while to work out, in wrapping up something that becomes shippable in a sprint, you probably take a little bit less in that sprint because you've got to test it or you've got to do a release in that sprint, or you're going to do a PIR in that sprint, or you're going to do a lot of retros in that sprint. Start to sort of formulate what you're going to take through the next planning cycle.
Andrew Malak:
So you've got to budget to that capacity, and I'll find that teams underestimate the magnitude of that work. So be okay with that. Overruns in the first few sprints don't mean you've failed, it means you're learning how to plan better. And then make sure your retros and your pivot off the back of that into your next planning sessions is taking information that is now new to you, and making sure you're working with it. I think as the leader, though, you have to set the expectations that teams can make mistakes and that it's a safe environment.
Andrew Malak:
And I've seen many agile... I was about to use the word transformation, even though I've just said I don't believe in transformation. Any teams that are adopting agile principles expecting that in their first few sprints they don't have any hiccups, and that if throughput falls in the first few sprints, then there's a bit of a, "Oh, well you told me this thing was going to increase our throughput." Yeah, but not straight away. So I think just being realistic with yourself and what's possible, and that shift in itself, until it normalizes, takes a bit of getting used to. The teams need to know it's a safe environment, that if their productivity suffers, if they make mistakes or if they break things, it's going to be okay. We'll fix forward.
Andrew Malak:
But then also there comes a point in time where we have to be very clear about the culture of accountability around using that capacity really well. So what I've found, that the best use of that is the showcase. And what we've done at Spaceship, because we're trying to reduce the amount of ceremonies, we've combined both the planning playback in a sprint as well as the showcase into the same ceremony. So what we do is we play back what we built last session using a demonstration of working software and comparing the amount of work we've executed versus what was planned in the previous sprint. We're saying we've got 80%, 90% through the work and this is what it looks and feels like, and this is what we're deploying to the customer. Then we actually showcase what we plan to do in the next sprint.
Andrew Malak:
And that's part of the showcase, is our hand on heart commitment to, "This is what we as a team are committed to doing in the next sprint." And then that accountability to the organization becomes something that keeps us on track throughout the sprint. As distractors or things that are not committed in the sprint come our way, we quickly think about, all right, can we accommodate these things? Do they need to be done? Are they going to take us off track with what is planned? Are they important enough? Is it a major defect of production, and can customers no longer access our app? Well, drop what you're doing and attend to that. Otherwise, if it's not material, keep focused on the work that you've committed to in front of the organization.
Andrew Malak:
After this you're going to start to experience some growing pain, and the growing pain is good because it means that agile is working and more teams or more feature opportunities become possible for the business. There's going to be a lot more hype around moving to agile. Other teams are going to come across and say, "Oh, how do we piggyback off what you're doing?" Et cetera. This is good. This is good, but what it means now is that some new risks are going to actually start to be introduced. Working with common code, common dependencies, or even common people being needed to be doing multiple things just means that you now need more coordination. I'd say to anyone who reaches this point in time, this is where people feel compelled to start introducing some new roles, coordination roles. And I'd just say, be careful because that can start add to your overhead really quickly.
Andrew Malak:
I find the best way to ensure that teams continue to be in sync is with the right dialogue at the right level with the right rhythm. And this is where I think keeping it simple to just the scrum of scrums works really well. I like the scrum of scrums to be balanced between both product owner and tech lead from each team being present, and a cadence of one to two times per week works really well. And as long as the product owners across the teams and the tech leads across the teams know what the other teams are working on, know what could impact their own work from a release perspective or scheduling perspective or an environment perspective, I think that tends to work really well as well.
Teagan Harbridge:
Yeah, wow. Lots of nuggets in there and certainly things that resonate with our experience here at Easy Agile, being a small company that's grown really quickly. So I can definitely relate. We've had conversations about, do we introduce new roles into this company? We've introduced a new cadence of meeting rhythms only the last couple of months, so we're going through these things too.
Andrew Malak:
Absolutely. Absolutely. What have been your biggest learnings so far?
Teagan Harbridge:
I think that you cannot underestimate communication, and it really does come back to that cadence and that rhythm with the team. And we're experimenting at the moment with a daily huddle where we're talking about, how do we embed showcases more regularly in our cycles? We've got a big demo at the end of the cycle. How can we make that a more ingrained part of our culture? And it really does come back to that culture of accountability as well. So yep, it's all resonating.
Andrew Malak:
Yeah, absolutely. Look, you can go to whatever industry you want but the problems are usually similar. And the great thing is that having these conversations is very important to fast-tracking your way forward, because your problem is not unique to you. Someone else has seen it in someone else has figured out a way. And I think what I like about the FinTech industry is that we compete on products and services, but there's a lot to learn from each other. And even if you just go outside of FinTech, there's a lot to learn from other industries who have adopted agile practices.
Teagan Harbridge:
If we take a bit of a flip, we've gone from your professional career and your experience into a more personal level. You mentioned that you use agile techniques outside of work. So I'm not sure if many others are in the same boat, but can you elaborate on this? What does that mean? What does that look like?
Andrew Malak:
Okay, I hope you don't think I'm extremely weird. We actually have a family campaign. So I guess if I go back to how we've come to actually doing this. Becoming parents, we would look at our children and see so many things that we want them to be better at. And in trying to give them constant feedback, which felt like the feedback was so much that it's all being drowned out because there's so much of it. In fact, my oldest son actually gave me that feedback. He goes, "Dad, why don't we focus on one thing at a time?"
Andrew Malak:
And I was like, "Wow, okay." For a ten-year-old to tell me that, that was amazing. So we came to realize that we needed to narrow and focus on one improvement area at a time, and we don't move on to the next one until we've actually closed out the first one. For example, my oldest son, very clever boy. We're trying to focus with him on the discipline of process over just getting the answer right, because he is clever and nine times out of 10, ask him a question, he's got the answer and he just wants to say it.
Andrew Malak:
But we've started to try to break down the question and work more on the process with him so that in following the process, coupled with his natural ability, we will get more answers right more often. And that's what we're working through at the moment. So our family's scrum wall at the moment has a mix of things on it. Everyone has their own swim lane, and in each swim lane there are a few tasks, some related work or study, some relating to household chores, some related to health or exercise, and some related to acts of kindness. And what we aim to do is make sure that we're moving things across in all four categories every single day. So yeah, you can use agility wherever you'd like but I think that mindset in general, that if I wake up every day and do things that make me better than I was yesterday, then I'll get to keep moving forward in my personal life as well as my professional life.
Teagan Harbridge:
And do you have WIP limits?
Andrew Malak:
We don't at the moment, and we're not doing showcases at the moment. We'll see how we can introduce them in the future.
Teagan Harbridge:
And how was the introduction of a Kanban board at home? How was that received by the family? Have they enjoyed it, has there been any feedback?
Andrew Malak:
Well, it wasn't actually planned. It started by just sticking some Post-its up on the fridge to remind us of stuff. And then one day I said to my wife, "You know what? This reminds me of what we do at work. Why don't we formalize it?" She had a bit of a chuckle but then one day she came back and then she found it there. So yeah, it wasn't really planned.
Teagan Harbridge:
Awesome. And you've already been super generous with your time so I'll close it out with one final question. What advice do you wish someone would have given you when you took the leap from product management into product leadership?
Andrew Malak:
Yeah, that's a really good question. I think first and foremost, that you've got to make sure that you drop your need for perfectionism, because first and foremost, you might have been the best product manager yourself. You might have been amazing. And I'm not saying I was, but if you were and you step up in leadership role, you're going to have people of different abilities working for you. And what you need to understand is that they're going to need some time learning their role and learning their trade. And just don't get in the way of them learn. So for example, you might see someone doing something that may not be the best or most optimal use of that capacity in that sprint. You might feel the urge to jump in and course correct. But if you let them go and just hear their feedback post the retro, they might've had that learning themselves, and a learning that they get for themselves rather than being told by their leader is going to be much more useful for them.
Andrew Malak:
You have to drop your need to make decisions and be in control because, again, the more you can relegate yourself to a servant leadership role and let the team make decisions, when they make decisions and now have to go back up that decision with execution, they're more likely to put their heart and soul into it. The more they feel like you are going to make the decisions, the less inclined they are to think through problems themselves, and then they'll keep bringing the problems back to you. So every time someone asks you a question that has a black and white answer, throw it back to them and ask them what they think, because that way you're coaching them to work it out themselves. And then the last thing that's really important is, I feel like it's really important to think through how your organization allows you to be different and take advantage of that differentiation.
Andrew Malak:
So for example, at Spaceship here, because we're small, we're not a large corporate, our customers are a little bit more forgiving. So you have a limited capacity to build experiences and you can't do all things at the same time. Understand that and take advantage of it, and get your team to also learn that. Because if you're trying to how the all edge cases, it will take a lot longer to get something to market and you might use a lot of the team's capacity to build edge cases. And you can't really afford that when you're in a start-up.
Andrew Malak:
So for example, we launched a new investment portfolio yesterday. We launched the Spaceship Earth portfolio, our first sustainable investment portfolio and it's a sign of more things to come hopefully in the sustainability space. But in launching that, we knew that we have a limitation in our experience or our product set today where each customer can only have one portfolio. We knew that existing customers would want to invest in sustainable investing, but our commitment to them is that it's in our backlog and it's actually the next feature that we're actually going to take to market.
Andrew Malak:
And in explaining that to our customers, they've been very understanding, that they know our throughput is limited but they also know that their voice is being heard and we are building the things that they're telling us about. So I would say that the best piece of advice to tell my young self is to make sure that you get the balance right between the voice of the customer. That's going to tell you all the hygiene things that your product lacks in terms of experience or gaps. And then get the balance between new strategic things that you can go after and new things that you can take to market, as well as a few Hail Marys every now and again. We call them moonshots. They may or may not work, but it's exciting, and if it works, can 10X your volume. And they are the things that are likely to go viral. So getting the balance right is very important.
Teagan Harbridge:
It's been wonderful, Andrew. I've definitely taken a lot away from our chat today, and I'm sure our audience will too. So thank you again so much for your time, and good luck.
Andrew Malak:
No Teagan, look, thank you very much. And it's been a pleasure speaking to yourself and Easy Agile, and I wish you guys all the best too.
Teagan Harbridge:
Awesome. Thanks Andrew.
Andrew Malak:
Have a good afternoon.
Related Episodes
- Podcast
Easy Agile Podcast Ep.13 Rethinking Agile ways of working with Diversity, Equity and Inclusion at the core
"The episode highlights that Interaction, collaboration, and helping every team member reach their potential is what makes agile work" - Terlya Hunt
In this episode join Terlya Hunt - Head of People & Culture at Easy Agile and Caitlin Mackie - Marketing Coordinator at Easy Agile, as they chat with Jazmin Chamizo and Rakesh Singh.
Jazmin and Rakesh are principal contributors of the recently published report "Reimagining Agility with Diversity, Equity and Inclusion".
The report explores the intersection between agile, business agility, and diversity, equity, and inclusion (DE&I), as well as the state of inclusivity and equity inside agile organizations.
“People are the beating heart of agile. If people are not empowered by inclusive and equitable environments, agile doesn't work. If agile doesn't work, agile organisations can't work."
📌 What led to writing the report
📌 Where the misalignments lie
📌 What we can be doing differently as individuals and business leadersBe sure to subscribe, enjoy the episode 🎧
Transcript
Terlya Hunt:
Hi, everyone. Thanks for joining us for another episode of the Easy Agile podcast. I'm Terlya, People & Culture business partner in Easy Agile.
Caitlin Mackie:
And I'm Caitlin, marketing coordinator at Easy Agile. And we'll be your hosts for this episode.
Terlya Hunt:
Before we begin, Easy Agile would like to acknowledge the traditional custodians of the land from which we broadcast today, the Wodiwodi people of the Dharawal nation, and pay our respects to the elders past, present and emerging, and extend the same respect to any Aboriginal people listening with us today.
Caitlin Mackie:
Today, we'll be joined by Jazmin Chamizo and Rakesh Singh. Both Jazmin and Rakesh are principal contributors and researchers of Reimagining Agile for Diversity, Equity and Inclusion, a report that explores the intersection between Agile business agility and diversity equity and inclusion published in May, 2021.
Terlya Hunt:
We're really excited to have Jazmin and Rakesh join us today. So let's jump in.
Caitlin Mackie:
So Jazmin and Rakesh, thank you so much for joining us today. We're so excited to be here with you both today, having the conversation. So I suppose today we'll be unpacking and asking you questions in relation to the report, which you were both principal contributors of, Reimagining Agility with Diversity, Equity and Inclusion. So for our audience tuning in today who may be unfamiliar the report, Jazmin, could you please give us a summary of what it's all about?
Jazmin Chamizo:
Absolutely. And first of all, thank you so much for having us here today and for your interest in our report. Just to give you a little bit of background of our research and how everything started out, the founder and the owner of the Business Agility Institute, Evan Leybourn, he actually attended a talk given by Mark Green. And Mark who used to be, I mean, an Agile coach, he was referring to his not very positive experience with Agile. So this actually grabbed the attention of Evan, who was a big advocate of agility, as all of us are. And they decided to embark upon this adventure and do some research trying to probe on and investigate the potential relationship between diversity, equity and inclusion and Agile.
So we had, I mean, a couple of hypothesis at the beginning of the research. And the first of hypothesis was that despite the positive intent of agility and despite the positive mindset and the values of Agile, which we all share, Agile organizations may be at the risk of further excluding marginalized staff and customers. And the second hypothesis that we had was that organizations who actually embed diversity, equity and inclusion directly into their Agile transformation and then strategy may outperform those organizations who don't. So we actually spent more than a year interviewing different participants from many different countries. And we actually ended up seeing that those hypothesis are true. And today, we would like to share with you, I mean, part of this research and also need to encourage you to read the whole report and also contribute to this discussion.
Terlya Hunt:
Amazing. And Jazmin, you touched on this a little bit in your answer just then, but I guess, Rakesh, could you tell us a bit more about what was the inspiration and catalyst for writing this report?
Rakesh Singh:
Yeah. So thanks for inviting once again. And it's a great [inaudible 00:03:51] talk about this beautiful project. The BAI was actually into this activity for a long time, and I happened to hear one of the presentation from Evan and this presentation actually got me interested into business agility and associated with DEI. So that was one thing. And second thing when Evan talked about this particular project, invited all of us, I had been with transformation in my job with Siemens for about three decades for a very long time. And we found that there were always some people, whenever you do transformation, they were not interested or they were skeptical. "We are wasting our time." And okay, that was to be expected, but what was surprising that even though Agile came up in a big way and people thought, "Okay. This is a solution to all our miseries," even though there was a focus on culture, culture was still our biggest issue. So it appeared to me that we are not really addressing the problem.
And as Jazmin talk about our goal and our hypothesis, and that was attractive to me that maybe this project will help me to understand why some [inaudible 00:05:12] to get the people on board in some of the Agile transformation.
Terlya Hunt:
Thank you. That was awesome. I think it definitely comes through in the report that this is a topic that's near and dear to all of you. And in the report you mentioned, there's a lack of consensus and some misalignment in defining some of these key terms. So thought to frame the conversation today, Jazmin, could you walk us through some of these key definitions, agility, diversity, equity, and inclusion.
Jazmin Chamizo:
That's a great question now, because over the last year, there's been a big boom on different topics related to diversity, equity and inclusion, I mean, especially with the Black Lives Matter movement and many different events that have affected our society in general. And with the rise of social movements, I mean, there's been a lot of talk in the area of diverse, equity and inclusion. And when we talk about agility, equality, equity and inclusion and diversity, I mean, it's very important to have a very clear understanding of what we mean with this terms. Agility is the mindset. I mean, it's really about having the customer, people, at the very center of the organization. So we're talking about agile ways of working. We're talking about more collaborative ways of working. So we can bring the best out of people and then innovate and put products into the market as fast as possible.
Now, when we were thinking about agility and this whole idea of putting people at the very core and customer at the very core of organization so we can respond in a very agile and nimble way to the challenges that our society presents at the moment, we found a lot of commonalities and a lot of similarities with diversity, equity and inclusion. However, when we talk about diversity, equity and inclusion, there's some nuances in the concepts that we need to understand. Diversity really refers to the mix. It refers to numbers, to statistics, all the differences that we have. There's a very long list of types of diversity. Diversity of gender, sexual orientation, ways of our thinking, our socioeconomic status, education and you name it, several types of diversity.
Now, when we talk about equality, I mean, we're talking about applying the same resources and support structures, I mean, for all. However, equality does not actually imply the element of equity, which is so important when we talk about now creating inclusive environments. With equity, we're talking about the element of fair treatment, we're talking about social justice, we're talking about giving equal access to opportunities for all. So it's pretty much about leveling the filed, so all those voices can be part of the conversation and everybody can contribute to the decision making in organizations and in society. So it's that element of fair treatment, it's that element of social justice that the element of equity has to contribute and that we really need to pay attention to.
And inclusion is really about that act of welcoming people in the organization. It's about creating all the conditions so people, everybody, can thrive and everybody can succeed in an organization. So I think it's very important, I mean, to have those definitions very clear to get a better understanding of how they overlap and how there's actually, I mean, a symbiotic relationship between these concepts.
Caitlin Mackie:
Yeah. Great. And I think just building on that, interaction, collaboration and helping every team member reach their potential is what makes Agile work. So your report discusses that there are lots of overlaps in those values with diversity, equity and inclusion. So I think, Rakesh, what are those key overlaps? It seems those qualities and traits go hand in hand. So how do we embrace them?
Rakesh Singh:
So if you see most of the organization which are big organization and being for about two decades or so, and you compare them with the startup organization, so in the traditional setup, normally people are working in their functional silos, so to say. And so the Agile transformation is taken care by one business function. It could be a quality team. It could be a transmission team. And DEI normally is a domain of an HR or people who enter the organization. And the issue is that sometime these initiatives, they are handled separately and the amount of collaboration that's required does not happen, whereas in a startup company, they don't have these kind of divisions.
So looking that as a basis, what we need to look at is that the organization should be sensitize that they work together on some of these projects and look at the underlying what is the commonality, and we can possibly either help each other or complement each other, because one example is, if I can give, it's very easy to justify an Agile transformation relating to a business outcome, okay, but any people related change is a very long-term change. So you cannot relate that to a business outcome in a shorter timeframe. So I call Agile and DEI as symbiotic. An Agile can be helped by a DEI process and DEI itself can be justified by having an Agile project. So they are symbiotic.
Now, what is the common thing between the two? So there are four items. I mean, there are many things which are common, but four things which I find are most important. Yeah? The first thing is respect for people, like Jazmin talked about being inclusive. So respect for people, both Agile and DEI, that's a basis for that. And make people feel welcomed. So no matter what diversity they come from, what background they come from, they're feeling welcome. Yeah? The second part is the work environment. So it's a big challenge to create some kind of a psychological safety. And I think people are now organizing, the management is now understanding that they think that they have provided a safe place, but people are still not feeling safe for whatever reason there. That's one thing.
The other thing is that whatever policies you write, documentation, policies or announcement, the basic things that people see, is it fair and is it transparent? Yeah? So I used to always see that if there are two people given bonus, if one person get 5% more, no matter how big is the amount, there's always felt that, "I have not got my due." Yeah? So be fair and be transparent. And the last one is that you have to invest in people. The organization need to invest in people. The organization need to invest in enabling them with opportunity to make use of new opportunity, and also grow and through learning. So these are four things that I can see, which actually can help both being an agile, and also having inclusive environment in the company.
Caitlin Mackie:
The report mentions that some of those opportunities to combine agile and diversity equity inclusion are being overlooked. Why do you think this is?
Rakesh Singh:
So I think that the reason why they're being overlooked is that, it's basically, educating the leaders. So it's just, if I'm in the agile world, I do not really realize that there are certain people related aspect. I think, if I just make an announcement, people will participate. Okay? So that's the understanding. On the other side, we got an input from quite a few responders saying that some of the DEI projects are basically words, are not really sincere about it. It's a waste of time. "I'm being forced to do certain training. I'm forced." So the sincerity part, sometime there's a lacking, so people have to be educated more at a leadership level and on at a employee level.
Caitlin Mackie:
I think a really interesting call out in your research is that many agile processes and rituals are built to suit the majority, which excludes team members with diverse attributes. Jazmin, what are some of those rituals?
Jazmin Chamizo:
Yeah, that's a great question. Now, if you think about agile and agile rituals and for example, I mean, daily standups, a lot of those rituals have not actually thought about diversity, or the design for diversity and inclusion. I mean, agile is a very on the spot and is a very, who can talk, type of rituals. But there's a lot of people, I mean, who might need more time to process information before they can provide inputs, so fast. So that requirement of processing information or giving input in a very fast manner, in daily standups, that might be overlooking the fact that a lot of people, with a different type of thought processing styles or preferences may need more time to carry out those processes.
So that would be, I mean, number one; the fact that it's very on the spot and sometimes only the loud voices can be heard. So we might be losing a lot of opportunities, trying to get feedback and input from people with different thinking styles.Now, also, if you think about organizations in different countries, where English is not the native language of a lot of people, they may also feel a lot of disadvantage. This happens a lot in multinational organizations, where people whose, you know, first language is English, they feel more confident and they're the ones who practically may monopolize now the conversations. So, for people who's first language is not English, I mean, they might feel at a disadvantage.
If you think about older employees who sometimes may not be part of an agile transformation, they might also feel that are not being part of the team and they may not have the sense of belonging, which is so important in an agile transformation and for any organization. Another example, I mean, would be people, who because of their religious belief, I mean, they need maybe to pray five times in a day, and I mean maybe a morning stand up might mean very difficult to adapt to, or even people with disabilities or language differences, they feel a little intimidated by agile. So there's a lot of different examples. And Doug report actually collects several lived experiences, by the respondents that we interview that illustrate how agile has been designed for the majority and for a more dominant type of culture and that highlights the need to redesign many of these rituals and many of these practices.
Caitlin Mackie:
Yeah, I think just building on that in your recommendations, you mentioned consciously recreating and redesigning these agile ways of working. What are some of the ways we can rethink and consciously create these?
Jazmin Chamizo:
Mm-hmm (affirmative). Well, the good news is that, during our research, and during our field work and the conversations that we had with some organizations mean there's a lot of companies and organizations that have actively implementing them different types of practices, starting from the way they're managing their meetings, their rituals, their stand ups, giving people an opportunity to communicate in different ways. Maybe giving some room for silence, so people can process their information or providing alternative channels for people to communicate and comment either in writing or maybe the next day. So it doesn't have to be right there on the spot., and they don't feel under that type of pressure.
Now, another example would be allowing people, I mean, to also communicate in their native language. I mean, not necessarily using English, I mean, all the time as, I mean, the main language. I think it's also important for people to feel that it can contribute with their own language, and also starting to analyze, I mean, the employee experience. We're talking about maybe using non-binary options in recruitment processes or in payroll. So, I mean, starting to be more inclusive in the different practices and analyzing, I mean, the whole employee journey. I mean, those are some examples that we can start implementing to creating a more inclusive environments. And the one that is the most important for me is encouraging leadership to intentionally design inclusive work environments through the use of, like creating environments that are really where people feel safe, where they have this. Psychologically safe.
Terlya Hunt:The whole section on exploring and challenging existing beliefs is so interesting. And I would definitely encourage everyone listening to go and read it. I could ask you so many questions on this section alone, because I think it was full of gold, and honestly, my copy is highlighted and scribbled and I read it and reread it, there was so much to absorb. The first thing that really stood out to me as a HR practitioner in an agile organization was this belief that focusing on one or two areas of diversity first is a good start. And from your research, what you actually found was that survey respondents found this method ineffective and actually harmful for DEI. And in your research, you also reference how important it is to be intentional and deliberate. So I guess, how do we balance this need for focus and creating change with these findings that being too narrow in our focus can actually be harmful? Might throw this one to you, Rakesh.
Rakesh Singh:
So actually, thanks to the reform data report, very interesting, in fact, we presented to quite a few groups. And one of the thing that I observed when we are talking about some of the beliefs and challenges, there were immediate to response say, "Hey, we do experience in our area." So, what we realized is that this whole aspect, as Jazmin talked about, many dimensions. So if you look at inclusiveness, and diversity and equity across organization, there are many streams, and many triggers. As diversity, we understand, okay, in very limited way, it may be gender, or it may be religion or country, but actually, it's much more in a working environment, there are many dynamics which are [inaudible 00:22:15]. So the challenges, what we saw was that if you pick up a project in a very sincere way and say, "I'll solve one problem, okay?" Let me say I solve problem of a region or language, yeah? Now the issue is that most of the time, we look at the most dominant and identify that problem.
So what happens is that you actually create an inequity right there, because there are other people they are suffering. They are, I won't say, "Suffering," but they're influenced by other factors of diversity and they felt, "Okay, nobody's really caring for me." Yeah? So you have to look at in a very holistic picture, and you have to look at in a way that everybody is on board, yeah? So you may not be able to find solution to every specific problem, but getting everybody on board, and let people work in some of the environment or either psychological safety or the policy level, so create an environment where everybody can participate, and issues can be different so they can bring up their own issues, and make sure they feel that they they're cared for. And that's what we actually observed.
Terlya Hunt:
And the second belief I thought was really interesting to call out was that this belief that we will adapt to somebody's beliefs if they ask. And your research found that not everyone is able to disclose their needs, no matter how safe the working environment, so that by relying on disclosure is the first step in the process,. Organizations will always be a step behind and, and also place the burden of change on marginalized groups. What are some things we can do, Rakesh, to remove this pressure and to be more proactive?
Rakesh Singh:
So there are a couple of things that we need to look at when we talk to people, actually, they discussed about the problem, and they also recommended what could be right, we are doing it. And we also discussed among ourselves. So one thing which was very clear that there was a little doubt about the sincerity of leadership. And so, we felt that any organization where leader was very proactive, like, for example, what is the basic reason, if I have a problem, if I talk about it, I am always worried what will happen when I disclose it? And is it the right issue to talk about it? So, these are the questions would inhibit a lot of people not to talk about it at all. So, that's where the proactive leadership can help people to overcome their inhibition and talk about it, and unless they discuss about it, you'll never know if there's a problem. So, that's the one thing. So, that's the approach.So there are a couple things that we could also recommend, is proactive leadership to start with, and something which can be done is there are a lot of tools available for the managers, yeah? People leaders, I would call it. Things like coaching, so you have a grow model where you can coach an individual person, even as a manager or as an independent coach, then having a facilitation techniques. When I started my career, they were not a training on facilitation, just going to the room and conduct the meeting. But they're very nice tools, facilitation techniques, which can be brought out to get people to participate, and so things like that can be very useful for being proactive and drawing people out of their inhibition. That definitely is with the leader. That's why we call it servant leadership. It is their job to initiate and take the lead, and get people out of their shell.
Terlya Hunt:
It ties quite nicely into the next question I had in mind. You both actually today have mentioned a lot of challenging beliefs, and calling things out. We need to build this awareness, and create safe spaces, and create psychological safety in our teams. What are some examples of how we can create safe spaces for these conversations?
Rakesh Singh:
The examples of someone creating safe places is ... I would say that educating people and the leaders. What I have seen is that if the leadership team recognizes that and educates the managers and other people ... You need to actually train people at different level, and create an environment that everybody's participating in the decision making, and they're free to make choices within, of course, the constraint of the business.
The focus, where I would put it, is that there are many educational programs and people would like to educated, because I normally felt that I was never trained for being a good leader. There was never training available. But these days we find that a lot of educational programs highlighting a various issue, like microaggression, unconscious bias, psychological safety. People should understand it. Things like being empathetic. These terminologies are there, but I find that people don't really appreciate it and understand it to the extent that they need to do, even though they are in a leadership position.
Caitlin Mackie:Thanks for sharing, Rakesh. I really love what you mentioned around proactive leadership, there. Your research found that 47% of respondents believed organizations who achieved this unity of Agile, and diversity, and equity, and inclusion will reap the benefits and exceed competitors. Jazmin, what did these organizations do differently?
Jazmin Chamizo:
Yes. That's a great question. Actually this ties very nicely with idea of servant leadership, inclusive leadership, and how leaders have this incredible challenge of creating workspaces that are psychologically safe, as Rakesh just mentioned. This is really everybody's responsibility, but it has a lot to do with a very strong leadership.
We found that several other organizations that we interviewed, they had a very strong leadership team, that they were really committed with diversity, equity, and inclusion in their agile transformation, and they were able to put DEI at the very core of the organization. That's number one, having a very strong leadership team that's actually committed to diversity, equity, and inclusion, and that does not perceive DEI efforts as isolated actions or initiatives.
This is something that we're seeing a lot nowadays. As a DEI coach and consultant, sometimes you see, unfortunately, several organizations that only try very isolated and very ... They don't have long-term strategy. What we have seen that actually works is having this committed leadership team that has been able to put DEI at the very core of their strategy.
Also a team that has been able to serve as an advocate in diversity, equity, and inclusion, and agility, and they're able to have advocates throughout the organization. It's not just one person's job. This calls for the effort of the whole organization and individuals to commit to DEI and be actively part of the agile transformation.
Also, I would say, leaders that embrace mistakes and embrace errors throughout the process. This is something that came up a lot during our conversations with people in different organizations, that in many cultures and in many organizations, mistakes are punished. They're not perceived as a source of opportunity.
One of the tips or best practices would be having leaders who are able to show the rest of their organization that mistakes are actually learning opportunities, that you can try things out of the box, and you can be more innovative. That even if you fail, you're not going to be punished, or there won't be any consequences because of that, and, quite on the country, that this is actually a learning opportunity that we can all thrive on.
Caitlin Mackie:
Yeah. I completely agree. What benefits did they see?
Jazmin Chamizo:
They definitely saw a greater working environment. This is something that was quoted a lot during our interviews with respondents, that individuals saw that they had the chance to try new and innovative ideas. Definitely greater innovation, more creativity. Business morale actually ultimately went up, because they saw that the organization was actually embracing different perspectives, even if they fail. This definitely called for greater innovation.
I would say innovation, more creativity, and a better working environment. Absolutely new products, new ideas. That if you think about the current circumstances with COVID, this is what organizations have to aim at. New products, more innovation to face all the challenges that we have nowadays.
Terlya Hunt:
Powerful things for the listeners to think about. Here at Easy Agile, our mission is to help teams be agile. Because we believe for too long the focus has been on doing, when the reality is that Agile is a constant journey of becoming.
There's a specific part in the report that really stood out to me that I'd like to read. "Agility is a journey with no fixed endpoint. The road towards creating diverse, equitable, and inclusive environments is the same. Agility and DEI can be pursued, but never fully achieved. They are a process of ongoing learning, reflection, and improvement. A team cannot enter the process of improving business agility or DEI with a mindset towards completion, and any model that unites Agile and DEI will ultimately be ineffective if those taking part are not ready to embark on an ongoing quest for self improvement."
I absolutely love this quote. Rakesh, let's explore this a little bit further. What more can you tell me about this?
Rakesh Singh:
Actually there's an interesting thing that I would like to share to start with. We wanted to look for a organization who would help us interview their people and talk to their people. The way organizations responded ... Some responded, "Shall I allow my people to talk to somebody? It could be a problem." But then we got other organizations, they were actually chasing us. "We would like to be part of this, and we would like to get our people interviewed." They were very positive about the whole thing.
I happened to talk to the DEI corporate manager, a lady, and the way she was talking was ... She was so much, I would say, passionate about the whole thing, even though at least I felt that they were very high level of awareness of DEI. But the quest for learning and finding out what they could do better was quite astonishing and quite positive.
That's where my answer is, is that ... If you look at the current pandemic, and people realized that, "Okay. We have to work from home," initially some people found it great. It's a great thing. Work-life balance. "I can attend my home." But after some time they found it's a problem. There's other problem.
The point is that, in any organization, where it's a business or a social life, or people, it just keeps changing. There's no method or policy which is going to be forever valid. There's a continuous learning process that we have to get in.
What we need to do is focus on our goal that we want to achieve. Depending on the environment, that's what we call business agility. Now bring it to people as well, because it is a people ... We talk about customer centricity, and all that. But finding it's the people who are going to deliver whatever organization want to. You have to see how their lives are getting impacted.
We are discussing about getting people back to office. The problem is that, a city like Bangalore, it's a very costly city and very clouded city. People have gone to their hometown and they can work from there. Now, to bring them back, you have to approve them back again. To cut short the explanation, our life is changing, constantly changing, and technology and everything is putting ... People have to look at methods and approach of how they can be adapting themself on a continuous basis.Learning is a continuous process. In fact, when I got into Agile and people ask me, "How many years of experience you have?" I generally say five years, because anything that I did before five years is actually the wrong practice. You have to be continuously learning, and DEI and Agile is no stranger to this situation.
Caitlin Mackie:
I love that. I think fostering that continuous learning environment is really key. I suppose, on that, a few of the recommendations from the report are centered around getting deeper training and intentional expertise. Jazmin, what further recommendations, or courses, or practitioners are there that people can engage with after this episode?
Jazmin Chamizo:
Sure. An important part of our report was a series of recommendations to the entire agile community, and practitioners, to organizations, and agile coaches. You can see that. You could get more specific information in our reports. I would like to encourage all of you to read. Definitely when it comes to agile coaches and consultants, we're encouraging people to learn more about diversity, equity, and inclusion because one of the insights and the learnings we drew from this research is that diversity, equity, and inclusion is not specifically included in the agile world.
When we talked to the respondents in many different countries, they did not spontaneously made the connection between agility, Agile, and diversity, equity, and inclusion. But the more we talk about it, they discovered that, indeed, they were very closely overlapped. There was a symbiotic relationship between them, because you're putting the person and everything that relates to that individual on the very core of the organization, on the transformation.
Definitely we do encourage ... Leaders and agile coaches need to start learning more about our DEI, building that proficiency, learning more about unconscious bias and the impact of unconscious bias, and discrimination, and racism that we'll continue to see in organizations. They're more mindful of those voices that are not being heard at the moment in the present conversations. They can learn different techniques or different methods to be more engaging and more inclusive.
When it comes to the agile community in general and influencers, it is important to mention that Evan Leybourn, the founder of the Agility Institute, is having at the moment some conversations with important institutions in the agile community, such as the Agile Alliance, because we are looking for ... That's what Gen Z-ers are looking for. There's a big call out there for organizations to embrace this type of transformation, but putting DEI at the very core of the organization. That's what I would like to say.
Contribute to the discussion. This is a pilot project. That we are hoping to conduct more research on other DEI areas related to agility. We would like listeners to be part of the conversation, and to contribute with their experience, to improve the state of agility in the current moment.
Caitlin Mackie:
Thank you both so much for joining us today. Thoroughly enjoyed our conversation. I can't wait to see how Agile and diversity, and equity, and inclusion evolves in the future. Thank you.
Jazmin Chamizo:
Thank you so much for having us. It's been a pleasure.
Rakesh Singh:
Thanks a lot to both of you. It was nice to share our experience. Thank you very much.
- Podcast
Easy Agile Podcast Ep.5 Andrew Malak, Chief Product Officer at Spaceship
"I really enjoyed my conversation with Andrew Malak. We talk integrating agile techniques and tips on how to achieve a culture of accountability"
Andrew is a firm believer that the customer trusts your business by joining, and you have an obligation to repay that trust by helping them achieve their outcomes.
Enjoy the episode!
Transcript
Teagan Harbridge:
Welcome to another episode of the Easy Agile Podcast. I'm Teagan, head of product here at Easy Agile. And we've got a really exciting guest on the show today, Andrew Malak from Spaceship. He's the chief product officer. Andrew is a true believer in creating products and experiences that solve customer problems. He believes that the customer trusts your business by joining, and you have an obligation to repay that trust by helping them achieve their outcomes. In his current role, Andrew aims to help people take control of their wealth from a young age, educating good money habits and helping people invest where the world is going. Andrew is a family man who loves his time with his wife and children. And believe it or not, he uses agile techniques in his personal and professional life. Andrew is an economics geek. He plays and coaches soccer, football. He's a big Liverpool supporter, loves to travel, loves amazing architecture, and loves working with children.
Teagan Harbridge:
There were so many takeaways from my chat with Andrew that I really struggled to pair it down to three. But if you say tuned, here are some of the things that you're going to learn from our chat with Andrew. Why we should stop using the term agile transformation and start calling it an agile evolution. Why it's important to be open-minded to our own limitations so to break the old mindset of protecting original scope. And tips on how to achieve a culture of accountability. So I hope you enjoy. Andrew, can you tell me a little bit about Spaceship?
Andrew Malak:
Oh, fantastic. Well, thank you very much for, first of all, having me, Teagan. Spaceship is a business that's on a journey to make good money habits and investing accessible to all people. So what we look for is trends to do with industries or companies who are building the future of both industry or economies. We invest in them for the longterm, we break down barriers of entry for people, we give them a fee-free product under $5,000, no minimum investments. It's really easy to sign up. You simply download an app and you sign up and make one product selection decision, and you're done. You can start investing on autopilot. We allow you to also invest your superannuation in a not too dissimilar way.
Teagan Harbridge:
So tell me a little bit about who your target customer is, then. Because it seems like you're trying to make something quite complicated accessible for maybe first time investors.
Andrew Malak:
Well, you're absolutely right. There's a niche segment of people out there at the moment, millennials or even gen Zs, that we just don't think have been well serviced by the incumbents. And what we're trying to do is resonate with these young people as much as possible. We're trying to reduce industry jargon and really make things simple to them, because investing doesn't have to be complex. It's really about a lot of discipline around, if I can manage my personal P&L, or money in, money out, then I can create a cash buffer that can go into my assets column on my balance sheet. That's really what we're trying to do. And that kind of language, if we can get it right, can really simplify things that have typically been in the hands of financial advisors and accountants and give it back to everyday Australians who are starting out in their investment journey.
Teagan Harbridge:
Yeah, awesome. And you've been on quite a journey before landing in the FinTech space as the Spaceship CPO. So can you tell me and our audience a little bit about what that journey has looked like?
Andrew Malak:
Oh, where do I start? If you asked a graduate Andrew Malak what he'd be doing now, I don't think I would've been speaking about this because at that point in time in my career I didn't know this space would actually be around, if that makes sense. So I'll go back to my younger years, and I always thought I was going to be an architect. I had this fascination with bridges and I wanted to design things and see them come to life. And let's just say that I do that in different ways right now, but I started out working in CommSec on the trading floor. I moved on to work as a business analyst, and that's where I started my critical thinking into how businesses work and how things can be made more efficient.
Andrew Malak:
I dabbled in teaching for a little bit, I taught high school economics and religion for a little bit. And then I eventually landed in a product role at St. George Bank prior to the merger with Westpac. At that point in time, the light bulb really came on. I realized, "Hey, I like creating things. I like to change things. I don't like to just do things," if that makes sense. And that wondering mind that doesn't like the conform was finally let loose, if that makes sense. And I haven't stopped enjoying it. I loved my time at Westpac, made lots of friends, worked on really cool, successful projects, and implemented lots of things that had great results. Worked on lots of things that have failed miserably and learnt a lot out of that. And when the opportunity at Spaceship started to surface late last year, it was just too good an opportunity to not really come in and have a go. So yeah, it's been quite the journey.
Teagan Harbridge:
Yeah, wow. And I love a good failure story. And you said you've had lots. Can you think, just off the top of your head, what one of those big failures has been?
Andrew Malak:
Where do I start? I think our first attempt at taking a digital experience to allow customers to acquire a product online was quite a failure that taught us a lot. We basically took the systems that our back office staff used and just made it available to customers. And the real good learning out of that is there was a lot of traffic and a lot of demand, but not enough completion ever. And the best learning that came out of that... This is back in 2006, so internet speeds were just starting to pick up. Broadband was starting to go mainstream and customers' trust around doing more transactions that used personally identifiable data was starting to normalize at that point in time. Up until then, people quite reserved thinking, "I'm going to lose my personal data," et cetera. So when we decided to do that, we saw that there was a lot of demand but we quickly came to the realization that we used to train staff for four to six weeks on how to use the systems before they knew how to service customers using them.
Andrew Malak:
But then we've deployed it into production for customers to self-service and realized quite quickly that the experience for customers had to be much more guided than the experience for a staff member. This is where the evolution of usability or design thinking started to come in. We started thinking of, "Well, how do we make these things so easy that a first-time user can go end to end and not encounter friction?" And this is where our understanding of design principles, customer testing using verbatim and anguage that can resonate with a first-time user becomes critical to the execution. It's not just good systems but it's good user experience sitting on top of systems.
Andrew Malak:
That's probably the one that resonates with me the most because I've held that to a very high regard throughout my whole career. Now everything I do I think of, "Where's the friction? How do we make sure there's no friction? What's the customer going to feel throughout this experience? How are we creating unnecessary anxiety in that experience for the customer, and how do we move that away? How do we become more transparent but still be simple?" And yeah, that's probably the one that resonates the most.
Teagan Harbridge:
Seems like a tremendous learning opportunity early enough in that project and something that's stuck with you since, so great learning opportunity.
Andrew Malak:
Absolutely.
Teagan Harbridge:
We've got a ton of customers who are at all stages of their agile transformations, and I know that this is something that you've had experience with if we go back to your St. George, Westpac days. Can you give our audience any tips or stories that you encountered when you were going through those agile transformations? What lessons can you share with our audience?
Andrew Malak:
Oh, I have lots of lessons to share, actually.
Teagan Harbridge:
This is what I love.
Andrew Malak:
Look, I like to position it more as agile evolution more than agile transformation because no matter what you try to do, you're not just going to drop waterfall and become agile next morning. Honestly, I've seen so many attempts and every single time I see that the graduality of the change is a better predictability of the final outcome that you're going to land. So ultimately the Holy Grail that everyone's aspiring to is that, as a leader, you can rock up to a team stand up unexpected and then, without being told who is in what role, who the product owner is, who the engineer is, who the QC is, who the designer is, it becomes hard for you as the leader to work out who's who because at that point in time the team is so well converged on customer outcomes that they will self-organize themselves around what each person needs to do.
Andrew Malak:
And most of the language being used is really around, what are we trying to define the customer? What's the best thing to do within the capacity that we have to deliver this feature to market as quickly as possible, capture value for the customer and the business as much as possible? This takes a long time to get to, where you can start normalizing to a standardized, common set of goals, common cadence, and common ways of working. And I think it's ultimately about how much empowerment you can give people and how much as a leader you can relegate yourself in the background to allow them to work it out themselves as long as you're coming in and nudging things along the way and helping people course correct along the way. So the good news is that I actually think at Spaceship, we're pretty close to getting there.
Andrew Malak:
We have been running scrum and we have been running sprints for a long time, but it has been largely ceremonials. But over the last quarter, we've done a really good job at embedding more cross-functional people into these teams. But the goal for us is that now we feel like our throughput has actually increased and that the constant flow of information between the teams is becoming more natural and there is actually less ambiguity between the teams around, "All right, we built it this way. The API is no longer consumable. It doesn't fit what we're trying to do from our front-end and there's less back and forth." So we can really see that the amount of friction between persons in the team is really starting to reduce dramatically and we're starting to see that throughput really increase. Having said that, the best way to go about an agile transformation is just get started.
Andrew Malak:
You can sit and plan out things and plan towards utopia as much as you want or you can actually just get going. So when I say by get going, I say you have to start by getting buy-in from all the leaders of the different cross-functional teams, because if you don't have that buy-in at the leadership level, it's just not going to work because there's going to be blockers, there's going to be escalations. And if all these things result in conversations around, "Should we keep doing this?" Or, "Hey, maybe this is not the right thing to do." That needs to be off the table really early on and it needs to be a total commitment at the leadership level that we're going to make this work and whatever we encounter we're just going to fix forward. Once you have that commitment at the leadership level, you need to very clearly define the values that the team is going to be handed to work with, because agile itself, it's not a process, it's a set of values that the team needs to just take and start working with.
Andrew Malak:
So we could go and rattle individuals and interactions over processes and tools or working software over comprehensive documentation. Well, give these to the team and they're going to say to you at day one, "We can't go to all of that straight away." So they might actually say that day one, "We're still going to need some documentation because we're not comfortable yet. We don't understand the language of the other people in the scrum team well enough to be able to go and actually code off the back of a conversation." But by the 10th sprint, the 20th sprint, that misunderstanding of what the product owner wants or what the designer is trying to achieve in an experience starts to become embedded in the mind of the engineer.
Andrew Malak:
The engineer understands the customer a lot more, and then you can make do with less process and less documentation and less negotiated outcomes and more commonality across the team. The other thing that then starts to kick in at that stage is that ability of the team to pivot in response to a change and not see that as a threat to what they're trying to achieve. The old ways of working was, define that scope, protect that scope, and not let things disturb that scope, whereas if you're halfway through a project and you get some really good information that tells you that maybe you are not on track to achieve a good outcome, you should be welcoming that. And the team itself in the beginning is going to find that an irritation, but over time they'll become more comfortable with pivoting off the back of new information.
Teagan Harbridge:
Yeah. It's a big mindset shift. I was just having a discussion today about, where does being agile and being reactive, where's that line in the middle. And when does taking information and pivoting because you think something will be better, when can we break that mindset of, "Oh, we're just being reactive?" No, we're being responsive.
Andrew Malak:
Yeah, yeah. And look, I think the word reactive itself naturally has a negative connotation to it, but agility in mindset allows you to flip that on its head and say that no one can work things out in totality to 100% of what's possible, so being open-minded to our own limitations first and foremost allows us to acknowledge that when new information comes in, it is because we didn't think through the solution 100%, but let's also be okay with that because no one can. So I think it's flipping on its head and acknowledging it upfront and saying that this is going to happen, but when it comes we will assess the information we have with the capacity we have with how far progressive we are and make a decision that's right for us, for the customer, and for what's possible.
Andrew Malak:
So I take it as the more information you get along the way, the more reinforcement of, are you doing what's right or should you pivot and change at that point in time? The other thing that happens really early on is that if you as a leader can create a really clear vision around customer outcomes and establish your first cross-functional team and hand over that vision to the team, it becomes theirs. Don't hand over the backlog to the team. Don't give them a ready backlog, just give them the vision and then tell them, "You guys work out what your backlog looks like." When they come up with their own backlog, as long as you as a leader don't see that it's just a list of Hail Marys in it and there is a fair bit in there that is well spread out between hygiene things, strategic things, and a few moonshots and the balance is right, if the team has come up with their own backlog, the motivation they have to build their own ideas just goes through the roof.
Andrew Malak:
And that's what you want to achieve. You want to achieve clarity that the work fits with the vision and the motivation that you get out of the backlog being created by the team itself gets you that throughput enhancement. The other thing that you're going to struggle with really early on is chunking things down to fitting within the sprint cadence. I think that's one that's often been my biggest challenge when moving towards agile practices early on. Typically in the first few sprints, you always have overruns and things don't complete in the sprint because we end up thinking we can do more than we can and it takes us a while to work out, in wrapping up something that becomes shippable in a sprint, you probably take a little bit less in that sprint because you've got to test it or you've got to do a release in that sprint, or you're going to do a PIR in that sprint, or you're going to do a lot of retros in that sprint. Start to sort of formulate what you're going to take through the next planning cycle.
Andrew Malak:
So you've got to budget to that capacity, and I'll find that teams underestimate the magnitude of that work. So be okay with that. Overruns in the first few sprints don't mean you've failed, it means you're learning how to plan better. And then make sure your retros and your pivot off the back of that into your next planning sessions is taking information that is now new to you, and making sure you're working with it. I think as the leader, though, you have to set the expectations that teams can make mistakes and that it's a safe environment.
Andrew Malak:
And I've seen many agile... I was about to use the word transformation, even though I've just said I don't believe in transformation. Any teams that are adopting agile principles expecting that in their first few sprints they don't have any hiccups, and that if throughput falls in the first few sprints, then there's a bit of a, "Oh, well you told me this thing was going to increase our throughput." Yeah, but not straight away. So I think just being realistic with yourself and what's possible, and that shift in itself, until it normalizes, takes a bit of getting used to. The teams need to know it's a safe environment, that if their productivity suffers, if they make mistakes or if they break things, it's going to be okay. We'll fix forward.
Andrew Malak:
But then also there comes a point in time where we have to be very clear about the culture of accountability around using that capacity really well. So what I've found, that the best use of that is the showcase. And what we've done at Spaceship, because we're trying to reduce the amount of ceremonies, we've combined both the planning playback in a sprint as well as the showcase into the same ceremony. So what we do is we play back what we built last session using a demonstration of working software and comparing the amount of work we've executed versus what was planned in the previous sprint. We're saying we've got 80%, 90% through the work and this is what it looks and feels like, and this is what we're deploying to the customer. Then we actually showcase what we plan to do in the next sprint.
Andrew Malak:
And that's part of the showcase, is our hand on heart commitment to, "This is what we as a team are committed to doing in the next sprint." And then that accountability to the organization becomes something that keeps us on track throughout the sprint. As distractors or things that are not committed in the sprint come our way, we quickly think about, all right, can we accommodate these things? Do they need to be done? Are they going to take us off track with what is planned? Are they important enough? Is it a major defect of production, and can customers no longer access our app? Well, drop what you're doing and attend to that. Otherwise, if it's not material, keep focused on the work that you've committed to in front of the organization.
Andrew Malak:
After this you're going to start to experience some growing pain, and the growing pain is good because it means that agile is working and more teams or more feature opportunities become possible for the business. There's going to be a lot more hype around moving to agile. Other teams are going to come across and say, "Oh, how do we piggyback off what you're doing?" Et cetera. This is good. This is good, but what it means now is that some new risks are going to actually start to be introduced. Working with common code, common dependencies, or even common people being needed to be doing multiple things just means that you now need more coordination. I'd say to anyone who reaches this point in time, this is where people feel compelled to start introducing some new roles, coordination roles. And I'd just say, be careful because that can start add to your overhead really quickly.
Andrew Malak:
I find the best way to ensure that teams continue to be in sync is with the right dialogue at the right level with the right rhythm. And this is where I think keeping it simple to just the scrum of scrums works really well. I like the scrum of scrums to be balanced between both product owner and tech lead from each team being present, and a cadence of one to two times per week works really well. And as long as the product owners across the teams and the tech leads across the teams know what the other teams are working on, know what could impact their own work from a release perspective or scheduling perspective or an environment perspective, I think that tends to work really well as well.
Teagan Harbridge:
Yeah, wow. Lots of nuggets in there and certainly things that resonate with our experience here at Easy Agile, being a small company that's grown really quickly. So I can definitely relate. We've had conversations about, do we introduce new roles into this company? We've introduced a new cadence of meeting rhythms only the last couple of months, so we're going through these things too.
Andrew Malak:
Absolutely. Absolutely. What have been your biggest learnings so far?
Teagan Harbridge:
I think that you cannot underestimate communication, and it really does come back to that cadence and that rhythm with the team. And we're experimenting at the moment with a daily huddle where we're talking about, how do we embed showcases more regularly in our cycles? We've got a big demo at the end of the cycle. How can we make that a more ingrained part of our culture? And it really does come back to that culture of accountability as well. So yep, it's all resonating.
Andrew Malak:
Yeah, absolutely. Look, you can go to whatever industry you want but the problems are usually similar. And the great thing is that having these conversations is very important to fast-tracking your way forward, because your problem is not unique to you. Someone else has seen it in someone else has figured out a way. And I think what I like about the FinTech industry is that we compete on products and services, but there's a lot to learn from each other. And even if you just go outside of FinTech, there's a lot to learn from other industries who have adopted agile practices.
Teagan Harbridge:
If we take a bit of a flip, we've gone from your professional career and your experience into a more personal level. You mentioned that you use agile techniques outside of work. So I'm not sure if many others are in the same boat, but can you elaborate on this? What does that mean? What does that look like?
Andrew Malak:
Okay, I hope you don't think I'm extremely weird. We actually have a family campaign. So I guess if I go back to how we've come to actually doing this. Becoming parents, we would look at our children and see so many things that we want them to be better at. And in trying to give them constant feedback, which felt like the feedback was so much that it's all being drowned out because there's so much of it. In fact, my oldest son actually gave me that feedback. He goes, "Dad, why don't we focus on one thing at a time?"
Andrew Malak:
And I was like, "Wow, okay." For a ten-year-old to tell me that, that was amazing. So we came to realize that we needed to narrow and focus on one improvement area at a time, and we don't move on to the next one until we've actually closed out the first one. For example, my oldest son, very clever boy. We're trying to focus with him on the discipline of process over just getting the answer right, because he is clever and nine times out of 10, ask him a question, he's got the answer and he just wants to say it.
Andrew Malak:
But we've started to try to break down the question and work more on the process with him so that in following the process, coupled with his natural ability, we will get more answers right more often. And that's what we're working through at the moment. So our family's scrum wall at the moment has a mix of things on it. Everyone has their own swim lane, and in each swim lane there are a few tasks, some related work or study, some relating to household chores, some related to health or exercise, and some related to acts of kindness. And what we aim to do is make sure that we're moving things across in all four categories every single day. So yeah, you can use agility wherever you'd like but I think that mindset in general, that if I wake up every day and do things that make me better than I was yesterday, then I'll get to keep moving forward in my personal life as well as my professional life.
Teagan Harbridge:
And do you have WIP limits?
Andrew Malak:
We don't at the moment, and we're not doing showcases at the moment. We'll see how we can introduce them in the future.
Teagan Harbridge:
And how was the introduction of a Kanban board at home? How was that received by the family? Have they enjoyed it, has there been any feedback?
Andrew Malak:
Well, it wasn't actually planned. It started by just sticking some Post-its up on the fridge to remind us of stuff. And then one day I said to my wife, "You know what? This reminds me of what we do at work. Why don't we formalize it?" She had a bit of a chuckle but then one day she came back and then she found it there. So yeah, it wasn't really planned.
Teagan Harbridge:
Awesome. And you've already been super generous with your time so I'll close it out with one final question. What advice do you wish someone would have given you when you took the leap from product management into product leadership?
Andrew Malak:
Yeah, that's a really good question. I think first and foremost, that you've got to make sure that you drop your need for perfectionism, because first and foremost, you might have been the best product manager yourself. You might have been amazing. And I'm not saying I was, but if you were and you step up in leadership role, you're going to have people of different abilities working for you. And what you need to understand is that they're going to need some time learning their role and learning their trade. And just don't get in the way of them learn. So for example, you might see someone doing something that may not be the best or most optimal use of that capacity in that sprint. You might feel the urge to jump in and course correct. But if you let them go and just hear their feedback post the retro, they might've had that learning themselves, and a learning that they get for themselves rather than being told by their leader is going to be much more useful for them.
Andrew Malak:
You have to drop your need to make decisions and be in control because, again, the more you can relegate yourself to a servant leadership role and let the team make decisions, when they make decisions and now have to go back up that decision with execution, they're more likely to put their heart and soul into it. The more they feel like you are going to make the decisions, the less inclined they are to think through problems themselves, and then they'll keep bringing the problems back to you. So every time someone asks you a question that has a black and white answer, throw it back to them and ask them what they think, because that way you're coaching them to work it out themselves. And then the last thing that's really important is, I feel like it's really important to think through how your organization allows you to be different and take advantage of that differentiation.
Andrew Malak:
So for example, at Spaceship here, because we're small, we're not a large corporate, our customers are a little bit more forgiving. So you have a limited capacity to build experiences and you can't do all things at the same time. Understand that and take advantage of it, and get your team to also learn that. Because if you're trying to how the all edge cases, it will take a lot longer to get something to market and you might use a lot of the team's capacity to build edge cases. And you can't really afford that when you're in a start-up.
Andrew Malak:
So for example, we launched a new investment portfolio yesterday. We launched the Spaceship Earth portfolio, our first sustainable investment portfolio and it's a sign of more things to come hopefully in the sustainability space. But in launching that, we knew that we have a limitation in our experience or our product set today where each customer can only have one portfolio. We knew that existing customers would want to invest in sustainable investing, but our commitment to them is that it's in our backlog and it's actually the next feature that we're actually going to take to market.
Andrew Malak:
And in explaining that to our customers, they've been very understanding, that they know our throughput is limited but they also know that their voice is being heard and we are building the things that they're telling us about. So I would say that the best piece of advice to tell my young self is to make sure that you get the balance right between the voice of the customer. That's going to tell you all the hygiene things that your product lacks in terms of experience or gaps. And then get the balance between new strategic things that you can go after and new things that you can take to market, as well as a few Hail Marys every now and again. We call them moonshots. They may or may not work, but it's exciting, and if it works, can 10X your volume. And they are the things that are likely to go viral. So getting the balance right is very important.
Teagan Harbridge:
It's been wonderful, Andrew. I've definitely taken a lot away from our chat today, and I'm sure our audience will too. So thank you again so much for your time, and good luck.
Andrew Malak:
No Teagan, look, thank you very much. And it's been a pleasure speaking to yourself and Easy Agile, and I wish you guys all the best too.
Teagan Harbridge:
Awesome. Thanks Andrew.
Andrew Malak:
Have a good afternoon.
- Podcast
Easy Agile Podcast Ep.30 Aligned and thriving: The power of team alignment
"Every time I meet with Tony, I'm always amazed by his energy and authenticity. In this conversation, that really shone through."
In this episode Hayley Rodd - Head of Partnerships at Easy Agile, is joined by Tony Camacho - Technical Director Enterprise Agility at Adaptavist. They are delving into the highly discussed subject of team alignment, discussing what it means to have synchronized goals, cross-functional collaboration, and a shared agile mindset.
They also cover the fundamental building blocks to get right on your journey to team alignment, like the power of listening and embracing mistakes as learning opportunities, stressing the importance of following through on retrospective action items + so much more.
We hope you enjoy the episode!
Share your thoughts and questions on Twitter using the #easyagilepodcast and make sure to tag @EasyAgile.
Transcript:
Hayley Rodd:
Here at Easy Agile, we would like to say an acknowledgement of country. This is part of our ongoing commitment to reconciliation. Easy Agile would like to acknowledge the traditional custodians of the land from which we broadcast and meet you today. The people of the Darova-speaking country. We pay our respects to elders past, present, and emerging, and extend the same respect to all Aboriginal, Torres State Islander and First Nations people listening in today. Hi all and welcome to the Easy Agile Podcast. My name is Hayley. Here's a little about us here at Easy Agile. So we make apps for Atlassian's Jira. Our applications are available on Atlassian's marketplace and are trusted by more than 160,000 users from leading companies worldwide. Our products help turn teams flat Jira backlog into something more visually meaningful and easy to understand.
From sprint planning, retrospectives and PI planning our ups are great for team alignment. Speaking of team alignment, this is what this episode is all about. Today I'm joined by Tony Camacho. Tony is the technical director of Enterprise Agility for Aligned Agility, which is part of the Adaptiveness group. I've met Tony a few times during my time here at Easy Agile and have learned that he's one of the most generous people along with being funny and a clever human being who is incredibly knowledgeable about Jira and a bunch of other agile related topics. It's really wonderful to have Tony on the podcast today.
Hey, everyone, we've got the wonderful Tony Camacho on the podcast today. This is our first time recording from our Easy Agile Sydney office, which is super cool. Tony, I'm not sure if you know, but Easy Agile is based out of a place called Wollongong, which is just south of Sydney. But we've got a Sydney office because we've hired a bunch of Sydney team members recently who wanted a place to come and hang out with each other. So we created this space, but it's 7:00 AM in the morning, so I'm all alone right now. That's how much I love you. So Tony, let's get started on the questions. Team alignment. What does it mean for a team to actually be aligned?
Tony Camacho:
So for us in an agile space that we're having, it's a collective understanding, a synchronization of your team members towards goals, principles, your practices that you're going in. Even more so I would even go down to the point of cadence, you would have those synchronizes. So it's a matter to be consistent with your agile principles and values, your mindset, your shared goals and vision, your synchronized work practices, DevOps, [inaudible 00:02:44], how we're going to put this out. Cross-functional collaboration between the teams, getting your tea shaped partners/teammates shining at that moment, learning from each other, roles, responsibilities things of that type. That's what it means to me. It really means.
It's all about human beings and at that point, having everybody aligning and working to our common goal, that objective that we want to do for the business partner. There's the gold that we're all after as a team. Does that make sense for you guys? We have the same objectives for this initiative and our practices. And finally for me, which I know this is not typically is we're coming to an agreement on the tools we're going to use and how we're going to use them and have a system source record where we know where we can get our troops, our dependencies, find out which teams do have capacity and move forward from there. That would be my overall definition of an agile team.
Hayley Rodd:
Wow.
Tony Camacho:
And teams.
Hayley Rodd:
You've had lots of experience over the years. I guess where my mind goes when you say all those really wonderful things about team alignment is that in my experience when team alignment is when people get it right, it's super great. When people get it wrong, it's really hard. And I actually think it's pretty hard to get team alignment right. You got to really work at it. What's your experience in that?
Tony Camacho:
To me it's like it can be a bad marriage or a great marriage, but it needs work. As we know, all relationships need work. We're human beings, we're not the same. Each one of us brings something to the table of value. So let me give you one example that I've lived with on a team. I'm an extrovert by nature, and I'm a developer, an engineer and typically that is not two skill sets that you hear together. So I've had to learn that when I'm working with my teammates that happen to be sometimes introverts slow down, listen, wait. They've also had to try to learn to respond faster because as an extrovert, if I ask you a question, all of a sudden I'm looking at you, I'm not getting a response, I'm thinking you're not understanding the question. I rephrase the question and now you're in a deficit to two questions.
And now I'm even worse because now I'm like, "Hayley isn't understanding me. What's happening here? Let me rephrase it again." And it can easily fall apart. What I have seen when teams aren't in alignment is that the team isn't a team any longer. It's miserable to go to the team. It's miserable to come into work, when the team is truly aligned, you're rocking and rolling. It's a feeling like you've never had. It's hard to explain to people that when you see the team, because you know it when it's working and you obviously know when it's not working, you're starting to miss deadlines. Integrations aren't happening on time. You don't have a single source of truth. You start having people explaining the same thing in two, three different matters, different priorities. We're not working from the same hymnal. The thing that I took from my... I'm an SPC, so as an instructor, the one thing I always try to explain to everybody, you may have the best of everything out there, but that's not necessarily mean it's going to work together.
So you have to have that type of understanding, how we're going to work together, what is our priorities, what's the tool sets we're going to have and what is our values as a human beings to this team if that... I'm hoping that helps describe some of the things that I've seen that have gone really bad. I have seen it at, I can share a customer that I have seen it gone, but we started off with good intentions. It's a financial institution in the United States and they were trying to make the jump to mobile applications. And at first we were on the same page as a team, but they decided that they didn't believe that cadence was required to be the same across the board. They didn't believe that we could use the same one tool set, we could use multiple different tool sets.
They had spreadsheets flowing all over the place. And what was happening was we lost trust. We were redoing work, there was ambiguity everywhere. We were misaligned and we started paying for it because our customers started complaining. They could see it in the quality of the work. One team had one schema, one background, one type of... You could see the difference when they integrated, it seemed like it was two applications being put out there mashed together. And when you're misaligned, that comes through very, very quickly in your work. There's a saying that we have here. There's a scrum master, I know her name was Sophia Chaley, one of the best I ever met. And what she will always tell people is what a team delivers is what the team is doing is learning. It's building knowledge, it's expressed as code. When we're misaligned, we're learning different things and we're expressing it differently in the code, if that makes sense.
Hayley Rodd:
Like thinking about the fundamental building blocks of team alignment, is there something that a team really needs to get right to be successful at alignment? And what is that in your mind?
Tony Camacho:
Oh, that is for sure. They had to get that right. First of all, the size of the team.
Hayley Rodd:
Yeah, okay.
Tony Camacho:
Human beings, and I'm not referring back... Going back to say for our scrum practices, I am a CSM. I do know they recommend 8 to 13 people. My best teams have been typically a little bit larger than that. But we had to have the same agreed to the size of the team where it didn't became, didn't become too large where we were over running each other and we weren't listening to each other. We had to understand our goals. We all had the same goals. We used to practice this by, when I worked at Microsoft, we used to have what we used to call our elevator speech. And we would stop somebody and I would go, we're working on this. Watch your elevator speech for this. And if your elevator speech wasn't... It wasn't meant that it had to be in sync with mines, but if I didn't understand it, we had a problem.
Or if it was a different goal where I'm looking at you going, but we're building a Volkswagen, but you're describing to me a Lamborghini, we have a problem. And those were the type of things that we also had to have to make sure that we had the right... Same practices and the tools. That's where I find Easy Agile exceeds. I mean it just exceeds, it meets above the market. It's transparent and it shows everything in front of you right there for me. So when we had the same tool and we were having the same cadence and we could see our dependencies and we could see what I had to deliver for somebody else or somebody had to deliver it for me, that was the types of things we had. We had to have respect. Somebody seems to always forget that we always had to have respect for each other.
We had to embrace the same values of collaboration, adaptability, transparency. The practices that we all know, but somehow we seem to forget when we get into a place where we are not aligned and if you respect my ideas and I respect yours and we're working together, we do not have to agree. But that respect will drive us a long way towards getting to that project vision that we want. And we're trying to meet the customer's needs. And those are the type of things that we needed. We needed leadership. Leadership, I can't say, and if you notice I'm not using the word management, leadership is where you're putting yourself out there in a situation where it can go bad for you as a person, as that leader, trying to make sure that we're making the right choices empowering the people and making them very clear what they can make decisions on and they can't. And it sounds so simple when I talk to you like this, but every time I've had to do some type of transformation, the baggage that sometimes we bring as human beings, the fears, the lack of trust that we have, that's where the scrum masters of product owners come in. And then you need something to make sure that you're having that vision to communicate that vision across. As I mentioned before, some of the tool sets that we have out there. Is that making sense for you at all?
Hayley Rodd:
Yeah, it really does. It's really resonating with me. I think when you talk about coming together as a team and putting together a set of values and a vision, it seems so much like a a "duh" moment. It's like, of course you would do that as a team, but I think at the end of the day as teams, we get in the daily business as usual and we think, I don't have time to get together as a team and set that vision because I've got to do X, Y, and Z, that's due next week. But I think it's one of those fundamental building blocks that really sets you up for success to do X, Y, Z quicker down the track. So that's what I've taken away from that.
Tony Camacho:
And I would agree with you. And you came up with a perfect example because a lot of people do that. I have ABC to do for next week, daily. I don't have time. And the problem is that if they would suddenly realize, and it does become apparent to your practices. So once you agree on your practices, your daily standups, if you're doing that, your retros at the end of your sprints and moving forward, once the person feels that they have that respect for you and they're not fearful, they can share that with you, "Hayley, I'm having a problem. I'm having way too much work. I don't know if I am going to be of value here. Or Do you really need me?" "Yes Tony, I do need you, we're going to discuss this and let's discuss your A, B, C and see how I can help you." And they suddenly realized they're not on an island alone. Developers by nature being introverted, we have to break that habit. We have to be able to share. And it's funny, I'm not saying share my lunch, fine, sure, let's share our lunch, but share the workload.
The one thing that I always try to mention to teams, and again that's... I'm sorry, but I do believe in Easy Agile, using this tool. That's where easy Agile also to me makes it apparent. A story belongs to a team, not to a person. And once you know that you suddenly realize, I'm not alone. I'm here working as part of a bigger thing. And most human beings want to be part of a bigger thing. You suddenly realize that it's almost like the baseball metaphor that I use for teams. And I know the market is not baseball, but I think it would apply for other sports, be cricket or sports like that. When I'm batting, it's me against everybody. When I'm on the field, it's us against... I prefer being with the us. And generally that's where things like that, let's do that.
Also, when you're working with more people as a team, there's things that happened there. You minimize the project risk, which I hate using the word project. It should be initiative. It's long living. You're usually a much more adaptable. I don't know all the answers. So when I worked with you, Hayley, and you showed with me some things there, you're one of the most humble people I've met, and I loved it. But when you walked through, you walked me through the tool, it became very apparent, you know it, you feel it, you love it, it's part of you. And that to me is invigorating. It's energy. Who wouldn't want to work with somebody like you? Why not? Let's do this. Right?
Hayley Rodd:
Thank you Tony. I guess one of the things that I wanted to touch on is when you're in a team and you're coming together as a team, you're working on something, how does an individual who seeks recognition for what they're doing, how do they get that? Or how do you leave that? How do you put that ego aside and say, "I'm doing something as a team to the better of the team?" Have you ever come across that or considered that? I'm interested in your thoughts.
Tony Camacho:
So the people that I felt that needed to have that typically how I... Yes, that's a great question because I'm thinking specifically. There was one, a scrum master that I thought that did it the most amazing way ever. Basically she would call out the ideas even if it wasn't that person's, yeah. I feel that Hayley is... You're not having a good day, Hayley. You're not having a good day. And I know you are not getting used to doing, working in the scrum team. It's new to you and everything else. And what she did typically was in front of everybody would be, and it wasn't even your idea sometimes. And she would just say, and Hayley came up with this wonderful idea that's going to save us something, move us forward. Hayley said this to me, it made us think as a team. And we went around it, we talked and we did it.
And that person always usually would be like, "Wow, I got credit for something. Good scrum-masters will see that. Or good product owners will point that out." The other way that I've done it was using something like Easy Agile. It's a great tool to use, believe it or not. I would back off, I'm a developer, but I also played the role of Scrum masters for years. I would step back and I would let one of my teammates run it, hear their voice, feel empowered. It's amazing when you can have people feel empowered because what you're all talking about, there really is about a lack of trust, a lack of psychological safety. And it's for us to be an aligned team, you have to have trust there and you have to break down the fear of judgment. So the other thing that one time happened with a scrum master that I thought was wonderful was is that again against Sophia Chaley, chief stood in front of her room when there was this a bad sprint.
The sprint didn't end well. And she stood up in front of everybody and she basically went, "Sometimes you win, sometimes you learn. This was a learning sprint." She pulled up Easy Agile, she was using at a time, pulled it up, showed the things that didn't work out the way they thought they were going to work out. And she said, these are the actions we're going to take to improve this. And then when somebody who was in management, again not using the term leadership, now I'm using the term management on purpose, was looking to assign blame. Her response was, not screaming, not raising her voice. Her response was, if we need to get rid of somebody or blame somebody, blame me. But I'm here to solve the problem. Let's move forward.
Hayley Rodd:
Wow.
Tony Camacho:
She wouldn't tell. And that was to me was one of the most outstanding moments I've ever seen. And she was at that point actually using Easy Agile that wasn't a financial institution in the United States. I would let you know that teachers use it, figure it out. And she basically showed the board and just went through everything and did that. That was leadership. That was leadership. And generally your teams will follow leadership and they will suddenly step up and you'll see that that's what people who want to stand up. Now, not everybody wants to do that. Some people want to just be team members and that's okay. That is perfectly okay, but the thing that's not okay is that if they don't have trust, right? And to me, that's the biggest thing. When you have people who are resisting change or siloed in their world, they suddenly realize if you can get them to open up it's really, they're just telling you, I don't feel safe.
I've been doing this all my life. I'm great at it and now you're asking me to do this. And you need to somehow get them to get the feel that they are bringing something of value. They are helping you move forward. And you're meeting them halfway if you have to. But yeah, that's the biggest problem I've ever seen that we've always, it always comes down to the human being in that. The rest of it, you can always come, you can always change that. But there's some of the things that you also have to do. I think that some people run into Hayley that I think me and you live in our world as we're moving up is sometimes we are, there's an ambiguity of the things that we have to do. And I've seen you do that, people in our roles will have suddenly, even if it isn't part of our role, will take it on and we have to learn. That's it. But yes.
Hayley Rodd:
Yeah, I think that, yeah, it's so true that the [inaudible 00:19:23] the psychological safety needs to be there. And I think back to so many teams that I've been a part of that it isn't there. So you have to feel like you got to lay your mark or put your mark on something and show your value. Because if you're not showing your value, then you get questioned. And so I think that that's such a common thing that I see in teams and it actually creates, not a camaraderie, but a competition between teammates and it breeds the wrong environment. So it's just really interesting. One thing that I did want to touch on that you spoke a lot about a couple of questions ago was respect and making sure that teams have respect for each other. How does a team member show respect for their teammates? What are some really good examples of respect and how can we display it or embody it or enact on it as team members?
Tony Camacho:
So let me show you a lack of respect right now. Yeah. Hayley, we're talking about this.
Hayley Rodd:
Looking off camera, avoiding me. Yeah.
Tony Camacho:
One of the main things was to really to learn to listen. Sit down, believe it or not, I found the best thing is sometimes taking a deep breath, listening, not responding, recognizing what that person may be feeling and going through at that moment because it's hard what we do. It's half art and it's half science. Let them learn that making a mistake is not a failure, it's a learning moment. Have that discussion there. Take their concerns real. So it's funny because you just made me think of something. That's one thing where I could show respect to my teammates would be as a scrum master, if I was a scrum master, hold effective retros. Really listen to what they're saying in the retros, report back on the things that you said you're going to improve in the retros. So we said these are the three things we're going to improve on or these are things that are assigned to me.
Make it real. Make it a story. Show it on the board and say, "This is where we're going. This is what's happening. This is what I'm blocked by. Can somebody help me?" But I am working this for you. Get them, really be sincere. I don't mean buying pizza or bring a lot of scrum masters will bring pizza and donuts to the office. No, it's make their lives really better. Be that advocate up for them. And if you're a teammate, be an advocate for each other and be sincere. Have the bravery to stand up and say that's not a fair assessment. But the biggest thing is to really listen. Because a lot of times when somebody's saying something to me, I'll make it personal. Me, I have sometimes have, I know I'm feeling uncomfortable, but I cannot explain why. And just having you there, looking at me and talking and going through it, I suddenly realize it may have been something different and I want to hear your ideas.
But I would have to, if I wanted to show myself to help that teammate, I also got to make myself vulnerable. If you're coming to me, I should share, but I should active listen, right? And really I respect your different perspective. It's okay. We all have different perspectives. Problem I find is that in ourworld, that we're moving so fast sometimes we don't stop to listen. We lack patience. We're moving too fast. So I'll share one for you that I'll be sincere. I had something medically came up and I was being a little abrasive with the team. So finally I called a meeting with our team and they saw me cry. I was okay with it. I was like, "I had no reason to be like this. You guys were showing me love, you were showing me respect, you're backing me up, helping me with my work. And I was still being utterly terrible."
And it hurt me. It hurt that I was doing that, but I needed them to see me and I needed them to listen to me, give me that second to get it off my chest. And in the end I started crying. A 60-year-old man crying in a meeting going, "I shouldn't have done that to you. That was wrong." And it wasn't contrived. Some of the people there were 20 year old people on my team and they were in tears. And it was because they felt, they told me after this, they felt my pain that I was in, because I wanted to help. It's the most frustrating thing. To your point before, how do I feel? I wanted to help. I wanted to be there and I couldn't. Physically, I wasn't there. My mind was all over the place and I was being rude, being blunt, and I could use some other terms. Please don't. But that's really the main thing for me was it's really simple what we do. I just listen and just show respect for other people. And sometimes we forget.
Hayley Rodd:
I think that so many of the messages that you are talking about are not just for developer teams, they're for every team, every team in every walk of life. I think that they're just so fundamental to successful human relationships, whether it be personal or professional, I think so. I think there's just so many good messages. One thing that I wanted to touch on was that you're talking about active listening and when you think back on your career, and maybe this is totally off script, but when you think back on your career, how have you become a better active listener over the years? How have you improved that skill? As you said, you're an extrovert, you want to get in there, you want to fix the problem. How do you get better at that?
Tony Camacho:
I had some very, very smart people that put up with me, listened to me, and then had the courage to approach me after and teach me and teach me and didn't embarrass me in front of anybody. Did it in a manner that they said, "Do you think maybe this could have been better Tony?" As I said, I'm 61 and still I'm an extrovert and I still have high energy and I still make mistakes. As I tell everybody, every day I wake up, I make a mistake, I just got up. But I could have stayed in bed longer. But also the thing that I've learned, and it's just by the nature of getting older, it's not the age part of it. It was watching people come up trying to do the same thing I did that I failed at and I was an instructor for Microsoft for a long time.
And seeing how, because to me seeing how a person's minds works is amazing. So what happens is I'll just... You know what I tried that, it didn't work for me, but I will say after class with you to show it to me again because maybe you solved it. I'm not that arrogant. And the nature of our business is that I find this, that the more you learn, the more you realize how little you know. That was the biggest thing that opened my eyes. Now it's like, oh my Lord. You meet somebody like John Kern, you meet somebody like Sophia Chaley who come from different perspectives, brilliant people, and you suddenly see that they happen to do things slightly different and you just watch them and you're like, "Wow." And the thing that I love about our job, which I guess you must love, everywhere we go, every team we work with, it's different. It's different.
Everybody always asks me, how do you do that. And I'll tell them, "Look, I will share with you the ways I did it. I have a varied background. I've always been consulting." I've done the ATM space, I did for space enabled warfare, I've done for health industry, everyone's been different. Someone from government regulation, but most of the time different human beings. So I have a saying, I've earned every scar in my back, their minds. I've learned people, you have to give people the chance to have their scars. Yes, it may be pain, I'm not saying fail, I won't let them fail. But sometimes people want to do something. So that's the way I would do it. Let them do it. And I just watched and learned that what happened was as I went in and the more I learned and I suddenly realized how little I know, I was like, I started with FORTRAN, I used to work in the dead 28.
And then you start working your way up and you start realizing, "Wow, I don't know as much as I thought I know." And I had the luck of running into working at Microsoft and having the pleasure of meeting Bill Gates. Now, no matter what you say about Bill Gates, because a lot of people do say some crazy things and some of them may be true or may not. But the one thing you can't take away from him is you go into a room with him and you suddenly see how he puts all these ideas together and comes up with a bigger picture. You suddenly realize, "Wow, people tell me I'm really smart, not that smart." And then you learn, humility is a good thing.
Hayley Rodd:
Yeah, I think humility is just such an important asset to have and to try and grow on because leaving your ego at the door and being open to learn from other people and not think that everything is definitely a life lesson that sometimes you need to go through. And some people go through it and still don't take away the life lesson. So yeah, I think it's so interesting. I guess we don't have too much longer left, but I wanted to touch on thinking about it from an ROI perspective. How important is team alignment from a return on investment? What do you gain from a business perspective when you have an aligned team?
Tony Camacho:
So I'm going to use a term that I dislike and Hayley, you can smack me the next time we meet. But I'm trying to use it as, I don't because it's effective resource utilization, right? But I'm not referring to human beings to that point because it may be human beings. The problem is that's a large market. But as Agile people I won't refer to you as a resource, I refer to you as a fellow human being, you are a partner on my team. You're my teammate. You're not a piece of wood. But that is unfortunately a term that is used. And we will have effective utilization, we'll have common goals across our organization. If you're using any of the message less, bad, safe, pick it, you start focusing on your value streams. You should have improved product quality because we have the same cadence. We're putting things out there and we're having the same views there.
You'll have I think better customer satisfaction and loyalty. They start seeing your product quality going up, being consistent, look and feel and hopefully you are delivering what they want. When you have your teams aligned, you're much more adaptable. Hayley, your team's got capacity? I don't. We don't have capacity to do this. Do you have capacity? Yes I do. Or we find someone or we break it down together and we present an idea to our partners. That's the things I like and I think in the end you have reduced risks at that point.
Also, I think that the thing that they have in is that it's indirect, but nobody knows about. Nobody really talks about it is that if I was upper management C-suite, when we start doing this and we're having the teams aligned, first of all, your teams become safer, your teams feel more comfortable, they're working with the same people. They start becoming very effective and they start producing ideas. They're the knowledge workers. They know this better than anybody else and then they feel empowered to share ideas. The places that I thought that I had the best teams was once they asked... Well, and I got it, I don't know how, I was running a train and they asked to talk to the CTO and all they wanted to do was to talk to the CTO and make that person human. They asked her what she did in a previous job. Amazing. She worked as a factory worker and she also worked in construction. She used to drive, one of the things, nobody would've believed this. And what happened was they started sharing ideas with her and she embraced them. You know what that did to the team, the teams all, they were like, now that's out there, that's ours. Look at that. That was ours. I mean ownership, it's unbelievable.
And unfortunately we are working on a capitalist market, which is fine, that's who we are. I mean we're in IT, it's a return on investment. Return on investment in the end, you start seeing much more efficient use of your money, much more efficient use of your dollars. Also, I would also imagine for the people above who are in the C-suite, they suddenly realize that the organization is going in the same direction. I think psychologically they feel that we now I have this team behind me pushing towards the same goal where a lot of times, every time I do an agile transformation, the first thing we always hear is we know they're working. We don't know what they're working on. And that's where something like Easy Agile bridges that and then you can use that information to go further. And that's wonderful because then at that point, everybody's on the same page. So you're a team now all the way from top to bottom. As opposed to I'm going to my team at work and that's it. So it's just really about return on investment, making sure that we are hitting our customers with everything we got. And I don't mean in a bad way, but we're delivering for our customers with everything we got. It's now efficiency, right? And that's it. That's about it.
Hayley Rodd:
Yeah, that's so powerful. I think it sort of nicely ties everything together because we've talked about a lot of things in the last half hour or so. And I think that at the end of the day, if you can get team alignment, just as you said, there's this ROI that can really shine through and it's a powerful thing for the whole organization to get right and to see the fruits of that work. So one last thing. Can you share your perspective on PI planning? I know you just mentioned safe a little bit for being the initial launchpad for team alignment.
Tony Camacho:
I love it. You have everybody in the room, you get to meet the people, you start making those connections to people. You start seeing them as human beings, not as this email or this text that you're sending across that you're going through there. So could I share one real experience from that? That's a PI planning house.
Hayley Rodd:
Please
Tony Camacho:
Do. So when I was working at Microsoft, I work for product quality online, which I know right now, considering the problems Microsoft is having, you're pretty much going now, "You suck Tony."
Hayley Rodd:
Never.
Tony Camacho:
No, we had our people distributed all over the world. And what was happening was that when I would talk to my short teams, I would ask them, and I was being facetious at a point because I just couldn't get the true answer was I would ask him, can you build the Twin Towers by tomorrow? And the answer would inadvertently be yes. Next day would come. Obviously you can't do the twin towers overnight. Ask them again, will you get it by next week? The answer would be yes. And they were feel for all of that. So when we had the PI planning, we did.
Microsoft went, got a hotel room in Seattle, a hotel room, a hotel in Seattle, rang our offshore teams. And then when they got to see me in person, they suddenly realized that I wasn't telling them I need the twin towers by tomorrow. I really wanted them to tell me when they could get me the twin towers. And I would defend it because they saw me right there in PI planning, defending, saying, "No, this is not possible." And when they saw me doing that, suddenly it was like the sky's open, sun's came through and now I was getting true answers. And what happened was it gave him an opportunity. And I realized that guys, you keep hearing me as sermon. It's always about the human beings, it's about those connections. It's about seeing the people. It's hard. It's two days of a lot of work. But once you get that work done, you come out of there a line, sharp direction. We know what our north is, now, do we know exactly where our true north is? As an agile team, we shouldn't, right? We should be refining it as we get there.
Find out exactly. But we know more or less where the direction is. We more or less know we're all on the same page. We all know that what we have to deliver to make this work out what other people have to deliver for us or we have to deliver for other people. So we suddenly feel part of something bigger. Bigger, right? We are now talking to the, if you're a developer or an engineer, software engineer, you're starting to see the power brokers and why they're doing this. You get the chance to ask them questions. What more could you ask for, right? I finally get to see the people who are making the decisions and I can ask them why. And they can tell me what the business value is and I can make the argument to them that maybe I don't think that's as much business value or we need to fix these things first before we can get that right and move our way on. What more could I ask for? I have an opportunity to make my case and I get to see the other people I'm working with. It becomes, when you're dealing with 125 people and you're on a train, you will become family.
We spend more hours sometimes with these people than we do with our family members at times. And it also gives you a sense of... Besides trust, a sense of a safety. You know it's not just you, it's all of us. So the saying that usually I see that the better executive say, I heard that in one PI planning, you fail, I fail. I fail, you fail. My job is to keep you employed. Your job is to keep me employed and to keep this company together. It's synergy, right? So it's amazing.
Hayley Rodd:
Beautiful.
Tony Camacho:
Yeah, I know. I'm all about the human. Sorry.
Hayley Rodd:
No, I am right there with you. I'm so glad that we got to have this conversation. We've talked a lot over the little while and every time we meet, I'm flabbergasted by your energy and your authenticity. And I think that this conversation that really shown true, so thank you Tony for taking the time to be with us. I'm going to say goodbye to all our listeners. I'm going to say another big thank you to Tony. So Tony is part of aligned agility and that is part of The Adaptivist Group. And yeah, thanks Tony for being here with us and thank you for everyone who has tuned in and listened to this episode of the Easy Agile Podcast. Thank you.