All Posts

8 Steps to PIM readiness - are you prepared make the jump?

There are many famous quotes that tell you to “Just Do It” (Nike Slogan), “Start before you’re ready. Don’t prepare, begin.” (Mel Robbins*) or “The Key to success is to start before you are ready” (Marie Forleo). While I agree with these people for self-help/motivation purposes, their advice doesn’t directly apply to an enterprise level PIM project.

The quotes in my opinion that directly apply to an enterprise level PIM project are a little more conservative. According to Alexander Graham Bell “Before anything else, preparation is the key to success.”  And my favorite, which has a mysterious origin, “By failing to prepare you are preparing to fail."

Some PIM vendors have what they call a PIM Readiness Assessment (see an example here). While this is a good start, these readiness assessments are meant to qualify whether or not you’re a good candidate for PIM. If you’re reading this, you probably already know that you need a PIM. This article is here to help you determine if your company is ready to implement a PIM.

There are eight readiness factors to consider before you implement a PIM.

1. Your Roadmap

You need to build a roadmap, a diagram that details what the to be future will look like and how to get there. Many times, a PIM project is an essential a building block for other projects, typically e-Commerce, print catalogs or sending data to downstream channels. The roadmap should diagram what systems and technologies will be in play and the timeline for when you will get there.

eis-roadmap-example

The purpose of the roadmap is to make sure you have a plan that will be needed for the journey. For instance, if the ultimate goal is to have an B2B ecommerce website with customizable products and complex pricing, the high-level components of your architecture will need to change. You would possibly need a pricing engine (for promotional / qty based /contract pricing). You could also need a CPQ (Configure, Price and Quote) engine for help with the customizable products. You could also need a logistics/warehouse application to help with delivery. These are things that a PIM doesn’t do, but could be needed in order to do the e-Commerce initiatives.

2. Requirements

All projects have requirements, but they need to be defined early in the process. They need to be defined before you do your PIM vendor selection. Requirements are key for proper PIM software selection and for determining the Gap Analysis.

eis-pim-requirements-example

3. Gap Analysis

Gap analysis is done at multiple stages in the project, one is needed for the high-level roadmap to make sure the high-level requirements are met. The roadmap shows all the systems which are in play. The gap analysis is used to make sure the high-level requirements are met by the roadmap. An additional gap analysis is done specifically for the PIM requirements during PIM Vendor Selection.

4. Data Flows & Integrations

When implementing a PIM, it is important to know which systems will need to be integrated and how (i.e. flat file, XML, or API). Here, we are trying to determine the system of record for each data piece, which system(s) the users will be updating data in, and ultimately how the data flows to/from each system.

5. Processes

Do you know all the datapoints and processes for a new product creation? How about retiring a product? These are all things that need to be thought about early (they do not need to be implemented early, but at least thought about). Not all PIM systems are created equal in terms of workflows and processes. Plan out your process flows and requirements before you dive in, make sure the PIM system is strong in these areas if that is important to your project.

6. Data Model / Taxonomy / Schema

While Taxonomy can be implemented anytime within most PIM systems, do not underestimate the time and effort that is required to design the taxonomy. For those of you who don’t know, taxonomy in this context is a hierarchy or categorization of products for the purposes of attribution, aka schema. This means when you classify a product into the “Pen” category it would inherit several attributes (or specifications) for instance “Ink Color”.

Additionally, you will need to start thinking about the data model or the global attributes that your products will share. For example, all SKUs (items) belong to a family (product) and we need the marketing information to belong to the family and the weights and dimensions to belong to the SKU. Again, not all PIMs are equal and handle this differently. Know your needs before you select your PIM.

Read more about the importance of taxonomy and attributes

7. Software Selection

Probably one of the most daunting and crucial steps in the PIM journey is the actual PIM sendor selection. This is really its own entire topic and you can read more on it in "How to pick the right PIM software for your ecommerce business." We can help you select the right PIM vendor for your needs. See PIM Vendor Selection to learn more.

8. Implementation Partner

