Technical writing/Strategies

User Involvement
The perils inherent in ignoring users while developing a product are as obvious as they are prevalent. Only a very few software projects consciously involve end users throughout the whole process. So almost every project is plagued with misunderstandings, slow communications, unclear requirements, and unrealistic expectations.

Yet, most often the developers get together in a room with a white board and cobble together bits of structure, hoping to support functions, that may or may not be of value to the users.

So what can we do about it?

If we look at the Systems Development Lifecycle, we can see that User Goals ought to be our focus:



The key processes always have to start with the User. How could it be otherwise?


 * For the process to begin the cycle with Structure leads to obvious problems of incompatibility.


 * Starting from Functions, you'll do a bit better. But because you've not really taken the time and effort to know the Users' Goals, meeting their approval is at best a fifty-fifty bet.


 * Starting from the User makes much more sense. By keeping the focus on the important Goals, you can be certain that what you produce will actually be used.

It's not enough only to start with the User, you must ensure that you remain in nearly constant contact with your User, always verifying that the Functions and Structures you make into a Product will meet your Users' Goals.

Online Literature Review Excerpts and Commentary
Note: This section is under development and welcomes assistance in commenting on the findings of the studies. Additional studies and commentaries are always welcome.

Source: Helping and Hindering User Involvement - A Tale of Everyday Design

Stephanie Wilson, Mathilde Bekker, Peter Johnson and Hilary Johnson HCI Group, Department of Computer Science Queen Mary and Westfield College

Commentary:

Source: | USER INVOLVEMENT AND ENTREPRENEURIAL ACTION

Eva Heiskanen and Petteri Repo National Consumer Research Centre Helsinki, Finland

Commentary:

The technical writings is very good work stalin_singh@infosys.com

Clear Statement of Requirements
Writing Clear Requirements is a skill that you must practise and build up over time.