I don't get it.
Only, we've caught almost all the tuna in the ocean, so please make sure to ask for something else at the bar.
Edit: Just to be clear, that was not Tom's point. His point was that the plate was empty, so by simply noticing it is empty, we can ask for more fish which "pulls" all the activity that ends up producing fish on our plate. In a kanban system, you only really need to worry about how much inventory you want to carry at each station and the connection to the previous station.
If you don't ask for it you don't get it.
Its just a organized way of building a todo list which has a few features like:
1. Priority.
2. Ability to see the work-item move through various stages of work(Accepted, in-progress, blocked-by, done).
3. Means to track the progress of the work-item.
4. Means to the improve the process through methods described by the process.
That's actually a very meta reply (like that joke about UDP).
This is kind of irrelevant, but somewhat amusing, so I figure I'll tell it. My neighbour (in the middle of nowhere in rural Japan) was some kind of automotive manufacturing expert before he retired. I don't even know his name (he tells me to call him "Tom"), but we go out drinking occasionally. He must have been a big wig because he spent a considerable amount of time in the US and even has a personally signed thank you card from George Bush Sr.
Anyway, we were at the bar and I was telling him about the use of kanban in software development. My wife interrupted and asked what kanban was (because in Japanese "kanban" just means "signboard"). I tried to explain the concept, but she remained confused. He said, "I can explain it very easily". He picked up an empty plate and handed it to my wife. "We're out of fish", he said, motioning to the bar. :-)