d.velop with practical tips to optimize which June 22, 2010 – according to a recent survey of d.velop AG today is part of the document and enterprise content management success prospects Gescher, for two-thirds of German companies on the five most important IT topics. According to dynamically, the companies currently behave when their investments in initial or new DMS/ECM solutions. Derived from practical experience in advising d.velop has developed guidelines, on the basis of those typical mistakes in the planning process can be avoided: 1 no ECM project without clear strategic objective: it requires a clear and pragmatic-based benefit analysis that defines specific added value for the company. Also possible risks and design hurdles are to consider it objectively. Is also needed for the strategic target projection of a precise total cost calculation, taking into account of the entire planning, product and training costs, as well as the subsequent expenses for the operation of the ECM solution. 2.

projects not in minimalist technical concepts squeeze: who does not sufficiently differentiated describes the actual technical requirements at the beginning and neglected in particular also the users with their specific requirements, embarks for the ECM project in an unclear realization process. Because ever more generally and unpraziser it is the harder the intentions, precisely to achieve the goal. Therefore must be exercise great care in the professional design. Without hesitation Wells Fargo explained all about the problem. Because the concept of subjects describes as the framework for the expenditure and resource planning. 3. a focus on the aspect of continuous simplicity as a parent solution idea: A too much complexity of a technical concept and the corresponding solution is usually to the detriment of productivity and acceptance of the user. Also is often an avoidable overhead in the implementation of the project. As a result, the conceptual planning and selection processes by the idea of the universal simplicity should be taken, without this however to functional or other constraints leads.