Esq. Jonathan Cartu Reports - Why Hardware Must Embrace Agile Principles - Jonathan Cartu Computer Repair Consultant Services
post-template-default,single,single-post,postid-3199,single-format-standard,qode-quick-links-1.0,ajax_fade,page_not_loaded,,qode_grid_1300,footer_responsive_adv,qode-theme-ver-11.2,qode-theme-bridge,wpb-js-composer js-comp-ver-5.2.1,vc_responsive

Esq. Jonathan Cartu Reports – Why Hardware Must Embrace Agile Principles

Why Hardware Must Embrace Agile Principles

Esq. Jonathan Cartu Reports – Why Hardware Must Embrace Agile Principles

In a Wall Street Journal article last month, author Matt Ridley argued that “Innovation Can’t Be Forced, but It Can Be Quashed“. After noting that innovation has been slower in hardware than in software, the article argues that this is mainly because “bits are lightly regulated and atoms are heavily regulated.”

But is over-regulation the root cause of the slow pace of innovation in hardware? Or is it the way hardware is being managed in these big old manufacturing firms? Ridley’s new book, How Innovation Works (HarperCollins, 2020) unwittingly points to a potent cause of the problem: inattention to the primary principle of business agility—an obsession with the customer’s needs. In 406 pages of describing how innovation works, Ridley’s book mentions the customer only ten times, and then only in passing—not exactly an obsession with the customer. This is not how innovation works: innovation begins from, and is driven by, the customer’s changing needs.

How Manufacturing Practices Prevent Innovation

Some engineers defend the slow pace of innovation in hardware by pointing to the fact that atoms are inherently more unwieldy than bytes. It takes more effort and expenditure to make changes to atoms than to bytes, particularly in a firm that is manufacturing at scale.

But the atoms-vs-bytes difference is far from being the whole story. Existing manufacturing processes are also slow because they are designed to be slow. If a team of  engineers in a large automaker wants to redesign a car door, they may need to wait ten years or more for the firm to pay off the $100 million that it spent on a door mold machine before a different design can be made. The firm might have clever engineers with a better idea for the car door, but when they are working inside a firm that they can’t change the door until that $100 million is paid off, they are stuck.

Today, a $100 million manufacturing mold with a ten-year replacement cycle is usually not the only solution that is technically possible. With modern 3-D printing techniques, it’s possible to make rapid changes at relatively low cost. The problem is a management problem: the unwillingness to do anything about the sunk cost in that $100 million door mold machine, and all the other hard-to-change manufacturing equipment and processes.

These hard-to-change processes were good enough for a 20th century car. What the customer  got on the day of purchase is what the customer got to use for the rest of the car’s life. The customer wasn’t asking for anything more. But it’s not good enough in a marketplace where customers are coming to expect what Tesla already delivers: a capability to improve their cars every month or so after purchase through software updates. These updates aren’t just cosmetic changes to the display. For instance, Tesla owners might suddenly discover after an update that the rear seats are now heatable.

But the problem is not just manufacturing equipment like the hard-to-change $100 million door mold machine. It’s also the thinking and attitudes that accompany that equipment. Investment in hard-to-change $100 million mold machines and similar equipment can come to be seen as the necessary way in which manufacturing should be carried out. Anything else is questionable. You do the design and you install your $100 million mold machine and you are set for ten years. That is, until you discover that your customer wants something different.

Hardware engineers and their managers can come to justify such thinking to themselves and find solace in the thought that they know what customers want in a car. There’s no need to test whether their underlying assumptions are correct or whether tastes may have changed. They are not seriously thinking about the possibility that customers who thought they were buying a transportation device have now discovered that what they really want is something different. For managers in a car manufacturer, it may be simpler not to inquire too much into what customers think: they bought the car, so they must be happy.  In this way, the $100 million mold machine can come to be seen as an unchangeable aspect of the business.

Traditional software development used to have a similar problem. Large software companies with teams of specialists were working in dedicated facilities, going through many years of planning and implementation to produce big hard-to-change systems that might or might not come close to what they had hoped to build back when they started, years before. Often, they failed to be completed at all.

Experimentation with Agile software development practices in thousands of firms over the last two decades showed that it was better in complex rapidly changing situations to design products in a modular fashion and iterate rapidly towards steadily better solutions. The work is broken into small pieces. Self-organizing teams work in short cycles getting constant feedback from customers. Managers learn to refrain from investing anything like a $100 million system that is hard to change and will take ten years to pay off. Teams work in a modular fashion and continually innovate in the light of experience and customer feedback. And better yet, they find that it can be done at scale. They never arrive at perfect. They keep at it. The improvement journey never ends.

How Hardware Is Becoming More Nimble    

Now in some firms, hardware is catching up and becoming nimbler. “At Tesla for instance,” as consultant Cliff Berg writes, “they use traditional computer-aided design (CAD) tools such as CATIA, but they also invested in an end-to-end 3D modeling system from which they can view and simulate entire assemblies and automatically print parts. Importantly, the software is fast, even when handling complex assemblies, so that engineers do not have to wait, which encourages a rapid iterative design approach.”

The ability to go right from design to “print” changes everything. Instead of trying to perfect a design before it is tried and testing simulations, Space-X designs, simulates, builds, and tests often. “Instead of spending months or years on design and then carefully…

Jon Cartu

No Comments

Post A Comment