Supporting how people do things

Just a few thoughts on the design of documentation. In my last blog I have introduced the idea of using a more goal-driven approach in documentation. To achieve a goal the user needs to perform activities, make decisions, choose from options and learn about something about the functionality of the product.

This approach might sound new, but it's origin goes back to the basics of user-centered design, as described by Donald Norman in his brilliant book "The Design of Everyday Things" (1988).

In his book, Norman describes how people do things with The Seven Stages of Action:
  1. Forming a goal, for example: I want to watch a movie on my television
  2. Forming the intention, for example: I will turn on the DVD Player and the television
  3. Specifying an action: I will pick up the remote control and turn the DVD Player and television on
  4. Executing the action: Attempting to do the action
  5. Perceiving the state of the world: I look at the television screen
  6. Interpreting the state of the world: Can I see the movie on my television screen?
  7. Evaluating the outcome: If I can see the movie, I have succeeded. If I can't see the movie, I have to perform another action.

From goal-driven to process-driven

When we look at this 7 steps, we can quite easily plot the role of documentation in it.


So what we try to achieve with our documentation is merely supporting users in reaching their goals. And what would be more natural than describing the activities they have to do and help them interpreting their context. A process-driven approach, describing every action within its context, would be ideal from this point of view. It would be the first step in creating smart user-centric documentation, that takes individual users by the hand and guides them towards their individual goals within their context.

However, to make this work we have to abandon our traditional print-oriented documentation approach and create smart documentation that guides individual users through the maze of actions, decisions and choices they have to make. Semantic technology gives us the tools and methods to create this smarter, user-centered type of documentation.

Follow me on my way to Atlanta

This process-driven approach to documentation is the central theme in my presentation at the STC Summit 2013 in Atlanta. During this session I will demonstrate how we can embed instructions in a process and make them actionable by using semantic technology.
  

STC Summit 2013

The STC Summit 2013 is probably the world's largest and most influential conference for everyone working in the area of technical communication. The Summit is packed with more than 80 sessions over the three full workdays with topics covering all aspects of technical writing, editing, project management, and publication production. It takes place 5-8 May in Atlanta, Georgia.

A preliminary overview of the sessions can be found on:
http://summit.stc.org/program-info/program-overview/

Follow me on Twitter 

Make sure to follow @beinformedcom, @cvanmansom and @millsdavis. 

#effectiveinformation
Tweets related to making information accessible by using semantic technologies 

#stc13
All information related to the STC Summit 2013






Comments

Post a Comment

Popular posts from this blog

Using the Golden Circle Model in your resume and LinkedIn profile

Image
The last three years I worked as a (senior) business consultant and information architect at software company Be Informed in Apeldoorn, the Netherlands. We worked on an amazing product, a ground breaking model-driven business process platform. And my job was to explain the possibilities of this platform to various audiences. The Be Free program, which I launched in September 2013 was a marketing campaign that targeted on making a wider group of people familiar with the product. The campaign was a great success and I had the feeling that I was really helping people in proving their ideas to their customers and managers. But the interaction was on-line and from a distance, never close enough to really understand their business goals and issues.  The sudden end of my contract with Be Informed, forced me to rethink my professional goals and ambitions. What do I really want? Do I want to be a product marketer, focused on 'pushing' a product? Or do I want to be a business cons
Read more

Improve Product and Brand engagement through smart documentation - A White Paper about the challenge of creating user-centric documentation

Image
For most product manufacturers, delivering adequate documentation is a constant challenge. The increasing complexity of products and the stricter regulations for product documentation often lead to extensive documentation sets with 500+ pages manuals on-line or in print. The question is: how effective is all this documentation? Smart, user-centric documentation Users can be overwhelmed by long, jargon-loaded user manuals, and frustrated by a lack of clear answers. When customers don’t find a solution, blame inevitably falls on the product and the company. Bad documentation - incomplete, unclear, out of date - creates a negative engagement with products and brands. Figure 1. Smarter documentation asks users what they need to know Smart documentation leads users to success and satisfaction. These are the users who share their positive experience with family and friends, and convince them to become customers in turn. Using semantic technology, we can create the smart document
Read more

Laying the foundation for an effective article

Image
In this series of articles you can follow my process in writing a new article on Robotics. In the  first episode  I explained my approach towards writing, the  second article  focussed on setting the goal, choosing an audience and finding the right approach. Now that we have a clear vision on goal, audience and approach, it is time to start setting up the structure. Writing requires a structured approach Writing is all about structuring your thoughts. And although this is a process that most of us do in a more implicit way, it sometimes helps - and is actually best practice - to write down your structure on a very high level. The goal of my article is to change the opinion of the reader towards accepting Robotics as a something that brings value to a business and motivates employees, rather than being limited to reducing FTE. So the structure of my article should be build up around the motives used to build up this case. As I want my article to be short and sharp, I don't
Read more