| | JULY 20249CIOReview2. Internal Structure ­ this is the first thing you really need, but the last thing that the companies want to invest in. In a perfect scenario, there will be a team dedicated to the project, with a P.O. (Product Owner), a P.M. (Project Manager), and developers who will need to pass through a good understanding period to know details of the new platform, and after start helping the consulting team. Better than this, only by hiring a team with previous expertise. Another good possibility is to have the consulting team allocated inside your company working daily with the IT Team to draw the solutions and speed up the process.3. Key User - for each CX module, choose an expert that will be the person who will be the point of contact for the internal team to determine things like:a. Describing needs (in detail)b. Determination of the MVP (minimum viable product)c. Prioritizing the backlog4. Leadership ­ It needs to be clear to the company who will lead the platform implementation. In my opinion, the best results will be achieved if this leadership is inside the IT Area but building the project extremely close to the key users.5. ERP ­ is your ERP an SAP platform? Why is it important? Native communication between platforms is not a must, but it is recommended because it is easier to connect things and flow with the information, so if your company already has a SAP ERP, connecting CX SAP Platforms is supposed to be a good and simpler choice.These are the main points to get started. The closer your company reaches this ideal situation, which I pointed out above, the better the evolution and success of the project will be in the end. Some characteristics of the SAP systems include this huge brand's unique positioning inside clients' and users' minds, mixing lovers and haters
< Page 8 | Page 10 >