What does it mean that shared schemas enable collaboration?

Teams that share mental models coordinate better than teams that do not.

Example: A navigation team on a Navy vessel brings a ship into harbor. No single person holds the full picture. The bearing recorder, the plotter, the pelorus operators, and the officer of the deck each hold a fragment of the schema — compass bearings, chart positions, timing, environmental context. But because they share a schema for how a fix cycle works (sight a landmark, call the bearing, record it, plot it, compute the position), they coordinate without needing to explain their reasoning at each step. When the system works, the team's cognition exceeds what any individual could produce alone. That is the power of a shared schema.

Try this: Choose a project or recurring collaboration where you and at least one other person must coordinate. Together, write down the shared schema that governs how you work: What are the key terms you both use? What is the implicit process flow? Where do you agree on definitions, and where have you been operating with different assumptions? Document it as a one-page 'schema map' — not a full process document, but an explicit representation of the mental model you are both supposed to share. Note every point where your versions diverge.