Over the past few months, I’ve been immersed in projects with very different dynamics: from restructuring the digital warranty ecosystem for the automotive and energy industries, to internal B2B operational traceability tools, to dynamic mobility platforms and digital interactions for cultural venues. At first glance, a corporate warranty system and the website for an interactive museum don’t have much in common. However, when you sit down to design the information architecture and user experience for projects of this scale, you realize that the underlying challenges are almost identical. Here, I’m sharing three key lessons that have recently become integral to my workflow:

1. Product design is, first and foremost, process architecture

It’s easy to fall into the trap of opening Figma and starting to put together screens once you have the initial requirements. But in enterprise-level projects—where service technicians, distributors, end users, and business rules involving prorated calculations are involved—the interface is merely the surface layer. If the operational process is fragmented or it’s unclear who performs which step behind the scenes, even the cleanest interface in the world will fail. Mapping out service blueprints, understanding the technical constraints of integrations (such as ERPs or CRMs), and validating workflows with the actual stakeholders before moving a single pixel is what truly prevents costly rework and ensures system adoption.

2. “Mobile-First” isn’t just a responsive layout; it’s a usage pattern

Designing for mobile is often taught as an exercise in rearranging desktop columns into a single vertical row. But when you analyze actual behavior in the field—for example, a user looking up a quick recipe while cooking or a visitor checking rates and maps just before entering a venue—you realize that context completely changes the user’s intent. On mobile, the user isn’t browsing out of curiosity; they’re trying to complete a specific task in the shortest time possible. Prioritizing accessibility, a clear content hierarchy, buttons within thumb’s reach, and optimal load times isn’t a visual luxury—it’s a functional necessity. If the mobile experience requires a user manual, the design has already failed.

3. Transparency and governance build trust

Whether on a B2B platform or a B2C channel, clarity of information is the number one factor in retention and satisfaction. When a user understands exactly where they are in a process (for example, through a clear tracking ID or reference number) or when a customer has transparent access to policies and terms without fine print, friction decreases dramatically. Designing with a focus on data governance and traceability not only protects business operations but also creates a sense of control for the user that no animation or pretty microinteraction can replace.

Final Thoughts

The design work doesn’t end when the Figma file is “ready for development.” The true value of a Product Designer lies in connecting business objectives with pragmatic solutions that simplify the lives of the people who use the software every day.