IA is the core of intelligibility. You need to have it for your product to have conceptual integrity; it is the metaphorical skeleton that holds up your product. If your team disagrees on this, maybe they should just throw some AI at it. That tends to work really well when your audience is gullible, thoughtless, and craven. A little like this whole AI answer feature — I’m gullible if I think this benefits anyone but LinkedIn’s thoughtless planners or craven investors.

Arrange an activity to define/iterate clear design principles and user needs/challenges the organization wants to prioritize in the product. After that, allow the team to co-ideate and co-create. Parallel design and get user feedback. It will clarify most of the indecisiveness.

At Stormdesigns we strive to focus on the users standards, norms and preferences. Ultimately that is what needs to guide the experience. Consider the balance of innovation with familiarity to create something “fresh yet familiar” so it feels novel and intriguing yet isn’t confusing or off-putting. Also note the benefits with each suggested approach and work to integrate the perspectives of any valid suggestions from your team. 👍

If the UX team is competent and doing UX correctly, their personal preferences shouldn’t be an issue. The job of UX is to create functionality that fits user needs, not developer opinions. Test, demo, research, ask, then design the way the data and feedback directs you to. Don’t do UX based on the personal preferences of a UXer.

Make a case using data and analytics. People often have differences of opinion in design. You have to prove your design choices via logic, facts and actual studies. In one of my recent gigs, there was a difference of opinion about displaying search results using pagination versus infinite scroll. Based upon user studies, competitive analysis, and also the age and experience of the user base, I made the case for why pagination was the better option for the project and was supported by management based upon my presentation of data and facts.

“If there is a problem, yo I’ll solve it.…” ~Research A note for the PM in charge of asking for my advice. Sometimes less is more. The minimum character count is lame.

Here are two ways to ensure IA usability optimization amidst conflicting design preferences: 1. What helps me is to focus on user-centered decision-making—Prioritizing clarity, simplicity, and consistency that aligns with users' mental models and task flows. 2. Aditionally, open discussion with the team using data-driven insights, ensuring decisions are backed by user needs rather than personal preferences, helps.

Bem , na minha opinião como designer / programador / utilizador de vários equipamentos com e sem IA , só posso dizer que tem que existir uma simbiose entre a equipa de design, equipa de programação , equipa de edição , e a IA , em que todos juntos com metodologia e com um algoritmo apropriado com instruções em módulos definidos , seja mais fácil e rápido implementação de layers e outros conteúdos !!

IA serves as a tool first and foremost for the user. If users can't navigate the product, intuitively, easily and comfortably, they will leave; therefore, personal team IA preferences are simply irrelevant. User testing methods like card sorting and tree testing can help. Personally, I prefer a more direct approach and get a more valuable user feedback through structured design reviews, which not only allow to validate the IA but also improve it upon deeper insights. Lastly, documenting decisions ensures transparency and consistency moving forward, turning this misalignment into an opportunity for everyone on the team to gain insights and align on how our users are actually interacting with our product.