Marco Stroppiana

Why the success of a B2B product is measured by how little the user notices the interface. In recent years, we’ve been sold the idea that design must be “eye-candy”—that without fluid animations or perfect gradients, we aren’t doing our jobs. But the reality is different, especially when you get down into the trenches of […]

Why skepticism is the most productive tool in a product team. Sometimes I get the feeling that our industry over-rewards rapid certainty. A requirement arrives, someone says, “We need a dashboard for this,” and ten minutes later, three people are already arguing over whether it should be a bar chart or a line graph. We

Why design profitability in B2B should be measured by the errors the user never commits. There is a metric in product design that never appears in reports, yet it is precisely the most expensive of all: the cost of confusion. In the B2B world, an error isn’t about “I don’t like this button; it would

Why a design system is a framework for decisions, not just a static catalog. Many people confuse a design system with a simple library of assets. They think that if they have an organized list of elements, the work is finished. But in reality, those files are often just “photos” of a past moment. They

In the age of information overload, our best tool is not the brush, but the scissors. Many people think a designer’s job is to add: add features, add graphics, or add layers of interaction. However, the most difficult and valuable task is curation. When a client says they need to “see everything on one screen,”

Most design projects focus on the “happy path”: the server is fast, the user makes no mistakes, and the data is perfect. But in the real world—especially in B2B or industrial tools—the happy path is rare. Designing for failure means treating errors as a central part of the system, not just an exception. A system