Principles
2,201 principles · page 28 of 46
Create explicit transactive memory systems by documenting…
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…
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…
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…
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…
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
Explicitly establish and enforce team norms that distinguish task conflict from relationship conflict, celebrating disagreement about ideas while immediately addressing personal attacks.
Design meetings with pre-work that moves cognitive effort…
Design meetings with pre-work that moves cognitive effort out of synchronous time, allowing the meeting to focus on work that requires real-time interaction rather than individual processing.
Limit meeting attendance to only those who need…
Limit meeting attendance to only those who need to participate, because each additional person increases coordination costs and reduces individual accountability.
Design asynchronous collaboration with bounded comment…
Design asynchronous collaboration with bounded comment periods, clear reviewers, and explicit decision mechanisms to prevent open-ended discussion that never concludes.
Separate high-signal channels requiring attention…
Separate high-signal channels requiring attention from reference channels consulted when needed and low-signal optional channels, because collapsing these into a single stream destroys the signal-to-noise ratio.
Design information routing with redundant paths for critical
Design information routing with redundant paths for critical information, because single-path routing creates vulnerability to individual absence or channel failure.
Push urgent information to recipients through notifications…
Push urgent information to recipients through notifications while making reference information available for pull when needed, to prevent notification floods that teach people to ignore all notifications.
Allocate team attention explicitly across categories…
Allocate team attention explicitly across categories (committed priorities, responsive buffer, exploration) and make this budget visible to stakeholders to prevent reactive work from consuming all capacity.
Identify your default role in recurring relational patterns…
Identify your default role in recurring relational patterns, then run controlled experiments changing one variable to test whether the pattern is as rigid as it feels.
Establish interrupt protocols that route different priority…
Establish interrupt protocols that route different priority levels through different channels, preventing low-priority interruptions from receiving high-priority attention and distributing the cognitive cost of responsiveness.
Conduct attention retrospectives to review how the team…
Conduct attention retrospectives to review how the team actually spent attention versus intentions, creating a feedback loop for calibrating and improving attention management over time.
Attach new epistemic practices to existing team rituals…
Attach new epistemic practices to existing team rituals rather than creating separate meetings to ensure adoption through reduced friction.
Develop individual epistemic skills as the foundation…
Develop individual epistemic skills as the foundation for team cognitive architecture, since team practices cannot compensate for low individual competence.
Individual metacognitive transparency—articulating…
Individual metacognitive transparency—articulating reasoning, evidence, and uncertainties—enables teams to evaluate and build on thinking rather than just conclusions.
Organizational schemas should be made explicit through…
Organizational schemas should be made explicit through independent elicitation across roles and levels, with convergences, divergences, and absences each providing distinct diagnostic information about alignment, conflict, and blind spots.
Periodically surface process schemas by extracting embedded…
Periodically surface process schemas by extracting embedded assumptions (about risk, capability, sequencing, quality) and evaluating them against current reality, because processes designed for past contexts become organizational fossils when their assumptions are no longer valid.
Conduct structured newcomer debriefs at 30/60/90 days…
Conduct structured newcomer debriefs at 30/60/90 days to capture schema observations before habituation renders them invisible, because newcomers occupy a unique vantage point where organizational assumptions are still visible as choices rather than facts.
Frame strategy as a single causal model ('We win by doing X…
Frame strategy as a single causal model ('We win by doing X because Y') rather than as a list of objectives, because a causal model enables distributed coherent decision-making while a list only enables plan-following when the plan applies.
Design strategy statements to make tradeoffs explicit…
Design strategy statements to make tradeoffs explicit through 'prioritize X over Y' framing, because strategy's power comes from what it excludes and ambiguous priorities provide no guidance when values conflict.
Track relational dynamics across multiple relationships…
Track relational dynamics across multiple relationships to distinguish your portable templates from situational responses specific to particular people.
Test strategy schema clarity through decision simulations…
Test strategy schema clarity through decision simulations across functions: if the schema produces consistent answers to hypothetical tradeoffs without central coordination, the schema is effectively shared; inconsistent answers reveal schema gaps requiring clarification.
When modifying processes, surface embedded schemas first…
When modifying processes, surface embedded schemas first to distinguish between processes encoding hard-won lessons (whose removal reintroduces risk) and processes encoding obsolete assumptions (whose removal reduces waste), rather than treating all processes as either sacred or disposable.
Create shared schemas or tradeoff frameworks…
Create shared schemas or tradeoff frameworks at cross-functional interaction points rather than forcing one function's schema to dominate.
Document critical organizational schemas explicitly…
Document critical organizational schemas explicitly with concrete examples to provide calibration references for informal learning.
Systematically collect information from outside existing…
Systematically collect information from outside existing schema filters—customers who left, growing competitors, adjacent industries—to detect schema obsolescence.
Question the assumptions underlying repeated failures rather
Question the assumptions underlying repeated failures rather than just correcting actions within those assumptions.
Maintain an explicit registry of core assumptions…
Maintain an explicit registry of core assumptions with scheduled review cycles to prevent invisible obsolescence.
Measure decision latency, problem recurrence…
Measure decision latency, problem recurrence, and strategy-execution gaps as proxies for accumulated schema debt.
For personal knowledge to become organizational knowledge…
For personal knowledge to become organizational knowledge, it must change something that persists: processes, documents, policies, shared models, or tool configurations.
Translate strategic schemas into level-appropriate…
Translate strategic schemas into level-appropriate expressions that specify what the strategy means for each organizational level's daily decisions and actions, rather than repeating abstract strategy statements uniformly.
Recognize that your interpersonal behavior systematically…
Recognize that your interpersonal behavior systematically pulls specific complementary responses from others, making you a co-creator of recurring dynamics rather than a passive recipient.
Align organizational systems (goals, metrics, incentives…
Align organizational systems (goals, metrics, incentives, daily tasks) with intended schemas to propagate those schemas effectively, because experience-based schema formation dominates message-based transmission.
Express cross-functional requests in the target function's…
Express cross-functional requests in the target function's schema by identifying the isomorphism between your concern and their priorities, using their vocabulary, metrics, and quality criteria.
Create boundary objects—artifacts designed to be meaningful…
Create boundary objects—artifacts designed to be meaningful to multiple groups while supporting different interpretations—as translation infrastructure between functional schemas.
Prioritize schema interventions by cost-of-misalignment…
Prioritize schema interventions by cost-of-misalignment rather than by visibility or urgency to direct improvement efforts where they create the most value.
Model desired schemas through leadership behavior…
Model desired schemas through leadership behavior, especially in high-stakes and high-visibility situations, because leadership actions are more observed and more schema-propagating than leadership communications.
Invest in schema design as infrastructural work that shapes…
Invest in schema design as infrastructural work that shapes behavior across all organizational domains, rather than treating behavioral improvement as application-level interventions in specific areas.
Test cultural values under costly conditions where following
Test cultural values under costly conditions where following them imposes measurable penalties, because costly signals establish values as genuine rather than aspirational.
Design knowledge systems around knowledge flow (ensuring…
Design knowledge systems around knowledge flow (ensuring knowledge reaches those who need it when they need it) rather than knowledge storage volume.
Identify the specific, repeatable daily behaviors that would
Identify the specific, repeatable daily behaviors that would deposit desired cultural patterns and design cue-routine-reward loops that make those behaviors automatic.
Examine the last ten significant organizational decisions…
Examine the last ten significant organizational decisions to identify whether actual decisions aligned with stated values, paying particular attention to decisions where values conflicted with performance.
Insert a competing response at the trigger point rather…
Insert a competing response at the trigger point rather than suppressing the unwanted behavior, because suppression keeps the original response mentally active while competing responses disrupt the behavioral chain before it executes.
Identify behaviors that violate stated values…
Identify behaviors that violate stated values but are tolerated, because each tolerated violation defines the cultural floor more powerfully than any positive example sets the ceiling.