Poor communication due to mind-set differences between technology developers and software users is cited as one reason why user requirements are not analyzed to the necessary level of detail and completeness, resulting in lower levels of usability. This book examines the apparent 'gap' between users and developers, particularly in relation to the gathering of user requirements. It considers an expanded role for the Technical Writer, and tests whether software can be made more usable by having the technical writer act as a facilitator between user and developer during requirements gathering. This book features an action research project in which the researcher works undercover as a technical writer on a commercial software development project. The statement of user requirements is developed from facilitated communication between software developers and users. The quality and usability of the resulting system is then evaluated. This book is valuable for technical writers seeking to add value to their services. It is also for students doing Action Research. Indeed, it is useful for anyone seeking practical ways to improve the software requirements process.