Aug 18, 2026 · 40 min · 10 segments
Digital transformation is often approached as a technology project: identify an outdated system, select a replacement, implement it, and move on. But as James Davies explains in this episode of **Tech…
James DaviesGuest
Carolyn FordHost
So if you think about an organization like a city, like a city infrastructure, when you help organizations modernize, transform, what are some of the bridges or tunnels that you see in this, you know, city metaphor as part of the organization's processes, what, what are some of the bridges and tunnels that get ignored until there's a traffic jam or, you know, the, the water's backed up so far that we're in trouble?

We, we, we tend to operate in silos and it's just, I think it's just, we, we, we try to find our, like our little our little communities, even within a big organization.

So again, on the commercial side, it's like a finance team and an HR team, etc.

But the biggest breakdown that I always find in gaining efficiencies is the handoffs between teams.

You know, there's a lot of processes that cross between teams, or it starts with one team and then moves to another.

And part of that is integrations with different systems and where people are working.

So you've probably worked for an organization and had to kind of start a process in system A and you finish it and maybe you get a ticket number at the end.

And then you got to re-enter all that information into system B and then into system C. I mean, it's just all over the place.

If an organization can own what I call the glass or the user experience, the windshield, so to speak, and they can have at a higher level some control over what that looks like, how that works, and then allow these silos to participate with their own systems, their own processes, etc., that glue helps you to really stitch together the organization and make it feel like one thing.

And I see that that's where a lot of the efficiency gains are that you'll get because it helps to move the process forward when there's handoffs between teams.

So that gets down, it does get down into integrations and how integrations work with different things.

But I think if you peel back the onion even more, it's like, what's the experience need to be like for an end user when they're having to interact with what they think of as one process, but it might cross between many teams and break down the friction there.

You know, something didn't get entered the right way into system B after doing, you know, starting its process in system A.

What our software does, what we aim to do is enable the people closest to the problem to solve the problem.

So if you think about an organization like a city, like a city infrastructure, when you help organizations modernize, transform, what are some of the bridges or tunnels that you see in this, you know, city metaphor as part of the organization's processes, what, what are some of the bridges and tunnels that get ignored until there's a traffic jam or, you know, the, the water's backed up so far that we're in trouble?

We, we, we tend to operate in silos and it's just, I think it's just, we, we, we try to find our, like our little our little communities, even within a big organization.

So again, on the commercial side, it's like a finance team and an HR team, etc.

But the biggest breakdown that I always find in gaining efficiencies is the handoffs between teams.

You know, there's a lot of processes that cross between teams, or it starts with one team and then moves to another.

And part of that is integrations with different systems and where people are working.

So you've probably worked for an organization and had to kind of start a process in system A and you finish it and maybe you get a ticket number at the end.

And then you got to re-enter all that information into system B and then into system C. I mean, it's just all over the place.

If an organization can own what I call the glass or the user experience, the windshield, so to speak, and they can have at a higher level some control over what that looks like, how that works, and then allow these silos to participate with their own systems, their own processes, etc., that glue helps you to really stitch together the organization and make it feel like one thing.

And I see that that's where a lot of the efficiency gains are that you'll get because it helps to move the process forward when there's handoffs between teams.

So that gets down, it does get down into integrations and how integrations work with different things.

But I think if you peel back the onion even more, it's like, what's the experience need to be like for an end user when they're having to interact with what they think of as one process, but it might cross between many teams and break down the friction there.

You know, something didn't get entered the right way into system B after doing, you know, starting its process in system A.

What our software does, what we aim to do is enable the people closest to the problem to solve the problem.
The rest of this transcript — segmented and speaker-labeled, so you land on the exact moment something was said
Search every transcript — by keyword, by phrase, or by meaning, across every show Radar indexes
Trends — what is surging across podcasts, measured against its own baseline
Alerts — when a name you follow appears in a newly indexed episode
No account is needed to search Radar.