Open & Proper Communication

Hardware concerns aside, let’s scrutinize software a bit more closely. Annual revisions to operating systems and computational software are now expected. Some of these revisions contain major changes. These create productivity problems. Users are always low on the so-called learning curve where they are not as productive and never get a chance to really learn the software before it again changes. Operators of graphical design software in the automotive business need nearly a two-year apprenticeship before they are deemed productive. With software upgrades arriving every year, a complex system of management is needed to assure that proficiency and productivity are always available from some while others are learning the newest upgrades. Are we being good stewards of human and other resources when we continue to encounter these upgrades, which often are barriers to real productivity?

Another software problem in industry is that computer packages often provide far more output than can be handled or needed. Software that models the plastic injection molding process yields twenty different output variables for over 2,000 locations in the simulated molding machine. What information is important? What information is needed? This all takes time (and money) to sort out. Information overload. A key obstacle along with frequent software upgrades is achieving productivity.

Another key productivity problem is lack of software flexibility. Computers operate following rules, but within human experience every rule seems to have an exception. For example, registration software for a college would not be flexible if it did not allow for exceptions in required courses. Most of my work with transfer students as a former department chair required decisions about exceptions. These often unique course equivalencies need to be captured appropriately by the software to maintain transcript integrity. Another norm or value for design is open and proper communication. In this context we want to use computer software that represents user intent. It is this intent, stored in the computer that, for example, communicates to someone at a later time (graduation) which course was substituted for the one required.

This issue of intent-communication is a problem within the paperless office or manufacturing process. Often, for example, the intent of the machine designer gets lost in the computer. A length dimension, important to the fit and function of a machine part, is given by the designer. The computer file of that part, however, only contains points on a surface used to guide automatic machine tools in making the part. This file does not store and hence communicate designer-intent that the dimension is significant. It is just given. And it is only this electronic file that is read on the computer screen by a quality control inspector. All dimensions appear equally significant to him or her. Design intent is then not communicated openly and clearly.