Latest / Leadership In Law: Growth & Leadership for Law Firm Owners / Why Great Engineering Teams Slow Down and How to Fix It with Thanos Diacakis
Transcript
- 0:52SPEAKER_00: The leadership in law podcast is going to equip you with the knowledge and tools you need to build a successful and fulfilling legal practice.
- 1:11SPEAKER_01: Welcome to another episode of the Leadership in Law Podcast.
- 1:14SPEAKER_01: I'm your host, Marilyn Jenkins.
- 1:15SPEAKER_01: Please join me in welcoming my guest, Thanos Diacakis, to the show today.
- 1:19SPEAKER_01: Thanos helps startups and growing companies overcome software bottlenecks, scale engineering teams, and deliver high-quality products faster.
- 1:27SPEAKER_01: With over 25 years of software development, his background spans both early stage ventures and tech giants like Uber and Included Health, where he led the technical integration of the Jump Bikes acquisition, scattering the platform to 45,000 vehicles and over two million monthly trips.
- 1:44SPEAKER_01: He's seen elite teams stall when outdated processes laid them two heads down to course correct.
- 1:49SPEAKER_01: With lean evidence-based-based practices, he unlocks faster delivery and greater developer satisfaction.
- 1:56SPEAKER_01: So velocity rises while burnout fails.
- 1:59SPEAKER_01: I'm excited to have you here, Thanos.
- 2:01SPEAKER_01: Welcome.
- 2:01SPEAKER_01: Thank you for having me on.
- 2:03SPEAKER_01: Absolutely.
- 2:04SPEAKER_01: Tell us about your leadership journey.
- 2:06SPEAKER_02: Oh, it's been a long it's been a long one.
- 2:08SPEAKER_02: I'm actually getting closer to 30 years now than 25, so that that's going to be a thing.
- 2:12SPEAKER_02: But I started my career in software almost 30 years ago now.
- 2:15SPEAKER_02: And one of the things that I started noticing even from the very beginning was that teams were struggling and not because they had bad ideas or didn't know what to do, but because they weren't experts in the software in the field of delivering software.
- 2:29SPEAKER_02: Like they had they knew their domain really well, they knew what they were trying to build really well, but they weren't able to take a step back and figure out how do we build software the better way.
- 2:37SPEAKER_02: So I did this in various forms with working for various employers and doing a variety of startups.
- 2:42SPEAKER_02: And it occurred to me that they all teams that I see in software nowadays are suffering from the same problems over and over again.
- 2:47SPEAKER_02: And so for the last three years, I've gone into solo practice and I helped them, I help coach teams go basically faster with better quality and happier.
- 2:54SPEAKER_01: Love that.
- 2:55SPEAKER_01: That means more profit for the company.
- 2:57SPEAKER_02: That always translates back to more profitable, but we tend to focus on the faster and more quality because that's the direct measures.
- 3:03SPEAKER_02: But then when your people are burning out and quitting left and right because they're just not happy there, that kind of eventually impacts the bottom line.
- 3:09SPEAKER_02: So I think now the focus is also we have to talk about happiness and we have to talk about satisfaction and make sure we have environments that people feel productive and they do their best work as opposed to places where they feel like, oh, I gotta go to work again today.
- 3:20SPEAKER_01: Yes, exactly.
- 3:20SPEAKER_01: We've all been at that point.
- 3:22SPEAKER_01: So you've worked everywhere from startups to companies like Uber and across all those environments, what's the biggest disconnect that you consistently see between business leaders and engineering teams?
- 3:33SPEAKER_02: Yeah, the most common one is that engineering and the business side don't really have the right language to speak to each other.
- 3:39SPEAKER_02: And they end up not being able to have what I call creative conflict.
- 3:43SPEAKER_02: They end up having not good conflict, the really bad kind where they're not able to argue for what each of their teams need in a constructive kind of way where they both get what they want.
- 3:52SPEAKER_02: And usually one team typically wins, and that's typically the business side.
- 3:57SPEAKER_02: And typically the business will want to have new features.
- 3:59SPEAKER_02: They want to ship more stuff because that's how they get valued and they can sell new things to their customers.
- 4:04SPEAKER_02: Now, engineers love to build new stuff, but they also have to do some kind of maintenance work every now and then, right?
- 4:09SPEAKER_02: We need to go in and clean up our systems and sharpen our knives and tools, metaphorically speaking, and make sure we have them in the most recent library so we don't get hacked.
- 4:16SPEAKER_02: But oftentimes engineers don't have the right way to express these things.
- 4:20SPEAKER_02: And the business doesn't understand that they have to do these things, so they just basically wrangle them into just building features, features all the time, and the product begins to suffer and complexity begins to increase, and the team is then demotivated because making the smallest changes get really buggy and they take a long time, and then no one becomes happy in this situation.
- 4:37SPEAKER_02: So oftentimes like giving you the right language to talk to each other and then saying, okay, this is our needs, this is your needs, like how do we mix those up and do a little bit of both and use the most recent and most effective techniques in implementing the software so we're not wasting time in doing this and slowing us down altogether.
- 4:54SPEAKER_01: You're right.
- 4:55SPEAKER_01: I hadn't really thought about it, but you're right.
- 4:56SPEAKER_01: It's completely different languages.
- 4:58SPEAKER_01: I've been in IT for many years, and it is completely different.
- 5:02SPEAKER_01: So helping that communication struggle has got to be very satisfying.
- 5:07SPEAKER_02: Yeah, it's a lot of fun.
- 5:08SPEAKER_02: And oftentimes it's fun because people usually reach out to me when they run out of the obvious solutions, right?
- 5:13SPEAKER_02: When you can see that if I move X and Y happens, then people can already pre-C that and do X and they get Y, and that's really great.
- 5:20SPEAKER_02: But sometimes the results are counterintuitive, right?
- 5:22SPEAKER_02: You wouldn't, if you haven't done this before, you don't know that, hey, I need to go move lever A to make B happen.
- 5:28SPEAKER_02: I thought if I moved A, C would happen, right?
- 5:30SPEAKER_02: And they don't, if they if they're looking for the result B, then that's just really hard to figure out.
- 5:35SPEAKER_02: So that's where through having having seen this so many times, it's easy for me to go in and say, look, in your situation, actually, if you did this, it's you'll get the good result here.
- 5:43SPEAKER_02: A very good example for this is oftentimes what I'll see with teams is they're overloaded.
- 5:47SPEAKER_02: They have so many things and everyone is just jumping left and right, and today's priority is different than yesterday's priority, and it's context switching and you forgot what you were doing.
- 5:55SPEAKER_02: And so for the team to go faster, you actually have to do less.
- 5:59SPEAKER_02: You have to ask the team to do less, and they will actually get it done faster than if you're asking to do 20 things at once, right?
- 6:04SPEAKER_02: So if you're asking the team to do 20 things, they're just going around and they're not really completing anything.
- 6:08SPEAKER_02: What is what if you pick the most important one and you just nail that one, got it done, get it out the door, right?
- 6:13SPEAKER_02: And now you just realize the value, everyone's happy because they got something out the door to a customer and they can see it.
- 6:17SPEAKER_02: You can move on to number two, number three.
- 6:19SPEAKER_02: And that often helps with dealing with prioritization.
- 6:22SPEAKER_02: You're if you can't prioritize anything, then you're just constantly stuck with like, hey, we need to do 20 things.
- 6:26SPEAKER_02: Right.
- 6:27SPEAKER_02: Joke is you can't really have more priorities than arms, right?
- 6:29SPEAKER_02: If you have three priorities, you don't really have priorities, there's nothing it seems important.
- 6:34SPEAKER_01: In all the design, we used to say if everything's bold, nothing's bold.
- 6:37SPEAKER_01: So yeah.
- 6:38SPEAKER_01: Exactly.
- 6:39SPEAKER_01: When you say companies and need to align better align their business goals with their engineering practices, what does that actually look like in the real world?
- 6:47SPEAKER_02: So I follow like a four-step framework to get them to get to a place where these things are aligned.
- 6:54SPEAKER_02: The general idea is that in software, there's an outer loop where you have some product hypothesis and you go build it, and then that might work or it might not.
- 7:02SPEAKER_02: And if it worked great, you go build the next one.
- 7:04SPEAKER_02: If it didn't, you also go build the next one.
- 7:06SPEAKER_02: And the inner loop is a software loop where you're given a feature and you put it out, you may have some bugs, and you repeat this and do it over and over again.
- 7:13SPEAKER_02: So our goal is to get this machine to work really well so that the inner loop engineering is working well, the outer loop, the product market fit loop is working well, and the communication there is working well.
- 7:24SPEAKER_02: And the framework that I follow to get these two teams talking is first we focus on being able to get stuff out to production, right?
- 7:29SPEAKER_02: If you can't go from an idea to getting something shipped, you don't have the ability of fixing a bug.
- 7:33SPEAKER_02: Because if someone says a bug and it takes you a week to put it to production, you can't really have any kind of quality.
- 7:38SPEAKER_02: So first we focus on can we get things out fairly quickly?
- 7:41SPEAKER_02: Once we can get them out fairly quickly, now we got to focus on quality because we don't want to be getting junk out fairly quickly.
- 7:45SPEAKER_02: We want to be able to get good stuff fairly quickly.
- 7:48SPEAKER_02: And when we get the bug reports that something is broken, we also want to get that one out.
- 7:51SPEAKER_02: So one is get the iterations going.
- 7:53SPEAKER_02: Two is get the quality going and make that work really well.
- 7:56SPEAKER_02: And then once you got good iterations and quality, you start building more and more stuff.
- 8:00SPEAKER_02: So you start suffering from complexity.
- 8:02SPEAKER_02: So three is wrangling that, right?
- 8:03SPEAKER_02: Figuring out what are the dimensions across when you scale, do we have more customers, more features, more partners, more clients, and arranging your software architecture and your team architecture in a way that supports these.
- 8:14SPEAKER_02: And once we've nailed one, two, three, iterations, quality, complexity, now we can go number four, which is planning and predictability.
- 8:19SPEAKER_02: Now we string all those things together and we're able to get those two loops really firing really well and get the business results that we want.
- 8:27SPEAKER_02: This usually turns in the whole IT infrastructure for being like this place that eats up a lot of money to something where we have an idea, we can go to production within days or week, weeks maybe, not months or quarters.
- 8:39SPEAKER_02: And that really turns into competitive advantage because now we're going to be taking the competitions to launch when we can ship so quickly and some customer wants something, yes, you can have it and you don't have to wait like a quarter to get it.
- 9:52SPEAKER_02: You can have it in a week, two weeks.
- 9:55SPEAKER_01: Wow, I love that.
- 9:56SPEAKER_01: Absolutely.
- 9:57SPEAKER_01: Now, if for non-technical CEOs and founders, how should they think about engineering teams conceptually so they can lead them better?
- 10:05SPEAKER_01: Because I know it's the language is not only different, it's also the outlook is different.
- 10:09SPEAKER_02: Yeah, I think one of the things that I would suggest is go make some friends in engineering and start becoming curious as to what they do and how they do it, and go have those lunches, talk to the talk to people.
- 10:19SPEAKER_02: A common pattern that I see is we don't have the time, we don't want to invest that.
- 10:23SPEAKER_02: So what we'll do is we'll write really tight specs, right?
- 10:25SPEAKER_02: We'll tell what we want, we'll write a piece of paper, we'll make it 20 pages, make it as detailed as we can, throw it over the wall, and come back in three months, and hopefully that's done to our satisfaction, right?
- 10:33SPEAKER_02: As you can imagine, that usually doesn't really work very well because there's misunderstandings and lack of communication.
- 10:39SPEAKER_02: You will not get what you wanted three months later, right?
- 10:41SPEAKER_02: If you can figure out how to talk to this group, you can figure out how in a time efficient way, you don't need to spend all your time in the engineering with engineering folks, but you can figure out what the right processes are to have the effective communication, the right checkpoints in the places that you need them, create the right feedback loops so your asks can be translated into actually what you want in a short period of time.
- 11:03SPEAKER_02: So I would say go make some friends and start learning a bit of language.
- 11:05SPEAKER_02: Again, you don't need to become a proficient engineer.
- 11:07SPEAKER_02: That's not the goal here.
- 11:08SPEAKER_02: Like each side has their expertise and they can stick to it, but there is that common language.
- 11:12SPEAKER_02: There's some places where you interact that needs to be developed.
- 11:15SPEAKER_02: And that's a place that is always fun to go into.
- 11:18SPEAKER_01: It is interesting the thought about just have lunch with the crew.
- 11:21SPEAKER_01: It's it opens up so much lines of communication with no matter what section of your business you're working with, just get to know your people.
- 11:28SPEAKER_01: You get to know the thought processes and how they work.
- 11:31SPEAKER_02: Yeah.
- 11:31SPEAKER_02: And nowadays, sometimes people would feel embarrassed because they'd go in that meeting and not really understand many things engineering.
- 11:37SPEAKER_02: But now someone tells you something, it's a really great icebreaker to say, hey, I have no idea what that is.
- 11:41SPEAKER_02: Explain it to me.
- 11:42SPEAKER_02: Or if you don't want to do that, you can go back home and go to chat or Claude and say, hey, someone mentioned this thing.
- 11:46SPEAKER_02: What the heck is that talking about?
- 11:48SPEAKER_02: And Claude will give you a really good executive summary of what that was, and you can feel happy that now you learned something engineering.
- 11:53SPEAKER_01: I don't hope in the communication.
- 11:55SPEAKER_01: And a lot of businesses think about speed and quality as complete opposites.
- 12:00SPEAKER_01: Why do you believe that's the wrong way they look at software development?
- 12:03SPEAKER_02: Yeah, I hinted this to this earlier, right?
- 12:05SPEAKER_02: Usually when an engineering team has a quality issue, the obvious solution is okay, let's add some more testing.
- 12:11SPEAKER_02: So when we finish it, we'll go do a bit more testing.
- 12:15SPEAKER_02: So we won't ship it.
- 12:16SPEAKER_02: Let's say we started on Monday, we finished it on Wednesday.
- 12:18SPEAKER_02: Instead of shipping it on Wednesday, we'll test it through Friday and it's a weekend, so we'll launch it on Monday.
- 12:23SPEAKER_02: And now we slowed it down, but we've added this quality gate.
- 12:25SPEAKER_02: Now we feel good about ourselves, right?
- 12:27SPEAKER_02: And that's where the counterintuitive part comes in.
- 12:29SPEAKER_02: What you've done is now that other bug that was filed last Friday that was ready to go is now sitting there and it was ready on Wednesday, but you're gonna have to wait till next Monday to ship it.
- 12:39SPEAKER_02: So now those bugs are piling in.
- 12:41SPEAKER_02: And now you're gonna make this really fairly big release because you're now shipping every week because you need two or three days to run all your tests by hand.
- 12:47SPEAKER_02: And that big release will have a bunch of problems.
- 12:49SPEAKER_02: You'll just cover them all at once, and now that's gonna have and that problem just keeps compounding, right?
- 12:53SPEAKER_02: It doesn't get any better.
- 12:55SPEAKER_02: So my intuition is backwards on this, which is you have to figure out what are the quality gates, automate them, and at least if you cannot automate some of them, be able to fix them quickly.
- 13:04SPEAKER_02: So you have to be able to ship many clients that I work with who ship many times a day, definitely weekly, even for the slowest of the projects sometimes, but you can certainly ship one or two times a day.
- 13:13SPEAKER_02: And when something comes in, you have the processes to figure it out and then get it out the door and get any fixes in.
- 13:19SPEAKER_02: The goal here is to not see those as trade-offs, right?
- 13:23SPEAKER_02: I can go slower or faster and get more quality, but see those, how can I move both of those?
- 13:27SPEAKER_02: Because if I can ship fixes faster, if I can ship code faster, I can get both speed and I can maintain the quality.
- 13:33SPEAKER_02: By the way, I'm not also saying YOLO, if you don't have any of these quality processes in place, do not go out tomorrow and try to ship every day or every few hours because it's going to break everything.
- 13:43SPEAKER_02: But the these investments pay back.
- 13:46SPEAKER_02: So if you recognize that you're in that situation, you can start investing five or ten percent of your time every day to that project.
- 13:52SPEAKER_02: And then maybe in a month or two months, you can be to the in the place where you can now start doing a bit more frequent releases and you can just build up to it.
- 13:59SPEAKER_02: Because these investments are cumulative, they compound over time.
- 14:03SPEAKER_02: So if you did spend 10% of your time for a month, that is then payback you're gonna be seeing for a really long time to come, as opposed to whatever that other 10% would have gone if you built a new feature.
- 14:13SPEAKER_02: That feature was built once, you sold it once, maybe you sold it to a few clients once, but that's the end of that.
- 14:17SPEAKER_02: But if you make that investment in infrastructure, you really can push it.
- 14:21SPEAKER_02: I have a client that's been a long-term client of mine, and over the past six to twelve months, we've really focused on re-engineering a bunch of the processes that we've had.
- 14:28SPEAKER_02: And we were looking at the leadership meeting charts yesterday, and we are now shipping 10x from where we are from where we were shipping six months ago.
- 14:36SPEAKER_02: So even if we hadn't built anything in the last six months, we can basically catch up within one or two weeks if we just started shipping right now, that would have paid back for all the work we did in the last six to twelve months.
- 14:47SPEAKER_02: So those compounded things are there to stay, and I highly recommend that people you know spend and invest in in those areas.
- 14:55SPEAKER_01: That's amazing.
- 14:55SPEAKER_01: 10X.
- 14:56SPEAKER_01: Yeah, that's crazy.
- 14:58SPEAKER_01: So let's talk about Agile for a little a minute.
- 15:00SPEAKER_01: Agile became a standard for so many teams, but you argue that doing agile isn't enough.
- 15:06SPEAKER_01: Where do most companies get it wrong?
- 15:08SPEAKER_02: Yeah, that there's agile with a capital A, and there's agile with a small A, right?
- 15:12SPEAKER_02: And I usually talk about Agile with a small A.
- 15:14SPEAKER_02: So don't get me wrong, by the way.
- 15:15SPEAKER_02: Agile with a capital A that came out like 20, 25 years ago was it was a great idea because it was solving the problem that we had at the time.
- 15:22SPEAKER_02: The problem we had at the time was we were shipping every three months, every six months, every 12 months.
- 15:26SPEAKER_02: And Agile said, no, that doesn't work.
- 15:28SPEAKER_02: We need those shorter feedback loops.
- 15:29SPEAKER_02: And a lot of the things that we've been talking about so far are really inspired from and come from Agile of shortening those feedback loops.
- 15:35SPEAKER_02: I think the problem that I see with Agile as it's being implemented in most places is it's Agile with the capital A.
- 15:40SPEAKER_02: Someone went to a seminar, they got like a stamp that they're now a scrum master, and they come and do a bunch of stuff.
- 15:46SPEAKER_02: And oftentimes, and it's not always, oftentimes they will do the things without understanding or explaining to their team why they're doing these things.
- 15:54SPEAKER_02: Right?
- 15:55SPEAKER_02: So we will have this Monday morning meeting, and these things are gonna happen, then we're gonna have a scrum every day, and these things are gonna happen, we're gonna do the other thing at the end.
- 16:01SPEAKER_02: And if you don't know why you're doing these things, it's very easy for this process to just get ossified in there and you're just doing it because you're doing it.
- 16:10SPEAKER_02: Is that the story with the apes that they're in the cage and they have some bananas on top of a ladder, and the apes try to climb on top to grab the bananas and they spray them with ice cold water.
- 16:18SPEAKER_02: So they learn not to go up the ladder to get the bananas, and then they put a new ape bin, take one of the old apes out, the new ape bin tries to climb up the ladder and grab a banana, the and the other apes will just pull them down.
- 16:28SPEAKER_02: And uh, they will eventually replace all the apes with new apes, so no one's ever been wet.
- 16:32SPEAKER_02: But every time an ape tries to go up the ladder, the the old the other apes just beat them up because they don't want to get wet.
- 16:37SPEAKER_02: Or they don't know why, but they're doing it anyway.
- 16:39SPEAKER_02: So it's these kind of situations where we're just doing the stuff because we just saw it getting done, and that was the culture that was built in without knowing why.
- 16:46SPEAKER_02: So I usually encourage people to learn why, and then if something, if there's a good reason why you should be doing this thing, then go ahead and implant it, steal it from agile and do it.
- 16:56SPEAKER_02: But if there's some process that no longer makes any sense, then throw it out.
- 16:59SPEAKER_02: Uh, one of my favorite ones to throw out are sprints.
- 17:02SPEAKER_02: We used to have sprints because we wouldn't want to ship every one or two weeks or month when we originally started these, because we were shipping every six months.
- 17:08SPEAKER_02: But now having a sprint that you that is like one or two weeks when we do deployments to production every day doesn't make any sense.
- 17:13SPEAKER_02: So a lot of my teams have switched from sprints to Kanban where you just have a pile.
- 17:17SPEAKER_02: And whenever someone is done with something, you just go grab the thing from the top of the pile and just go build it and ship it and scrap the next thing from the pile and just keep repeating this.
- 17:23SPEAKER_02: And so we got rid of a two-hour meeting on Monday morning that taking everyone's time with doing the planning, and everyone's grown up enough to go get grab a thing from the pile.
- 17:31SPEAKER_02: So that sort of solving a problem that does no longer exists.
- 17:35SPEAKER_01: I'm loving this.
- 17:36SPEAKER_01: I have a coach that says whenever you're brought in with a new process, take the fish and leave the bones, right?
- 17:42SPEAKER_01: Yeah, not every process is ideal for your business.
- 17:45SPEAKER_02: My my version of that is solve problems you have, not problems you imagine you have.
- 17:50SPEAKER_01: I love that.
- 17:51SPEAKER_01: That makes sense.
- 17:53SPEAKER_01: Amazing.
- 17:53SPEAKER_01: So let's with technical debt, that's something founders often ignore until it's becomes painful.
- 18:00SPEAKER_01: How would you explain technical debt to a business owner who doesn't come from an engineering background?
- 18:05SPEAKER_02: So technical debt, I think the easiest way to visualize this is the same way that in leaning manufacturing we had inventory.
- 18:11SPEAKER_02: It's stuff that is you've built and it's just sitting there and it's rusting away or it's getting lost or it's getting misplaced and it's just really slowing you down.
- 18:20SPEAKER_02: And if you were to say, hey, I'm gonna relay out this factory because I can see that these things need to move around in a certain way, again, these are the investments we were talking about that pay you back forever or for a very long time.
- 18:31SPEAKER_02: And it's very common for people to ignore this because engineering doesn't know how to advocate it for themselves.
- 18:37SPEAKER_02: We we're probably the only profession where there's some very good professional standards that get ignored for the whole for a very long time.
- 18:46SPEAKER_02: You wouldn't imagine you would ever go build a bridge and say, and we'll get some light traffic on it and then we'll put the barriers on the side.
- 18:53SPEAKER_02: Because in the beginning there's going to be very little traffic, so there's no point having barriers inside because no one, there's no one there to fall off it, right?
- 18:58SPEAKER_02: The equivalent in engineering being like, we'll go write the software, we'll write the tests later.
- 19:02SPEAKER_02: So there's certain things that we just should not be doing that we need to like just stop, and that that sort of creates technical debt.
- 19:10SPEAKER_02: That said, even if there's like unintentional stuff that just happens, we need to go in and clean it up.
- 19:15SPEAKER_02: If you have a new company, you may not have any technical debt.
- 19:18SPEAKER_02: So you could be spending 90% of your time just in new features and very little time doing maintenance.
- 19:23SPEAKER_02: But for most mature teams, if you've been around for six months or 12 months, it is very likely your breakdown may be looking like you're spending a third of your time building new features, a third of your time fixing bugs, and a third of your time dealing with technical debt.
- 19:33SPEAKER_02: By the way, technical debt is a really nice, not very nice term because it just implies that it's like it's like boring stuff that we have to go do.
- 19:40SPEAKER_02: And I usually talk about it as investments.
- 19:43SPEAKER_02: These are things that make us go faster.
- 19:44SPEAKER_02: This is removing cruft, this is adding new things, this is changing processes, this is hiring new people.
- 19:50SPEAKER_02: It doesn't have to be just go cleaning up old things, but investing in ourselves.
- 19:54SPEAKER_02: This is learning new technologies that help us go faster in the future.
- 19:57SPEAKER_02: If you are doing the work and just doing the work, your competition is going to take your lunch because they're going to be doing the work and improving how they do their work, and you're not going to be around for a very long time.
- 20:07SPEAKER_02: So for me, that's technical debt, that's investments.
- 20:10SPEAKER_02: Spend those, those compound, your team will be awesome if you start investing in it.
- 20:16SPEAKER_01: Invest in yourself and you can beat the competition.
- 20:19SPEAKER_01: You're right, because if you're not moving, working to move ahead, then someone else is going to move ahead of you.
- 20:25SPEAKER_02: Yeah.
- 20:26SPEAKER_01: Common sense.
- 20:27SPEAKER_01: So we talked about how the feedback loops and the growth.
- 20:30SPEAKER_01: What are the long-term costs for repeatedly choosing quick fixes over durable solutions?
- 20:36SPEAKER_02: Simply put, you just collapse under your own weight.
- 20:39SPEAKER_02: It's just that your system becomes so fragile.
- 20:41SPEAKER_02: And I say system, it's not your technical system, but it's also your culture and your processes and everything that you have there, where and every time you want to make a new change, it is just so hard and it breaks so many things that it just slows everyone down.
- 20:54SPEAKER_02: And that's not a happy environment to work in.
- 20:56SPEAKER_02: So it creates stressful situations because people want new stuff and you can't deliver new stuff.
- 21:00SPEAKER_02: And it it is not a fun place to be.
- 21:03SPEAKER_02: It's literally that just that collapse.
- 21:06SPEAKER_02: And it's a little bit hard to get out of, but you can that there is a methodology to get out of it, right?
- 21:11SPEAKER_02: You can start pairing back in some of the feature development, steal some of that time to make some investments.
- 21:15SPEAKER_02: As the investments start paying back, then you're gonna have fewer bugs.
- 21:19SPEAKER_02: Now you have a little more time, and then you can do a bit more investments, start putting some features back in, and you can get back into a virtuous cycle.
- 21:26SPEAKER_02: I've worked with various clients, one of I can think of recently, that they were struggling with that, and we said we don't need to slow everything down.
- 21:32SPEAKER_02: We don't need to just stop everything that we're doing and just start investing and do everything investments, but let's do 10% investments and just make that non-negotiable.
- 21:40SPEAKER_02: Every week, we're gonna be spending 10% of our time into these investments.
- 21:43SPEAKER_02: And about a year later, they're just crushing it.
- 21:45SPEAKER_02: They went from shipping one feature for one feature per week altogether, they have four or five engineers, to having shipping each engineer shipping three or four features per week each.
- 21:55SPEAKER_02: So 10, 20x, whatever, like some massive improvement.
- 21:58SPEAKER_02: Again, that doesn't scale forever, but you can see the difference of just spending 10% of your time in investments for six to twelve months can make a huge difference in a team.
- 22:06SPEAKER_01: Oh wow, that's fantastic.
- 22:08SPEAKER_01: And we know that burnout is common in engineering engineering teams.
- 22:12SPEAKER_01: What are your what are the operational habits or leadership mistakes that create burnout even in high performing teams?
- 22:19SPEAKER_02: The most common thing is not having that language to talk to each other.
- 22:23SPEAKER_02: And then the team is just usually get jerked around a lot by okay, we want this, now we want that, now we want all these too many things, and there there is inability to prioritize.
- 22:32SPEAKER_02: You're pulling me in a hundred different directions.
- 22:34SPEAKER_02: I'm not seeing the value of what I'm doing in this company, right?
- 22:37SPEAKER_02: I as an engineer, I like building things, I like shipping things, I like seeing, hey, I put this thing together and now actual people are getting benefit out of this thing.
- 22:45SPEAKER_02: If you're in a burnout type situation, you don't see that, right?
- 22:48SPEAKER_02: Because nothing ever ships, it's always buggy, people always complaining to you.
- 22:51SPEAKER_02: So that that is not a happy situation.
- 22:53SPEAKER_02: And unfortunately, it's all too common.
- 22:54SPEAKER_02: And it doesn't need to be this way.
- 22:56SPEAKER_02: I think we do have the tools.
- 22:57SPEAKER_02: Actually, we've had the tools for a very long time of how to deal with this, and we need more companies applying this.
- 23:03SPEAKER_02: And this is not just the business saying, hey, engineers, we're gonna now work in this nicer way.
- 23:08SPEAKER_02: Here's less things to do, please do them faster.
- 23:10SPEAKER_02: But it's also the engineers being able to advocate for themselves and saying, There's a professional way of doing this, and this is how we should do this, and this is how we're going to balance the needs of both sides of this equation for the long-term benefit of the company.
- 23:21SPEAKER_01: And that helps grow the culture as well.
- 23:23SPEAKER_01: People just need to be not burnt out and be knowing what it's expected of them.
- 23:27SPEAKER_02: Yep.
- 23:29SPEAKER_01: So if a founder or a company leader feels like their software team is moving too slowly, what's the first thing they should examine before assuming the team itself is the problem?
- 23:38SPEAKER_02: The first thing I'd do is look at the level of work.
- 23:40SPEAKER_02: Is the team just have too many things and they're scrambling?
- 23:43SPEAKER_02: That that is usually the most common thing that I would look at.
- 23:46SPEAKER_02: The second thing I would dig in is the technical debt and what is the investment?
- 23:50SPEAKER_02: What is the plan for having long-term feature delivery as opposed to how do we get the new thing that someone asked yesterday that this client is yelling really loudly they must have tomorrow?
- 23:59SPEAKER_01: Love that.
- 23:59SPEAKER_01: All goes back down to communication things, just making sure you know what people are doing and they give them the easiest path to complete.
- 24:05SPEAKER_01: Awesome.
- 24:06SPEAKER_01: Now it you've been doing this for 30 years, I guess.
- 24:08SPEAKER_01: Now, what do you think separates teams that scale cleanly from teams that collapse under their own growth?
- 24:14SPEAKER_02: I think it's that introspection, right?
- 24:15SPEAKER_02: Teams that go back and have the maturity to see how they're doing things and going back and improving their systems.
- 24:21SPEAKER_02: And most teams are usually pretty busy.
- 24:24SPEAKER_02: I don't think I've ever been to a software team where it's like, yeah, we have so much free time, we can just sit around and chill.
- 24:29SPEAKER_02: It's usually everyone is pretty overworked.
- 24:31SPEAKER_02: But those that figure out how to go and make those small investments, they end up being a lot better.
- 24:37SPEAKER_02: So sometimes they actually have to hide it from the business, and that's not great because that is not always sustainable.
- 24:43SPEAKER_02: But I think the teams that really go out the way is where the business actually understands this and encourages it and has the right incentives in place, where we have the right mix and balance in doing the work and improving the work as well.
- 24:55SPEAKER_01: Love that.
- 24:56SPEAKER_01: This has been really interesting, and especially I love the ROI that just keeps going exponentially as you're investing in your in your growth.
- 25:05SPEAKER_01: I know my listeners are going to want to reach out to you and connect with you.
- 25:08SPEAKER_01: Where can they do that?
- 25:10SPEAKER_02: So you can check me out on LinkedIn.
- 25:11SPEAKER_02: I post a lot over there.
- 25:12SPEAKER_02: My website is also cosmicteacups.com and I post some articles on my blog over there.
- 25:17SPEAKER_02: I recently launched a new tool called Team Metrics, which actually enables you to visualize if you're on linear for your bug tracking system, that you can visualize like the features and bugs and investment work that you're doing over time.
- 25:29SPEAKER_02: And it's a really handy tool to start diagnosing what's happening so people can check that one out.
- 25:33SPEAKER_01: Awesome.
- 25:34SPEAKER_01: I'll make sure that those links are in the show notes.
- 25:36SPEAKER_01: And yeah, this has been a great conversation.
- 25:38SPEAKER_01: I really appreciate you joining us, Thanos.
- 25:40SPEAKER_02: I enjoyed it as well, Marilyn.
- 25:41SPEAKER_02: Thanks for having me on.
- 25:42SPEAKER_01: That's a wrap on today's episode of the Leadership in Law Podcast.
- 25:45SPEAKER_01: Before you go, I want to make sure that you know about something that could be a real game changer for your firm.
- 25:50SPEAKER_01: If you've been doing the work, showing up, serving clients, but your marketing still isn't producing the caseload you know you deserve.
- 25:56SPEAKER_01: That's exactly the problem Law Marketing Zone was built to solve.
- 25:59SPEAKER_01: My team and I work exclusively with law firms, and we don't do cookie cutter.
- 26:03SPEAKER_01: We build a strategy around your practice, your market, and your goals.
- 26:06SPEAKER_01: More high-quality leads, better cases, less stress, and more profit.
- 26:11SPEAKER_01: Head over to LawmarketingZone.com slash book a call and book your free case growth session today.
- 26:16SPEAKER_01: The link is in the show notes.
- 26:18SPEAKER_01: Thanks for listening, and we'll see you next episode.
- 26:21SPEAKER_00: Thanks for joining us on another episode of the Leadership in Law Podcast.
- 26:26SPEAKER_00: Remember, you're not alone on this journey.
- 26:29SPEAKER_00: There's a whole community of law firm owners out there facing similar challenges and striving for the same success.
- 26:35SPEAKER_00: Head over to our website at LawMarketingZone.com.
- 26:39SPEAKER_00: From there, connect with other listeners, access valuable resources, and stay up to date on the latest episodes.
- 26:47SPEAKER_00: Don't forget to subscribe and leave us to review on your favorite podcast platform.
- 26:52SPEAKER_00: Until next time, keep leading with vision and keep growing your firm.