Ries says it is more efficient because if you were to do 100 at a time, you would first have to sort everything and then start the process, but if you were to do that the 1 batch at a time group would already be done.
For Hardware becoming software we could simply use some of the many unused buttons on our joystick to do simple tasks for the robot. For example, we could use it to do a quick 180 turn or if we are in a position that we are in a lot of the time we could just press a button so then we could just finish the task without having to keep doing the same thing. For fast production changes we could have some people quickly do cad models and prototyping to find flaws in the designs by using the materials that are sitting in the robotics room and also have people ready for fall back ideas in case the specific design is too flawed. For rapid prototyping tools we could make use of the scrap metal and wood we already have instead of having to make a cad model and send it to Mcneilus steel. I don't know if we did that all of the time, but we could simply just use the scrap metal and wood that is just sitting there.
Some things that cause people to leave are moving, graduating, and simply just not wanting to be on the team. Well some things that cause these things to happen are fairly simple reasons like getting a new job, or doing well in school, or just not liking the people on the team or not liking the sport. We can control the graduating not wanting to be on the team by not letting people graduate. No just kidding, but we could have the graduates able to mentor our team the next year after they graduate. We could also be very welcoming to new people and show them things on our team.
The purpose of the "Five Whys" is to find the initial cause for something. To perform it you must ask yourself "Why" five times..
We could simply let them use a robot that is nothing close to the final design and have them suggest things about how we should fix it. We could ask them what they think of it and what they want on the robot and do what they want.
I have learned that we must question ourselves to learn. We must also get other opinions from other people. We also don't have to do the same ideas as other teams. For example, many teams don't make hardware software, we could do that. We also don't have to rack our brains for complex solutions when we can just fix something with the easiest. "The best solution from a problem is usually the easiest one" -Glados.