Please enable JavaScript.
Coggle requires JavaScript to display documents.
Chp 9 Batch (Why small batch would be better than a big one with…
Chp 9
Batch
Why small batch would be better than a big one with specialization of labor
Takes times to organize and stack etc in specialization
wouldn't know abt a problem until end
what if by the time done - customers decide they no want it
also gap to reduce "changeover time" - ie. time to reconfigure from 1 purpose to another
Allows for greater customization
Immune System key
(Continuous deployment)
That checks for accidental stupid mistakes and corrects / notifies immiediately
Then everyone on relevant team should be notified
The team should be blocked from any further changes until root cause analysis done and prob fixed (this was point 4)
beyond software
By hardware becoming software (eg. So much value in automobiles from software)
fast production changes (with smaller changeover times)
3D printing and rapid prototyping
form, fit and functionality need to be well (first 2 3D printing deals with)
Pull - not push
responding to a gap made when a customer buys - going all the way back to scratch
super helpful in changing decisions / pivoting - testing new hypotheses
Large batch death spiral
keep investing more and more in single batch - ignoring risks of future changes etc
Startup way table in App1, Table1