Can anyone share experience or advice when it comes to building and/or operating a successful product information management (PIM) practice? Guidance on everything people, process, technologies is all appreciated.

2.1k views3 Comments

CIO in Manufacturing, 501 - 1,000 employees
People: define the proper governance or accountability in the different phases of the product lifecycle. Typical "ERP" master data team and Marketing-Sales-PIM Team are the more relevants. 

Process: A Project Manager with proper cross-department leadership, ERP architects and keyusers to streamline and cleansing of data are "a must". Workflow definition for internal PIM data population and governance, as well as external sindication to digital platforms (digital catalog, Amazon, etc), are the main processes to setup

Technology: Easy-to-use, workflow internal and external with your suppliers for product-data-sheets, good data-model support and integration capabilities internal (ERP, etc) and external (sindication with most popular platforms) might be some of the top topics
Director in Manufacturing, 1,001 - 5,000 employees
Ownership of the project needs to be with the business. While IT implements the tool (building the hammer, nails, buying the boards) the business needs to own building the data and maintaining it. If the business expects to hand data to IT and IT to upload content and maintain it you are likely going to fail after initial load. We used multiple different tools so no particular recommendations

Our struggles were always with Marketing properly managing the data content
CEO in Services (non-Government), Self-employed
A business leader/business ownership is required. Preferably someone who also understands Industry 4.0 which is an optimization strategy not a technology strategy and will be able to connect the dots between value that can be derived from the PIM across business units, from engineering to sales and between IT and OT.    Consider Propel Software's PIM for its ease of integration.

Content you might like

CTO in Software, 201 - 500 employees
Without a doubt - Technical Debt! It's a ball and chain that creates an ever increasing drag on any organization, stifles innovation, and prevents transformation.
Read More Comments
40.7k views131 Upvotes319 Comments

Limited environment/Infrastructure resources31%

Inability to quickly identify the root cause of CI/CD pipeline failures45%

Lack of standardized CI/CD pipeline templates across the organization53%

Integrating security tools - inefficient security implementation leading to false positives38%

Poor communication across business and product teams/coordination challenges26%

Cost/resource management26%

Implementation of CI/CD into on-going projects and workflows22%

Internal resistance: training issues, culture, etc.14%

Inefficient implementation of CI/CD due to lack of expertise, poor training, etc.19%

Poorly written unit and acceptance testing9%



We are not doing regression testing10%

25% manual, 75% automated50%

50% manual, 50% automated27%

100% manual, 0% automated8%

Don't know2%


1.6k views3 Upvotes2 Comments