8.4. REPAIR: ANOTHER NEW VALUE CREATION 41
Long-term expectations fall outside of the bounds of rationality. While Simon told us
satisficing is the only solution outside of the bounds, he did not show any quantitative solu-
tion [2]; Keynes, however, told us we can manage to do long-term quantitative expectation, if
we feel confident.
Simon is more interested in decision making and Keynes’ work is in the area of economic
expectations. So, their goals are different, but it is interesting to know how confidence or trust
can extend our quantitative evaluation outside of the bounds of rationality.
8.4 REPAIR: ANOTHER NEW VALUE CREATION
We have discussed how continuous prototyping software development contributes to trust build-
ing. Now, let us look at it from another angle.
If we turn the software development figure (Fig. 8.3) upside down and compare it with the
hardware one (Fig. 8.2), we realize both are identical (Fig. 8.6). en, aren’t there any ways we can
apply to control degradation of hardware? When hardware engineers talk about deterioration,
they say they must prevent failures. But deterioration and failures are different. Of course, after
deterioration failure occurs. But that is the last and final stage. Until then, deterioration goes
on gradually. And if we look at deterioration from another angle, it is the process nothing other
than fitting. All products come to fit us after using sometime. en, we feel the product is MY
product. It fits me perfectly. But most hardware engineers do not regard deterioration as the
process of fitting. ey just regard it as a step to failure. So, they believe if they can prevent
failure, that is the best way to guarantee product quality. eir mindset is still stuck with mass
products. But just as software is doing, if we can introduce a closed-loop control to deterioration,
we could possibly reduce time to fitting and keep fitting time longer. en, we can secure lifetime
customers.
Function
Software (Continuous Prototyping)
Validation
Customizing
Function
ShippingUse
Design
Function
Degradation
Restore
Shipping
Verification
Hardware
(Delivery of Finished Product)
Production
Maintenance
in Use
Figure 8.6: Looking at software development upside down.