I was talking with a client recently, and she said something that made me smile.
“So now nobody's calling me, and it's lonely.”
She was joking, of course, but I was really happy to hear that.
She's the CEO of a fast-growing construction company, and like many CEOs I work with, she has a lot on her plate. As the company has grown, she's found herself answering questions and solving problems that really shouldn't require her involvement.
She told me that drivers would call her with questions like what to do when they were asked to pick up demolition debris but still needed room in the van for their next delivery.
Imagine being the CEO of a growing company and having to stop what you're doing to figure that out.
It's not necessarily that the employees aren't capable. Often, they simply don't have clear instructions or haven't been trained on how to handle those situations. So they call the person who knows the answer.
And in this case, that person was the CEO.
Something Interesting Happened as We Documented Her Processes
When I work with business owners to document their processes, I ask a lot of questions. I want to understand exactly what happens, in what order, and what someone should do when things don't go according to plan.
Sometimes the answers are obvious to the CEO because they've been doing things a certain way for years. But when I ask them to explain it so someone else can follow the same steps, they have to stop and really think about it.
That's what happened as we worked together.
We were taking the knowledge she had in her head and organizing it into clear procedures. But we were also identifying the questions she kept getting from employees and figuring out how those situations should be handled.
Instead of continuing to answer the same questions, she could decide ahead of time what she wanted her team to do.
One example came up during our recent meeting when we were reviewing the procedure for handling missing or incorrect materials.
She explained that if a crew discovered a missing grab bar, she didn't want someone automatically deciding to make a long drive just to deliver that one item.
She wanted them to think about the situation. Could they deliver the missing item the next day when another crew was already going to be in that area?
She wanted employees to identify the problem and come up with a reasonable solution.
So we reviewed the form we had created for reporting missing materials and confirmed that it included a section for documenting the resolution.
This is one of the reasons I enjoy the documentation process so much. These conversations give business owners an opportunity to look at how things are being done and decide whether there's a better way.
And once we've worked through those decisions, we can write them down so employees have something clear to follow.
Why We Need Both Documentation and Implementation
I sometimes hear business owners say they just need to train their employees better.
But what are they training them on?
If the instructions are only in the owner's head, they have to explain them every time someone new joins the company. And even when employees are trained, people forget things or interpret instructions differently.
That's why documentation matters.
In this client's case, we documented procedures for managing deliveries, checking materials, handling missing items, and other daily activities. We also included short videos to demonstrate certain steps.
During our meeting, she commented on those videos.
“I love the video clips,” she said. “It's so helpful.”
Now, when someone needs to learn how to perform a task, there's a written procedure they can refer to, along with a video when it's helpful.
But creating the documentation doesn't automatically mean people will use it.
After we worked through the procedures and guidance, my client took the time to review them with her employees during a production meeting.
She explained what she expected and made sure everyone understood.
During our next conversation, I asked her what kinds of questions she was still getting from the drivers.
That's when she laughed and said nobody was calling her anymore.
She told me they had gone over the guidance during the meeting and that the employees understood what to do. She described it as a “real big issue” they had fixed.
I was so happy to hear that because she was already noticing a difference.
And it illustrates why I always emphasize that documentation and implementation have to go together.
We need to document the processes so employees have clear instructions they can follow and refer back to. But we also need to train people, review the procedures with them, and make sure they're actually being used.
Otherwise, we haven't really changed the way the business operates.
The CEO Has to Change Some Habits, Too
There was another part of our conversation that I thought was important.
My client mentioned how difficult it can be to get work done when people are constantly interrupting her.
I told her something I often recommend to the CEOs I work with.
When an employee asks a question that's already answered in a documented procedure, don't immediately give them the answer.
I know it's tempting, especially when answering would only take a minute.
But if you keep answering those questions, employees learn that the easiest way to get information is to come to you.
Instead, ask them to review the procedure first. If they still have questions, then you can coach them.
I told her, “You're not the ChatGPT of the office to answer every single question.”
She laughed and said, “Yeah. That's a good one.”
Of course, that only works if the procedures are clear, accessible, and employees know how to use them.
But the CEO also has to be willing to let employees take more responsibility.
And that can be a difficult adjustment when you've spent years being involved in almost everything.
What I Took Away From This Experience
What I enjoyed most about working with this client wasn't just hearing that her phone had become quieter.
It was seeing how she was thinking through her business as we documented the processes.
She was identifying recurring questions, clarifying how she wanted things done, and coming up with solutions to problems that had been taking up her time.
Then she took what we had documented and went over it with her team.
And the team started handling more of those everyday situations without calling her.
For me, that's what makes this work so rewarding. We're not just creating documents. We're helping business owners turn what they know into processes their employees can actually use.
Of course, there will always be situations that require the CEO's attention. I don't expect employees to stop asking questions altogether.
But if you're answering the same questions every day, it's worth looking at why.
Maybe the process isn't clear. Maybe it hasn't been documented. Or maybe the procedure exists, but nobody has taken the time to implement it properly.
The next time you get one of those recurring questions, instead of just answering it, consider whether there's an opportunity to create a process that will help your employees handle it themselves.
That's how you start reducing the day-to-day dependence on you.
And who knows? Maybe one day you'll find yourself joking that nobody calls you anymore.
I think that's a pretty good problem to have.