A restoration leader walks into the office Monday morning with problems… project managers are spending too much time chasing information, updates live in too many places, follow-ups are getting missed…everyone agrees, there must be a better way.
By Tuesday, someone has found a software that promises to solve all of it. By Wednesday, the team is sitting through a demo; there is AI, automation, dashboards, integrations and a slick mobile app. By Friday, the conversation has shifted to pricing and implementation.
Somewhere along the way, we stopped talking about the problem…
Technology moves incredibly fast, and artificial intelligence has compressed the distance between discovering a tool and deploying it, even tighter. Anyone with a browser can find, trial, and begin using powerful technology in minutes.
That makes one discipline increasingly valuable: the power of pause.
There is a familiar leadership principle that between stimulus and response there is a time-space, and inside that space is our opportunity to choose our response. Technology leaders need that same discipline.
A frustrating workflow is a stimulus. An impressive demo at a restoration conference is a stimulus. A competitor announcing an AI initiative is a stimulus. A team member saying, “There has to be an easier way to do this,” is a stimulus.
But before responding with technology, pause and ask, “What friction are we actually trying to remove?”
Start With the Friction, Not Technology
Some of the best technology projects begin with an irritation.
Someone enters the same information three times. A project manager searches four systems before calling a customer. An estimator spends 20 minutes finding something that should have only taken two. A leader has plenty of data but can’t quickly determine which jobs need attention.
These are friction problems.
“We need AI” is not a problem statement. Neither is “we need another dashboard” or “we need to automate this.”
A better problem statement is: Our Project Managers spend too much time searching multiple systems for the information they need to communicate with customers.
Now we have something worth solving.
Maybe the answer is new software. Maybe it’s an integration between systems we already own. Maybe AI can assemble the information. Maybe the process itself needs to change. Or maybe we can simply eliminate an unnecessary step.
The pause keeps us from falling in love with a solution before we understand the problem.
And in restoration, that’s important. We already operate across job management, estimating, accounting, CRM, documentation, moisture monitoring, customer communication, TPA platforms, business intelligence and countless other applications.
So, every new platform may remove one point of friction, while quietly creating three more.
When Solving Friction Creates Shadow IT
Here’s where this gets complicated: the people introducing technology into our companies usually aren’t trying to create complexities or problems, they’re trying to solve them.
A team member gets frustrated, finds an online tool and starts a free trial. Someone discovers an app that eliminates a manual process and clicks Sign in with Microsoft. Five minutes later, their problem is solved.
However the organization may have just acquired another technology platform without knowing it.
That’s Shadow IT.
Now ask: Where is the data stored? What permissions were granted? Who owns the account? Do we already pay for something that does the same thing? What happens when that team member leaves?
AI has accelerated this problem through Shadow AI.
An estimator can upload a document for analysis. A project manager can paste claim information into an AI tool. Someone can ask AI to rewrite a customer email or summarize a contract.
No installation. No implementation project. Sometimes no credit card. Just a browser and a problem.
Again, they’re trying to remove friction. But what happened to the information they provided? Is it retained? Is it used for training? Did it contain customer, carrier, financial or personally identifiable information?
That’s why I don’t believe “Don’t use AI” is a sustainable strategy.
Instead, teach people to pause, before they connect, upload or authorize.
The Demo Shows the Feature. You Inherit the System.
Once we determine new technology might be the right answer, we need another pause.
A great demo shows what a product can do. Your company inherits everything around it. The authentication. Permissions. Data. Integration. Training. Support. Vendor relationship. Renewal. Security exposure.
So don’t just ask, “Does it work?”
Ask how users authenticate. Ask what permissions it requires. Ask where your data is stored and how it is protected.
And one of my favorite questions, “How do I get my data back out?”
Does the platform have an API? Can you access your own data programmatically? Is it available in real time or through a nightly export? Can it participate in your broader data environment, or will it become another island?
Today’s software purchase needs to solve today’s friction, without creating tomorrows.
AI Raises the Stakes
AI introduces another important consideration, because we’re moving from AI that tells us things, to AI that does things.
There is a major difference between an AI reading your calendar and changing your calendar. Identifying an overdue task and changing its due date. Drafting an email and sending it.
I think about AI in three stages: read, recommend and write.
Let AI read the information it needs within appropriate security boundaries. Let it use that context to make intelligent recommendations. And be increasingly intentional as you give it permission to write back, change records or act on someone’s behalf, with this in mind:
The greater the consequence, the more important human judgment becomes.
An AI assistant saying, “You have seven overdue commitments, three customer messages requiring attention and 90 minutes of open time today. These appear to be your three highest priorities,” could remove tremendous friction.
But, automatically moving meetings, changing deadlines and responding to customers without appropriate controls, could create unintended friction and consequences.
AI should eliminate the administrative work surrounding good judgment, not eliminate good judgment itself.
Don’t Automate Something That Shouldn’t Exist
The same pause applies to automation.
“We do this manually” does not automatically mean “we should automate it.”
Before automating a process, ask why the process exists.
Can we eliminate it? Can we simplify it? Can we standardize it?
Eliminate. Simplify. Standardize. Then automate.
Otherwise, we risk building incredibly sophisticated ways to perform unnecessary work.
AI makes this temptation stronger because the barrier to building is falling rapidly. We can create applications, automations, and agents faster than ever.
As the barrier to building gets lower, the discipline to ask whether we should build it needs to get stronger.
Don’t Become the Department of “No”
There is another side to the pause.
If Shadow IT and Shadow AI continue appearing inside your organization, don’t only ask, “How do we stop this?”
Ask, “Why did our people go looking for it?”
Maybe the approved tools aren’t solving their problems. Maybe they don’t know what capabilities already exist. Maybe requesting new technology is too difficult.
Shadow technology creates risk, but it also reveals friction.
Technology leadership should not become the department of “no.” Our responsibility is to create safe lanes for “yes.”
Give people approved AI tools. Teach them what information can or cannot be shared. Make it easy to bring forward technology ideas. Encourage controlled experimentation.
When someone brings you a new application, don’t immediately reject it.
Ask, “What problem are you trying to solve?”
Now you’re solving the problem together.
Slow Down to Move Faster
This isn’t an argument for moving slowly.
Restoration companies should be moving aggressively toward better technology, stronger data, responsible AI and intelligent automation, because there is tremendous friction in our industry that technology can remove.
The goal isn’t to slow innovation. It’s to aim it.
Moving fast without architecture creates technical debt. Moving fast without governance creates Shadow IT. Moving fast without AI-guardrails creates Shadow AI. Moving fast without integration creates silos. Moving fast, without defining the problem first, gives us better versions of things we may never have needed.
The restoration companies that lead the next wave of technology won’t necessarily have the most applications, automations or AI agents.
But they will have become exceptionally good at identifying friction and applying the right amount of technology to remove it.
So, when the next impressive platform lands in your inbox, or a team member discovers a new AI tool, or someone says, “There has to be an easier way,” don’t immediately say “yes,” and don’t immediately say “no.”
Pause long enough to understand the friction. Look at what you already own. Follow the data. Understand the permissions. Consider the security. Decide whether you’re solving the problem or simply adding technology to it.
Then move.
Because the goal isn’t more technology. The goal is less friction.
Taylor Carmichael
Taylor Carmichael is the Director of Systems at Southeast Restoration, where she leads the integration of technology and operations across the cleaning and restoration industry. With a Master of Information Systems and over a decade of industry experience, Taylor focuses on streamlining workflows, improving communication, and driving scalable solutions. She’s passionate about making technology practical by bridging innovation with day-to-day execution to help restoration teams work smarter and grow stronger.
Related Posts
