#Business and UX

1 messages Ā· Page 1 of 1 (latest)

acoustic star
#

I think it’s important as the UX designer to bring in customer insights. Part of your role is juggling what’s good for the business versus what’s good for the customer.

In terms of prioritizing, why are your features important, if not more important, than the business team’s? What if you design it, implement, and ship but no one uses because none of your users had a need for it.

As the ā€œvoice of the customerā€, you have to bring these insights to the table when deciding what to work on next. You have to be compelling and you have the prove the impact your features will have.

The ideal situation is business needs align with customer problems, but that’s not always the case zrmmcry

dense valve
#

Thank you so much for replying this. I was wondering if there was a need to talk to user since the feature specs are so bare bone, yet crucial to the business.

But then I guess there was assumptions on what actually a user needs and interacts, so I would still need to talk to user to understand their pain points, regardless of these crucial feature specs for the business?

acoustic star
#

Yeah! So a checkout flow is crucial for users to make a purchase, right? But how would you design a flow that people successfully complete and not drop out of? How would you design something that users intuitively know is a checkout flow? And so on and so forth.

I’d say look at how companies like Shopify and Stripe approach the process. (here’s one I found: https://www.shopify.com/partners/blog/microinteractions)

Hopefully this answers your question!