Working in PIM Project Management

Two minds, one goal, and a whole lot of teamwork

What does a typical day in PIM project management actually look like? In short: quite varied. Because it’s not just about systems and data - it’s about structuring complex requirements, bringing different perspectives together, and working collaboratively to bring projects to the finish line. To make this more tangible, we spoke with two colleagues from our team. Kevin and Alice both work in the PIM field at valantic DXA, but they bring different strengths to the table - and that’s exactly what makes working together so exciting.

Kevin describes his role as an interface between the client, technology, and strategy. Alice sees herself primarily as a translator between different requirements, stakeholders, and teams. Or, as she puts it herself:

“For me, a PIM project manager is like a friend who organizes a vacation for a whole bunch of friends and family.” She doesn’t fly the plane herself or cook for everyone - but she makes sure everyone arrives on time, everything fits together, and no one ends up in the wrong city.

Why PIM Project Management Is All About Teamwork

PIM projects bring together many disciplines. Structured product information, content, images, technical details, and documents all converge in a central infrastructure. That is precisely where the added value lies - and that is exactly why this field doesn’t work in isolation.

“I serve as the link between the client, technology, and strategy. My role is to translate complex requirements into structured processes and bring projects to a successful conclusion.”

“Only by working together can we ensure that all requirements are understood and that data is consistent and complete. No single person can understand all perspectives, systems, and processes on their own.”

What they both have in common: PIM project management is teamwork because it requires bringing together different perspectives. The client provides the goals, the development team handles the technical implementation, and project management brings the two together.

The Timeline Check: What a Typical Day Looks Like

A typical day doesn’t start with routine, but with prioritization.

Kevin: “I start with a coffee and a quick project check. What’s on the agenda today? What’s the priority today? What will actually move the project forward?”

Alice: “I always start the day by going through my emails and notifications so that important last-minute changes can be addressed immediately and I can react quickly.” Then it’s straight into coordination. Daily tasks, open issues, dependencies, new requirements. Always with the goal of keeping the project up to date and making decisions where they’re needed. Especially in PIM projects, things quickly get complex. Many projects start with legacy data landscapes, outdated logic, or inconsistently maintained Excel structures.

Alice: “We don’t start with a blank slate or from scratch, but rather with Excel spreadsheets from various departments or outdated systems. Then we have to decide: What still makes sense, what do we keep, and what do we clean up?”

Kevin: “The biggest challenge is usually reconciling the client’s expectations with IT or with the current IT systems in a way that yields a realistic baseline for the project.”

Things get particularly intense right before go-live. That’s when the pressure mounts, new issues arise, and one thing is needed above all else: clear communication, quick decisions, and structure.

Ping Pong Interview: A Glimpse into Everyday Project Life

When do you realize you’ve chosen exactly the right job?

Alice: “When we find a really good solution that not only works but is also really smart. Then I think: Okay, I love my job.”

Kevin: “When two projects went live at the same time and we received thank-you emails from both clients afterward—along with feedback on how much benefit it brought. That was definitely a cool moment.”

How do you keep track of things with complex data structures?

Alice: “The first step is always to create transparency. I try to make structures, dependencies, and stakeholders visible.”

Kevin: “You introduce structure early on. You create work packages, group areas together, and define clear steps. Once you write down a complex structure or visualize it, it often isn’t that complex anymore.”

What role does AI play in day-to-day project work?

Kevin: “I actually work with AI a lot. It has really drastically restructured my daily work. Speed is kind of the keyword.”
Kevin uses AI for analyses, documentation, ticket creation, spreadsheets, and conceptual work, among other things.

Alice: “AI is particularly good when you need to structure and formulate longer texts. It’s also a great source of ideas during the conceptual phase.”

At the same time, both are in complete agreement about where the limits lie.

Alice: “AI can help organize these uncertainties, but it can’t take on responsibility.”

Kevin: “Of course, AI doesn’t replace communication, responsibility, and logical thinking.” Facilitating workshops, mediating between stakeholders, building trust, making decisions—all of that remains a human task.

What you should bring to this role

Once again, the two perspectives complement each other quite well.

Kevin: “You should be enthusiastic about digital systems. You need to have an affinity for what’s possible, what isn’t possible, and how to achieve our clients’ goals.”

Alice: “The most important quality is adaptability, because requirements change every day. And you should be curious. There’s just so much to learn every day.”

In addition, the following qualities clearly emerged from both interviews:

A structured approach to work
Strong communication skills
Proactivity
Technical understanding
And the ability to maintain a clear overview even in complex situations

Or, as Alice puts it: “Chaos should just be another word for an exciting challenge to you.”

Why valantic DXA?

What both of them particularly appreciate about their work at valantic DXA is, above all, the environment in which these projects take shape.

Kevin: “Project success is achieved from trust, collaboration, clear goals, and genuine teamwork.”

Alice: “I can learn something new from every colleague, and that means the work never gets boring.”

At valantic DXA, complex projects meet strong teams, a high degree of personal responsibility, and deep technical expertise. That’s exactly what makes working in the PIM environment so exciting.

And that’s also where Kevin and Alice have something in common: Both enjoy complexity, both want to build great solutions, and both love working with people who share their expertise.

If you’re interested in helping shape digital structures, taking on responsibility, and developing truly great solutions as part of a team, then check out our open positions in the PIM environment.