Organizational memory information systems have a diversity of contents and may need a variety of information technologies. To cope with this diversity, OMIS requires specific development methodological guidelines. First the OMIS’s objectives have to be stated in organizational functional requirements. Second, the conceptual OMIS model has to be defined at a high level in terms of organizational memory subsystems, and a diversity of modelling techniques are required to develop these subsystems. An OMIS also may profit more from a description of its technological and organizational infrastructure than from a business-led architecture definition. An OMIS needs clear role definitions of its stakeholders, an organizational (improvisational) change scenario, and a non-linear systems procurement scenario. Much of OMIS development happens in its use-stage. Consequently OMIS development has to cope with high levels of complexity, diversity and organizational and IT developments. Several suggestions for further research complete the paper.