In this episode of Leadership Launchpad, guest David Hirschfeld, a seasoned software development veteran, discusses the role of systems and protocols in building exceptional teams. Drawing from his extensive experience and his work at Techies, Hirschfeld sheds light on the importance of focusing on the root problems faced by customers rather than becoming consumed by product features. The conversation delves into AI’s evolving role in software development, emphasizing the current limitations and the need for effective project management systems to enhance team productivity. Hirschfeld also shares insights into hiring smarter team members and encourages the creation of playbooks and measurement systems to foster continuous improvement within teams. This episode provides valuable perspectives on leadership, team dynamics, and innovation in the tech industry.
David Hirschfeld [00:00:00]:
Exceptional teams create very predictable results at a very high quality all the time. So to do that, they have to have systems and protocols in place that they follow and ways of measuring it.
Matt [00:00:30]:
One thing that new leaders are often hesitant to do is to tell their teams how to get work done or to create standard systems for how work gets done. The truth is that no work happens in a vacuum, and the best people often create systems for how to document what they're working on, how to back up their work, how to send updates to clients, and all those things that just have to happen in order for work to be done effectively. And if you let everyone on your team come up with their own way to get all these things done, then there's a chance that these various systems are going to come into conflict and the overall productivity of your team is going to be harmed. This week's guest on the Leadership Launchpad is David Hirschfeld, a 35 year software development veteran with a unique perspective on technological innovation and business growth that he currently uses at the company he founded and techies. David specializes in AI driven workflow transformation for scale ups and startups. Having Collaborated with over 70 startups, he developed the first launch method, a systematic approach that minimizes risks and accelerates software company success with reduced reliance on investor funding. This episode really touches on this idea of how do you create systems that will enable your teams to be incredibly successful? We start off talking a little bit about the current state of AI software development, which I thought was a really interesting discussion. We then dive a little bit deeper into understanding why so many founders or the people with kind of this founder intent tend to build too much and lose focus on the problem they're trying to solve.
Matt [00:02:18]:
And then we finally dive into the importance of systems. It's really a great discussion, but before we get into that discussion, I do want to remind you that if this is your first time listening to the show, please make sure you subscribe so that you never miss a future episode. And if you are listening to my voice right now and you happen to be someone who is responsible for leadership development in your organization, I would love to talk to you. Please reach out to me at Matt better everyday studios.com so we can see if we can help make the leaders in your organization better. With that, let's get into the discussion with David Hirschfeld. David, welcome to the Leadership Launchpad. How are you doing today?
David Hirschfeld [00:02:58]:
I'm doing great. Thanks for having me, Matt.
Matt [00:03:01]:
Yeah, I'm really excited that you reached out to me and that we kind of connected a Few like a week or so ago and started talking because you have a very interesting business and so I wanted to start there of could you tell. Tell us a little bit more about Techies and kind of what you've been doing the last few years?
David Hirschfeld [00:03:21]:
Yeah, sure. Well, I started founded Techies 18 years ago and it was after I had two startups, one in the 90s that I sold in 2000 that was a successful exit. And then one in 95 that I failed in 97. So that was a failure. So I've seen both sides just from my own personal experience in terms of startups. And the second one failed because I didn't follow the playbook that I followed the first time, not realizing exactly what that playbook was. Anyway, then I founded Techies in 2007. So that's 18 years ago.
David Hirschfeld [00:04:01]:
And we've been working with startups and scale ups doing custom software development for that whole time. And some of my clients are even, you know, 10 years. I've had them for 10 years or more.
Matt [00:04:13]:
Oh, wow.
David Hirschfeld [00:04:14]:
Oh, wow. Yeah, yeah. Where we become their outsourced IT and development team.
Matt [00:04:20]:
Yeah. Wow. So you've been doing that for a while, I guess. Well, since I have you, you're the perfect person to ask this question. I don't think it was on the list that I originally sent you, but it always piques my interest. Yeah. Because I always get different opinions. What is happening with AI coding right now? Is that something that you're really leaning into? Like how's I keep hearing that that's transforming software teams?
David Hirschfeld [00:04:46]:
Well, it's very funny that you brought that up because this will be my fourth conversation today about that topic with people on my team and customers and anyway, so everything we've been benchmarking, really in the last two months, we've been benchmarking and trying to do problem solving. So this has gone through a big evolution because the technology is changing so quickly and we've been using AI code generation in some form or fashion for two and a half to three years now. Right. For building small modules or refactoring small pieces of code and then growing and growing. About seven, eight months ago, I started trying out some of the CodeGen tools that can build full applications. And as recently as a couple weeks ago, I even tried one of those things like Replit and Bolt and Vercel and products like this. And they all provide some value, but they fall short in some really key ways. And so we're not able to use those to build whole applications.
David Hirschfeld [00:05:57]:
We want to Build a very simple prototype of an application that has some functionality. We can do that pretty well with those. But if we get into any sophisticated function, not even sophisticated, but. Well, the semi sophisticated functionality, they just fall apart and they don't write good code and they don't architect the code properly. And so there's big limitations that we have in those tools. Interesting. Okay, but that was. I thought we might be able to use that for quick MVPs.
David Hirschfeld [00:06:30]:
We're a long way from that. Interesting. However, so we've been testing all the code editors and we've found Cursor so far to be the best code editor that for AI code editing. But it has some huge limitations. So the problem with all these tools is there's a context problem.
Matt [00:06:51]:
Yes.
David Hirschfeld [00:06:52]:
When we as. So I. This is how I liken it. If you want me to explain what I mean by this context problem for the listeners. Do you. You. When you're developing software, you're like a juggler. And the more you concentrate, the more balls or the more things you can keep in the air at the same time.
David Hirschfeld [00:07:12]:
So I think I liken it to spinning plates, like on sticks. You know, it's pretty easy. Most of our tasks have been three plates. Even four plates isn't too tough. But you get to the fifth plate, you start your. The level of concentration starts to grow significantly. And when you're working on really complex architectural and coding issues where you have to keep all different aspects of the application in your brain at different levels simultaneously, it's like having seven or eight plates all spinning at the same time. And you've probably walked in on a developer who's in the middle of one of those.
David Hirschfeld [00:07:46]:
And you said, hey, I've got a quick question, Matt. And they go. The arms go up in the air, right? And they freak out because they realize how much energy it's going to take to spin all the plates up because they're listening to them all crash and break on the floor. Right.
Matt [00:08:01]:
And I remember there's a scene, old, you know, old movie Swordfish, where Hugh Jackman plays a coder. And there's this scene where he's like, deep in. Or maybe. Yeah, he's coding some, like, software virus and he's like, drinking wine and music is blaring. He's got 18 screens up and he's just like, deep in it anyway.
David Hirschfeld [00:08:21]:
Right, Exactly. Exactly. And then nobody. You don't interrupt them. Right. Yeah, I remember. I remember when my wife was doing her national boards. This is like your PhD.
David Hirschfeld [00:08:34]:
If you're if you're a schoolteacher, most school teachers don't do it because it's such a big deal to do it. You know, it's a lot of work. But anyway, she was writing her national boards and it was the same thing because she had to keep all these different pieces of information in her head and all these. Because there's a lot of evidence that she collects in her own classroom as she's teaching certain things, and all of that has to be in her head while she's writing this very complex. And I'd walk into her office, I'd say, becca, can I? And she go, not now, not now, not now. It was so funny. And then she. Yeah, so that's something that I sucks at.
Matt [00:09:12]:
Yeah.
David Hirschfeld [00:09:13]:
And I think I know. Yeah. Yeah, go ahead.
Matt [00:09:16]:
It's funny because I've even noticed that in just simple usages of doing some basic research for a course I'm creating or something like that. And it is. When you try to have kind of like a dialog of. Yeah, that was interesting. But what about this direction? Or can you give me a little bit more information? After two or three of those back and forth, you can totally notice it, like dropping off pieces of context that you gave it early. And, you know, it focuses on this thing and expands on that, but it forgets that you had, like, pinned it in on this thing. So that. That's interesting.
Matt [00:10:16]:
To ask that question. So. So thank you for kind of giving us the lay of the land from your perspective.
David Hirschfeld [00:10:20]:
I do want to add one little thing there. We are working to solve this problem as everybody else is. The real problem is that AI doesn't realize when its context has shifted, that there's something else out there it may need to consider, but it's not considering. We as people know that. Right. We're getting into an area. We're not focused on this other area, but we know it might have an effect on that. And so maybe we need to back up and Take a look.
David Hirschfeld [00:10:51]:
And. Right. AI doesn't do that. Not yet. Right. And what it does is it says, oh, this is my new context. And it runs away with it very often destroying good work. It's done before that, which is right.
David Hirschfeld [00:11:04]:
And we have to manage and control that. There are some tools coming out from OpenAI and from Claude and from Google that are trying to kind of reign in this problem and give you. And continue to keep the full context in its mind, but it's still not there. And we are working at building scaffolding around this as well to do it. Because right now we're probably at about 40 acceleration, 40 to 80% acceleration, depending on that area that we're working on from what we were six months or nine months ago. We want to get to, I want to get to 90% consistently across the board.
Matt [00:11:43]:
Yeah.
David Hirschfeld [00:11:43]:
And we've got. There's some big things that have to happen for us because that would put us at 10x from the productivity and acceleration and that's huge, right?
Matt [00:11:54]:
Yeah, absolutely. Absolutely. Yeah.
David Hirschfeld [00:11:57]:
Okay.
Matt [00:11:58]:
Well, in that discussion, one of the things you mentioned is that, you know, making minimum viable products is something. Is one of the first things that you're trying to use AI for. In our last discussion, I think one of the things that you focused a lot on as, and I don't know if this is exactly part of kind of the protocol that you mentioned, you know, launch first and, and things, but one of the things that you mentioned was that it's really hard for leaders to stay focused and not overbuild that. One of the things that it's easy for a leader to do is to just kind of, yeah, lose track of the story. What's the most important thing right now and get focused on a lot of details that don't matter. Why, why do you think that's so hard? What makes that so hard? In your experience, all the startups you've.
David Hirschfeld [00:12:41]:
Worked with, it's, it's a basic perspective and that's a really good question. I think it's just a basic perspective of founders because to start something new that, like what a founder is doing, they have to step out of their comfort zone and go and, and go in a direction and create and that creative process, you need a lot of motivation to do that. A lot of people aren't motivated to do that. They want security and comfort. But founders seek this kind of excitement and it's not so it's not exciting to do the hard work, the analysis, the constant reflection, the risk mitigation. Planning. Those aren't the fun tasks. Unless.
David Hirschfeld [00:13:33]:
Unless you just happen to be that kind of founder that finds all that stuff fun. But usually the people that find that kind of stuff fun aren't the ones that are creating new businesses. So it's a natural tendency to go towards the thing that's exciting, which is the creation part. And the problem is you might be creating something that nobody cares about. And that's where founders go off track. So founders that understand that their business is about the problem that their potential customers are dealing with, and every aspect and nuance of that problem and wanting to spend their time talking with customers, those are the founders that will consistently find a path to success, because the customers and the problems continually remind them of what they need to focus on.
Matt [00:14:28]:
Yeah. As you're talking, the thing that. Tell me if this is kind of what you're mentioning. I always think about, like, house projects. I used to be really bad about starting too many house projects, because one thing that I realized is that when you are 90% of the way, like, visually done, you're 50% of the way actually done. Right. Because that last visual 10% is really like 50% of the time. Is this, like the small little tweaks, the little cleanups, the.
Matt [00:14:58]:
The. Oh, I got to measure this just precisely. And yeah, I think it is really hard to be somebody who likes to do something new, but can also focus on the details.
David Hirschfeld [00:15:11]:
You know, it's funny you say house project. So first of all, what you're talking about is there's a director of development of a big firm that I worked with maybe 15 years ago, and what he. He called this being done done. So not just being done, but then making sure that all of the eyes are dotted, all the T's are crossed, all the deployment things are done, the. The communications and delivery and the documentation. Right. So that when you say you're done, you're really done. So he called that done done.
David Hirschfeld [00:15:48]:
And that has always worked. As far as house projects go, that's like, my passion is. I love woodworking and. And building and creating in that way as well. Right. And when I. My wife says, how long will that take you? And I say, oh, I'll probably have it done this weekend. She immediately multiplies by four.
David Hirschfeld [00:16:08]:
Yeah. And then that's. And she's usually right.
Matt [00:16:11]:
Yeah, yeah, absolutely. And you mentioned this in the context of founders, but I think it's often a lot of the people that get attracted to startups as well, and a lot of those early leaders in startups get attracted to startups at, in my experience, because they are that, that builder kind of personality. And so whether you're working, you know, with the founders or some of those early leaders you mentioned, it's kind of like a perspective shift. Do you, have you developed any methods or questions that you ask or just how do you help people and what can people do themselves to kind of like break that shift of their. If somebody's listening to this and being like, oh yeah, maybe we are doing too many things, or maybe my team is suffering from a lack of focus right now. How can you refocus in on kind of making sure you're focusing on the right problem, the right customers, that kind of thing?
David Hirschfeld [00:17:02]:
Okay, I want to talk about it from two different perspectives. One is kind of like when what I, how I talk to founders, when I start working with them and the first thing I ask them, you know, is I say, what's your product? What are the requirements? What. And then I say, okay, what's the genesis of this? What's the problem? It solves what I explain. And getting them to describe the problem is usually a lot of effort. Founders have lost interest. They usually lost the problem already at that point because they've decided they want to build this thing. So when I say, what's the problem you're solving? And they'll start telling me about, well, this will just make it easier for so and so. Right? And I say, okay, that's a, that's kind of a benefit.
David Hirschfeld [00:17:43]:
What's the problem? It's solving. It's. And then they go, well, it's solve it. It's. What it's doing is it's giving you the ability to do this. And I said, okay, that's a feature, but sounds like a great feature, but I don't know what's the pro. I'm not hearing a problem statement. This is very common conversation.
David Hirschfeld [00:18:01]:
Almost all founders, not all, but almost all founders, have a lot of trouble articulating a problem statement. Then when I finally get them to articulate a problem statement, it's usually a very high level one because they haven't stepped back, put their feet in the shoes of the person who they're solving the problem for and thinking, what is the real struggle? Why does it matter if they're not talking about why that person feel threatened by this problem? Because it's going to cause this terrible outcome if I don't solve it. They're not at the root level problem. And that's really where you have to get to. So that's usually the first process conversation I have with founders is getting them kind of redirected. And then I'm constantly asking them about the problem. They want to talk about features. I want them to stop talking about features and forget features even exist.
David Hirschfeld [00:19:01]:
The feature will just naturally happen as we mitigate the problem. But if you don't know what problem you're mitigating, you're not building the right thing. So you should only be talking about founders that love the problem find paths to success, and the ones that love their products fail all the time.
Matt [00:19:18]:
Yeah, that was one of the biggest things that came out of the last conversation that I had with you is just that importance of falling in love with the problem. And it's so important these days because the potential solutions to problems are changing so much. You know, the, you know, the technologies that we have available, the landscape in which it's in, they're changing so quickly that if you don't truly care about a problem, you're just not going to stick with it for long enough to really, really go after it and solve them. Awesome. Okay, so I really, I really like that framework of, well, you know, and.
David Hirschfeld [00:19:53]:
Here'S one other thing that kind of supports that framework. So I tell founders, talk to your customers or your potential customers. Spend as much time as possible doing that, and don't tell them anything about your product or about any features, and don't ask them if this will fix that problem. Don't just talk about the problems. Ask them why that's a problem. Ask them what it costs them. Ask them how much they feel personally impacted by the problem. Ask them historically, what have they done to try to mitigate this problem? Or have they.
David Hirschfeld [00:20:31]:
If they have, if they used other software to try to mitigate it, did it work? What was. Where did it fall short? Why. Why aren't you still using it? Why don't. There's other solutions out there? Why haven't you tried using those? You know, get into the history of the problem, Problem, problem, problem. They will talk because they want to talk about their problems. They want somebody to hear them and understand. They don't want to talk about your features. They're not going to be honest with you about your product, but they will be honest with you about the problems they're struggling with.
David Hirschfeld [00:21:01]:
Especially if they recognize that you really care about the problem and you really want to understand it, and you've heard other people talk about the problem and they've found some ways of reducing the impact of the problem. Doing this or that have you tried those things, you know, this is what your cus. This is what. This will teach you what to build.
Matt [00:21:20]:
I love it. Yeah. Yeah. I love, I love all that. And, and to all the leaders or, you know, all the listeners who are thinking like, well, I'm deep inside a company, you know, I don't have a customer. Everybody has a customer, you know, and I think that's really important to remember. I think some of the best organizations that I work with often use this idea of everybody in the company. Wherever you sit, you have a supplier and you have a customer.
Matt [00:21:44]:
And you need to figure out who in your customer. Maybe they're internal, maybe they're external, but it's about having that obsession with your customer, whoever they are, to understand their problems. And that's, that's how you can be successful.
David Hirschfeld [00:21:57]:
Yeah, everybody in. Has a job, if that has a job, which is anybody who's earning money, and a lot of people that aren't have to deliver something to someone. Right. So it's. So if you don't think you have a customer, then, then why are you working? Right. What are you. You're producing something or, or preventing things from being produced or whatever. Your job is that you're doing it for some stakeholder of that thing.
David Hirschfeld [00:22:26]:
And so, and, and understanding that person and what they're struggling with and what matters to them will help inform you how to do your job better. Right. It's absolutely doesn't matter where you are. Right. But people just want their problems mitigated. That's what drives all of us. People think it's about excitement and happiness and, and that is just a way of getting over this fear of missing out and, And, Yeah. And being sad and struggling.
Matt [00:22:55]:
Yeah. I mean, you know, human psychology, Tony Robbins always talks about there's two ways to motivate people. Either, you know, people either flee pain or pursue pleasure. And usually for most people, the much stronger lever is fleeing pain. That's the much stronger lever. And so identifying those problems, solving those problems is the true way to help people the most.
David Hirschfeld [00:23:19]:
And I think pursuing pleasure is just, is, is just a version of the other anyway, because you only pursue pleasure because you have fear that you're not having enough pleasure in your life or some fear, something motivating you away from a point, which is why you look for these other. If you were perfectly happy and satisfied and thrilled every moment of your life, there would be no reason to ever pursue pleasure. So.
Matt [00:23:44]:
Yeah, yeah, yeah. Interesting, interesting. I want to shift the conversation a little bit from focusing specifically Kind of on the leader to broader teams. Again, when we last spoke, you used this great phrase where you said exceptional teams leave artifacts.
David Hirschfeld [00:24:01]:
Right.
Matt [00:24:02]:
What did you mean by that?
David Hirschfeld [00:24:04]:
Yeah, they produce artifacts as a natural process of what they do that makes them exceptional. So what I mean by that is exceptional teams create very predictable results at a very high quality all the time. So to do that they have to have systems and protocols in place that they follow and ways of measuring it so there's output as a result of that. For example, we track time spent doing everything. Everybody tracks it. It's very easy. It takes a minute or two every day to basically put a bullet in a timesheet and say, I did this. And it can be a five word sentence, right? And if they have three bullets in the day or four bullets, plenty, right.
David Hirschfeld [00:24:58]:
And that way we can track exactly what they did and where they spent their time. As a result of that, we can take that and do produce reports and analytics and give it to our clients that show how the time was spent. We also go to a very deep detail for all of our estimates. Whether it's a brand new product we're building or it's new functionality on top of an existing product or new features or whatever that is, or a refactoring, whatever that thing is that we're doing an estimate for. We break it down into a lot of detail. We look at downstream effects, we look at any kind of conversion, deployment costs, whatever that is, in terms of effort and time. And we can report all this. So we know what we were expected to deliver from build to build to build, from major release to major release.
David Hirschfeld [00:25:52]:
We know when it was expected to be done and how much effort we were supposed to spend to get there. And we have all the actuals, which, from a daily, weekly, monthly basis of what we actually did, how much we actually spent, how long it actually took, and. And we make it a habit of every week in our status reports to our clients, we produce a report that shows this is what we did last week, this is what we expected to do. This is where we are month to date. This is what we expected to be month to date. Here's where we are year to date or quarter to date, right? This is our actual. What's our variance? Is our variance more than 10%? Then we need to spend some time and do a postmortem and explain to the client, maybe somebody was sick or out, maybe we ran into an unexpected problem and that we thought we understood the technology we did whatever makes that and our goal is to always be less than 10% variance from what we estimate to what the actuals are. But to do that you have to track all that.
David Hirschfeld [00:26:53]:
To be able to trackle that, you have to have an exceptional team. And that has been inculcated that understands the need for this. Not that's being forced to do it, but that just does it as a natural DNA of the right. These are artifacts.
Matt [00:27:08]:
Have you ever read Cal Newport?
David Hirschfeld [00:27:12]:
No.
Matt [00:27:13]:
No. So Cal Newport, he's probably my second favorite author. One of, one of, one of his great books is a book called Deep Work. And actually A World Without Email is probably my favorite book of his.
David Hirschfeld [00:27:26]:
But I already like him. A World Without Email.
Matt [00:27:29]:
Yeah, exactly, exactly. Everybody's like, oh, wouldn't that, wouldn't that be amazing? But what you were just saying really reminded me of a lot of what he talks about because kind of what he says, he spends a lot of time kind of comparing what happened to industrial work during the Industrial Revolution to what's happening today with information workers. And that one of the big backlash, basically what happened during the first Industrial Revolution is that we had all these craftsmen who could kind of work however they wanted to. They were artisans that, you know, they, they, they took a lot of pride in their work. And a lot of the backlash about the Industrial Revolution is we kind of systematized a lot of their work and some of them felt like they were losing things, but we gained tons of productivity. And one of his arguments is that the ch. What we're going through today in information work is similar in that historically we've thought of the workplace, especially for information workers or white collar workers or whatever you want to call them, as the right way to do it is to be very hands off. Not be, be very specific about the outcome you want, but don't be specific or prescriptive about how to get that work done.
Matt [00:28:50]:
You leave that up to the experts who can do their thing. And similar to what I'm hearing, what you're saying is, and this is, I think what Cal Newport talks about is like, you know, you don't need every software engineer to spend a portion of their time figuring out how they're going to document their work or answering the emails or keeping track of the other project, you know, figuring out their own method for project management. The most effective workplace is going to be one where the system for how the other stuff gets done, the documentation, this, you know, the project planning, that needs to be a very robust system. And then the workers don't have to figure all that out and 100% of their energy can be devoted to getting the work done because they don't have to spend time worrying about all this other stuff. That. That's at least some of what I heard in what you were saying. Does that, does that sound right?
David Hirschfeld [00:29:50]:
Yeah, that I think is exactly right. And one of the ways that we're able to accomplish this. So I have a hiring philosophy, and that is I only hire people if they're smarter than I am, and that ball rolls uphill. So my director of operations, who's really smart, it's hard to find people smarter than her. But again, she only hires people if they're smarter than she is. Right. In terms of what they're able to deliver in the context of what we're. They're being hired to do.
David Hirschfeld [00:30:21]:
Because if they're. Because otherwise you send the wrong message to the team. If you don't hire people that are smarter, that pick up the. Elevate the team and add value to everybody. But also, then you're also having to carry people that. Which means that you can't. So I, I look at it like this. Our job as me, as a company owner and director of operations and project manager, our job is basically chimney sweeps.
David Hirschfeld [00:30:49]:
Our job is to sweep all the impediments out of the chimney so that our developers, our QA people, our analysts, can just work fast and freely and be creative and add value to the systems and the processes. Not to drive them. Our job is not to drive them. We want to motivate them in terms of we're working on exciting things, look at the cool things we're doing. But. But then we want them to be. Create a vacuum in front of us. Right? Because they're going so fast and so broadly that it's sucking all the oxygen and we're rushing to fill it back in from behind, not pushing them.
David Hirschfeld [00:31:27]:
So that's kind of how I look at our role as, you know, as managers is a bottom. It's a we lead from underneath.
Matt [00:31:38]:
Yeah, I like that. I like that. To. To play devil's advocate for a second, because I can hear somebody saying, you're saying that your job as a people manager is to remove all the impediments. But on the other hand, you're saying you have these, like, very prescriptive rules about document it this way, do this thing, put it in here at this time. Aren't those barriers to getting. Just getting to the work.
David Hirschfeld [00:32:01]:
They're systems that they work within. So no matter who you are, you're always Working within a system of some kind, unless you're working by yourself. And if you work by yourself, you start to develop systems because otherwise you end up losing big chunks of work because you didn't back it up properly or you end up rewriting things because you didn't abstract it properly or whatever as you start to develop your own systems. Right? So we're providing these systems and protocols and we're providing a lot of automation around it so that they don't have to do a lot with it, right? They just have to learn it. And, and then we provide a lot of scout management scaffolding that can account for the work that they've done and remind them what they're missing and that they need to do this until they get into the habit of doing those things. But we don't have people that are pushing back on. Oh God, here's another rule that we have to follow. It's not like that.
David Hirschfeld [00:32:57]:
Yeah, there are certain things like we have standard operating procedures when we develop Screen, a screen, for example, we want our, our styling, our prompts on the screen to look and behave a certain way. So. But we document all this stuff, right? And we teach our developers, you know, when you're doing something, go to the place where all the SOPs are and look up the sops for your particular, for the thing that you're working on and see if there is one. If not, then don't worry about it. And we document playbooks so that everybody understands if they have to do something that follows certain protocol, there's a playbook that documents it and that gives you all the visual flows and everything. We have to do some of that because we have a lot of projects that are compliance oriented like healthcare, law enforcement, and we have to follow very strict compliance guidelines in those cases. That has to be enforced and wrapped around the project. But everybody knows that going into these projects and they just learn what those workflows are, even how a bug is reported, how that gets the feedback loop, the flow through development and tests.
David Hirschfeld [00:34:09]:
All that has to be very accurate because we get audited yearly by a third party auditor on whether we have the last six months we've been compliant in a pristine way or not. Nothing to do to get around those things other than provide automation and tools that make the documentation really easy and effortless to, you know, to stay within those guidelines.
Matt [00:34:33]:
Well, I love, I love how you pointed out that the creation of systems is, is just natural, that it just does happen. Because I used to always say that I thought organizations that had the most disdain for bureaucracy, were the most likely to succumb to bureaucracy and red tape, because bureaucracy, it's a thing that just naturally occurs in a large organization. And the way to avoid it is to embrace it and deliberately plan it out and plan those structures. And, you know, I think everybody.
David Hirschfeld [00:35:06]:
Including everybody in that process.
Matt [00:35:09]:
Exactly. And I. And I think that's the same. You know, what's true at the organizational level is true at the small team and even the individual level of if you're going to get work done, you have to develop systems. And so you might as well be proactive about it and really think about it. Because as you say, exceptional teams have those artifacts. It's not an accident that you achieve exceptional results again and again. There's systems there that you can point to and say that is why they are achieving those exceptional results.
David Hirschfeld [00:35:39]:
And, and we have a kind of a philosophy that we're never good enough either. And we have never had, you know, we're never exceptional enough. And so we understand the gaps that we have and where those gaps can make us better and faster and more accurate and improved quality and, and improve team morale and, you know, in every respect. Right.
Matt [00:36:02]:
Yeah.
David Hirschfeld [00:36:03]:
So. Because what will happen is if you don't constantly strive for all that stuff. Right. Then. Then, like I was saying, and like you were saying, everybody starts to build their own systems for the things that they're doing all the time. Then you've got two or three different people doing similar things with completely different systems in place. Yes. And there's no consistency from one project to the next or from even at one developer to the next in terms of how they're creating and developing and, and communicating and orchestrating.
David Hirschfeld [00:36:31]:
Right. And then you. And that's not uncommon, by the way. That's probably fairly common in most development teams. That there's some of that. And that's.
Matt [00:36:41]:
Yeah.
David Hirschfeld [00:36:42]:
And I call that sort of the average mediocre development team that's productive. But, but they, but they have all these limitations because of this lack of, you know, highways, you know, technology highways internally.
Matt [00:36:55]:
Yeah. Yeah. Well, this is. This has been great. I mean, I think if I'm. If I think back to the conversation, kind of the two biggest takeaways that I would have for a leader at any level in any organization. Number one, it's the importance of understanding your customer and their problems. That is the kind of the path forward to making sure you're not creating what you don't need to create, building what you don't need to build.
Matt [00:37:20]:
And that you really get passionate about solving the problems of your customers. And then once you're clear on that, if you want to deliver on those, solving those in an exceptional way. David and I are giving you the green light to create systems and rules for your team. Because I do think a lot of new leaders are hesitant to do that. You know, they don't like whether there's systems there or not. They're very hesitant to create standards of how work is done on a team. You don't want to be draconian about it because you said include everybody. You don't want to say like this, it's my way or the highway.
Matt [00:37:55]:
But I think hopefully this episode gives you the green light, gives people a green light to start to have that conversation of norming the ways that you get work done on your team so you can get it done faster.
David Hirschfeld [00:38:09]:
Do we have time for me to add one more aspect to that?
Matt [00:38:12]:
Yeah, absolutely.
David Hirschfeld [00:38:14]:
Okay, so one other thing is maybe you're thinking there. Well, actually two other things. One is the idea of playbooks. When you have a system that does work really well and you have a lot of tribal intelligence around the thing, like you've got a few people that really know how to do this certain thing, have them start to document these processes and playbooks. And if you say, oh, I can't because there's just too many decisions, I call those nuances. Then have them document the nuance, the nuances, the decision point. And when they veer off the standard approach to doing that, and there may be lots of those, but that's okay because when you want to scale and bring new people in, you don't want them sucking all the energy out of your most productive people that know how to do these things. Well, you want those people only to do some high level training to get them started and give them a resource where they can find out all the nuances and every little aspect of that job.
David Hirschfeld [00:39:16]:
Because it's all been documented really solidly in a playbook. So that's number one. And, and playbooks aren't. You don't build the whole playbook for your business all at once. You do it kind of.
Matt [00:39:26]:
Yes.
David Hirschfeld [00:39:27]:
One, one little channel at a time. Right. And you just keep evolving it. Right.
Matt [00:39:32]:
The. The number of companies that get bogged down in forever. And like, okay, we're creating the official. We're just documenting it all today. And it's like you're just, you're never going to it done.
David Hirschfeld [00:39:42]:
That just doesn't happen the other. But playbooks just Recognize the more you have this stuff documented, the more your business is worth because somebody that might eventually buy your business is also buying all of this documented knowledge about how to operate effectively. The second thing is if you, if you're not sure about where to grow exceptionalism or how would you know that you get there, that sort of thing, you probably don't have a system of measuring yet. And that's the place where you start. Because you can't become exceptional if you don't have a way of measuring it. And if you don't know where a way of measuring how not exceptional you are yet, then you need that before you start. Because once you start to measure it, you start to recognize what has to transform to start to bring you to that, to a higher level. So systems of measurement are like critical success factor for becoming exceptional.
Matt [00:40:41]:
I love it. Those. Yeah, those last two bits were absolutely perfect. If anybody happens to be listening, since we got a lot of. I know we have a lot of engineers that listen thinking about their next company. If they're looking for help with some software, where can they find you?
David Hirschfeld [00:40:56]:
They can find me@techies.com. techies is spelled T E K Y Z T E K Y z dot com. If you've made it all the way to the end of the show, then I'll give you my email. It won't be in the links, but it's davidechies.com and I'm easy to find on LinkedIn.
Matt [00:41:17]:
Perfect. Yeah. Everybody make sure to prove to David that you made it to the end and email him directly with your questions. This has been great. Thank you so much, David, thanks for having me. Matt, thank you so much for listening to today's show. If you are looking for help turning your organization's great engineers into great managers, me and my team at Better Everyday Studios would love to help we deliver targeted and interactive training workshops that are designed to help build the three fundamental skills of any new manager. Building trust, giving feedback and setting goals.
Matt [00:41:55]:
Reach out to me through matt better everydaystudios.com so we can start making your organization better every day.

