Access to the same information is only the beginning; teams still need to compare interpretations, priorities and risks.
Teams and collaboration AI and automationStart here
Question
How do people build shared understanding?
How teams interpret context, surface disagreement and work across Product & Engineering boundaries.
Shared documents, dashboards and AI tools can make the same information available to more people. They cannot ensure that everyone interprets it in the same way, notices the same risks or gives the same weight to each constraint.
The notes in this path look at the work that remains after access improves. In my experience, people begin to build shared understanding when they compare how they have interpreted the context. The notes on disagreement and Product & Engineering boundaries show what can remain unclear even after everyone has seen the same material.
Thinking
Notes that develop the question.
This is a curated path rather than a complete topic archive. Each group approaches the question from a different part of the work.
Context still needs interpretation
Shared documents and tools help, but understanding depends on what people notice and how they interpret it.
- Most product disagreements come from missing information Product discussions often look like disagreements of opinion. In reality, teams are often missing the same piece of information. Product decisions Teams and collaboration
Collaboration is more than a hand-off
Product and engineering work improves when differences are surfaced and responsibilities remain connected.
- The real job of a Product Manager is managing disagreements Much of product work is about helping smart people who see the problem differently find a way forward. Teams and collaboration Product decisions
- The transition to Product Management starts before the title changes The transition into Product Management often begins before the role changes, when attention shifts from implementation alone to problems, trade-offs, communication, and product judgment. Product decisions Teams and collaboration
Influences
Ideas that sharpen the question.
Selected external arguments and research that add evidence, language or a useful challenge.
-
Common software project conflicts and how to navigate them (opens in new tab)
A practical catalogue of the conflicts that software teams repeatedly need to navigate.
-
Blurring boundaries: Toward the collective empathic understanding of product requirements (opens in new tab)
Research on building a collective understanding of product requirements across roles.
-
Boundaries Between Product & Engineering (opens in new tab)
A useful challenge to treating Product & Engineering as isolated functions.
-
Even with AI, cognitive digital twins retrieve information more than they actually understand work (opens in new tab)
A reminder that retrieving shared information is not the same as understanding tacit work.
Experience behind the ideas
Working across Product & Engineering
How a technical foundation shaped later work with engineering leadership on roadmaps, constraints and risk.
See the experience behind this question