If you’ve ever tried to “automate the chaos,” you already know the answer to the question: what came first, the process or the automation?
The process did. Almost always.
But that doesn’t mean you should wait until everything is perfectly documented and polished before you touch technology. The real work is understanding how process and technology shape each other—and designing them as a pair.
The uncomfortable truth about tech adoption
In my time as a process consultant, one pattern showed up everywhere: the level at which a team can truly use technology is directly correlated to the strength of their processes.
Not the existence of a checklist. Not a binder of SOPs collecting dust.
The thoughtful design of how work actually moves through the business:
who does what
what “done” means at each step
where decisions get made
what information is needed to move forward
how exceptions are handled (because real life is mostly exceptions)
When those things are fuzzy, technology becomes a very expensive way to create more confusion—because software doesn’t remove ambiguity, it exposes it.
Why process design matters (even when you’re “too busy”)
In property management (and in most service businesses), process design—often called systems thinking—doesn’t exist to make things feel “corporate.” It exists to make outcomes better.
Well-designed processes improve:
Client experience (fewer dropped balls, clearer communication, faster resolution)
Team effectiveness (less rework, fewer “who’s doing this?” loops, fewer fire drills)
Financial outcomes (higher throughput, fewer errors, better utilization, better retention)
And yet, the hardest part is never agreeing that process matters.
The hardest part is finding the time to write it down… or even to stop long enough to ask, “Are we missing steps? Are we doing steps that don’t matter anymore?”
Because when you’re drowning, it’s hard to step out of the water to build a boat.
“We need the process before we can automate” — yes, and also no
Some would say you need solid processes before you can begin working on AI and automation. I tend to agree—to a point.
But there’s a second level that gets missed:
Your processes should also be shaped around what’s technologically available to you.
That’s not cutting corners. That’s designing for reality.
When technology changes, the “best” process changes. And if you ignore that, you end up doing something I see constantly:
The trap: forcing manual work into automated tools
Trying to fit a manual process into an automated tool doesn’t work. You end up creating to-dos or instructions for steps that aren’t needed anymore.
You create layers:
a form, plus a spreadsheet
a ticket, plus a Slack thread
a CRM, plus “our real system”
automation, plus “the human workaround”
And then everyone concludes, “This tool isn’t helping.”
The tool may be fine. The design is what’s broken.
A better approach: design process + automation in tandem
Here’s what I’ve found works better—especially in operations-heavy teams like property management:
Start with the outcome
What does “great” look like for the resident, owner, vendor, and the internal team?
Map the real workflow
Not the “ideal” workflow. The one people actually follow on Tuesday at 4:47pm.
Identify decision points and data needs
Where does the process stall because someone doesn’t know what to do next?
What info is required to move forward—every time?
Automate the movement, not the mess
Automate handoffs, reminders, routing, and communication patterns.
Don’t automate a broken decision.
Let the tool eliminate steps
The best automation isn’t “doing the same work faster.” It’s deleting work entirely.
The real question isn’t “process vs. automation”
The real question is: are you designing a system that your team can actually operate—and improve—over time?
Process isn’t a prerequisite. It’s a living part of the product you’re building inside your business.
And automation isn’t the reward at the end of a perfect documentation project. It’s a design partner—one that forces clarity, exposes weak points, and (when done well) gives your team breathing room to focus on what only humans can do.
If you’re exploring AI and automation right now, I’d encourage you to ask one simple question first:
Where are we compensating for uncertainty with human effort?
That’s usually where the next process redesign—and the highest-leverage automation—begins.