Tag techcomm

The Evolution Of User Manuals – Forbes.com

Documentation, once siloed in the realm of how-to guides, is actually feeding
top-of-the-funnel activity. In fact, some companies that I have spoken to are
reporting that their documentation is bringing in over 50% of their qualified
leads.

This article (from the ad-busy Forbes) speaks generously to user documentation’s benefits to both sales and support. Backed up with new data.

8 Major Trends That Will Change ECM in the Coming Years – Digital Landfill

Enterprise content management is already composed of a complex, broad set of ideas and technologies – over the next 5 years, a convergence of trends across multiple software categories will have a massive impact on this space.

Aaron Levie outlines the trends that will most impact the direction of the ECM market. These include the efficiencies of cloud computing, mobile productivity, expanded definitions of “content”, the integration potential of open API’s, ever more powerful search capability, increased collaboration functionality, social-ready features (and their contribution to folksonomy, I would think), and intelligent data mining.

The case against links

http://ping.fm/M8c8s

Jakob Nielsen says Sharepoint won’t nec’ly kill designs …but they’ll surely need even more user experience work

http://ping.fm/zdzsI

Weinberger, “Bringing on the info overload: | KMWorld

When information overload started off, it created the same sorts of difficulties as sensory overload: Info overload was a psychological syndrome in which we lose our ability to act rationally…But that’s not how we think about information overload now, even though the amount of information far outstrips what Toffler feared would unhinge us…

We now think of information overload as a social issue, not a psychological one. We do not worry about losing our minds so much as not being able to find the information we need.

This is a remarkable story of adaptation. What we thought as a predicament that would destroy our ability to make rational decisions and might even drive us mad has now become simply our environment. It’s where we live. Rather than fleeing from the overload of information, our concern is that we’re not getting enough of it. We have adapted well.

Resignation straddling the glee of Shirky and the cynicism of Carr.

Discovery Is The New Cocaine—Going Beyond Engagement

The deck I’ve needed for some time—and it’s 11 months old as of this writing. Herein is a McLuhan-esque guide to a sophisticated complicity (addiction’s not the word, if you ask me).

Eyeball kicks abound.

The Growing Need for Terminology Management

I continually marvel at just how intrusive ‘luck following the prepared’ can be. I’m trying to work over here! Anyway, just in time to fortify my current research diet into Content Strategy, in Whaddya Call It?, Don DePalma makes valid arguments around the justification for a more focused approach to what we call things:

The question of correct and consistent terminology is one that should command the attention of a company across its product lines and within the industry where it operates. Simply stated, terminology management concerns the terms that represent the system of concepts of a particular company, industry, science, art, government, or even social entity like a family unit.

DePalma’s ideas are equally as valid as other less easily-digestible fare, and they reinforce many of the discussions I’ve been having internally around the need for a controlled vocabulary at my company. Certainly, any kind of technological innovation we implement for document and content management will rely on a search system that has the flexibility to translate disparate terms into valid searches across the board. But socialization of a controlled vocabulary would go a long way toward sparing us those conversations we overhear in the hallways that typically include on or about the 4-minute mark, “Yeah, yeah, same thing… Tomato, Tomahto…”

“About Us” Information on Websites

Jakob Nielsen’s Alertbox reports finding “a 9 percent improvement in the usability of ‘About Us’ information on Websites over the past five years, but companies and organizations are largely still unable to explain what they do in a single paragraph.”

An accurate representation of a company or organization on the Internet is one of a Website’s most important tasks, as effectively explaining the company’s purpose and what it stands for provides support for all of the Website’s other goals.

The Alertbox suggests providing About Us information at four levels of detail.

  • First, a tagline on the homepage, just a few words or brief sentence, should summarize what the organization does.
  • Second, a one- to two-paragraph summary at the top of the main About Us page should offer more detail about the organization’s goals and main accomplishments.
  • Third, a fact sheet following the summary should elaborate on key points and other essential facts about the organization.
  • Fourth, subsidiary pages with greater depth should provide more detailed information for people looking for more about the organization.

Such a layered approach creates an inverted pyramid that uses hypertext to shield users from overwhelming details, while simultaneously providing specific information for those who want it.

The Forms of Content & the Modular Document

Each day, a typical Sales organization produces and distributes to its customers and prospects a wealth of information in the form of e-mails, standard marketing collateral, and customized selling documents. But rarely is Sales the actual producer of the information it uses.

Instead, multiple individuals and departments are responsible for producing critical sales information—and more often than not, in the form of a document. Producing a customized deliverable in response to a customer request is often an exercise in hunting down source materials, copying and pasting relevant points into a new document, then cleaning the whole thing up: a burdensome task in terms of time, quite often beyond the reaches of the typical salesperson’s desktop publishing skills, and consistently inconsistent.

While speaking specifically to technical communicators, Mott and Ford (Managing Objects…)(Creating Objects…) echo the perspective common in information architecture circles around information granularity and portability:

To deal most effectively with information tools over the course of the next generation, technical communicators know they must break out of the genre-motivated concept of communication. Instead of focusing on end-products—the traditional deliverables of brochure, annual report, user manual, or Web site—technical communication professionals must now manage, create, and present pliant chunks of information that will be integrated into a wide variety of communication products.

Thus, a hierarchy of object levels emerges. At the Highest level, you have large objects such as letters and quotes. At an Intermediate level, you have components objects such as paragraphs and illustration.  At the Lowest level, you have the objects inside those objects, such as product names, prices, and individual company or contact names.NestedInfoObjects_gif

When viewed as modular dynamic objects rather than frozen, maintenance-intensive end products, every stakeholder on the content lifecycle continuum—from creator to end user—can benefit from robust customization of deliverables and single-sourced (rather than redundant and fallible) content maintenance routines.

Writing self-contained chunks of information requires the ability to write modularly and to ensure that the language used will be appropriate for various audiences, genres, and purposes. One distinct advantage is that the same text base can serve multiple audiences and multiple purposes for reading. When texts are composed in screen-size chunks, the same modular text fragments can be used to build different documents or different paths through a document.

An argument against single-sourcing content objects is that “mass produced” document deliverables will lack cohesiveness, will not flow for the reader, will resemble an RFP with the question prompts removed. In response, one need only step inside a well-apportioned modular home. Add the customization of furnishings and personal effects, and each becomes uniquely identified with the needs of the occupant.

That significant cost was removed from the home’s construction is a non-issue to the homeowner—but a market differentiator for the builder, who can service more customers in less time at less cost.

A modular selling document, by the same token, is a starting point—featuring components selected by its creator for an intended audience. Furnish with opportunity-specific talking points, company specifics, and individualized messaging, and the modular document is indistinguishable from one created from scratch. Development times for larger documents go from days to hours. Shorter documents take only minutes.

The salesperson now has the power to incubate targeted prospects to the next level of opportunity, and can leverage time savings in servicing more pressing deals.

Reblog this post [with Zemanta]

Joe Lamantia on The Challenge of Dashboards and Portals

Over at Boxes and Arrows, there’s a thorough-going series underway concerning the building blocks approach to portal building. Offering “standardization, modularity, and interoperability,” Lamantia speaks to the freedom designers have with this approach to individualize the dashboard experience. Richly illustrated and annotated, this is one to watch.