Law of the Instrument¶
Core Idea¶
The tools an agent possesses systematically bias what the agent recognises as a problem, what category the problem is sorted into, and what intervention is generated. The bias is not mere preference for the familiar; it is perceptual — the world's joints get carved into shapes the tool can grip, and joints the tool cannot grip become invisible or get re-described into shapes it can. Maslow's formulation — "if the only tool you have is a hammer, it is tempting to treat everything as if it were a nail" — names a structural pattern that operates well beyond the cognitive psychology in which it was found. The structural commitment is capability-shaped perception: the inventory of available tools (cognitive, methodological, technological, institutional) determines the inventory of visible problem categories and the inventory of imagined solutions. Acquiring a new tool does not merely add a capability; it re-carves the perceived problem space. Losing or refusing a tool does not merely subtract a capability; it makes a class of problems perceptual non-events.
What changes when one names this pattern is the third-order question that becomes askable: not "is our tool the right tool?" (instrumental) nor "do we have the right tools?" (inventory), but "is the problem we are seeing the actual problem, or the projection of the problem onto our tool's categories?" The frame demands that the analyst step behind the problem statement and audit the tool that shaped it. The structural relation is between three objects — a world-situation with multiple structural features, a tool inventory the agent possesses, and a problem-as-perceived that is the world-situation carved into the categories the tools can engage — and the standard model wrongly assumes the perceived problem equals the world-situation, with the tool selected to address it, whereas the law of the instrument places the tool upstream as the shaper of perception. The pattern is inherently about cognitive agents with tool repertoires and carries a mild normative load (perceptual bias as failure), which is why it reads as framed even though the capability-perception relation is fairly abstract.
How would you explain it like I'm…
Everything Looks Like A Nail
Your Tool Picks the Problem
Tools Shape What You See
Structural Signature¶
the world-situation with multiple structural features — the tool inventory the agent possesses — the carving of the situation into the tool's engageable categories — the problem-as-perceived standing in for the problem-in-the-world — the upstream placement of the tool as shaper of perception — the projection invariant: features the tool cannot grip become perceptual non-events
An agent exhibits the law of the instrument when each of the following holds:
- A world-situation. A situation in the world has multiple structural features, only some of which any given tool can engage.
- A tool inventory. The agent — person, team, profession, discipline, institution, or software system — holds a finite repertoire of cognitive, methodological, technological, or institutional tools.
- A carving operation. The tools carve the situation into the categories they can grip; joints the tools cannot grip get re-described into shapes they can or become invisible.
- A problem-as-perceived. The output is a problem statement that is the situation projected onto the tool's categories, not a veridical reading of the world.
- An upstream tool. The tool sits upstream of perception as its shaper, inverting the naive flow in which perception is veridical and the tool is merely selected afterward to address it.
- The projection invariant. Acquiring a tool re-carves the perceivable problem space and losing or refusing one makes a class of problems perceptual non-events; when N experts read one situation as N problems, each is internally coherent within its tool's categories.
The components compose into tool-auditing: before trusting a problem statement, ask which features would be invisible under a different tool, then broaden the inventory or introduce an external referent rather than reaching for more tool.
What It Is Not¶
- Not generic
bias. Bias is any systematic deviation in judgment; the law of the instrument is the specific claim that the tool inventory shapes perception of the problem itself — the world is re-carved into the tool's categories — a stronger and structurally distinct mechanism, not a catch-all skew. - Not
confirmation_bias. Confirmation bias selectively weights evidence toward a held belief; the instrument claim is upstream of evidence-weighting — features the tool cannot grip become perceptual non-events, so the problem is mis-framed before any evidence is assessed. - Not
cognitive_entrenchment. Entrenchment is an expert's deepening rigidity within one domain over time; the law of the instrument operates from the first use of a tool and at every scale (person, team, institution), with the tool placed upstream of perception regardless of expertise tenure. - Not
mental_model. A mental model is the internal representation a reasoner holds; the law of the instrument is the causal claim that the available tools (methods, instruments, doctrines) determine which problem categories are perceivable, treating the tool as the shaper rather than the model as a given. - Not
affordance. An affordance is what an environment offers an agent's action; the instrument claim runs the other direction — the agent's tool repertoire shapes what it perceives as a problem in the environment, not what the environment offers. - Common misclassification. Reading every over-use of a familiar tool as the law of the instrument. The pattern is perceptual (you see a nail because you hold a hammer), distinct from correctly selecting a hammer because the problem is a nail; only an external referent the tool did not generate distinguishes projection from veridical fit.
Broad Use¶
- Academic research: methodological monoculture, where a researcher's primary method (regression, ethnography, RCT, formal model) becomes the lens through which all problems are read, foregrounding method-amenable problems and dismissing others as out of scope.
- Software architecture: the golden-hammer anti-pattern, where a team that has mastered microservices reads every requirement as a microservices decomposition while a monolith-comfortable team reads the same requirement as a monolith feature.
- Military strategy and clinical practice: doctrinal lock-in, where armies trained on one doctrine recategorise engagements that resist it, and therapeutic monoculture, where pharmacology-, psychotherapy-, and family-systems-trained clinicians see different problems in the same patient with the same presentation.
- Consulting and pedagogy: a team trained on a particular framework (Five Forces, BCG matrix, Jobs-to-be-Done) carves every engagement through it, and curriculum, assessment, and classroom-management experts read the same underperforming school as different problems requiring different interventions.
- Public policy and engineering: the economist reads a policy question as price signals, the sociologist as power and structure, the lawyer as rights and procedures, and the mechanical, electrical, and software engineers see vibration, noise, and state problems in one device.
- Diagnostic medicine and statistics: the cardiologist, gastroenterologist, and neurologist see heart, GI, and nervous-system problems in one chest-pain patient, and the Bayesian, frequentist, and ML practitioner see prior-choice, test-construction, and feature-engineering problems in one dataset.
Clarity¶
Naming the pattern distinguishes three things everyday language collapses: the problem in the world, the problem-as-seen, and the tool used to see it. The default assumes the first and second are the same and the third is downstream; the law of the instrument inverts the flow — the tool shapes the problem-as-seen, which is then mistaken for the problem-in-the-world. The analyst is required to audit the tool-to-perception transformation before trusting the problem statement. The clarifying force is to make the tool a visible upstream cause of the problem statement rather than an invisible choice made after the problem is already framed.
The frame also distinguishes appropriate tool selection (choosing the hammer because the problem is a nail) from tool-shaped recognition (seeing a nail because you hold a hammer). Both produce the same behaviour — applying the hammer — and the difference is invisible without an external referent, so the prime's distinctive content is naming the second case as structurally distinct from the first. This matters because the two have opposite remedies: appropriate selection needs no correction, while tool-shaped recognition needs an external referent or a broadened tool inventory. A further clarity benefit is that the frame reorganises interdisciplinary work: when N experts read the same situation as N different problems, the meta-question is no longer "which expert is right?" (usually unresolvable) but "what is the union of the problems-as-seen, and how do we triangulate to the problem-in-the-world?" (structurally available).
Manages Complexity¶
The frame manages complexity by compressing what would otherwise look like a series of unrelated professional dysfunctions — methodological monoculture, doctrinal lock-in, therapeutic monoculture, framework over-application, disciplinary capture in interdisciplinary work — into one pattern: tool-shaped perception. The same diagnostic (audit whether the problem-as-seen is a projection of the available tool's categories) and the same intervention class (broaden the tool kit, introduce external referents, force category-translation exercises, practise problem-statement-before-tool-selection discipline) apply across all of them. The complexity absorbed is the appearance that each profession's blind spot is a local pathology, when each is the same capability-perception relation with a different tool inventory.
The frame also organises the two operations that follow from the relation. Tool-broadening enlarges the tool inventory to enlarge the perceivable subset of the world, so cross-trained agents see more categories of problem than mono-trained agents. Tool-bracketing temporarily suspends a tool to see what becomes visible when its categories are absent — approaching a problem "as if you didn't have your usual method" surfaces features the method was suppressing. The prescriptive content is tool-auditing: before trusting a problem statement, ask which features of the world-situation would be invisible if the analyst held a different tool. The portable interventions follow directly: audit the tool that named the problem; run cross-disciplinary problem-statement exercises where the variance across statements maps the tool-shaping; introduce external referents (ground truth, user behaviour, field data) that resist tool-projection; cultivate multi-tool fluency so cross-category checks are available; resist intensification responses, since applying a failing tool harder deepens the misperception, so switch tool rather than intensify it; and treat "we don't have that data" claims as a sign that the available tools cannot ingest a feature of the world that is nonetheless present.
Abstract Reasoning¶
The prime trains a reasoner to model the relation between a world-situation with multiple structural features, a tool inventory the agent possesses, and a problem-as-perceived that is the situation carved into the categories the tools can engage. The standard model wrongly assumes perception is veridical and the tool is selected to address it; the law of the instrument places the tool upstream as the shaper of perception, so problem statements are tool-projections, not world-readings. Two operations follow from the relation. Tool-broadening enlarges the tool inventory to enlarge the perceivable subset of the world, so cross-trained agents see more categories of problem than mono-trained agents. Tool-bracketing temporarily suspends a tool to see what becomes visible when its categories are absent, surfacing features the method was suppressing.
The prescriptive content is tool-auditing: before trusting a problem statement, ask which features of the world-situation would be invisible if the analyst held a different tool. From this the prime licenses several portable inferences. The reasoner learns to audit the tool that named the problem and to introduce external referents — ground truth, user behaviour, field data — that resist tool-projection and pull the perceived problem toward the world-problem. The reasoner learns to resist intensification responses: when the tool produces poor results, the default is to apply it harder, and the prime predicts this deepens the misperception, so the move is to switch tool rather than intensify it. The reasoner learns to read "we don't have that data" claims as a sign that the available tools cannot ingest a feature of the world that is nonetheless present. And the reasoner is given a structural reframing of interdisciplinary disagreement: when N experts read the same situation as N different problems, the resolvable meta-question is not "which expert is right?" but "what is the union of the problems-as-seen, and how do we triangulate to the problem-in-the-world?" — converting an unresolvable contest into a tractable triangulation.
Knowledge Transfer¶
The transferable content is the world-situation / tool-inventory / problem-as-perceived relation together with the two operations (tool-broadening, tool-bracketing) and the intervention catalogue (audit the naming tool, cross-disciplinary problem statements, external referents, multi-tool fluency, resist intensification). The role mappings are regular across human-practice substrates: the tool inventory maps to a method repertoire, an architectural style, a military doctrine, a therapeutic modality, a consulting framework, a disciplinary lens, a clinical specialty; the problem-as-perceived maps to a prediction problem, a microservices decomposition, an engagement category, a heart problem, a price-signal question; the external referent maps to held-out data, user interviews, field observation, ground truth.
The transfers are reuses of one capability-perception relation. A SaaS churn problem read by four teams as a prediction problem, a feature-gap problem, an onboarding problem, and a value-capture problem — each internally coherent and true within its tool's categories — is structurally the same as the cardiologist/gastroenterologist/neurologist triage of chest pain, the regression/ethnography/RCT triangulation in policy research, and the manoeuvre/attrition/counter-insurgency doctrine selection in military planning: the same world-situation projects to different problems through different tools, and seeing the projection as a projection is the prime's contribution. The load-bearing recognition that transfers is the perception-shaping direction — the claim is not that the tool gets over-applied (instrumental) nor that recall is biased (availability) nor that past investment locks in (sunk cost), but that the world is re-described into the tool's categories, a stronger and structurally distinct claim — and the remedy is always to broaden the tool inventory or introduce an external referent rather than to reach for more tool. The agent can be a person, a team, a profession, a discipline, an institution, or even a software system, and the structural relation between tool-inventory and perceived-problem-space is the same in every case. Because the pattern is inherently about cognitive agents with tool repertoires and carries the normative load of perceptual-bias-as-failure, the transfer runs across human-practice substrates — research, software, military, clinical, consulting, pedagogy, policy, engineering, diagnostics, statistics — and within that wide family the capability-shaped-perception relation and its intervention catalogue carry intact.
Examples¶
Formal/abstract¶
Diagnostic medicine supplies a sharp instance precisely because the world-situation is held fixed while the tool inventory varies across observers. A single patient presents with chest pain — one world-situation with multiple structural features (cardiac, gastrointestinal, neurological, musculoskeletal, psychological). Send the same presentation to three specialists, each holding a different tool inventory: the cardiologist's repertoire of stress tests, angiography, and ECG; the gastroenterologist's endoscopy and pH monitoring; the neurologist's imaging and conduction studies. The carving operation projects the situation onto each tool's engageable categories: the cardiologist sees a heart problem, the gastroenterologist a reflux problem, the neurologist a nerve problem — and each problem-as-perceived is internally coherent and genuinely true within its tool's categories. The upstream-tool placement is the structural insight: the tool is not selected after a veridical reading of the world but sits ahead of perception, shaping what registers as the problem, so features no specialist's instrument can grip become perceptual non-events. The diagnostic move is tool-auditing — asking which features would be invisible under a different tool — and the resolvable meta-question is not "which specialist is right?" (usually unresolvable) but "what is the union of the problems-as-seen, and how do we triangulate to the problem-in-the-world?" An external referent — a held-out biomarker panel, the patient's actual outcome — resists tool-projection and pulls the perceived problem toward the world-problem.
Mapped back: The chest-pain triage instantiates every role — one world-situation, three tool inventories, three internally-coherent projections, the tool placed upstream of perception — and the projection invariant (features no instrument grips become non-events) is what makes the union-and-triangulation move the structurally correct response rather than a contest over which specialist is correct.
Applied/industry¶
A SaaS churn problem read by four product teams is the applied instance and exercises the same relation in software organisations. The world-situation is rising customer churn with many structural features. Four teams hold four tool inventories and carve it accordingly: the data-science team (regression, classifiers) sees a prediction problem ("we need a better churn model"); the product team (feature roadmaps) sees a feature-gap problem ("we're missing capability X"); the design team (user research) sees an onboarding problem ("users never reach activation"); the pricing team (unit economics) sees a value-capture problem ("we're priced wrong for the segment"). Each problem-as-perceived is coherent and partly true within its tool's categories, and the intensification failure mode is predictable: when a team's tool produces poor results, the default is to apply it harder — a better model, more features — which deepens the misperception rather than correcting it, so the prime prescribes switching tool over intensifying it. The tool-broadening and tool-bracketing operations follow: enlarge the inventory so more categories of the churn become visible, and temporarily suspend the dominant method ("approach this as if we had no churn model") to surface what it was suppressing. The "we don't have that data" claim is read as a signal that the available tools cannot ingest a feature of the world that is nonetheless present — for instance, the qualitative reason customers leave, invisible to the prediction tool. The cross-disciplinary problem-statement exercise maps the variance across the four statements onto the tool-shaping itself.
Mapped back: The four-team churn reading is the same capability-perception relation as the chest-pain triage, with method repertoires as tool inventories and prediction/feature/onboarding/value-capture as the projected problems — the contribution being to see each projection as a projection and triangulate to the world-problem rather than reaching for more of any one tool.
Structural Tensions¶
T1 — Tool-shaped recognition versus appropriate tool selection (sign). The prime's distinctive claim is perceptual — you see a nail because you hold a hammer — but this looks identical in behaviour to correctly selecting a hammer because the problem really is a nail. The boundary is with veridical fit. The failure mode is projection over-diagnosis: treating every successful application of a familiar tool as a symptom of tool-shaped misperception, so genuine expertise is pathologised and the analyst churns through external referents to debunk a perception that was correct. Diagnostic: introduce an external referent that the tool did not generate — if the independent referent confirms the problem statement, the recognition was appropriate, not projected.
T2 — Broaden the inventory versus paralysing pluralism (scalar). Tool-broadening enlarges the perceivable problem space, but more tools means more candidate problem-framings, and past a point the agent sees every situation as N coherent problems with no basis to choose. Here the boundary is with analysis_paralysis. The failure mode is perspective sprawl: cross-training so widely that every problem dissolves into competing framings and no intervention is ever committed to, the mirror image of monoculture. Diagnostic: pair tool-broadening with a triangulation discipline (union of problems-as-seen, then converge via external referent) so added tools sharpen the world-reading rather than multiplying irreconcilable readings.
T3 — Switch the tool versus intensify it (temporal). When a tool produces poor results the default is to apply it harder, which the prime warns deepens the misperception — but sometimes the tool is right and the results are poor because the work is incomplete, so switching prematurely abandons a correct approach mid-execution. The failure mode is either intensification lock-in (hammering harder on a misperceived nail) or its mirror, premature tool-abandonment (switching away from a correct tool that just needed more iterations). Diagnostic: check whether poor results trace to the tool mis-carving the problem (switch) or to under-application of a well-matched tool (persist) — the external referent, not the result alone, distinguishes them.
T4 — One agent's inventory versus the team's union (scalar, local vs global). The frame applies at every level — person, team, profession, institution — but the tool inventory and its blind spots differ across levels, so an individually broad analyst can sit inside an institutionally monocultural unit whose shared tools carve the world identically. The failure mode is level-confined auditing: auditing one's personal tool repertoire while the binding monoculture is the team's or discipline's shared inventory, which individual breadth cannot see past. Diagnostic: locate the tool inventory that actually shaped the problem statement at the right level, and check for institution-wide projection (everyone reaching for the same method) separately from individual projection.
T5 — Problem-as-perceived versus an actually-absent feature (measurement). A "we don't have that data" claim is read as the tool failing to ingest a present feature — but sometimes the data is absent because the feature genuinely is not there, and treating every gap as a suppressed-perception artifact manufactures phantom problems. The failure mode is phantom-feature inference: insisting a tool is hiding a world-feature when the feature does not exist, sending the analyst hunting for a referent that confirms nothing. Diagnostic: before concluding the tool suppressed a real feature, seek independent evidence the feature exists; absence of data is a prompt to check, not proof of suppression.
T6 — Tool-auditing versus infinite regress (scopal). Stepping behind the problem statement to audit the shaping tool is itself done with tools, so the audit is shaped by the auditing repertoire — there is no tool-free vantage from which to read the world-situation directly. The failure mode is meta-tool naïveté: trusting the tool-audit as if it delivered the unmediated world-problem, when it merely substituted one projection for another. Diagnostic: ground the audit in external referents (ground truth, field data, user behaviour) that resist projection, rather than in a second analytic method — only a referent the tools did not generate breaks the regress, and even then only partially.
Structural–Framed Character¶
Law of the instrument sits on the framed side of the structural–framed spectrum, at aggregate 0.6 — past the midpoint toward framed, driven by one criterion at the maximum. The capability-perception relation underneath is fairly abstract and genuinely relational: a world-situation with multiple features, a tool inventory, and a problem-as-perceived that is the situation carved into the categories the tools can grip, with the tool placed upstream of perception. That relation recurs across research, software, clinical practice, military doctrine, and engineering, which gives the prime real breadth.
The criterion that lifts the aggregate is human_practice_bound at 1.0: the pattern is inherently about a cognitive agent with a tool repertoire — person, team, profession, institution, or software system — and capability-shaped perception has no meaning without an agent that perceives and holds tools, so it does not run in physical or biological substrates indifferently. The other four criteria sit at 0.5. vocab_travels: tool, problem-as-perceived, carving, and external referent travel across the human-practice substrates, but the framing leans on a cognitive-and-methodological lexicon (Maslow's hammer-and-nail is the home image). evaluative_weight is 0.5: the prime carries a mild normative load, reading tool-shaped perception as a bias-and-failure to be corrected, while conceding (T1) that the same behaviour can be veridical fit. institutional_origin is 0.5: cognitive-psychology origin, generalised across professional practice. import_vs_recognize is 0.5: invoking the prime imports a tool-auditing frame (step behind the problem statement, broaden or bracket the inventory, introduce an external referent) as much as it recognises a pre-existing projection. The relational core is real and moderately abstract, but the binding to a tool-holding cognitive agent is constitutive, correctly placing the prime just past the midpoint toward framed.
Substrate Independence¶
Law of the instrument is a strongly substrate-independent prime — composite 4 / 5 on the substrate-independence scale. Its domain breadth (5 / 5) is exceptional: Maslow's "if all you have is a hammer, everything looks like a nail" pattern recurs with the same force across scientific research (the methods one knows shaping which questions are asked), software engineering (reaching for the familiar framework), the military (fighting the last war with the available doctrine), clinical medicine (specialty-shaped diagnosis), consulting, pedagogy, public policy, and engineering. The structural abstraction (4 / 5) reflects that the core claim — a tool inventory re-carving the world's joints into shapes the tool can grip, so that ungrippable features become perceptual non-events — is a moderately abstract relational pattern about capability-shaped perception, sharper than generic bias because it acts on the upstream construction of the problem rather than the downstream verdict. The transfer evidence (4 / 5) is concrete across these fields: the pattern is named and documented independently in each (Kaplan's law of the instrument, deformation professionnelle, the streetlight effect, specialty bias in medicine), with the same diagnostic and the same remedy (broaden the inventory or introduce an external referent the tools did not generate) recurring rather than being analogized. What caps the composite below 5 is that every instance runs on a human-practice substrate: the pattern requires an agent with a tool inventory and a perceptual frame, so there is no physical or biological instantiation — capability-shaped perception presupposes a capable perceiver. Within the wide space of human-practice substrates, however, the pattern is recognized rather than imported wherever a held capability shapes what problems are seen.
- Composite substrate independence — 4 / 5
- Domain breadth — 5 / 5
- Structural abstraction — 4 / 5
- Transfer evidence — 4 / 5
Relationships to Other Primes¶
Parents (1) — more general patterns this builds on
-
Law of the Instrument is a kind of, typical Bias
The cross-batch note + the file both frame law_of_the_instrument as a bias, but a STRONGER, structurally-distinct one: the tool inventory shapes which problem is PERCEIVED (upstream construction), not just the downstream verdict. is-a bias, specialized to capability-shaped perception. The file: 'often filed loosely as a cognitive bias' — admit bias as parent while preserving the perceptual-upstream distinction.
Path to root: Law of the Instrument → Bias
Neighborhood in Abstraction Space¶
Law of the Instrument sits in a sparse region of abstraction space (87th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely rather than landing on a neighbor.
Family — Systems Thinking & Cybernetic Agency (15 primes)
Nearest neighbors
- Agency — 0.69
- Invariance — 0.68
- Gestalt Principles — 0.68
- Local Sequence Legality — 0.68
- Performativity — 0.68
Computed from structural-signature embeddings · 2026-06-14
Not to Be Confused With¶
The most important confusion to dispel is with generic bias, because the law of the instrument is often filed loosely as "a cognitive bias" and thereby flattened. Bias names any systematic deviation in judgment from a normative standard, of which there are scores. The law of the instrument makes a specific and stronger claim than mere skewed judgment: the tool inventory does not just tilt the verdict on a correctly-perceived problem — it shapes which problem is perceived at all, re-carving the world's joints into the shapes the tool can grip and rendering ungrippable features perceptual non-events. This is a claim about the upstream construction of the problem statement, not about a downstream distortion of an already-framed judgment. The distinction is load-bearing because the remedies differ: a generic bias is corrected by debiasing the judgment, whereas tool-shaped perception is corrected only by broadening the tool inventory or introducing an external referent the tools did not generate. A practitioner who treats it as ordinary bias will adjust weights on a problem that was mis-framed from the start.
The prime is also confusable with confirmation_bias, which is closer but still distinct. Confirmation bias is the selective seeking and weighting of evidence that supports a prior belief. The law of the instrument operates before evidence is weighed at all: it determines which features of the world even register as data. Where confirmation bias says "I over-weight evidence for what I already believe," the law of the instrument says "features my tool cannot ingest never become evidence in the first place" — the we-don't-have-that-data claim is read as a tool failing to ingest a present feature, not as biased weighting of available data. The two can compound, but the instrument claim is the deeper one: it shapes the input space confirmation bias then operates within. Conflating them sends the practitioner to police evidence-weighting when the real failure is that a whole class of features was never perceived.
A subtler confusion is with cognitive_entrenchment, since both describe a reasoner locked into a way of seeing. Entrenchment is specifically an expertise-and-time phenomenon: deep experience in one domain calcifies into rigidity, so the expert struggles to see alternatives. The law of the instrument is not tenure-dependent — it operates from the first acquisition of a tool, applies to novices and experts alike, and applies at collective levels (a team, a discipline, an institution) where no individual is "entrenched" but the shared tool inventory carves the world uniformly. Entrenchment is one path into tool-shaped perception, not the pattern itself. A practitioner who diagnoses entrenchment will look for an over-experienced individual to refresh, missing the institutional monoculture where everyone, junior and senior, reaches for the same method because it is the only tool the unit holds.
These distinctions decide the intervention. Framing the problem as generic bias debiases a verdict that was mis-framed upstream; framing it as confirmation_bias polices evidence-weighting when whole features went unperceived; framing it as cognitive_entrenchment hunts a rigid expert when the binding monoculture is the team's shared inventory. The prime's contribution is the perception-shaping direction — the world is re-described into the tool's categories — and its remedy: broaden the inventory or introduce an external referent, never reach for more of the same tool.
Solution Archetypes¶
No catalogued solution archetypes reference this prime yet.