Your People Aren’t the Problem. Your System Might Be.

Barry’s 80/20 Five-Page Review of The Toyota Way by Jeffrey K. Liker

When something goes wrong in a company, there is a very popular management strategy: find somebody to blame. The client wasn’t followed up with. The employee dropped the ball. The project ran late. The order went out wrong. The new person “just doesn’t get it.”

Sometimes a person really did make a mistake. People do that. I have even done it myself once or twice, although I am still reviewing the evidence.

But The Toyota Way asks a more useful question: What was it about the system that allowed this mistake to happen, and what can we change so it is less likely to happen again?

That shift sounds simple. It isn’t. It changes how you lead, how you train people, how you delegate, how you measure work, and how you respond when something breaks.

Jeffrey K. Liker studied Toyota for decades and organized what he learned into 14 management principles. The book is associated with lean manufacturing, but treating it as a factory book would miss most of its value. Toyota’s larger lesson is about building an organization that learns. It is about creating good processes, developing people who can think, and making improvement part of the work instead of something management announces at the annual retreat.

That makes The Toyota Way a very good TeamBuilders book.

Why I’m Doing These Reviews

There are thousands of business books. Most of them contain a handful of ideas that can genuinely change how you operate, surrounded by a few hundred pages of stories, explanations, and supporting material.

That is the reason for Barry’s 80/20 Five-Page Book Review. I am looking for roughly the 20% of a book that delivers 80% of its practical value.

This is not meant to replace reading a worthwhile book. It is meant to help you answer a different set of questions: What are the ideas worth stopping for? Where do I agree with the author? Where would I add something? And what can an actual business owner do with these ideas Monday morning?

The Toyota Way gives us plenty to work with because it does not treat systems and people as competing ideas. It treats them as inseparable. Toyota formally describes its philosophy through two pillars: continuous improvement and respect for people. Liker shows what those ideas look like when they are carried into the daily operation of a company.

The result is not a trick, a tool, or a productivity hack. It is a way of running the business.

80/20 Idea #1: Fix the Process Before You Blame the Person

Most companies say they want employees to take responsibility. What they often mean is that when a result is bad, they want a name to attach to it.

Toyota takes a different approach. It places enormous attention on the process that produces the result. Was the work clearly defined? Was the person properly trained? Could the problem be seen quickly? Was the handoff confusing? Did the process make the correct action easy, or did it practically invite an error? Did the employee have the authority to stop and ask for help?

This does not eliminate personal responsibility. It makes responsibility more intelligent.

If one employee makes an unusual mistake, you may have an individual issue. If five people keep making versions of the same mistake, you almost certainly have a system issue. Changing employees without changing the process is like replacing the driver because the bridge is out. You may get a different driver. You still have a missing bridge.

BARRY AGREES

I have always believed that an owner does not need to be the technician doing every task, but the owner does need to understand what good work should look like. You need standards. You need people with technical expertise who can review work, provide quality control, and correct what is being produced. Then you use what you learn to refine the process, improve the training, and apprentice people until they can produce the result reliably.

That is very different from hovering over everybody and fixing everything yourself. The owner’s job is not to become the permanent repair department. The job is to help build a company that can identify, correct, and learn from its own problems.

That is the connection between The Toyota Way and The E-Myth Revisited. Gerber tells us to build systems so the business is not dependent on the owner. Liker adds something important: the system itself must be examined and improved by capable people. Otherwise, you can end up doing the wrong thing very consistently.

80/20 Idea #2: Standardization Is the Starting Line, Not the Finish Line

The word “standardization” makes some people nervous. They picture bureaucracy. Checklists. Corporate manuals. Somebody telling a talented person there is only one approved way to move a paper clip.

Bad standardization can absolutely become that. But Toyota’s idea is more useful. A standard captures the best method the organization currently knows. It gives people a stable starting point and creates a baseline from which improvement can be measured.

Without a standard, everyone has a different process. When results improve or decline, you cannot easily tell why. You are comparing one person’s improvisation with another person’s improvisation.

The standard is not supposed to be holy scripture. It is the best-known version today. When the team discovers a safer, faster, clearer, or more reliable way, the standard should improve.

That distinction matters enormously. A standard that can never change becomes bureaucracy. A company with no standards becomes chaos. The useful position is between the two: establish the best-known method, use it, observe the result, and keep making it better.

BARRY AGREES

