Latest / Engineering Influence from ACEC / Engineering Isn't Broken-The Flow of Work Is
Transcript
- 0:05Hello and welcome to another episode of the Engineering Influence podcast.
- 0:09My name is Shreya Jain and I will be your host for today.
- 0:12Engineering firms are full of talented people doing important work,
- 0:16yet so many teams struggle with burnout, rework, slow decisions,
- 0:20computing priorities, and communication breakdowns.
- 0:23This conversation will explore a different way to understand those challenges.
- 0:27Rather than assuming the problem lies with the people, we're going to examine
- 0:31the flows and the workflow that are created through the organization.
- 0:35We'll discuss organizational conditions that create friction or flow,
- 0:39and how leaders can identify systemic barriers that make great people's jobs
- 0:43harder than they need to be.
- 0:44I'm very pleased today to be joined by Jessica North, the CEO and co-founder
- 0:48of Evernorth Solutions, to walk us through fixing these broken workflows and
- 0:52addressing the issues facing engineering firms. Thank you so much for joining us today, Jessica.
- 0:57Hi, Shreya. Thank you so much for having me on.
- 1:00Amazing. You always say that engineering firms aren't broken. Workflows are.
- 1:05So what are we getting wrong when we treat organizational problems as people
- 1:08problems? I'm really glad you asked that.
- 1:11Engineering isn't broken. The flow of work is.
- 1:14We're often too quick to blame people for poor performance when the real problem
- 1:20is incomplete information, unclear decisions, competing priorities, or broken handoffs?
- 1:28I think before we ask who failed, we should perhaps be asking what made it difficult
- 1:34for this person to succeed?
- 1:36That's a really great answer. And I think that really addressing what could
- 1:40have made it difficult for a person to succeed is so important because when
- 1:44you hire someone, you're not going to hire someone who you think is going to fail, right?
- 1:49It's just that they might not have been able to understand the communication
- 1:53within the firm that they joined. Absolutely.
- 1:57So what does this organizational flow look like inside an engineering firm?
- 2:02And in your experience, where do people most commonly see friction that might
- 2:07disrupt otherwise high-performing employees or teams?
- 2:11Yeah, so friction can really show up anywhere.
- 2:15And when we talk about flow, let's look at metrics.
- 2:21I kind of want to scooch over to the metric side because technically metrics are not a bad thing.
- 2:28Metrics are necessary, but I think they only tell part of the story.
- 2:32And at the end of a project, metrics can tell you that a project succeeded.
- 2:39It can tell you how well it succeeded.
- 2:42And same with our performance metrics as an overall organization.
- 2:47What those numbers don't tell you is how the organization accomplished that?
- 2:55What work had to happen in order for those numbers to become true?
- 3:02So when we're looking inside of an organization, the friction areas can really
- 3:10be from just about anywhere.
- 3:13Those extra 30-minute, hour-long meetings where they're not really necessary,
- 3:19but we have to have them five times because we haven't quite gotten the message
- 3:23through. That's a communication process.
- 3:26Problem, potentially a communication problem.
- 3:30Or we look at rework. How much of rework is actually necessary or is perhaps
- 3:36a learning gap or a capability gap or a communication, again, a communication gap.
- 3:43And so friction can come from anywhere. And it's not a single point of friction that causes an issue.
- 3:52It is the aggregation of a lot of friction that we're looking at that comes
- 3:59up and really starts showing a breakdown in organizational flow.
- 4:05Yeah. I mean, the whole, this meeting could have been an email thing.
- 4:08Like, I know it's a joke now, but sometimes it really can be emails. Yeah.
- 4:14And joking actually can be a really good sign that there is something in the
- 4:19system that is struggling.
- 4:21When we start joking about, oh, that's just the way it is.
- 4:27That's an opportunity to take a beat and be like, why? Does it have to be this
- 4:31way? Is there a way we could do this better?
- 4:33Often, our human path of least resistance is to do what we've done before or laugh it off.
- 4:45What we like to dig into and look at is, is there a different way to do this? Is there a.
- 4:51Maybe not a better way, but is there a way that's going to cut down some of the friction?
- 4:57Yeah. And like every firm's better is going to look different.
- 5:01What is better for one firm may not work for the other. Everyone is different,
- 5:05different priorities, different people with different personalities.
- 5:08So it's really about what works best for a single team in a single firm.
- 5:13Absolutely. And that's where we like to talk about culture, right? Right.
- 5:17100%. So speaking of different firms, different solutions, engineering organizations
- 5:25will respond to problems with new processes, new technology,
- 5:29training programs, initiatives.
- 5:31Why do those solutions fail sometimes if like the underlying organizational
- 5:36system was attempted to be addressed?
- 5:40Yeah. So that is something we often run into is either a process needs a workaround.
- 5:49So you've got an engineer that's creating their own spreadsheet,
- 5:52their own way of tracking, or training is set up to be done by individuals.
- 6:00Usually, from what I've seen and I've experienced, is senior engineering or
- 6:06senior leadership are the ones that are also doing the mentoring.
- 6:11And I think when we throw in a new process or a new technology or a new initiative,
- 6:22what we're doing is we're trying to solve an outcome.
- 6:26We're seeing an outcome that we don't like and we're trying to solve the outcome.
- 6:32Where we like to see and where we like to dig in is are we solving the conditions
- 6:40that created that outcome,
- 6:43and oftentimes adding a new process adding a new platform,
- 6:48adding a new training program actually just can create more friction you are
- 6:54asking more of your senior leadership or your senior,
- 6:59engineering staff to carry more of that burden,
- 7:04in order to accept these new initiatives.
- 7:11Definitely. And I think that's also like what you mentioned about culture 100%.
- 7:15And it also has to do with, I think the workforce shortage that's currently
- 7:19happening because so many of these senior leaders, they might be close to retiring
- 7:24soon and they don't want a loss of knowledge to happen.
- 7:26And this mentorship and making sure this knowledge transfer happens,
- 7:30that responsibility is on them, even though that's not technically something
- 7:34that can really be evaluated in terms of metrics.
- 7:37Yeah, absolutely. And there is not usually a very good mechanism for...
- 7:45Sending that information back and forth for maintaining what we call institutional knowledge.
- 7:52That tacit knowledge is a really difficult thing to pass down.
- 7:59And that is another challenge that we understand and we aim to help address.
- 8:09I think that's so important, acknowledging and addressing that problem.
- 8:12So moving on to the next question, how can leaders distinguish between an individual
- 8:17performance problem and a systemic problem that is making it difficult for people to succeed?
- 8:23Yeah, that's a hard one. I think that's kind of the crux of,
- 8:28why we're doing what we're doing and why we're seeing what we're seeing is we
- 8:33tend to see our issues as people problems,
- 8:39and that's where we look first because let's be honest the system's been the system,
- 8:47but I think what we've forgot is that as our projects have complexity and industry complexity has grown,
- 8:58what we've done is added more trade-offs more handoffs and more communication points So I think.
- 9:07A good way to look at this is that you can have great engineering teams.
- 9:11You can have great construction teams.
- 9:14You can have great permitting teams.
- 9:17But what is potentially broken in between those teams?
- 9:24You can have stellar PMs.
- 9:27And it's not that they're not getting the work done. It's not that they're not doing.
- 9:32We're of the belief that individuals are just trying to do their best.
- 9:38They're doing their best job.
- 9:41What is it about the organization that exists that's actually making their job harder?
- 9:48That's what we find really interesting.
- 9:51Yeah, definitely. I think that's so interesting. And what you described,
- 9:55like individually, teams can be great, but maybe collectively there could be issues.
- 10:01And, you know, like no company works, it should work in silos.
- 10:04Everything is interconnected. Everything is interdisciplinary.
- 10:08So I think that's an extremely important point.
- 10:11Yeah, and so often we do. So often when I have conversations with executives,
- 10:19I ask that question and, oh, yeah, well, we're so siloed is a very common response that I get.
- 10:30And that just tells me that we're building friction into our actual organization,
- 10:38and possibly calling it a people problem.
- 10:42We need more people. We need less people. We don't have the right people.
- 10:47Maybe it's not the people.
- 10:51And that goes back also to like the rework. And obviously you mentioned the
- 10:55friction also. Because if you don't know what another team is doing and then
- 10:58you do it again, then that is definitely a problem.
- 11:01Right. Exactly.
- 11:04So when you speak with these executives and like, you know, they admit sometimes
- 11:08they're siloed or they admit they have other problems.
- 11:11When a leader does suspect that organizational friction is costing their team
- 11:15the time, their energy, lowering their performance, where should they start
- 11:19looking? What should they address first?
- 11:21Yeah, I think it's hard. You can't just jump in and address something.
- 11:26And I wouldn't be a good engineer if I didn't say, it depends.
- 11:32What I would encourage leaders to do today is to ask hard questions and then listen.
- 11:40Don't try to solve. Don't try to give an excuse. Don't try to help them understand,
- 11:47why things are the way that they are.
- 11:49Really listen.
- 11:52And if you give them the psychological safety to start giving you honest responses,
- 11:59because that plays a big role in it too.
- 12:02Are they telling you what you want to hear or they think you want to hear or
- 12:05are they telling you what's really causing them heartache?
- 12:10Ask them hard questions.
- 12:12What is making your job harder today than it was yesterday? Let them go.
- 12:19I think that's really important, just being able to listen without immediately,
- 12:24trying to offer a solution.
- 12:28We had a guest speaker at one of our conferences last year, and she was talking
- 12:34about how it's important that the leaders be the ones to speak last in the room
- 12:38if they have ideas or anything, because if they present their idea first,
- 12:41then a lot of people are going to want to go along with that.
- 12:43But if you let everyone present their ideas, you might come up with something
- 12:47that you hadn't thought of before, but you can actually go along with it now
- 12:51because people aren't agreeing just to your idea as a leader.
- 12:55Absolutely. And I think it's important to understand when you've created psychological safety.
- 13:01Because I've been in those rooms as a leader, and I've put the question out
- 13:05there, and I've sat in silence for five minutes waiting for somebody to speak up.
- 13:14And I think that's a really big signal there, is if folks aren't willing to
- 13:19speak up, they either haven't thought about the question before.
- 13:26Or is there a potential that they don't feel safe enough to tell you what the real issues are?
- 13:33And then you've got a whole nother issue on your hand. Then you've got a whole
- 13:37nother thing to dive into and explore.
- 13:41I guess that's a really good place to start, though, to really understand what
- 13:45problems people might be facing. Yeah.
- 13:48I think we are getting close to about all the time we have for today.
- 13:52Do you have any other final thoughts you'd like to leave us and our listeners with?
- 13:57Yeah. You know, I would just like our listeners to understand that we're looking
- 14:06at what happened versus what produced that.
- 14:11So when you're looking into your organization, it's really important to understand
- 14:18that those existing metrics are there for a reason and they are important,
- 14:23but to possibly understand that they're only part of the story and that learning
- 14:30organizational flow and workflows is helping discover that other half of the story.
- 14:38Let's make decisions based off of better, more well-rounded,
- 14:44fuller data, not just partial data.
- 14:49That is extremely, extremely important. And I thank you for bringing that point
- 14:54and this whole issue of it's not a people problem, it might be a workflow problem
- 15:00to light to our podcast today.
- 15:02So, Jessica, thank you so much for joining us today. I enjoyed our conversation.
- 15:06Thank you for being here.
- 15:08To our listeners, thank you for joining us for another episode of the Engineering Influence podcast.
- 15:13Please make sure to like and subscribe and we'll see you next time. Thank you.