‭Information analysis strategies‬ I‭nformation analysis is the determination of the information needs at the time of developing the‬ ‭administrative information management system.‬ ‭ he way in which information needs can best be determined is situationally‬ T ‭determined. We therefore endorse a contingency approach when it comes to the‬ ‭c hoice of how the information analysis should take place. Davis and Olson have‬ ‭formulated four possible strategies and indicated when each strategy is best used.‬ ‭-‬ ‭W aiter strategy‬‭: Asking directly is a strategy in which the user of the information is‬ ‭ sked to define the need himself. This can be done, for example, during interviews‬ a ‭or with the help of questionnaires. Naturally, this strategy only has a chance of‬ ‭success if the user is able to define his requirements crystal clear and the‬ ‭information analyst can record these correctly. A manager generally does not know‬ ‭what his information needs are and this strategy is therefore often unusable. Low‬ ‭degree of uncertainty and risk.‬ ‭-‬ ‭Reference strategy‬‭: When there is a stable information system that can be‬ ‭ nalyzed and there is a relatively similar 'case', the possibility can become‬ a ‭c onsidered copying the useful elements or adapting them to their own situation.‬ ‭The comparability of the situation can be based on various (combinations of)‬ ‭variables, for example the primary process of the organization, the size or the‬ ‭structure of the organization. Toll typology. Average degree of uncertainty and‬ ‭risk.‬ ‭-‬ ‭Development strategy (designs)‬‭: the other strategy takes a more analytical approach.‬ ‭ ased on the most important characteristics of the organization, a translation is made‬ B ‭into the information needs. This presupposes the availability of thorough knowledge‬ ‭about the organization by both the user and the information analyst, or the ability and‬ ‭willingness to build up this knowledge. Spinning top model. Average degree of‬ ‭uncertainty and risk.‬ ‭-‬ ‭Evolutionary strategy‬‭or‬‭prototyping strategy (evolutionary development)‬‭: In‬ t‭hose situations where the user and information analyst are not able to determine‬ ‭the information need in advance (waiter strategy) and there is no clear reference‬ ‭available (reference strategy), two strategies remain. In the extreme casea 'trial and‬ ‭error' approach can be chosen. In that case, parts of the information system are‬ ‭realized step by step. The The user always evaluates whether the system provides‬ ‭relevant information and adjustments are made if necessary. High degree of‬ ‭uncertainty and risk.‬ ‭ structured approach to determining information needs always consists of the following‬ A ‭three phases:‬ ‭-‬ ‭To design:‬‭In addition to financial, internal information, managers also need‬ ‭non-financial, qualitative, external and future information. We use the toll model here,‬ ‭which is primarily in line with the aforementioned design strategy.‬ ‭-‬ ‭Selecting:‬‭Need to know versus nice to know, making qualitative requirements and wishes‬ ‭explicit, costs versus benefits.‬ ‭-‬ T ‭ o build; the infrastructure:‬‭first build a prototype with a simple application (for‬ ‭ xample a spreadsheet). Don't want to fully automate everything; this is at the‬ e ‭expense of flexibility. Manual work is often necessary to achieve lasting good‬ ‭results.‬