In conventional software development, user experience (UX) designers and engineers collaborate through separation of concerns (SoC): designers create human interface specifications, and engineers build to those specifications. However, we argue that Human-AI systems thwart SoC because human needs must shape the design of the AI interface, the underlying AI sub-components, and training data. How do designers and engineers currently collaborate on AI and UX design? To find out, we interviewed 21 industry professionals (UX researchers, AI engineers, data scientists, and managers) across 14 organizations about their collaborative work practices and associated challenges. We find that hidden information encapsulated by SoC challenges collaboration across design and engineering concerns. Practitioners describe inventing ad-hoc representations exposing low-level design and implementation details (which we characterize as leaky abstractions) to "puncture" SoC and share information across expertise boundaries. We identify how leaky abstractions are employed to collaborate at the AI-UX boundary and formalize a process of creating and using leaky abstractions.
翻译:在常规软件开发中,用户经验(UX)设计师和工程师通过将关注问题(SoC)分离而合作:设计师创造人际界面规格,工程师建立这些规格。然而,我们认为,人类-AI系统挫败了SoC,因为人类需要必须决定AI界面的设计、AI的次级组成部分和培训数据。目前设计师和工程师如何在AI和UX设计方面进行合作?为了发现这一点,我们采访了14个组织中的21名行业专业人员(UX研究人员、AI工程师、数据科学家和管理人员),了解他们的合作工作做法和相关挑战。我们发现,由SOC包罗的隐蔽信息对设计和工程方面的协作提出了挑战。从业者描述发明的自动组合,暴露了低层次的设计和实施细节(我们称之为渗漏式抽象),以“渗漏式” SoC,并分享跨专业界限的信息。我们确定如何利用泄漏式的抽象数据在AI-UX边界进行合作,并正式确定创建和使用泄漏式抽象数据的过程。