Shared understanding
Shared understanding is a common interpretation of relevant information, context, assumptions, or goals held by multiple people.
Collaborative Software Design: How to facilitate domain modeling decisions
A shared understanding is a common interpretation of relevant context, assumptions, concerns, and decisions among participating people.
- How it is used
- Aligns stakeholders and software teams around business problems and design decisions through collaborative modeling.
- How deep it goes
- Defines the goal and gives visualization, participation, sensemaking, and documentation practices without prescribing a single modeling process.
- Examples
- Uses BigScreen hand-offs, EventStorming for movie extensions, and a standard-product-versus-custom-solution polarity exercise.
- What you can do after
- Apply it via collaborative modeling to make assumptions explicit, align perspectives, and support sustainable design decisions.
BDD in Action, Second Edition
A common and sufficiently detailed interpretation of requirements, behavior, and value held by the people collaborating on a product.
- How it is used
- Aligns stakeholders and delivery teams on valuable features through conversations about business goals, rules, and behavior.
- How deep it goes
- Works through ambiguous password criteria and a conversation-to-scenario process; defers Java automation.
- Examples
- Uses overseas-transfer design questions and password-strength cases to expose assumptions that an initial feature request or acceptance criteria leave unresolved.
- What you can do after
- Practice/perform cross-functional example conversations, clarify expected behavior, and express agreed examples as scenarios suitable for automation.
Read how BDD in Action, Second Edition explains shared understanding →
Effective Behavior-Driven Development
A common interpretation of requirements and expected behavior held by the members of a team.
- How it is used
- Aligns business and delivery participants on a story’s detailed requirements during discovery and formulation.
- How deep it goes
- Builds understanding through concrete examples and domain terms, then leaves exhaustive test coverage to delivery work.
- Examples
- Uses order-address changes before and after collection to clarify expected acceptance or rejection.
- What you can do after
- Evaluate whether participants agree on expected behavior before code or tests are written.
Read how Effective Behavior-Driven Development explains shared understanding →
Hidden Influences
A commonly held understanding of events, facts, or social conditions among members of a community.
- How it is used
- Frames shared reality as a condition for an informed public and healthy civic engagement amid personalized news feeds.
- How deep it goes
- Explains its civic role and how personalization can weaken it, without specifying how to measure it.
- Examples
- Uses personalized news, a cousin encountering conspiracy theories, and streaming “should” versus “now” movies.
- What you can do after
- Evaluate how personalized feeds may weaken common awareness needed for public discussion.
Also covered in
What to know first
- requirementsA requirement is a stated need, capability, quality, condition, or constraint that a system, product, solution, or project is expected to satisfy.
- stakeholderA stakeholder is a person, group, or organization with an interest in, influence over, or potential to be affected by a system, project, decision, or its outcomes.
- assumptionAn assumption is a proposition or condition provisionally accepted as true or applicable as a basis for reasoning, planning, modeling, or action.
- behavior-driven developmentBehavior-driven development is a collaborative software development practice that specifies and verifies desired behavior through examples expressed in terms understandable to stakeholders.
Related concepts
- collaborative discovery and modelingproduced by · Collaborative discovery and modeling is a group technique in which stakeholders jointly create and refine representations to establish shared understanding of a domain or system.
- formulationused by · The behavior-driven development practice of expressing understood behavior as precise scenarios.
- discoveryproduced by · Discovery is the process of identifying, locating, or examining information, entities, problems, or opportunities relevant to a particular purpose.
- discovery workshopproduced by · A discovery workshop is a collaborative, structured session for exploring and refining user needs, business problems, domain concepts, or software requirements.
- Example Mappingproduced by · Example Mapping is a collaborative technique for clarifying a requirement by organizing its rules, examples, and open questions.
- expectation managementproduced by · Expectation management is the practice of clarifying, communicating, aligning, and adjusting expectations about capabilities, responsibilities, processes, and outcomes.
Questions about shared understanding
What is shared understanding?
Shared understanding is a common interpretation of relevant information, context, assumptions, or goals held by multiple people.
Which Manning books explain shared understanding?
Collaborative Software Design: How to facilitate domain modeling decisions, BDD in Action, Second Edition, Effective Behavior-Driven Development and Hidden Influences.
What should I know before learning shared understanding?
Manning books that teach shared understanding usually introduce requirements, stakeholder, assumption and behavior-driven development first.
These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.



