This article proposes a document-driven approach to analysis of system requirements. The objective of this approach is to establish better ways of communicating with novice users. We have based our research on two principles: 'connecting to what is known' and 'shifting between abstractions and concretions.' The former principle means that existing familiar documents have been used as a starting point. The latter principle refers to relating the abstractions made in the system development process to something that is concrete to the user. Our document-driven approach was implemented in a case study discussed in the article. Our approach resulted in improved conditions for communication between users, in conceptual improvements, and in process improvements.