Waste 7: Unused Talent

This waste wasn't in Toyota's original seven—it was added later because knowledge work makes it painfully visible.

Unused talent means not using people's skills, knowledge, and ideas. It's the developer who sees process problems but isn't asked. The designer whose insights about users go unheard. The junior engineer with a better solution that management overrides.

In manufacturing, workers might primarily follow prescribed motions—though even Toyota engaged workers in improvement. In knowledge work, the work IS thinking. If you don't use people's brains, you're wasting their primary contribution.

This waste matters because:

• The people doing the work understand it best
• Improvement depends on frontline insights
• Disengaged workers produce disengaged work
• Talent leaves when it's not valued

Command-and-control management: Managers decide; workers execute. Ideas flow down, not up. Decisions happen in rooms far from the actual work.

Ignoring expertise: When developers say "this will take longer" or "this is risky," they're often overruled by people with less context. Their expertise is dismissed.

Learned helplessness: After enough dismissed suggestions, people stop suggesting. "That's above my pay grade." "They wouldn't listen anyway." "I just work here."

Role rigidity: "That's not your job" applied to ideas, not just tasks. The developer with product insights is told to focus on code. The QA engineer who sees process problems is told to focus on testing.

No improvement time: When every hour is scheduled with feature work, there's no space for improvement. Improvement becomes something that happens "later" (never).

Blame culture: When problems lead to punishment, people hide problems. When suggestions that fail lead to blame, people stop suggesting. Safety to experiment is essential.

The tragedy: organizations hire smart, capable people and then design systems that prevent those people from being smart or capable.

Ask for input, then act on it: Don't ask what people think if you're going to ignore them. But do ask, and do act. Close the feedback loop.

Improvement is everyone's job: Not a separate activity delegated to a special team. Everyone identifies problems. Everyone proposes solutions. Everyone implements improvements.

Psychological safety: Make it safe to raise problems, suggest changes, and fail at experiments. Punishing failure guarantees you'll stop hearing about problems.

Self-organizing teams: Let teams figure out how to organize their work. They understand their context better than management does.

20% time or equivalent: Dedicated time for improvement, learning, and exploration. Google's famous 20% time, or Atlassian's ShipIt days, or just "Friday afternoons are for making things better."

Gemba walks: Leaders going to where work happens and asking "What gets in your way?" Then fixing those things. Not suggesting—fixing.

Rotate and cross-train: People who only see one part of the system only improve one part. Rotation builds systems thinking.

The return on investment is massive. Engaged workers produce better work, stay longer, and improve the system for everyone. Disengaged workers do the minimum and leave.