The Digital Transformation of Manufacturing is achieved when the concept of updates becomes commonplace through the Law of Disassembly.

Microsoft's Windows 95 was an incredibly successful operating system. It is often mentioned by critics as the most significant historical advancement for personal computers, and it played a significant role in overwhelming its competitors. However, it is not well-known that this remarkable software, Windows 95, was released with over 3,500 bugs (software defects).

"Updates vs. Issue Response: Differences from the Perspective of Online and Offline Companies"

In the manufacturing industry, particularly hardware manufacturing, there is a significant cost involved in the manufacturing, distribution, and logistics of products. Updates are nearly impossible. Retrieving products, storing them somewhere, applying new updates, and going through verification before shipping again would incur substantial costs. Therefore, unless there is a significant quality issue, companies in the industry do not have the concept of "updates." The development process for physical products involves meticulous quality verification before release to ensure there are no updates (typically focusing on issue response) afterwards.

"The Digital Transformation of Hardware Products Requires a New Grammar of Updates and Different Perception"

The foundation of hardware products is Quality. They should perform the promised functions without issues under any adverse conditions. Simulating various adverse conditions that may occur in the real world and creating products that function flawlessly within them is essential. In fact, it is similar to exception handling in software development. When such exceptional situations/issues occur in online/software scenarios, it is relatively easy to update and distribute fixes. However, it is more challenging in hardware.

Recently, with hardware products becoming connected to the online world through technologies like Wi-Fi and Bluetooth, the basic foundations for post-release updates have been established. However, the reason why they cannot be applied as easily and quickly as one might think is that the hardware domain still exists, and there is a possibility that hardware products may not function properly after updates. The cost of retrieval/storage/shipping/logistics for hardware is too high, so it is impossible to ignore quality issues on the hardware side.

"The Law of Disassembly: Creating Independent Problems"

To address this, a new grammar of updates is needed. The problems should be independent but related, minimizing interference with each other to solve them. There can be various ways to minimize interference. Physical separation/Virtuazliation is one option, although it incurs significant costs and time. To proceed cost-effectively, creating "promises and standards" is a viable approach. The first thing to remember is "adhering to defined specifications," and the second is "not forgetting the first promise." While working on individual developments, occasional needs for new improvements/additions/changes may arise. It is crucial to strictly adhere to the promises and postpone improvements. Now, even hardware manufacturing can accommodate updates.