“We need better scheduling software.”
That was the problem as it was first explained to me.
And honestly, it would have been easy to start there. I could have compared platforms, looked at features, made a recommendation, and set something up.
Done.
Except I wasn’t convinced that scheduling was the problem yet.
So instead of opening a list of software, I asked a different question:
Walk me through what happens when a job comes in.
From the beginning.
Who gets it first? What information comes with it? What happens if something is missing?
Who decides who gets assigned? How does everyone know where the job stands?
What happens when someone has to go back? When is the work considered complete? And once it is complete, what happens next?
That is when the problem started changing.
It was bigger than the calendar
The more we walked through the work, the clearer it became that “scheduling” was sitting in the middle of several other things: intake, assignment, communication, missing information, return visits, completion, and billing.
And underneath all of it, accountability. Who was responsible for what?
The calendar was where the frustration was showing up. But the calendar had not created the problem.
If I had recommended software immediately, we could have taken an unclear process and simply put it inside a new system.
The screens would have looked better. The process underneath them would have been the same.
The recommendation changed
Once I understood how the work was moving, I wasn’t ready to recommend a scheduling platform.
Not yet.
First, we needed to define some basics.
What information has to exist before a job can be scheduled?
Who owns the job at each stage, and what does “assigned” actually mean?
What does the person doing the work need to know before arriving?
What happens when the work cannot be finished the first time?
Who decides it is complete, and what triggers billing?
Those are operating decisions. Software can help carry them later. Someone in the company has to make them first.
Choosing a tool before answering those questions could have meant designing the business around whatever the software happened to allow.
The problem is often a few steps earlier
The owner usually knows exactly where the business hurts. What they may not know yet is where the problem begins.
Those are not always the same place.
The scheduling problem might begin at intake. The follow-up problem might begin with ownership. The customer-service problem might begin with missing information.
And the owner’s lack of time might begin with work nobody ever clearly defined how to hand off.
That is why I keep asking people to walk me through the work.
Not the ideal version. Not the version written in a procedure somewhere.
The real version.
What happens on an ordinary Tuesday when something goes wrong?
That is usually where the business tells you what it needs.
And sometimes the most valuable recommendation I make is the one I decide not to make yet.