Summary
UX practitioners often overlook the fact that UX terms do not naturally translate into business contexts, particularly when high-stakes decision-making and unclear communication become barriers. In this session, Shan Shen will highlight instances where UX terms consistently hinder collective problem-solving between UX and product teams.
Key Insights
-
•
Unstable and inconsistent UX language creates costly confusion across product teams.
-
•
Translating UX jargon into simple business terms facilitates alignment and trust.
-
•
UI polish and usability elevation represent distinct priorities that need clear linguistic separation.
-
•
Card sorting exercises can expose underlying user needs beyond visual arrangement, influencing conversion rates.
-
•
Product managers often focus on sprint constraints and direct value delivery, which UX must consider when proposing research.
-
•
Standard UX terms like 'tree test' may need explanations or alternative naming to be meaningful for cross-disciplinary use.
-
•
Educating product teams on UX terminology and activities builds shared understanding and smoother collaboration.
-
•
Code switching between UX and business language is a valuable skill rather than a betrayal of design discipline.
-
•
Reciprocity in language adaptation—designers learning business language and product managers engaging in UX language—strengthens partnerships.
-
•
Measurable UX improvements, like a 10% lift in conversion, can stem from clarifying information architecture and simplifying action hierarchies.
Notable Quotes
"Translation is key to earn the seat at the table."
"An eight-page long study plan wouldn’t fly in a one-sprint product timeline."
"We reduced buttons from six to two and saw a 10% increase in conversion rate over three weeks."
"Card sort as a phrase may not require translation, but the value discovery it represents certainly does."
"Instead of explaining phrases like card sort from a book, prioritize code switching to clarify value and relevance."
"Product team misused ‘prototype’ to describe tree test artifacts, which have very different outcomes."
"Language adds prestige to the equation, but leveraging well-established language attracts a wider audience."
"Speaking a fluent language that translates into business discussions forces us to think like business owners as well as designers."
"Start small and learn as you go to avoid failure from expecting huge success right away."
"Be strict in what you emit but liberal in what you accept is like an engineering principle for communication."
Or choose a question:
More Videos
"We want teams to have autonomy and power to make pivot, shelve, and proceed decisions, not leadership dictating."
Standardizing Product Merits for Leaders, Designers, and Everyone
June 15, 2018
"Very few people in business are familiar with situational awareness unless they served in the military."
Simon WardleyMaps and Topographical Intelligence (Videoconference)
January 31, 2019
"If you’re in tech, you are in social change, whether you realize it or not."
Sandra CamachoCreating More Bias-Proof Designs
January 22, 2025
"It takes at least one team member to choose to set healthy standards for collaboration."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"ChatGPT didn’t have the full context of what was most important to stakeholders, so I had to edit its output before sharing."
Fisayo Osilaja[Demo] The AI edge: From researcher to strategist
June 4, 2024
"There is a common thread in craft: dignity, purpose, utility, and beauty."
Uday GajendarThe Wicked Craft of Enterprise UX
May 13, 2015
"No official kickoff was held, which meant shifting expectations and lack of alignment."
Davis Neable Guy SegalHow to Drive a Design Project When you Don’t Have a Design Team
June 10, 2021
"We did a great cleanup of patterns from every decade and deleted anything off brand or untested."
Eniola OluwoleLessons From the DesignOps Journey of the World's Largest Travel Site
October 24, 2019
"Finding a single source of truth for design documents and artifacts is extremely hard because most tools operate in silos."
Aurobinda Pradhan Shashank DeshpandeIntroduction to Collaborative DesignOps using Cubyts
September 9, 2022
