Getting Started with Graphics for an Enriching User Experience

Good web design does not necessarily mean good use of colors and layouts, but it does transcend beyond it. Design elements like color, font, size, frame, etc. play an important role nonetheless, but what is more important is that how it affects the aesthetic sensibilities of the users. The warmth and the feel of the web site, or in another words, the texture of the web site is a crucial area to turn our attention to. By texture of the web site what it means is the subtleties of the surface of the web site. Varied aspects as discussed in this article, when sensibly used -- and in combination with good deign skills aimed at creating intuitive appeal -- are of definite help of when it comes to developing engaging graphics on your web site.

Rahbre Azam. Amateur Writerz (2008). Articles>User Experience>Technical Writing>Graphic Design

The Sacred Cow Blocking the Road

When product teams ask technical writers to document software products, writers usually start their projects by analyzing the tasks users will perform when working with them. A task analysis generates a list of procedures—plus the supporting information users need to follow them—and eventually results in a document in which sequentially numbered instructions are the dominant type of information—neatly organized under user-centered task headings and preceded by enabling knowledge. It sounds ideal, classical even. The problem? Users don’t read procedures.

Hughes, Michael A. UXmatters (2007). Articles>User Experience>Documentation>Technical Writing

From Technical Writer to User Engagement Specialist?

Products and tools must evolve to ensure that user experience does not suffer as technical writers evolve their delivery to suit this modern age. If a user has a question, there should be only one place to search, and those results should contain relevant hits from all possible content sources.

LugIron Software Blog (2009). Articles>Writing>Technical Writing>User Experience

Growing Happy Users -- One Customer at a Time

Technical writing is a profession in transition. The way companies think of, use, and manage the people who help users make sense of and use products is absolutely changing. A lot of companies have started to use the term “information developer” to describe their technical writing positions. I don’t really care what label the profession chooses for itself, but I do know this: if technical writers don’t transition more than their job title then they will be missing out on a huge opportunity to move from the “gotta do it” category into the “can’t live without it” one.

Stern, Paula. LugIron Software Blog (2009). Articles>User Centered Design>User Experience>Technical Writing

Does Your Documentation Suck?

I’ve been browsing a lot of online documentation lately and in a past life I spent an enormous amount of time worrying about how my users were interacting with documentation. It never ceases to amaze me how bad most product documentation is, especially when the documentation is published in a half-measured attempt on the web. Do companies not realize the negative effect poor documentation, both content and presentation, have on their users?

LugIron Software Blog (2009). Articles>Documentation>Technical Writing>User Experience

Moving into User Research: Establishing Design Guidelines

The best technical writers do user research to understand the audience for their documentation, create user profiles or personas, perform task analyses, and do usability testing to ensure that their documentation meets users’ needs. All of these are activities in which a user researcher engages. Thus, as a technical writer, you can start amassing experience in user research and building a portfolio of user research documentation.

Six, Janet M. UXmatters (2009). Articles>User Experience>Research>Technical Writing

Why Technical Communicators Should Help with Product Text

A huge problem for projects is the lack of a common language between the developers and the users. When my colleague and I were preparing a presentation for an internal conference on this subject, he said something that has stuck with me. He said, “The goal of the project is to make the user successful.” I added to that: It’s not to write code or validate code. It’s not even to ship a product or make money (of course, this last one is especially true in a non-profit organization). At least, it shouldn’t be these things.

Minson, Benjamin. Gryphon Mountain (2009). Articles>TC>Technical Writing>User Experience