Possibly just as important as the PIM software selection, is choosing a PIM implementation partner, sometimes referred to as a Systems Integrator or SI. There are plenty of SIs out there, again not all are equal.

I can’t tell you how many “Rescue Operations” that my team has overseen in the past. These typically don’t have anything to do with the software that was selected. It has to do with the implementation partner. Experience is key. Just because your implementation partner is good at one thing, doesn’t necessarily make them good at implementing PIM. Additionally, just because they are good at one PIM doesn’t make them good at another PIM. While there are definitely some “common” best practices when implementing PIM, there are also software specific best practices and gotchas.  Make sure your implementation partner has proper training and the team that will actually be on the project also has the training. Get the teams' Resumes/CVs.

To me everything starts with preparation and not jumping into the deep end before you know how to swim. One thing is always true, “You don’t know what you don’t know.” That being said, start learning to swim now.

You don’t start to build your house before you have a blueprint (you need to know local ordinance, building codes, the right materials for the location). Same could be said for PIM. You need to do a PIM Readiness assessment. So when I read “The Key to success is to start before you are ready”, what I hear in my head is “... start the process of PIM Readiness Assessment before you are ready to do the readiness assessment”, however that doesn’t quite flow off the tongue.

Our team of product information experts are ready to help get ready for PIM.  Give us a shout to see how we can get you started.


* Robbins, Mel. The 5 Second Rule: Transform Your Life, Work, and Confidence with Everyday Courage.  Post Hill Press, 2017

Recent Posts

[Earley AI Podcast] Episode 26: Daniel Faggella

Human Cognitive Science Guest: Daniel Faggella

[RECORDED] Master Data Management & Personalization: Building the Data Infrastructure to Support Orchestration

The Increasing Criticality of MDM for Personalization for Customers and Employees Master data management seems to be one of those perennial, evergreen programs that organizations continue to struggle with. Every couple of years people say, “we're going to get a handle on our master data” and then spend hundreds of thousands to millions and tens of millions of dollars working toward a solution. The challenge is that many of these solutions are not really getting to the root cause of the problem.  They start with technology and begin by looking at specific data elements rather than looking at the business concepts that are important to the organization. MDM programs are also difficult to anchor on a specific business value proposition such as improving the top line. Many initiatives are so deep in the weeds and so far upstream that executives lose interest and they lose faith in the business value that the project promises. Meanwhile frustrated data analysts, data architects and technology organizations feel cut off at the knees because they can't get the funding, support and attention that they need to be successful. We've seen this time after time and until senior executives recognize the value and envision where the organization can go with control over its data across domains, this will continue to happen over and over again. Executives all nod their heads and say “Yes! Data is important, really important!” But when they see the price tag they say, “Whoa hold on there, it's not that important”. Well, actually, it is that important. We can't forget that under all of the systems, processes and shiny new technologies such as artificial intelligence and machine learning lies data. And that data is more important than the algorithm. If you have bad data your AI is not going to be able to fix it. Yes there are data remediation applications and there are mechanisms to harmonize or normalize certain data elements. But looking at this holistically requires human judgment: understanding business processes, understanding data flows, understanding dependencies and understanding of the entire customer experience ecosystem and the role of upstream tools, technologies and processes that enable that customer experience. Until we take that holistic approach and connect it to business value these things are not going to get the time, attention and resources that they need. In our next webinar on March 15th, we're going to take another look at helping organizations connect master data to the Holy Grail of personalized experience. This is an opportunity to bring your executives to a webinar that will show them how these dots are connected and how to achieve significant and measurable business value. We will show the connection between the data, the process that the data supports, business outcomes and the and the organizational strategy. We will show how each of the domains that need to be managed and organized to enable large scale orchestration of the customer and the employee experience. Please join us on March 15th and share with your colleagues - especially with your leadership. This is critically important to the future of the organization and getting on the right track has to begin today.

[Earley AI Podcast] Episode 25: Michelle Zhou

Data Tells the Story Guest: Michelle Zhou