The PIM selection team: roles, time and a RACI matrix

Who belongs on a PIM selection team?

A PIM selection team needs three leadership roles and four to five functional members, with procurement joining from week 6. The core team usually holds five to seven people (PIMvendors estimate). Larger teams slow decisions, and smaller teams miss requirements. The team is in place by the end of week 2 of the 12-week PIM selection process.

Not every company has each role as a separate person. A mid-market brand may combine e-commerce and marketing. A medical device manufacturer may add a regulatory affairs specialist. Keep the functions even when the people overlap.

What does each role decide?

Each role decides within its area and contributes evidence to the final decision, which belongs to the sponsor. Clear decision rights stop the loudest voice from winning.

The sponsor approves the goals, the budget range and the final recommendation. The sponsor also removes blockers, such as a department that will not release time.

The selection lead decides how the process runs: the plan, the scoring rules, which vendors receive the RFP and how disputes are settled. The lead is the single point of contact for vendors.

The product data owner decides the data model. That includes product families, attribute groups, attribute owners and which system masters each attribute. This is the most important role in the first four weeks, and the reason most failed selections fail, as described in why PIM selections fail.

Functional members own the requirements and scenarios in their area, and they score those scenarios in the demos. IT owns architecture and integration fit. Procurement and legal own the commercial process and the contract.

What does the RACI matrix for a PIM selection look like?

The RACI below assigns one accountable role to each of 12 selection activities, with the business accountable for content and IT for architecture. Copy it and adjust the roles to your organisation.

R = responsible, A = accountable, C = consulted, I = informed.

Each row has exactly one A. When two people believe they are accountable for the same row, settle it in week 1. The sponsor holds the A for the final decision, but the decision rests on the evidence produced by every other row.

How much time does each role need?

The core team needs about one day per week over 12 weeks, and the selection lead and product data owner need two to three. Peaks fall in weeks 3 to 4 for requirements and data model, and weeks 8 to 9 for the demos.

These are PIMvendors estimates from typical engagements. Teams with a validated data model need less in weeks 3 and 4. Teams with several business units need more.

Protect the time in calendars before week 1. The scenario demos need every scorer in the room for half a day per vendor, and missing scorers weaken the comparison. Selection teams that treat the work as a side task run out of capacity in week 8.

When should you bring in external help?

Bring in external help when the team lacks selection experience, market knowledge or a neutral voice in a politically sensitive choice. The team still owns the decision, and external support adds method, market knowledge and neutrality.

Three situations justify outside support. The team has never run a software selection of this size. The market is unfamiliar, with 250+ PIM systems to consider and no time to research them. Or stakeholders already favour different vendors, and a neutral process owner is needed to keep the comparison fair.

Check independence before you hire anyone. Ask whether the adviser receives margins, referral fees or other incentives from any vendor on your longlist, and ask for the answer in writing. An implementation partner that also advises on vendor choice has a conflict of interest worth naming.

PIMvendors runs full selections and shortlist-only engagements, and in 2025 it supported 15+ companies through one of the two. Its vendor records carry no sponsorship or partner-tier field, which keeps the advice neutral by design.

How do you keep the team aligned for 12 weeks?

Keep the team aligned with a fixed weekly rhythm, a decision log and a sponsor checkpoint at the end of each block. Alignment fails slowly, so the rhythm matters more than any single meeting.

Run a 45-minute weekly team meeting with three standing items: progress against plan, open decisions and risks. Record every decision in a log with the date, the owner and the reason. The log becomes the backbone of the board-ready recommendation in week 12.

Hold sponsor checkpoints at three points: end of week 4 (requirements and data model signed off), end of week 9 (scenario results) and week 12 (decision). Each checkpoint asks the sponsor to confirm direction before the next block starts.

Keep stakeholders outside the core team informed with a short update every two weeks. People who feel excluded tend to reopen decisions late. The stakeholder alignment page covers the wider organisation.