You can ask a question back to your stakeholder about what they liked or valued on that reference design. Oftentimes they might not want an exact copy but they like certain aspects.

This is the right answer. Especially if the pattern allows intuition providing less friction for users moving to your product. Not having to teach is a benefit.

Ah yes, the classic "let's unpack this, shall we?"

Oh yea. 😉 It is a classic for a reason.

As a designer who moved to pm, I would say don’t do something because someone tells you. They need to communicate the why. The why in this case should be something you align with or challenge. If align then yes go with it. If challenge then you provide justification

I often say no since I’m building zero to one product now, but if I strongly believe in the benefit, I’d articulate what you said and take the risk without a doubt. [2/2]

I usually ask the following questions first:

What will be the benefit of exploring a new pattern? Is it worth spending time on that?

Do I have enough time/resources to validate my pattern? If not, trusting my instincts would cause any significant risks? [1/2]

Context: I'm treating it a lot case by case, measuring risk, time and resources available. 

When the conditions are right (clear opportunity to improve vs. competitor, resources and positive indicators available), I try to explore more.

Is this a universal experience?

Question for designers: how do you balance repeating existing patterns from your vertical vs. exploring new solutions? 

I often get asked to "just do as company X", but I'm aware that those companies are not offering a great experience overall (and customer base differs etc).

All great points, @kagan. I am genuinely curious about how others handle and measure this risk. Thank you sharing

Posts