The authors discuss the information needs of developers in the early prototype phase, where the developer requires input that provides guidelines for the tryout revision cycle that cannot be satisfied by pre- and post-test data. When a develop-user relationship conducive to open communication allowed users to convey their perceptions and problems to developers, developers listened, interpreted, reformulated and re-presented the product to the user. The authors suggest that pilot testing of prototypes for adult users can be regarded within the framework of a two-way communication system. The communication model identifies barriers impeding the sending and receiving of messages, such as differences of role, expectation, and language. These barriers must be acknowledged and broken before the developer can obtain information critical to further development of the product. (Author)