This matters even more with remote teams and virtual assistants. When people work in different countries, time zones, and roles, you cannot depend on everybody learning through osmosis. They are not sitting three desks away, listening to how the experienced person handles a call.

You need the process where people can find it. That might include a written procedure, a short screen-recorded video, a checklist, an example of a finished product, a quality-control step, and a statistic that shows whether the process is working.

It also needs an owner. Somebody must be responsible for noticing when the written procedure no longer matches reality. Otherwise, the manual becomes an archaeological record of how the company operated three years ago.

In 2026, AI can make this easier. It can help turn recordings into procedures, summarize recurring errors, maintain searchable knowledge, and support people while they work. But AI does not remove the need for judgment. It can document a bad process just as efficiently as a good one. The team still needs to understand the desired result, examine the work, and improve the method.

80/20 Idea #3: Don’t Just Delegate Tasks. Develop Problem-Solvers.

Weak delegation sounds like this: “Do exactly what I told you. If anything unusual happens, come back to me.” Then the owner wonders why everybody keeps coming back.

Toyota’s model puts great emphasis on developing people. Leaders are expected to understand the work, teach the philosophy, and help others learn to solve problems. That takes longer than giving an order. It is also how you build a company instead of a collection of assistants attached to one overworked executive.

When an employee brings you a problem, the fastest thing may be to give the answer. The more valuable move is often to help the person see the situation clearly: What should have happened? What actually happened? Where did the difference begin? What evidence do we have? What is the smallest sensible change we can test? What result would tell us the change worked?

Those questions develop judgment. And judgment is one of the hardest things to delegate because it cannot be transferred with a job description. It has to be built through observation, practice, correction, and increasingly difficult responsibility.

BARRY AGREES

I want people trained, corrected, and apprenticed until they can produce the result. That means I do not have to be the best technician in every department. But I need to know enough to recognize the expected outcome, and I need strong technical people who can help review, correct, and train others.

The goal is not merely to get today’s task off my desk. The goal is to increase the number of people in the organization who can see what is needed and competently handle it. That is a much higher form of leverage.

If delegation only transfers motion, you save a few hours. If delegation develops ability, you increase the capacity of the whole company.

That is one place where TeamBuilders earns its name. A team is not just a group of people receiving assignments. It is a group whose ability to produce together becomes greater over time.

80/20 Idea #4: Stop Hiding Problems. Make Them Visible Early.

Toyota’s production system is famous for allowing work to stop when an abnormality appears. That can seem inefficient. If the goal is to keep the line moving, stopping it looks like failure.

But keeping work moving while it produces defects is not productivity. It is just making the problem larger and more expensive. Toyota tries to expose problems close to where they begin. Quality is built into the process instead of inspected into the product after everything is finished.

That lesson travels very well outside manufacturing. In an agency, the defect may be a campaign launched with the wrong audience. In recruiting, it may be a candidate who reached the final interview despite missing an essential qualification. In publishing, it may be an error that survives editing, formatting, and proofing before somebody finally notices it in the printed book. In appointment setting, it may be weak messaging that produces poor responses for three weeks before anyone reviews the conversations.

The later you discover the problem, the more work has accumulated behind it. Good management creates early warning points. What should be reviewed before the next stage begins? What number would tell us the process is moving off course? What does the team member have authority to stop? Who needs to know immediately?

A company that punishes people for revealing problems trains them to conceal problems. Then management receives good news right up until the roof falls in.

BARRY AGREES

This is where statistics become valuable. A useful statistic is not decoration for a dashboard. It helps you see a change early enough to do something about it. If appointments drop, response rates change, production slows, or errors rise, you should not wait for a monthly meeting and a 47-slide presentation. You should be able to see the condition, inspect the real work, and make a correction.

But numbers alone are not enough. Liker emphasizes going to the source to understand the actual situation. In other words, do not manage exclusively from a report when the report is only a distant summary of what occurred.

Read the messages. Listen to the call. Look at the customer complaint. Review the work product. Talk to the person doing the job. The dashboard tells you where to look. It does not do the looking for you.

80/20 Idea #5: Small Improvements Beat Occasional Reinventions

Entrepreneurs love breakthroughs. New offer. New software. New campaign. New organizational chart. New AI tool that will apparently replace half the company by Thursday.

Toyota built much of its strength through something less dramatic: continuous improvement, or kaizen. The basic principle is that the work can always become better and the people closest to the work should participate in improving it.

