One classmate’s problem

Every student in the Green Belt class brings a real problem from their own workplace — a bottleneck, a backlog, an approval no one can quite defend. Early in the course the class hears them all, agrees on what makes one worth choosing, and votes. Only one problem gets worked in depth. But that is not what most of the room takes home. What they take home is the method used to work it — a way of getting at their own problems, the ones still sitting back at the office.

Guided by the instructor, the class works that one problem the way the discipline works any problem. It starts with a clear, measurable statement of what is actually wrong — harder than it sounds, and usually the first correction of the week. Then the class maps the process as it really runs, not as the org chart imagines it, until the work is visible on the wall. The turn the week is built around comes next: learning to see the operation as a single system rather than a row of separate tasks. That is the shift that makes the delays, the bottlenecks, the handoffs no one needed, and the rest of the waste finally show themselves. Only once the whole is understood does the class design a better version — and it changes the few things most likely to move flow, not everything at once.

The people doing this come from everywhere — a machine shop, a hospital, a county office, a construction firm in the same room. None of them can lean on knowing the owner’s industry, so they lean on the discipline instead, and they bring the one thing the owner cannot: distance. It is simply easier to see a problem clearly when you have no stake in it. Anyone who has spent a dinner happily untangling a friend’s problem at work knows the pull of it. Your own problem comes wrapped in the reasons it got that way; a stranger’s comes with none of that, and the stranger looks straight at it. So the outsiders routinely spot what the owner, too close to it, had stopped seeing.

One class took up a manufacturing process losing time to long lead times and bottlenecks, and worked on how material and information moved through it. Another took up an administrative process buried in delay and rework, and found the familiar culprits — approvals no one needed, work done twice, responsibilities no one owned — before designing a simpler version with clearer ownership and less lost time.

None of this is academic. The problem is real, carried in from a working operation, and its owner is in the room the whole week — which means a fix that would not survive their floor gets caught on the spot, by the one person who knows it would not. What the class produces is a solution its owner has already tested against reality. And because the point was never the single answer but the method behind it, Lean stops being a box of tools and becomes a way of thinking. Every student leaves with two things: a plan for the problem they brought, and a repeatable method for the ones they have not met yet.

Rishi Malhotra, who teaches the class, put the point this way to Extended Studies:

The most rewarding part isn’t handing someone a certificate. It’s seeing them return to work with a different way of looking at their organization. Once they learn to see processes as systems, they begin finding opportunities for improvement that were always there but weren’t visible before.

The certificate records that the week was finished. It is not the part worth keeping. What the participant takes home is a way of looking — they arrived able to see the one problem they brought, and they leave able to see the ones they did not: the delays and detours and doubled work that had been sitting in plain view the whole time, unremarked because no one had ever been taught to notice them. Only one problem was solved in the room. Everyone in it left able to solve the next.

· · ·