The irreducible epistemic atoms underlying the curriculum. 4,828 atoms across 8 types and 2 molecules
Genuine service produces transcendent connection by redirecting attention so completely toward another's need that self-referential processing quiets, not through moral obligation or mood enhancement.
Service that seeks transcendent connection as an outcome prevents that connection from arising because the seeking reinstates the self-referential attention that transcendence requires dissolving.
Natural environments restore depleted directed attention by engaging involuntary attention (effortless, fascination-based) while directed attention recovers.
Use awe experiences as diagnostic data: when awe disrupts a schema, it reveals that schema's boundaries and rigidities, creating a map of cognitive infrastructure limitations.
Frame generative contributions as investments in capability development rather than reputation management, using anonymity as a test of motivation.
Recognize that mentorship transfers sensemaking capacity—ways of interpreting experience and relating to uncertainty—more than it transfers specific knowledge or techniques.
Lower the threshold for offering mentorship by recognizing that developmental value comes from being slightly-further-along rather than being an expert, because proximity to the learner's current position provides navigational wisdom that expertise has forgotten.
Design team interaction patterns explicitly rather than allowing them to emerge from social dynamics, because team performance depends more on interaction architecture than on individual capability.
Build team cognitive protocols before crises occur rather than during them, because approximately 60% of team performance is determined by pre-conditions rather than real-time intervention.
Build detailed mental representations of your own successful performance conditions with sufficient granularity to serve as replicable templates.
Require independent articulation before group discussion to surface the full diversity of team understanding rather than allowing early convergence to suppress divergent perspectives.
Separate idea generation sessions from evaluation sessions to prevent anchoring on early options and allow full exploration of the solution space.
Implement structural interventions rather than relying on awareness to mitigate team cognitive biases, because group-level biases operate below conscious deliberation and resist correction through individual effort.
Assign explicit information ownership roles to ensure that unique information held by specific members enters team discussion rather than remaining suppressed by shared information bias.
Combine high psychological safety with high performance standards rather than choosing between them, because the learning zone requires both the safety to take risks and the motivation to pursue challenging goals.
Create structural guarantees for contribution (structured input rounds, anonymous channels) rather than relying on individual courage to speak up, because structures remove interpersonal risk more reliably than exhortations to be brave.
When assembling a team to solve a complex problem, deliberately include members with different professional backgrounds, training, and problem-solving orientations to expand the solution space the team searches.
Structure team processes to surface and integrate diverse perspectives through independent-then-compare methods rather than sequential verbal discussion.
Create explicit transactive memory systems by documenting who knows what, maintaining this meta-knowledge actively, and routing questions to the appropriate expertise holder.
Use pair programming and knowledge-sharing rotations to build redundancy into team transactive memory, creating multiple paths to critical expertise.
Engineer confirmed success pattern conditions into new projects from the start rather than hoping they emerge organically.
Begin each retrospective by reviewing previous action items and requiring explicit accountability—either completion or a decision to deprioritize—to prevent insight without implementation.
Structure retrospectives around comparing expectations to actual outcomes rather than just listing what happened, to reveal where team mental models were inaccurate.
Explicitly establish and enforce team norms that distinguish task conflict from relationship conflict, celebrating disagreement about ideas while immediately addressing personal attacks.