Many improvements are small. Remove an unnecessary handoff. Clarify one instruction. Change the order of two steps. Catch an error earlier. Automate a repetitive action. Improve the template. Add an example that prevents the next new employee from making the same mistake.

None of those changes will make the cover of Forbes. Together, they can transform a company.

There is also an important psychological difference between improvement being a special event and improvement being part of everyone’s normal job. If management owns all improvement, employees learn to follow the existing process even when they can see the flaw. If people are invited to notice and test better methods, the organization gains hundreds or thousands of additional eyes.

BARRY AGREES, WITH ONE WARNING

I agree strongly with the idea of continuous improvement. I also think improvement needs direction. You can optimize a low-value process until it becomes the finest low-value process in the state of Florida. That does not mean the company needed it.

Before improving a task, ask whether the task should exist. Can it be eliminated? Can it be automated? Can the desired result be produced through a simpler route? Then, if the work still matters, improve it.

Toyota developed its methods in a world of physical production. Today we also have AI, automation, and globally distributed teams. The principle still holds, but the available solutions are broader. Sometimes the right improvement is a better checklist. Sometimes it is better training. Sometimes it is giving the responsibility to a more suitable person. And sometimes it is letting software handle the repetitive part so a capable human can use his or her attention on something that requires thought.

80/20 Idea #6: Long-Term Thinking Changes Who You Hire and How You Lead

The first principle in Liker’s framework is to base management decisions on a long-term philosophy, even when that creates tension with short-term financial goals. That is easy to admire and difficult to practice.

Short-term pressure is real. Payroll is not philosophical. Clients want results now. Owners need revenue. But a company that makes every decision for the current week eventually steals from its own future. It hires quickly but trains poorly. It takes bad-fit clients for immediate cash. It tolerates recurring problems because fixing the underlying process would take time. It promotes the strongest producer without determining whether that person can develop others. It cuts quality controls because they appear to slow production.

Then the same company acts surprised when turnover rises, clients leave, and the owner is pulled back into every department.

Long-term thinking does not mean ignoring today’s numbers. It means making today’s decisions in a way that builds tomorrow’s capability.

BARRY AGREES

The true test of a hire is not just whether the person completes assigned tasks this month. Does the person become more capable? Does the role become better organized? Does the person help improve the process? Can the person eventually train somebody else? Does the employee reduce the amount of management attention required, or create a permanent stream of questions and rescues?

That does not all happen immediately. People need training, clear expectations, feedback, and a chance to grow. But the destination matters.

The best team member does more than carry part of the load. Over time, that person helps increase the organization’s ability to carry a larger load.

Where I Would Be Careful With The Toyota Way

This is an excellent book, but it is easy to copy the visible tools while missing the management philosophy underneath them. A company adopts checklists, efficiency measurements, standard procedures, and daily meetings. Management proudly announces that it is now “lean.” Meanwhile, employees are afraid to report mistakes, nobody has time to improve the process, and every decision still has to go through the owner.

That is not the Toyota Way. It is bureaucracy wearing a Toyota hat. The tools work because they sit inside a larger culture of problem-solving, learning, leadership development, and respect for people.

There is another caution for small businesses. Toyota is a massive global manufacturer. Your company probably does not need Toyota-sized infrastructure. A seven-person agency that builds a 90-page procedure for ordering printer paper has not become operationally excellent. It has become bored in a very organized way.

Take the principle, then fit the method to the size and reality of the business. Create enough structure to make the result visible and repeatable. Do not create structure merely to admire the structure.

Does The Toyota Way Still Hold Up in 2026?

Yes, perhaps more than ever.

The tools have changed enormously. We now have AI, automation, real-time dashboards, remote collaboration, searchable company knowledge, and access to capable people around the world. But those tools make management principles more important, not less.

If you automate a confused process, you produce confusion faster. If you give AI an unclear standard, it can generate a large volume of work that is almost right. “Almost right” is a charming phrase until you are the person paying to redo all of it. If you hire virtual assistants without training, expected outcomes, or quality control, distance magnifies the weaknesses that already existed.

Technology increases leverage. Leverage multiplies both good systems and bad ones.

The Toyota approach offers a useful sequence: Understand the actual work. Define the desired condition. Make problems visible. Develop people who can solve them. Improve the process continuously. Then use technology to increase the power of what works.

That is a much safer order than buying another platform and hoping it will supply the management nobody provided.

Monday-Morning Application

You do not need to transform your company into Toyota by lunch. Start with one recurring result that causes frustration, delay, or rework.

1. Choose One Recurring Problem

