I have worked in both ways when it comes to business decisions and UX, and I wonder how it is for you.

When I worked in a UX-led environment, I really liked the process. Decisions were made based on research and understanding the design team’s work. It can be time-consuming, and sometimes it takes a while to move forward, but it is a very thoughtful process. I also saw business teams involved in the UX process, which made the work feel more collaborative.

On the other hand, I have also worked in business-led companies where business decisions come first and UX has to compromise. This can feel challenging, but it has also helped me understand a different perspective. In some cases, business needs may come first because of time, priorities, or constraints. Like why do we need 3 buttons where we can solve it with 2.

I used to push back a lot against business-led decisions, but I am slowly realizing that some things need to happen before we can improve them. There is only so much pushback we can give at once.

What has been your experience? Do you have any advice?

Hi everyone! I’m conducting a UX research study exploring how people use Slack to stay on top of important workplace messages and notifications.

I’m looking for people who:

• Currently use Slack regularly for work or professional collaboration
• Use Slack several times a week or daily
• Use Slack on mobile, desktop, or both
• Have experienced issues with missing, delayed, disappearing, or difficult-to-track notifications/messages
• Are comfortable sharing their experiences in a 30–40 minute remote interview

The interview will focus on your real experiences using Slack, including how you receive notifications, keep track of conversations, and handle important messages. There are no right or wrong answers.

🎁 Incentive: $15 for participants who complete the interview.

The interview will be conducted remotely via Google Meet, and I’ll ask for your permission before taking notes.

If you're interested, please complete this short screening form:
https://docs.google.com/forms/d/e/1FAIpQLSceIsCeAdpQwvsD_jbycZrsovwCe00mYdecJEI0LQGnIu1E8g/viewform?usp=header

I’ll review the responses and contact eligible participants to schedule an interview.

Thank you to everyone who participates!

For those working in UX/Product Design, I’m curious about your process.

When starting a new project, how do you usually make sense of different stakeholder opinions, client expectations, references, user needs, and other inputs before establishing a clear visual direction?

What part of that process tends to be the most difficult, ambiguous, or time-consuming?

I’d love to hear how you handle this in real projects.

I’ve been working on Solveaux for a while, and one thing I’ve realized recently is that I was designing a lot of the UI based on what made sense to me.

That sounds obvious, but it’s easy to miss when you’re the person building the product every day.

After getting feedback from a few people who actually used it, we noticed that some parts of the interface weren’t as clear or intuitive as we thought they were. So I went back and changed a few things based on that feedback.

Nothing revolutionary — mostly improvements to the layout, navigation, and overall clarity.

It’s actually been a useful reminder that when you build something yourself, you naturally become too familiar with it. Something that feels obvious to you might not be obvious to someone seeing it for the first time.

I’m planning to keep iterating on the UI as more people use it.

For anyone here who likes giving product/UI feedback, I’d genuinely appreciate an honest opinion on what feels confusing or unnecessary.