What do you do at Impresoft Syscons?

At Impresoft Syscons, I joined the Quality Management team right from the start as a Functional Analyst within the PLM & Logistics division.

My main responsibilities involve gathering and analyzing customer requirements, transforming them into solutions that can be implemented within the SAP system, and determining whether to propose a solution already provided by the SAP standard or one that requires the technical team’s involvement and, therefore, some customization.

I oversee various phases of the project, from requirements analysis through testing, training, and user support.

Specifically, working with the SAP QM module, my focus is on managing quality-related processes throughout the supply chain; however, integration, synergy, and collaboration with departments adjacent to Quality—such as Logistics and Production—are also essential.

It’s a role that requires understanding both business needs and how the system works, acting as a bridge between the client and the technical team.

If you had to explain to a close friend the impact your daily work has on the clients you support, what story or achievement would you share with them?

One of the most fascinating aspects of my job is observing how the relationship with the client evolves throughout a project’s lifecycle, especially once we’ve crossed the go-live threshold.

Before go-live, every major digital transformation project brings with it a natural degree of uncertainty.

Sometimes, the optimized processes and the new product can be perceived by the operational teams in the supply chain as an imposition or a rigid process they must endure. During this delicate phase, testing and on-site support activities risk appearing as an obstacle to daily work rather than an opportunity for improvement.

The go-live radically changes this perspective. On-site support allows us to empathize with users, guiding them step by step through their new tasks and reassuring them in the face of inevitable initial difficulties.

This is precisely where the perception of the consultant evolves: from a figure who “introduces a complex new system” to a strategic partner with whom to solve problems. Users begin to grasp the true value of the project, realizing that the ultimate goal is not the technology itself, but the quality and simplicity of their work.

This proves that the heart of consulting lies not only in technical processes, but in knowing how to guide people through change with active listening, clarity, and presence.

What’s a small habit, team tradition, or detail of your office or work routine that you’d never give up?

Definitely coffee breaks—they mean chatting, exchanging ideas, and connecting with colleagues. Even on the busiest days, I think it’s important to have those little moments to pause, catch up, talk about things other than work, and simply unwind for a few minutes.

Since this is my first job, my relationship with my colleagues has played an important role for me from the very beginning: I joined the company after attending an Academy alongside 10 other young people, with whom I had the chance to share my first few months of training and transition into the workforce.

Over time, my relationship with them has grown into a friendship that continues to this day, even though we work in different departments and therefore don’t often work closely together. In fact, precisely for this reason, the moments during breaks when we run into each other, exchange a few words, and even talk about things beyond work are particularly precious to me.

I believe this is one of the most beautiful aspects of the workplace: growing professionally together, but also managing to build relationships that go beyond the project or the role we hold.

Looking back at who you were when you joined the company and who you are today, what skills (hard and soft) have you gained?

When I joined the company—as this was my first job—I certainly had some theoretical knowledge, but I still had to learn how to turn that into skills I could actually apply on the job.

From a technical standpoint, I’ve gained a deeper understanding of SAP and, in particular, of processes related to quality management. I’ve learned to navigate real-world projects and understand the phases of complex projects—such as those involving management transitions in large manufacturing companies—to analyze requirements, configure the system, conduct tests, and tackle problems that don’t always have a predefined solution—primarily because the requirements themselves are often unclear.

I am on a path of continuous growth: even though I have only participated in one project, every project phase and every rollout allows me to tackle different processes and challenges and to expand my skills.

Much of this growth has also been on a personal level. I’ve learned to better manage my priorities, to communicate and interact daily with people whose roles and skills are very different from my own—whether within the company and my team or at the client company and other consulting firms— and, above all, to have greater autonomy and confidence in performing my duties and finding solutions when faced with challenges.