Loading articles…
Field notes for building a business that can move without you.
We write from the intersection of operating systems, software, sales, marketing, and leadership—for owners building a more capable company.
Loading articles…
We write from the intersection of operating systems, software, sales, marketing, and leadership—for owners building a more capable company.
Loading article…

Article
When more people can confidently do the work, a business can support its customers without everything depending on one person. That takes practice, useful documentation, and a clear finish line.
A customer shouldn’t have to wait for one particular person to become available before they can get help. And the person who knows how to solve the problem shouldn’t have to carry every question alone.
As a business grows, this becomes less about finding people who are willing to help and more about making sure they have the knowledge and confidence to do it. That knowledge might be in a document, in a conversation, or in the head of someone who has done the work for years.
This week, I sat down with a teammate to talk about the skills involved in supporting our Accelerator clients. We weren’t trying to test whether he knew enough. We wanted to understand what he could already do, where he wanted more practice, and what would help him take on the next set of work confidently.
We came away with a list of ten areas to work through. The conversation reminded me that sharing knowledge isn’t a matter of putting someone through a training session and hoping it sticks. The goal is to make the work possible for another person to do well.
We began by listing the things my teammate was already comfortable doing. Some came to mind immediately. Others showed up after we talked through recent client work and the different ways he had helped people.
That mattered. If we had started with a list of everything I thought he should learn, we could have spent time covering things he already knew. We also might have missed skills he had developed without thinking of them as a separate part of his job.
We found a few different kinds of gaps. There were things he hadn’t done before, things he had done once but wanted a refresher on, and things he understood but hadn’t yet felt comfortable helping clients with.
Those are different starting points. Someone may need a walkthrough, a chance to practice, or simply a conversation about where their responsibility begins and when to bring someone else in. The more accurately we understand the starting point, the more useful the next step can be.
Once we had the list, we talked about working through it in short sessions, one area at a time. The plan is to prioritize the ten items and spend around ten or fifteen minutes on each, spaced over time.
That doesn’t mean every skill can be mastered in fifteen minutes. Some will need more practice, questions, or a second conversation. But a short session gives us a manageable place to start, and it lets the next piece of learning connect to actual work rather than getting buried in one long training day.
We also put the work into a project. Each item has a place to track the training and follow-up, and the project has a finish line. When we’ve worked through this set, we can close it and decide what the next set should be. We don’t need one training project that stays open forever.
We’re at the beginning of that process. The list and the project are in place; the sessions and practice are still ahead of us. What interests me is the standard we set for when that work will be finished.
It’s easy to mistake exposure for understanding. I can show someone where to click, explain why I’m doing it, and answer questions along the way. All of that is useful. But it doesn’t necessarily mean they’ll be comfortable doing it themselves next week, when the screen looks a little different or a client asks a follow-up question.
For this project, I want my teammate to practice each skill himself, either in a test environment or as part of real client work. We also want to make sure there’s a useful supporting document for the areas where a Telos user might need help.
That gives us two things: a person who has had the chance to learn and practice, and a reference they can return to later. The document can also help the next person who needs to learn the same thing.
A document on its own isn’t enough, either. If the instructions are difficult to follow, out of date, or skip the part where a person has to make a decision, having a document may create confidence without creating understanding. We want the person learning the task to check the relevant instructions against the product and confirm that they make sense.
A useful document helps the person learning a task. It becomes more valuable to the whole team when it has a home in the business’s central brain. In Telos, that’s the Knowledge area: a shared place for the processes, guidance, and context the business wants its people to be able to find and use.
When that knowledge is in the central brain, other team members can find it too, rather than having to know who wrote the document or where it was saved. The AI can index the knowledge and help bring relevant information into a conversation. That makes the document useful beyond the training session it was originally written for.
Someone learning a skill might use it to prepare for a practice session or revisit a step afterward. Later, while working with a client, they might ask the AI a question about the situation and use the relevant business knowledge it finds as a starting point. They can check the source, apply their judgment, and ask for help when the situation calls for it.
That only works well if the knowledge stays useful. The team needs to keep it accurate, give the right people access, and update it when the work changes. The aim isn’t just to collect more documents; it’s to make the right information easier to find when people need it.
I don’t think every part of a job can—or should—be reduced to a checklist. Good support involves listening, understanding what a person is trying to accomplish, and recognizing when the situation is different from the last one.
Documentation can make that judgment easier. It can explain the normal path, what the work is supposed to achieve, what to check before making a change, and where to go when something doesn’t match. It gives someone a starting point without pretending that every situation is identical.
It also makes it easier to ask a better question. Instead of “How do I do this?” the conversation can become “I followed the normal process, but the client needs a different outcome. How should we handle that?” That’s a useful conversation to have, and the answer may make the documentation better for the next person.
You don’t need to start by documenting every process in the business. I would start with a piece of work that matters to customers and regularly waits for one person to become available.
Then ask:
The answers don’t need to produce a huge training program. They might lead to one short session, a practical exercise, and an update to an existing document. The important part is making the next step clear and following through.
The goal isn’t to remove the people who have experience from the work. Their judgment is valuable, and they’ll still be needed for unfamiliar situations. The goal is to share enough of what they know that more people can contribute, customers can get help, and the team has room to keep learning.
That’s how I want to approach this work as we support businesses using Telos. Help someone build the skill, make the knowledge available to the team, and make sure they have the opportunity to do the work themselves.
A business gets stronger when its knowledge can be passed on—not because everyone knows everything, but because more people can confidently do the work that matters.