{"id":1954,"date":"2023-01-31T11:06:17","date_gmt":"2023-01-31T09:06:17","guid":{"rendered":"https:\/\/dam-evangelist.blog\/?p=1954"},"modified":"2023-02-03T14:19:20","modified_gmt":"2023-02-03T12:19:20","slug":"dam-pim-einfuehrung-mit-diesen-fuenf-fehlern-werden-sie-scheitern","status":"publish","type":"post","link":"https:\/\/dam-evangelist.blog\/en\/2023\/01\/31\/dam-pim-einfuehrung-mit-diesen-fuenf-fehlern-werden-sie-scheitern\/","title":{"rendered":"DAM & PIM introduction: You will fail with these five mistakes!"},"content":{"rendered":"\"\"<\/a>\n

I have written numerous articles on how to be successful when implementing a DAM and\/or PIM system.
\nToday I will show you five significant mistakes you will fail with:<\/p>\n

    \n

    \n
  1. The business case or goal is not defined!<\/li>\n<\/h4>\n

    This is the classic mistake at the beginning of a project:
    \nThe system evaluation is started without having a clearly defined business case and goal beforehand.
    \nOne believes to know with absolute certainty which functions the new system “must” have, but has not considered and defined the big picture in advance.
    \nWithout a clearly formulated goal and a business case that one wants to fulfil, the software introduction is pointless and will fail!<\/p>\n

    \n
  2. The system is supposed to be brand new and modern, but the processes are not!<\/li>\n<\/h4>\n

    Another classic! If the business processes are not efficient, then no PIM or DAM system will help! I encounter this problem especially in the area of PIM implementation.
    \nMany companies are under the misapprehension that a PIM will solve all their problems as if by itself. Of course, the frustration is then extremely great when you realise that this is not the case!<\/p>\n

    \n
  3. The change process is completely neglected!<\/li>\n<\/h4>\n

    My absolute “favourite topic”. With the introduction of a DAM\/PIM solution there will be changes. Changes that affect people. If they are not involved in this process, resistance will arise and overcoming this resistance is almost impossible!
    \nChange \u2013 This is how the entry succeeds!<\/a><\/p>\n

    \n
  4. The stakeholders are not sufficiently involved!<\/li>\n<\/h4>\n

    It is one thing to implement change together, it is another thing to actively involve the stakeholders in requirements engineering. Those who work with the system directly or indirectly must be involved in the selection process.
    \nIf this is not the case, the system will fail at the latest when it comes to achieving a positive return on investment after implementation.
    \n    In 3 steps to agile software selection \u2013 1. The stakeholders and their stories<\/a><\/p>\n

    \n
  5. Lack of resources and competences in the project team!<\/li>\n<\/h4>\n

    An employee becomes the product owner of the new DAM system. Of course, in addition to this new job, he or she must continue to do his or her previous daily business – no question about that!
    \nIn companies, it is generally underestimated that the role of the PO is a time-consuming task from the company side. Keeping a PO fully involved in the day-to-day business will have an extremely negative impact on the progress of the project.
    \nThe introduction of a PIM or DAM system should also be seen as an iterative project. Issues will arise during the project on which decisions have to be made.
    \nA lack of decision-making competences can delay the project or bring it to a standstill. It is therefore important that these competences are available in the team.\n<\/ol>\n

    You have questions\/ comments on this topic, or would like to arrange a free consultation:
    \n