Resilient Supply Chain — How Leaders Keep Business Moving
Resilient Supply Chain is for supply chain, operations, procurement and technology leaders who need practical ways to manage disruption, reduce risk and keep business moving.
First launched in 2019 as Digital Supply Chain and later known as Sustainable Supply Chain, the podcast continues today as Resilient Supply Chain, with the same extensive archive of more than 525 episodes covering supply chain technology, resilience, logistics, procurement and sustainability.
Each Monday, technology and sustainability analyst, keynote speaker and former SAP Global VP Tom Raftery speaks with the executives, operators, founders and innovators redesigning how goods, information and decisions move through global supply chains.
These are candid conversations about what works in practice—not polished PR narratives or vague predictions. Guests explain how they are responding to supplier failures, geopolitical shocks, volatile costs, capacity constraints, changing regulations and rising pressure to improve both performance and sustainability.
The podcast examines:
Faster planning and decision-making under uncertainty
Supplier risk, sourcing strategy and business continuity
AI, automation, visibility and operational intelligence
Warehousing, logistics and fulfilment performance
Scope 3 emissions, circularity and responsible sourcing
The systems, incentives and organisational changes needed to turn data into action
The central question is simple: what helps a supply chain withstand disruption, adapt quickly and continue serving the business?
New episodes are published every Monday at 7am CET. Resilient Supply Chain+ subscribers also receive bonus analysis, highlights and briefings on emerging industry trends.
Follow Resilient Supply Chain for practical lessons from the people solving real operational problems—and building supply chains that perform when conditions do not go to plan.
A production line can go down because two people are passing an Excel file back and forth with no audit trail. That is the uncomfortable reality behind this episode: some of the biggest supply-chain risks sit inside ordinary workarounds that nobody questions because, until they fail, they appear to work.
My guest is Patrick Van Hull, now an Agentic Operations Consultant at Salesforce and, when we recorded this conversation, an Industry Consultant at Tungsten Automation. Drawing on experience across companies including Dell, Rio Tinto, Apple and CVS Health, Patrick has seen how document flows, manual hand-offs and disconnected processes can create delays, downtime and business interruption far beyond the back office.
We examine why automating a broken process can simply make the inefficiency faster, why a single inbound supply chain can involve more than 30 documents, and what frontline teams know that formal process maps often miss. We also challenge the assumption that an AI strategy should come before clarity about the work itself — and ask where human judgement still matters most.
Listen now to understand where hidden workflow risk enters your supply chain — and what to fix before you automate it.
If disruption hit tomorrow, would you know where your supply chain was most exposed? In 15 minutes my free scorecard helps you assess 27 resilience statements, calculate your score, and turn the result into three priorities and a 30 day action plan. You can download the scorecard free at tomraftery.com/scorecard.
Podcast supporters I'd like to sincerely thank this podcast's generous Subscribers:
Alicia Farag
Kieran Ognev
Gary Lynch
And remember you too can become a Resilient Supply Chain+ subscriber - it is really easy and hugely important as it will enable me to continue to create more excellent episodes like this one and give you access to bonus episodes of topical, timely supply chain resilience analysis.
🎤 Looking for a keynote speaker on supply chain resilience, AI, and sustainability? I help leaders understand the forces reshaping global supply chains, from geopolitical disruption and climate risk to AI and real-time decision-making.
Download my Speaker Pack: https://tinyurl.com/spkrpck
Finally If you have any comments/suggestions or questions for the podcast - feel free to just send me a direct message on LinkedIn, or send me a message using this link.
But let's take a break and just say, Hey, you know what Here's how this process works in reality is we're, sending an Excel file back and forth with no check and balance, with no audit. And it's two people. When that process breaks down, the outcome is a production line going down. That's problematic.
Tom Raftery:
The real fragility in a supply chain isn't always where you expect it. Sometimes it's buried in the handoffs, spreadsheets, and workarounds people rely on, just to keep things moving. Good morning, good afternoon, or good evening, wherever you are in the world. Welcome to episode 143 of Resilient Supply Chain Stories and strategies that Keep business moving. I'm your host, Tom Raftery. My guest today, Patrick Van Hull has seen that firsthand across companies including Dell, Rio, Tinto, Apple, and CVS Health. And one detail really stood out to me. A single inbound supply chain can involve more than 30 documents. So before we automate more, we need to ask a harder question. Do we actually understand how the work gets done? Let's get into it. Patrick, welcome to the podcast. Would you like to introduce yourself?
Patrick Van Hull:
Thank you, Tom. It's a absolute pleasure to join you. Certainly we've run in similar circles for a number of years and now we're getting the chance to sit down. My name is Patrick Van Hull. And I'm focused on the supply chain vertical where we're looking at the opportunities to automate many of the documents and data and processes that are foundational to the success of modern supply chains. And it's often overlooked the things that go into that. As we think about all of the successes or unfortunately the failures of supply chains, but it's persistent throughout. As we look at that intersection of the physical and informational and the financial flows that all come through supply chains.
Tom Raftery:
And what made you realise that, you know, supply chain resilience, this being the Resilient Supply Chain podcast, that supply chain resilience is often a document and workflow problem.
Patrick Van Hull:
Just pain quite frankly, is, is the, those moments throughout the course of my career. My career started as a practitioner and, and so I spent a lot of time working for companies like Dell, Rio Tinto, Apple, and then CVS Health, the retail pharmacy chain here in the US before moving into executive advisory types of roles. And then since into strategic roles with SaaS solutions. And a couple of stories of Excel failures. Times that I sent the wrong version of a file, time that I didn't refresh a pivot table. And those are the things that made me realise how the simplest mistakes have those cascading impacts. And that it's not just what we see of moving a truck or a plane or a pallet or a box, but it's often all of it that comes together and really just that visceral memory of some of those painful moments that sticks out that, really underpins my entire philosophy, I'd say.
Tom Raftery:
Yeah. I mean, we, we've all done it. As well a shipment can be stopped by a port closure, but equally it can be stopped by an incorrect customs form.
Patrick Van Hull:
Exactly, and it's, it's one of those things too, is that when we see the disruption in supply chain, we see an empty store shelf. It's very easy to blame the generic supply chain for that. But there's so many steps that happen beforehand. There's so many documents that are part of those transactions, and oftentimes what we see is actually something that manifested itself days, weeks, months earlier. And it's just getting to the point where it's reached a breaking point. And really, it's unfortunate, but a lot of times we have to go back and recreate what happened, to really understand where that failure occurred, because it's not something that's evident to us in those moments.
Tom Raftery:
And we're seeing now that Amazon is opening more of its logistic network to other businesses. And so the expectations as a result of speed are going to rise. So, what does that change for everyone? And where do companies usually feel the pain of this first?
Patrick Van Hull:
One of the things that's really interesting about the Amazon proposition and, and certainly thinking about kind of the Amazon ification of expectations and, and I always talk about the fact that when we go to checkout using Amazon, we always get those radio buttons that say you can get it in one day, two days. You can get it in a week with some type of discount or incentive. And so really that's the, level of Amazon saying, look, you can feel like you have a choice in the matter, but these are all things that we're gonna execute it upon whether or not you decide one versus the other. And so it's oftentimes that we are now trying to extend that to others. They've got that same expectation, even though they've never built those supply chains along the way. It's going to expose some things. And so when we think about that last mile, that's only part of the process. And, and we think about all of the steps that occur from that. There's a lot that goes into getting it from my distribution centre to Amazon's. It's takes a lot to get it from my suppliers to me. And so delivering on that point to point, as many supply chains have done historically, creates many friction points. And we work around them. The expectation now becomes this has to be seamless because the Amazon effect is something that we're signing up for and the expectation that we're going into is something we've never had to deal with before. And so I think that's just one of the callouts there is that it's fantastic. Anytime an industry leader is willing to share and help others grow, we absolutely need to embrace it, but we can't go into it blindly knowing that they're gonna fix all of our problems.
Tom Raftery:
Okay. And those workarounds that you mentioned, what kinda workarounds, what do they look like in a real supply chain?
Patrick Van Hull:
Just, for example, if we're talking about integration between systems and we talk about the swivel chair types of behaviours that exist, or I'm going to export out of my ERP system and I'm going to put it into an Excel file and I'm going to take data from a my planning solution and I'm going to then apply V lookups. And those are a lot of things that we put into place. It's manual brute effort to try and force things together, but it's not necessarily the right way to do it. It's to say that we're using what we have, the ingenuity that we have to get us to the point where we're successful today. But now we're looking at tariffs and geopolitical conflict and all these different things that are happening all at once. And our supply chains were never built to deal with the entirety of it. We're just built to try and get through that next thing on our task list. And we should celebrate that. And first and foremost, I think that our supply chains have done a fantastic job of dealing with all of this. It never gets enough credit for the, fact that supply chains enhance the human experience or even deliver the human experience. But we're now looking at the people doing the work. I've just been so bombarded with tasks and activities that they've put themselves in the position where they're taken from one hand and given to the next, and they're going as fast as they can. And it's not necessarily that it's the right process, but it's a process that helps them move.
Tom Raftery:
Okay, and these hidden workarounds, when do they become a business risk?
Patrick Van Hull:
The day they're instituted, frankly, I, I, I would say that that's the piece. And so, like for example, I use that story, the Excel file, story is that, I was working for a major consumer electronics company during a product launch and we were sending files from the factory back and forth. And part of the reason for that was that, the frequency upon which we were sending the files overrode any type of system capability. We didn't have any checks and balances in place. It was person to person, peer to peer file transfer, and it was, unstructured. And so when I look back at that example and I, I, I see that the, problem occurred because I got the file, didn't double check it, and then sent it back. It created the ripple effect that the factory didn't expect what I sent to them. So they needed to take a moment to digest what had actually been sent to them, And that became a business process. The fact that we were sending emails back and forth with Excel files attached, that first time it worked. And so we just started doing it more and more. And that's the place when it became a business risk is because we don't ever go back and say, is this the right way to be doing this? It just becomes the way that we've always done it.
Tom Raftery:
Right. And what type of documents create the most operational drag? Is it Excel like you said, or is it something else?
Patrick Van Hull:
Everything. When we look at the combination of the documents, it's less about any single document, a bill of lading, a PO, an advanced shipment notification, goods, receipts, invoices, all of those types of things. It's never any one of those, but it's the ability to bring all of those into the process and then being able to match them, to reconcile them, to process them. It's just the volume of documents and, and we see that it can be 30 plus documents over the course of an inbound supply chain by which that's what it takes to get a product from supplier to customer. So to say that it's one thing, and if we just fix that one thing, the problem secured is really just ignorance. It, it's trying to understand the information that's in all of that, trying to identify where there's gaps when we receive it, as it happens, as opposed to trying to rectify it after the fact. And that's one of the things that, even when I use that Excel example, is that I spent a week trying to figure out what had gone wrong. And it came down to the simple fact that I got the wrong version of the file, but I wasted hours and then I eventually fell on my own sword, so to speak, and, said, this is what the problem was. My management team nodded its head and said, yeah, that's a risk that we've accepted as part of the process. Good to know. What should we do about it? And it wasn't stop sending Excel files. It wasn't stop processing the data, it was put checks in place so that you don't do it again. That's the thing that happens extensively with these products and, and these processes.
Tom Raftery:
Mm. Yeah. Yeah. And these kind of document issues, where do they turn into things like cost, delay, customer damage, all that kind of thing?
Patrick Van Hull:
Yeah, just think about if something gets stuck in a bonded warehouse, a product's coming in, you have a number of different documents that come into this process. In order for it to be picked up, you need to clear everything. But let's say you get stuck because there's not the hazardous material declaration and it's got batteries in it. It's got something like that. It's that one out of five documents in one out of a thousand shipments. But that one piece of document, that one form isn't completed, so you're holding up an entire container's worth of product. And so that's where you start to see the manifestation of the, delays is that it's not anything that we really are looking for, but it's, we catch it after the fact when someone says, Hey, this is missing. As opposed to doing the kinda the rules and the the process upfront where we know what's missing as it comes so we don't have to deal with it. We can start that process as it's happening in motion.
Tom Raftery:
And with that Excel document example that you gave, what would've been the right way to fix it as opposed to putting the checks in place?
Patrick Van Hull:
Yeah, I, I, I mean ultimately I think that it in that moment, because we were moving so quickly, it was a product launch. We were on a schedule. There wasn't anything that we could have done at that moment, but to go back and do a debrief, to go back and say, Hey, this problem arose during that, launch. And it was a process that we'd used in previous launches, and we used it in launches later. And so we never took that time to, go and, and do the, post-mortem on it. But even to say, do a pre-mortem, to go forward and say, where do we get stuck? What has happened in the past? What have we learned from? What are the types of issues that we see as problematic? And even if we just stop for a minute and say, where are we spending our time?'cause it's, that's a big piece of this. And especially with supply chains, the amount of manual effort, that's what's burning people out. And there's so much of it, even as we go and look at what the job descriptions say when we're hiring for roles. It's accumulating data, it's distributing data, it's analysing data. It's a lot of it that's foundational work that has to happen. But we're putting it in the hands of people that have limited capacity to process something that's so fundamental, but it doesn't seem as important as it is. And so I think there's that balancing act to say, this is really, truly important and we need efficiency and consistency in it, because by doing that, we're going to enable optimization of our workforce beyond.
Tom Raftery:
Okay. Well obviously in that case, the solution, with everything else, has to be AI, right?
Patrick Van Hull:
Not necessarily. I mean, we, we, we had a great conversation just, two weeks ago. We were running, one of our summits. Somebody in the room said, I want everything to be run by AI. And, people in the room kinda laughed and, and said, okay, that's, that's great. Which, LLM? What do you use? ChatGPT, Gemini, Claude, whatever. The guy, he, he said, look, I, I really don't care how it works. I just want that work to be automated. And it led into a question that said, should it be an AI solution? Because so much of what we see, certainly we saw this with a, a major logistics company, is that if we just throw a contract into an LLM and say, tell me everything that's important, without the right context, it's gonna give us what it thinks is important. It's going to come back and say, I have a hundred percent confidence that this is what's important because you asked me to give it to you. And so I'm confident. That's what it's designed to do. But instead, if we're able to build out almost a portfolio approach to these things, you can apply ML, you can apply rules-based processing, RPA bots, all of those types of things can work in conjunction. So from the agentic side of being able to coordinate all of that, certainly AI is advancing those capabilities. But it doesn't mean that it has to be AI. And I often say that when individuals, when companies come to us, come to me and they say, what should my AI strategy be? I say, it's, it's kinda like asking, what should my math strategy be? Yes, you should use it. Okay, now what? What should we be trying to achieve? What are the outcomes that are desired? What is the work that we're trying to do? And so when we start to formulate the way it should be, the process we want, it becomes where is it problematic? Where can it be automated? Where does it need advanced intelligence? Where is it just something that's a repetitive task that we don't want to do anymore? That's where I think a lot of the discussion needs to go. Because in many cases, companies don't even know where they want to go. They don't even know what documents are hindering their process. They don't even know what's structured or unstructured. So it could be, cumbersome. They just want that solve. And magical AI often gets the tag.
Tom Raftery:
And what should companies fix before they start talking about agentic AI AI at all?
Patrick Van Hull:
They need to be open about the fact that the process that it is, that they use may not necessarily be the right process. There's definitely the motivation to keep the business running. Don't get me wrong on that, but we have a lot of work that exists in supply chains and in enterprises globally, is that we spend a lot of time celebrating the way it's always been done. We use that excuse frequently, but the way that it's always been done is something to celebrate, to say that we've been successful, the investments we made in the past got us here today, but there's a great concept of what got you here won't get you there. And knowing that we need to advance to places that we haven't yet gotten to, we've seen more volatility, it's more interconnected. We go back to the pandemic, it wasn't that demand increased and or lead time, both of them increased. So what do you do in a formula and everything in it changes all at once? It's not anything that we've had to adapt to. And, and, and so I think that's really a baseline expectation is saying, here's what we want to be able to do in the future. Not necessarily knowing what the solution is, but saying this is what we believe is going to be our strategic drivers of value going forward. And then let's start to build toward that. What are our roadblocks? What are the things that we process daily? Like I mentioned before, there's so many times when I asked that question of how many documents does it take to process an international shipment? Somebody in the room said four. And I said, I can give you, 10 just off the top of my head right now. And she said, okay, maybe it's more than four. And I said, how about 36? And she said, yeah, that's possible. So we immediately multiplied the number she came up with initially by nine. And that was still a plausible number. I think that's one of the things that, having those conversations in a constructive way. No fault of hers because that's the work that she's doing, but it's really the awareness of there's so many things coming together all at once. And we need to be open to the fact that as humans, we have limited capacity and we're really good at the logic and the decision making and, and the rationale that comes with that. We just don't need to do a lot of the repetitive pieces anymore. And the pieces that are gonna extract that really critical information that can be done or done better than you or I or anybody going through a contract with a highlighter.
Tom Raftery:
Okay, well, what kind of processes or what should still need human judgement and what should not need a human in the mix at all?
Patrick Van Hull:
Well, a, anything that's, repeatable, right? So if we think about that from the standpoint that if it's a rule, if it's if a, then b, if we can create those rules, that's something that's an easy task there. But certainly when we start to get into the points where, what are the decisions that we need to make? What are the places? Yes, we, we can get to the place where AI can make a suggestion on what's the right thing to do. But again as humans, we have to define what those characteristics are. We have to say, here are the decisions that are high repetition, low variability, and then we have to be able to say, here are the things that are high stakes and high variability. These are the ones that I want to be in the process for. And so it's that, the strategic connection where we know what we're trying to achieve and we know that the fundamentals are taken care of. Great. Now we know that there's been a disruption. What are my options? Okay, we can use all sorts of solutions to come up with what our options are. Help me narrow that down and we can walk through that process. We're still at that stage where that's very much human. That's the the discussion of what do you want to do and why? We're not quite to that place where we're ready to hand over the keys. There's explainable AI, but there's a point where somebody needs to be held accountable for the decisions and the recommendations, and ultimately that's gonna be a human thing. We're not at that place where AI gets the blame or the credit for a business decision quite yet. It'll be interesting when that time comes though.
Tom Raftery:
And what about things like document intelligence projects, then? They often fail, even when the business case looks strong. Why would you say that is?
Patrick Van Hull:
Again, you're trying to automate what you know. And so if you're trying to automate the work around, you're just accelerating it. You're accelerating the inefficiency. You're amplifying it. The second piece to that is trying to automate one piece of an end-to-end process will only get you so far. There's a company that we were working with and they were talking about the measure that they've determined is efficiency for their purchase requisition process. And they said that they had gotten to round numbers, let's say 60% efficiency, but they no longer could advance it because the process had been refined over and over and over, and they were no longer seeing substantial improvements. They simply said, We've taken it as far as we can, which was eyeopening. But they said, we're now realising that that perfect process is still dependent on a number of inputs. The data in that, those inputs, the transference of the information that comes from those inputs into the process. We're doing a lot of work with that with customers today that, have automated accounts payable, for example, but they haven't really brought into the process what their goods receipts look like, their supplier onboarding, being able to connect those processes where the output of one becomes the input of the next. That's where you start to get the amplification of the right types of efficiencies as opposed to the inefficiencies.
Tom Raftery:
And who needs to be in the room before workflow design starts?
Patrick Van Hull:
So this is the point that becomes tricky is that if you're looking at, say, accounts payable and you're looking at logistics receiving and you're looking at procurement for supplier onboarding, none of those groups talk to each other. So, there needs to be a place that it needs to go up in the organisation and, certainly go to the CFO and, and ask the CFO and O obviously access to the CFO to the C-suite. That's everybody's dream, right? You can just, you can't just pick up the phone. But by being able to connect the work to the strategic drivers, look at working capital, for example, it's a combination of accounts payable, accounts receivable, and inventory. Oftentimes accounts receivable and accounts payable and inventory don't talk to each other. But if working capital is a CFO level initiative, then all of a sudden the person who can connect those dots is driving the process. Really it involves the executive level engagement or certainly mid-management because the people doing their jobs are, gonna keep doing their jobs. And there's that, that age old, concern that a robot's gonna take their job anyway. So there's that death gripping on the work to some extent too. There's a change management aspect, certainly.
Tom Raftery:
Okay. And what do frontline teams understand that process maps usually miss?
Patrick Van Hull:
What happens if it doesn't go well. Because there's so many different variation points. And this is one of the, the struggles of scenario management is we can come up with a million possible scenarios that might happen, but the likelihood is there's very few that will actually come to fruition. So what is it then are the most likely exception paths? Who is it that needs to be involved in those? But when we design the process, we think about the flow from portion A to B to C. The document has to get signed off, it has to be scanned, all of those types of things. But the reality is, is that in the moment, the people doing the work are just focused on getting that thing done. And that's the place where it says, here's the thing that I do when the process breaks down, I don't care what you tell me to do because I've got a load of pallets sitting on a dock and I need to get this one out of the way so I can process the rest. Well, that's where you need that conversation to say, this is how the work was really getting done as opposed to what the to be looks like.
Tom Raftery:
And where does trust breakdown then?
Patrick Van Hull:
Trust always breaks down when somebody tells somebody else what to do. So it's the engagement of why we're doing it. Why is it that I'm being brought into this conversation to do the work, and oh yeah, by the way, this isn't just a matter of you educating me on the right thing to do. I need to have a say in the matter. There's that level of engagement, and it's ultimately there was a period of time, a number of years ago where millennials got this bad rap for wanting to have purpose in their work, but the reality is that we all want to feel like it's part of something bigger. Like there's meaning behind what I do, even if it's something that is repetitive. And so the trust breaks down when you tell me, my work doesn't matter. The trust breaks down when you tell me I'm doing it wrong without explaining why I should be doing it differently. And so the drawback of that top down approach that I'd mentioned where you start to have executive level intervention is it becomes dictatorial as opposed to the wholeness, the organic nature of trying to drive value. And really when you start to see that my work impacts the next person and so on, that's the place where we can start to say, oh, we don't have to make this as painful anymore. You don't need me to do that one thing that I always do that nobody cares that I do. Well let's not do that anymore. And, and that happens with conversation and, and the genuine human interaction. That's the place too. I think that still AI is, it can say what should be done, but we still have emotions and rational or irrational moments that people tend to bring into their work environments.
Tom Raftery:
And what has surprised you about how people react when manual work starts disappearing?
Patrick Van Hull:
They feel like they're going to be bored or they're going to be judged on not doing enough. And part of that, I've seen that in my career. For example, we implemented a new forecast and replenishment system at one of my companies. My team, the senior leadership wanted to prove that the team was using the solution. So they were being judged on the number of forecast items that they were tuning. It was just a volume play. The more you did, the better you were rated. And when we made the argument that the system should be doing the work, we should only be managing a categorization or those, those ones that are abnormal. Everybody looked at it and said, well, what do all people do? if they're only doing 10% of the work, then why, why do we have them? And it it's that extrapolation where people go from my identity is tied up in my ability to do the volume of work that's in front of me. That's challenging because again, we want to feel like we're doing something important. If you tell me that a robot can do my job well then what have I been doing with my life? And, and that's the place where it says, this is less about what you've done in the past and more about how do we stop, start to optimise the work you can do, optimise your experience because you can actually do more. And it's not because of anything that you've done, but because of the system limitations we've put in place. And that's complicated. It, it certainly is, but it's that, resistance to let go of the work is definitely the most eye-opening thing.
Tom Raftery:
Okay, and what's harder than expected once companies start redesigning workflows?
Patrick Van Hull:
People just need to accept the fact that it's not gonna be perfect. And, and I think that, that the idea is to say how, how close can we get with this? And where can we start to tweak? Transformation is not doing the same thing as before, but better. And it's also not finite. That's the, place that companies can struggle is we've got a three year transformation project. Great. We started in 2021. It's 2024, we're done, we're stopped. No more transformation. That's not how the world works. That's not how supply chains work. We're, we're sitting at the intersection of so many different things that if we don't accept the fact that we're gonna continue to need to evolve and, and define what those foundational aspects are, that's where we're gonna fail. We're gonna stop growing. And, really that's a challenge for companies because I, I sat in a room with a team of chief supply chain officers at one point. I said, if you could have 15% return at the end of five years, or 1% return every year for five years, which would you pick? And they said, if I delivered zero for four years and then 15 at the end of five, I'd never make it to five because I didn't deliver any kind of return. That's part of the the mindset is still incremental return, get a little bit better, but we need to do it in a way that's not just tweaking and, just inching along. We need to try and accept the fact that there are ways that we can do this, that can start to grow and compound.
Tom Raftery:
And that puts the team in a difficult position. If I'm judged on how many forecasts I adjust, letting the system handle them could make me look redundant. Changing the workflow also means changing how my contribution is recognised. Okay, but on the other hand, what's, one mistake then that companies make because they're trying to move too fast?
Patrick Van Hull:
They try to automate everything all at once. That's the, the craziest part is that, okay, we're gonna do this, that, and the other thing, and we're gonna bring all these resources in. And there's no definition of success at that point in time. There's no baseline because again, we're looking at things that are so interconnected that we can get to a point where we can build 10 different, perfect processes, but if they don't connect, we're still going to have those inefficiencies that existed previously. So it's less about trying to do all of it, but it's about trying to find those ways to be successful, to deliver the value, to try and see what's next and certainly that's what comes into building a roadmap. Here's how we're gonna build this. Here are what my inputs are, here are what my outputs are, and now let's try to build this in a way that is something that we can engage on and we can prove that it works. Sometimes the value, by the way, is showing that this doesn't work too, but saying this, what didn't work? These are the lessons learned, and here's where we pivoted. There's absolutely value in the mistakes. But if we just try to do everything and, and we just throw our hands up and we walk away from it because it wasn't perfect, we're never gonna get anywhere.
Tom Raftery:
Yeah. Yeah. And if, if people listening to this want to start fixing inside their own organisations, where should they begin?
Patrick Van Hull:
A lot of times it just, it's simply a matter of, if we think about it from the automation standpoint, a lot of the work that we're doing now is helping companies audit the documents that they use. The processes supplier onboarding. What are the forms that go out to your suppliers? What's every single document? How does it come back to you? Is it structured? Is it unstructured? Is it handled by email? Is it handled by a human? Is it in a repository? But let's take a break and just say, Hey, you know what Here's how this process works in reality is we're, sending an Excel file back and forth with no check and balance, with no audit. And it's two people. When that process breaks down, the outcome is a production line going down. That's problematic. But that's, the way that it shook out for me. And, and rather than saying that, that's the process, let's figure out how to work around it. It's saying No, what are the documents really need to move? What are the ways that we can control them better? What's the information we need in there? And then how can we go and do something that's sustainable and consistent and efficient as opposed to just trying to brute force it.
Tom Raftery:
And after this conversation, what should listeners see differently when they look at a late shipment?
Patrick Van Hull:
Just, I, I think one is the fact there's no singular cause often. And, just thinking about all of the different pieces to it. Obviously heads down doing the job. It's one thing to blame that person upstream or, or whomever. We want to place blame on this, but it's, it's to say something happened along the way. The document got stuck. The, container didn't get loaded on time. Somebody didn't show up for work. There's a level of grace that comes with this to accept the fact that the late shipment is there. We have to do something about it. Hemming and hawing and, and blaming and, and accusing isn't gonna get us anywhere, but we do need to take that inventory and come back to it. We need to commit to coming back to it to say, here's something that's broken down and it's happening over and over again. We're doing the best we can to manage it, but we need to fix this because this is what's burning out my people to the point where nobody wants to work here anymore. That's the type of thing that happens in supply chain. You look at the career longevity in many of these roles and it's just, they get exhausted. But a lot of it's because we don't stop to think about what's causing the exhaustion.
Tom Raftery:
Fair. Time now, Patrick, for the lightning round, I'm gonna ask you some quick questions and you've got a one sentence answer, okay?
Patrick Van Hull:
All right.
Tom Raftery:
Okay. Here we go. Speed or control, which wins in a crisis?
Patrick Van Hull:
Control. Control absolutely wins just from the standpoint of not trying to control everything, but controlling the controllables and accepting what you can.
Tom Raftery:
Okay. Which workaround is the most dangerous?
Patrick Van Hull:
Excel manual, manual data entry with no verification.
Tom Raftery:
Okay. What should never be automated?
Patrick Van Hull:
Given some of the things we've seen in the world today, terminating employees, managing employees should never be automated. That should never be handled by AI.
Tom Raftery:
Perfect. Yep, completely. Where does resilience fail first?
Patrick Van Hull:
When the, the lack of confidence in the processes that underpin the work being done. If we're not confident in what's happening and, and how the work gets done, we're not gonna be confident in our ability to respond to it. And that's really where true resilience is, is accepting that things are gonna throw us off stride, but knowing that we're gonna be able to get back on, to try to do something about it.
Tom Raftery:
Which team feels friction first?
Patrick Van Hull:
Customer facing, anybody that's directly interfacing with the customer is gonna get the friction first because the customer's going to be the loudest.
Tom Raftery:
Yeah. And lastly, one bold prediction for next year?
Patrick Van Hull:
I think that we're going to get to a point where somebody's going to have that a business failure, and they're going to blame it on AI and it's going to be something that somebody blindly accepted, something an LLM told them as a strategic business decision, and it's gonna fail miserably and it's gonna get publicised as some executive, some person made a call that was completely unfounded, but ChatGPT told them to do it.
Tom Raftery:
Right, a left field question for you now, Patrick, if you could have any person or character, alive or dead, real or fictional as a champion for document intelligence, who would it be and why?
Patrick Van Hull:
Man, I, I love stoic philosophy. so I would say Marcus Aurelius, just because of his self-reflection, his ability to understand all of the things that are happening around him, being grounded in the imperfection that lies within him and the process. But then being grounded in the fact that he can only decide on what's within his control, and then having the courage to do that, the compassion to do that in a human way. Um, probably a little bit of a left field answer to your left field question but
Tom Raftery:
Perfect.
Patrick Van Hull:
Certainly that's the first one that comes to mind.
Tom Raftery:
Brilliant. I love it. I love it. Patrick, if people would like to know more about yourself or any of the things we discussed on the podcast today, where would you have me direct them?
Patrick Van Hull:
Sure, You can find me on LinkedIn, p van Hull. is my username on LinkedIn.
Tom Raftery:
Fantastic. Patrick, that's been really interesting. Thanks a million for coming on the podcast today.
Patrick Van Hull:
Thank you, Tom. It's a pleasure and I'm glad that we were finally able to connect.