Lean is a bias about waste, not a board tool and not a personality. Value is what the customer will pay for or wait for. Everything else is a candidate for removal — including the heroic utilisation that keeps everyone busy while the work sits. Busy is a local optimum. Flow is the point.
Value, and the wastes that impersonate it
Start with the value stream: the steps a piece of work actually takes from request to usable result. Walk it. Time how long it sits versus how long someone touches it. The usual finding is that most of the calendar is waiting — for review, for a specialist, for a decision, for an environment that is 'nearly ready.'
The classic wastes are easy to spot once you are looking: transporting work between queues, inventory of half-finished items, motion and hand-off theatre, waiting, overproduction (starting work nobody asked for), over-processing (the gold-plated form), and defects that come back. Unused talent — people who can see the fix and are not allowed to make it — is the waste organisations add when they treat staff as pairs of hands.
Do not hunt waste with a witch trial. Ask what delay or rework the customer would notice. A daily status meeting that produces no decision is over-processing. A backlog of started stories is inventory. A defect found in production is the expensive edition of a miss that could have been a cheaper review. Name the waste in the work, not in the people.
Flow beats utilisation theatre
A team at 100% utilisation has no slack to finish, review, or absorb a blocker. Work then queues. Queues grow cycle time. Cycle time growth is how you get a department that is fully booked and a customer who is still waiting. That is not a paradox. That is a full motorway.
Optimise the stream, not the local hero. A designer who is 'efficient' because they keep starting new files while development is clogged is producing inventory. Reward finishing, not starting. If your metrics clap for utilisation, you will get utilisation, and the waste will move to the next column and hide.
Make work visible before you 'improve' it. Invisible queues — in inboxes, in 'I am just finishing something' — are how waste denies it exists. The next lesson is the system that makes the queue undeniable. Lean without visibility is a sermon.
Respect for people, and stop pushing work in
Lean without respect is just cost-cutting in a nicer font. The people who do the work can see the waste. Your job is to give them a way to say so and a policy that lets them stop starting. If only the PM is allowed to name a bottleneck, you have a reporting culture, not a lean one.
Push systems assign work because capacity exists or a date exists: 'you are free, take this.' Pull systems start work when the downstream step has a slot. Push maximises starting. Pull protects finishing. Most project plans are push documents. That is not a crime. Pretending a pushed start date is a pull system is.
One improvement at a time is already a lean habit. If you remove five wastes in a week you will not know which change helped. Stabilise, see, then change. The board, the limit, and the metrics exist to make that possible — they are not the philosophy. Do not buy stickers and call it lean.
Summary & next steps
Lean hunts waste in the value stream and prefers flow over looking busy. The usual wastes hide as inventory, waiting, defects, and unused judgement. Pull starts work when there is a slot; push starts work because a plan is lonely.
Next: Kanban systems — making the work and the queue visible so pull is a rule, not a mood.