16.10.2015 Views

Managing Computers in Large Organizations

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Manag<strong>in</strong>g</strong> Microcomputers <strong>in</strong> <strong>Large</strong> <strong>Organizations</strong><br />

http://www.nap.edu/catalog/167.html<br />

About this PDF file: This new digital representation of the orig<strong>in</strong>al work has been recomposed from XML files created from the orig<strong>in</strong>al paper book, not from the<br />

orig<strong>in</strong>al typesett<strong>in</strong>g files. Page breaks are true to the orig<strong>in</strong>al; l<strong>in</strong>e lengths, word breaks, head<strong>in</strong>g styles, and other typesett<strong>in</strong>g-specific formatt<strong>in</strong>g, however, cannot be<br />

reta<strong>in</strong>ed, and some typographic errors may have been accidentally <strong>in</strong>serted. Please use the pr<strong>in</strong>t version of this publication as the authoritative version for attribution.<br />

A PERSPECTIVE FOR THE CHIEF EXECUTIVE OFFICER 76<br />

educators. Both alternatives represent new career paths for MIS people.<br />

All of these issues are important. But which ones should legitimately<br />

concern the chief executive officer (CEO) of a company? Where should top<br />

management focus its efforts? And who is best suited to deal with the rema<strong>in</strong><strong>in</strong>g<br />

issues?<br />

I believe that some of these issues should not, and <strong>in</strong> some cases cannot, be<br />

addressed through top management control measures. They can be adequately<br />

resolved through normal bus<strong>in</strong>ess practices or by further developments <strong>in</strong><br />

technology. From my perspective, the CEO should focus on the first and last<br />

issues outl<strong>in</strong>ed above—data management and the shift <strong>in</strong> skill sets. The other<br />

three categories—product proliferation, acquisition practices, and level of user<br />

maturity—are best dealt with at lower levels <strong>in</strong> the organization.<br />

In terms of the first of these lower-level concerns, it is not at all clear that<br />

we should try to control product proliferation at this stage. The diversity of<br />

products is a good <strong>in</strong>dicator that the potential uses and the best approaches for<br />

personal computers are still evolv<strong>in</strong>g.<br />

The technology will cont<strong>in</strong>ue to evolve as well. Although some de facto<br />

standards have emerged they may be only temporary. The IBM PC has<br />

obviously created some of these standards, but that product represents only one<br />

of several plateaus <strong>in</strong> the evolution of personal computer technology. The next<br />

plateau probably belongs to systems runn<strong>in</strong>g UNIX, the AT & T operat<strong>in</strong>g<br />

system, and support<strong>in</strong>g more sophisticated user <strong>in</strong>terfaces derived from the<br />

Apple Lisa.<br />

Unfortunately, even though we may be able to identify some of the likely<br />

future standards, today's products do not yet support them. The best approach,<br />

therefore, is to take advantage of currently available products to meet current<br />

needs. The connectivity issue can be addressed where necessary, but sett<strong>in</strong>g<br />

standards for centralized development and support isn't worth the effort.<br />

Centralized developers cannot possibly keep up. Besides, vendors will provide<br />

technical support and ma<strong>in</strong>tenance to ma<strong>in</strong>ta<strong>in</strong> their reputation and survive <strong>in</strong><br />

the marketplace. The choice of products should be driven primarily by the<br />

personal needs of the <strong>in</strong>dividuals who are to use them. The current basis of<br />

personal computer purchases should be specific needs and opportunities, not<br />

anticipated potential.<br />

Copyright © National Academy of Sciences. All rights reserved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!