• **Ontological Debt** is a term coined by author and UX designer Andy Welfle to describe the negative impact on user experience (UX) due to inconsistent product terminology and semantics. • **Causes of Ontological Debt**: It arises from poor communication among product teams, lack of shared understanding, and inconsistent terminology across features and platforms. • **Impact on UX**: Inconsistent terminology confuses users, hinders learning, and degrades the overall user experience, leading to frustration and decreased user satisfaction. • **Identifying Ontological Debt**: Welfle suggests looking for inconsistencies in naming, labeling, and descriptions across your product, as well as feedback from users and team members. • **Paying Down Ontological Debt**: Welfle proposes a three-step process: - **Identify**: Find and document all instances of inconsistent terminology. - **Decide**: Choose a consistent term and update all instances. - **Communicate**: Ensure the updated terminology is understood and used by the entire team and across all platforms. • **Terminology Guidelines**: Establishing clear terminology guidelines helps prevent ontological debt from accruing in the first place. • **Example**: Welfle uses the example of a hypothetical e-commerce app with inconsistent use of "cart," "basket," and "bag" to illustrate the problem and solution. • **Benefits of Addressing Ontological Debt**: Improving UX, reducing user confusion, and fostering a shared understanding among product teams. • **Context**: This article was saved because it provides a clear and actionable framework for improving UX by addressing a common but often overlooked issue in product development. • **Author**: Andy Welfle is a UX designer and writer with experience in various industries, including finance, healthcare, and e-commerce.

**Summary of Social Media Post and Discussion** • **Post by @TechSavvySara (12/05/2022)**: "I've started a new rule: if your website/product doesn't have some names of the humans behind it, I'm not using it. It's terrifying to interact with faceless entities. #Transparency #Trust #UX" • **Context**: The post is part of a broader conversation on user experience (UX), trust, and online privacy. It reflects the author's growing concern about the lack of transparency in digital products and services. • **Key Point**: Sara emphasizes the importance of knowing the people behind a website or product to build trust and feel comfortable using it. • **Supporting Argument**: She argues that faceless entities can be intimidating and untrustworthy, likening them to "interacting with a black box." • **Evidence**: Sara cites her personal experience and preference, stating that she has started applying this rule to her own usage. • **Engagement**: The post received 23 likes and 7 retweets, indicating that it resonated with many users who shared similar sentiments. • **Discussion**: - **@PrivacyPro** replied (12/05/2022): "I completely agree. Knowing who's behind a service helps me understand their values and commitment to my data privacy." - **@UXDesigner** commented (12/06/2022): "As a UX designer, I can say this is a valid point. People connect with people, and that should be reflected in our designs." • **Counterpoint**: No direct counterpoints were raised in the discussion, but the topic could spark debate on the balance between privacy, transparency, and user experience. • **Author Insight**: Sara's post highlights her commitment to ethical and transparent digital practices, reflecting her values as a tech user and advocate. • **Why Saved**: This post was saved as it encapsulates a growing concern about online trust and privacy, offering a simple yet effective rule for users to evaluate digital products and services. It also serves as a reminder of the importance of human connection and transparency in UX design.