A lean approach to problem-solving starts with defining the problem correctly to avoid rework. Sandbox environments let you test ideas safely and delete them if they fail, cutting waste before production.
If you think about all the steps that you need to go through in the original setup, where you need to define the problem, you need to define it right the first time, because if you get it wrong, you have to start all the way back again. So define the problem, get management approval, get the budget, find the skilled resources. It's about eliminating all of that waste. Someone can sit down, can just have a play. I have this idea. If it doesn't work, you've lost a couple of days. But if it does work, that means that you can then deploy it into an operational setting. So it really is about lean. It really is about eliminating as much of the waste as possible and getting people to just focus on what really delivers value.
That's really neat. Just another question about that. A lot of times people do development in what I would call a sandbox. Is that environment also very helpful in this sort of approach where you have a place where you can play? Before you make it live or just give it a try? What— tell me, what's your experience there?
Well, depends on the environment that you're in, but normally if the solution has the right level of role access and the security rights, etc., it's— it doesn't really matter. You can experiment. If it doesn't work, just click delete and it's gone.
