Respect for People
The overlooked pillar that makes everything else work.
1The Second Pillar
Toyota's house has two pillars. Everyone knows the first: Just-in-Time and continuous improvement. Few discuss the second: Respect for People.
This isn't HR fluff. It's the foundation that makes improvement possible.
Think about it: Lean depends on workers identifying problems, proposing improvements, and implementing changes. Who's closest to the work? The people doing it. If those people are afraid, disengaged, or treated as interchangeable cogs, improvement stops.
Toyota's insight: The people doing the work know the most about improving the work. Management's job isn't to design the perfect system—it's to create conditions where workers can improve the system continuously.
This requires respect. Not just being nice, but genuinely trusting that the people closest to the work have valuable knowledge and good intentions.
Ohno's View
Taiichi Ohno said standards should be set by workers, not engineers. The people doing the work understand it best. Engineers should help workers improve standards, not impose them from above.
2What Respect Actually Means
Respect in the Toyota sense is not coddling. It's challenge.
Respect means trusting people enough to challenge them. A Toyota manager who accepts substandard work is being disrespectful—they're implying the worker can't do better. A manager who says "I know you can figure this out" and then supports the learning process is being respectful.
Respect manifests as:
Listening: Actually hearing worker feedback about problems, not dismissing concerns.
Development: Investing in people's growth, not just their output. Toyota famously develops employees for decades.
Involvement: Including people in decisions that affect their work, not dictating from above.
Challenge: Setting high standards and providing the support to meet them.
Blame-free culture: Focusing on fixing systems rather than punishing individuals.
The opposite of respect isn't cruelty—it's indifference. Treating people as expendable resources. Not caring about their development. Ignoring their insights. This is disrespect, and it kills Lean.
A developer says 'I can't meet this deadline.' The manager asks 'What's blocking you?' and works with them to remove obstacles or adjust scope. The developer feels heard and empowered.
A developer consistently delivers late with bugs. The manager says nothing to avoid conflict. The developer never improves, the team suffers, and eventually the developer is fired without ever getting honest feedback.
3Why This Matters for Improvement
Without respect for people, Lean tools become weapons.
- A value stream map becomes a surveillance mechanism
- WIP limits become punishment for not working faster
- Root cause analysis becomes a blame exercise
- The andon cord (stop the line) is never pulled because of fear
Psychological safety—the term Google popularized—is just modern language for what Toyota understood decades ago. People must feel safe to raise problems, or problems stay hidden.
Consider: Toyota workers can stop the entire production line when they spot a problem. No permission needed. This is unimaginable in most organizations. But it only works because:
- Stopping is celebrated, not punished
- The focus is on fixing the problem, not finding fault
- Workers are trusted to make good judgments
- Management actually wants to know about problems
In software, this translates to:
- Developers who can push back on unrealistic deadlines
- Engineers who can raise concerns about technical debt
- Teams who can fail safely and learn from it
- Individuals who can say "I don't know" without shame
If your organization punishes the messenger, no Lean tool will help. Fix the culture first.
The Litmus Test
Ask: When was the last time someone raised a serious problem and was thanked for it? If you can't think of an example, your Respect for People pillar is weak.
4Developing People
Toyota doesn't just hire skilled workers—they develop them. This is long-term investment, not training programs for next quarter's project.
Development includes:
- On-the-job coaching: Learning through real work with mentors
- Job rotation: Understanding the whole system by working in different areas
- Problem-solving skills: Teaching people to think, not just execute
- Leadership paths: Growing leaders internally who understand the culture
This requires patience. It takes years to develop a worker who can identify waste, propose countermeasures, and implement improvements. But once you have that workforce, improvement becomes self-sustaining.
In software, this means:
- Pair programming and mentorship, not just code reviews
- Rotating people through different parts of the system
- Teaching problem-solving, not just coding
- Promoting technical leaders who embody values
The temptation is to hire experienced people and expect immediate performance. But you can't hire culture. People who grew up in a different system will reproduce that system unless you invest in developing them into something new.
- Respect for People is essential, not optional
- Respect means trust and challenge, not coddling
- Without psychological safety, Lean tools become weapons
- Developing people is a long-term investment that enables improvement
- You can't hire culture—you have to develop it