问HN：为什么更多的产品团队不在领域模型上进行合作？
我是一名产品设计师，拥有前端背景（Rails、Swift），希望加深对领域建模的理解。
我认为领域模型是产品、设计和开发之间的共享基础。但在团队中，我并没有看到这种情况的发生。它帮助我理解可能性，将功能流程锚定在可实现的范围内，避免过度设计。
那么，为什么更多的产品团队不在ERD（实体关系图）上进行协作呢？有时当我请求一个架构或ERD以便理清思路时，我得到的只是茫然的目光。开发者在数据建模方面是否有超越ERD的不同思考方式？
在设计与工程之间，协作领域模型是否是一个良好的切入点？在你们的组织中，这种协作通常是什么样的？
我很想听听其他人是如何处理这个问题的，特别是那些与设计师紧密合作的工程师，或者是随着时间推移在这方面变得更加出色的设计师。
查看原文
I'm a product designer with a front-end background (Rails, Swift) trying to deepen my understanding of domain modeling.<p>I see domain models as a shared foundation between product, design and dev. But I don't see it happening on teams, ever. It helps me understand what's possible, anchors feature flows in what's possible, avoids over designing.<p>So why aren't more product teams collaborating on ERDs? Sometimes when I ask for a schema or ERD to get oriented, I get blank stares. Are there different ways developers think about data modeling beyond ERDs?<p>Is collaborating on the domain model a good entry point between design and engineering? What does that collaboration usually look like in your org?<p>Would love to hear how others approach this, especially from engineers who work closely with designers, or designers who’ve gotten better at it over time.