Pick something that has happened more than once. Examples:

• Leads are not followed up with consistently.

• Client work reaches review with the same preventable errors.

• New employees ask the same questions.

• Projects stall during handoffs.

• The owner keeps being pulled into routine approvals.

• Customers are surprised because expectations were not made clear.

• Do not choose twelve problems. Choose one.

2. Go See What Is Actually Happening

Do not begin with assumptions. Look at the real emails, forms, recordings, CRM entries, work product, or handoffs. Talk with the person performing the work. Ask what makes the task confusing or difficult.

You are not holding a trial. You are trying to understand the process.

3. Define the Desired Result

What should “done correctly” look like? Be specific enough that two reasonable people would reach the same conclusion. Whenever possible, include an example of an acceptable finished result and an example of what is not acceptable.

4. Map the Current Process

Write down the actual steps, not the steps you imagine people follow. Where does the work wait? Where does information get lost? Where does somebody need approval? Where are errors usually discovered? Where does the work come back to you?

5. Ask the Toyota Question

What in the process made this problem possible?

That question moves the conversation from accusation to improvement. Maybe the expectation was unclear. Maybe the training was weak. Maybe no one owned the handoff. Maybe the person had no way to see that something was wrong. Maybe the process has five steps that should have been two.

6. Make One Improvement

Do not redesign the whole company. Change one meaningful thing. Add a checkpoint. Remove a handoff. Improve the template. Clarify the standard. Record the training. Give the employee authority to stop the work when a particular abnormality occurs.

7. Decide How You Will Know It Worked

Choose a simple measure. Did errors decline? Did the turnaround time improve? Did fewer questions come back to management? Did client satisfaction improve? Did the employee become able to handle the task without intervention?

8. Update the Standard and Train the Team

If the change works, put it into the procedure. Then make sure the people involved understand it. A process that lives only inside the owner’s head is not a process. It is a secret.

The Friday Improvement Question

At the end of each week, ask every team member: What is one repeated problem, unnecessary step, or preventable error you noticed this week, and what change do you recommend?

You will not implement every suggestion. But you will begin teaching the organization that noticing and improving the work is part of the work.

Who Should Read This Book?

The Toyota Way is especially useful for:

• Business owners whose companies keep pulling them back into daily production

• Leaders dealing with recurring quality problems

• Managers building remote or virtual teams

• Companies documenting and standardizing their operations

• Owners who want employees to use better judgment instead of waiting for orders

• Agencies and service businesses that assume lean thinking only applies to factories

• Leaders introducing AI and automation into existing workflows

If you want a five-minute collection of productivity tricks, this is not that book. If you want to think seriously about how a company develops people, improves processes, and produces consistent quality over time, it is worth the effort.

Barry’s 80/20 Verdict

The 80/20 value of The Toyota Way is not any single tool. It is the relationship between good processes and capable people.

Build standards, but let the standards improve. Measure results, but go look at the actual work. Delegate tasks, but develop judgment. Make problems visible before they become disasters. Fix the system instead of cycling endlessly through blame. And treat continuous improvement as part of everyday production, not an occasional management project.

The book also corrects a false choice that hurts many companies. You do not have to choose between caring about people and demanding excellent results. Developing people is how you create excellent results that last.

My biggest takeaway is simple: A great company does not merely get work out of people. It builds people who can make the work, the system, and one another better.

That is a company with the capacity to grow.

Barry’s Rating: 9/10

It is detailed, occasionally more manufacturing-heavy than a small service-business owner may need, and it requires some translation into your own environment. But the central principles are outstanding. They belong in any serious conversation about leadership, delegation, quality, training, and building an organization that improves without requiring the owner to personally solve every problem.

Want to Build a Team That Gives You Time Back?

If too much of your business still depends on you, the answer is not simply hiring more people. You need the right people, clear outcomes, useful systems, effective training, and a structure that allows the team to become more capable over time.

That is exactly the kind of work we help business owners accomplish through TeamBuilders.

Schedule a conversation with me: SCHEDULE WITH BARRY

Want My Next Book Before Everybody Else?

I’m getting ready to release 7-Figure Networking.

Join my early-access book list and you will have an opportunity to get 7-Figure Networking before the general public. You will also be on the early-notification and early-access list for my future books as they are released.

Barry Coziahr

Barry’s 80/20 Five-Page Book Review

I read the whole book. You get the 20% that matters most, what I agree with, what I don’t, and what you can actually use Monday morning.