In “Document Engineering: Analyzing and Designing Documents for Business Informatics and Web Services”, Robert Glushko and Tim McGrath write, “Practitioners of document engineering will most likely come from other disciplines from which document engineering was synthesized. The principles of document engineering seek to find a balance between technology and business, between process and information, between bottom-up and top-down thinking, and between concepts and implementation. Successful documents engineers,” the authors say, “will do the same.” Read my recent book review in the July 2006 The Rockley Bulletin. Then, put on your headphones an listen to Jon Udell’s interview with Robert Glushko. If you’re ready for a career in document engeering, you’ll soon find yourself purchasing the book.
About The Author
Known affectionately as "The Content Wrangler," Scott Abel is an internationally recognized global content strategist who specializes in helping organizations deliver the right content to the right audience, anywhere, anytime, and on any device. He writes regularly for business and content industry publications, is frequently selected as a featured presenter at content industry events, and served on the faculty of the University of California, Berkeley, School of Information. Scott's message is clear: Content is a business asset worth managing efficiently and effectively. His firm, The Content Wrangler, exists to help content-heavy organizations adopt the tools, technologies, and techniques they need to connect content to customers.
January 29, 2007
December 29, 2006
Receive exclusive access to members-only content, invitations to in-person and virtual events, and sneak peeks at new tools and emerging technologies. Join today!Join Now!
- How to fuel creativity in the workplace
- WHAT STORYTELLING MEANS TO VOICE AND TONE STRATEGY
- Viewpoint: Patient-focused Healthcare Information Requires an Omnichannel Content Strategy
- Viewpoint: The Disconnect Between Content Strategy, Information Science, and Healthcare
- The Need for Plain Language in “Terms and Conditions”