c-- styles for logos and headline links do not modify internet, red, or black styles -->

Intranet Journal   Earthweb  
Events Jobs Premium Services Media Kit Network Map E-mail Offers Vendor Solutions Webcasts

   Intranet Journal Subjects
Search Earthweb

Privacy Policy



internet.com
IT
Developer
Internet News
Small Business
Personal Technology

Search internet.com
Advertise
Corporate Info
Newsletters
Tech Jobs
E-mail Offers

internet commerce
Be a Commerce Partner
















 

[ Home | Discussion Forum | How Do I... | Lotus Notes Intranets | Microsoft SharePoint | Products | Shopping  ]

free news!

The Elements of Intranet Style
By Eric Brown and James W.Candler

New

Excerpts From
Chapter One
"Don't Even Think of HTML, Servers, or a Budget Before You Read This..."

 

PLANNING YOUR INTRANET
 

Those Who View an Intranet Project as a Technology Project Will Fail.

Managers are accustomed to viewing projects involving many computers as technical tasks to be turned over to "real people" only after the technicians have had their say.

An Intranet project most wisely begins with a group of non-technical people who know the kind of information they need and the kind of information others are asking for.

AN INTRANET IS A COMMUNICATION PROJECT; TECHNICIANS MAKE IT HAPPEN.

Exclude Technical Specialists From Early Intranet Look and Feel Planning

The technology is changing so rapidly that there is no benefit in including technicians in look and feel planning. They will only slow the process by discussions of bandwidth and streaming.

 

Let communications people get excited about what can happen with an Intranet. Then bring in the technicians
to make it happen. If they are smart, they will thank you. Relieving the technicians of this burden will allow them to practice their craft with a new freedom and excellence.

In the Beginning There was Adam, not a Computer. Your Goal Should be to Make the Intranet a Network of People, not of Wired Machines.

 

The goal of a network of people isn't as natural and obvious as it may seem. At its core, the Intranet is a network
of machines, not of people. Everyone's computer has a natural place on the network expressed by a number, an Internet Protocol (IP) address, e.g., 123.456.789.123.

People, on the other hand, have to be "made" to exist on the network by means of applications of various kinds that force the rules of the Intranet to apply to them, e.g., Email and Directory Services.

Concentrate on technology that strengthens the people relationship of the network; avoid that which unnecessarily strengthens the machine's position. If a technophile tells you that streaming is essential for your system, your question is always: "What people function will this technology assist?"

In order to avoid yet another round of expensive unfulfilled expectations, the Intranet must be placed primarily in the hands of general business professionals. If the exclusivity normally granted to technologists during times of rapid technical change can be transferred quickly to these professionals, the promise of the computer age will finally be realized. The corporate Intranet will be the means of fulfilling that promise.

Intranets will, on the one hand, offer technophiles the opportunity to practice their craft in exciting new dimensions, while, on the other, extending to traditional management the real ability to obtain real business results.

 

An Old Concept Reapplied: The "Media" and "Message" Apply to an Intranet. (In Intranets, the Media is Definitely not the Message.).

Concentrating on the technology of the Intranet is like having the writer of a novel worry about the kinds of presses and typesetting used to print the publication. We would never think of having printers worry about content (plot of a novel for example), or have a writer insist on a DocuTech5000 printer. Yet, most Intranet projects are led by technical personnel (the printers) operating in just that illogical way.

Business generalists (writers)should be responsible for message; technicians (printers) should be responsible for how the message is delivered, that is, the media.

BOTTOM LINE

  • An Intranet is a Communication Project, NOT a Technology Project.
  • First Question/Last Question: What Services for People will the Intranet Provide?

    < Table of Contents


    Browsers>


    To purchase or find out more about The Elements of Intranet Style go to fatbrain.com  or  Communications Associates.

  • The Authors

    Eric Brown founded his consulting firm Communication Associates in 1980. His clients include major Fortune 500 companies who use his presentation design, communication training, writing services, and web expertise in many contexts. He is author of Throw Away Your Pencil: Writing with a Word Processor (Prentice-Hall), of The FedEx Personnel Division Intranet Style Book, is a Houghton Mifflin Finalist, a writer for Hearst publications, and many professional journals .

    James W. Candler
    s currently Vice President of Personnel Systems and Support at Federal Express where he has worked for the last 18 years. In that time he has been responsible for the design, development, and maintenance of the company's on-line, reql-time human resource information system called PRISM. PRISM has resulted in all employees being able to access personal, benefit, and similar HR information at the stroke of a key. Most recently he has led the development of Personnel.link, the FedEx Personnel Division corporate Intranet.He has presented across the nation and written frequently for IHRIM.link: A Publication of the Association of Human System Professionals where he has also served as editor.



    [print version of this page]

    Of Interest
    · Modern Daze
    An empathetic, sympathetic and all around hilarious take on today's technology oriented workplace.