Before adopting a practice from another era or scale…
When importing best practices or frameworks from another era or scale, explicitly verify that the contextual conditions (organizational size, technological infrastructure, market maturity) that made the practice optimal still hold before adopting it.
When This Fires
- Adopting a practice you read about in a case study or book
- Implementing a framework from a larger (or smaller) organization
- Importing processes from a previous role at a different company
- Any time "they do it at [company/era], so we should too" drives a decision
Common Failure Mode
Importing a practice because the source is prestigious: "Google does this" without asking "does Google's context match ours?" Prestige is not transferability. A practice that works at Google's scale, with Google's engineering talent pool, and Google's infrastructure may fail catastrophically at a 50-person company with different constraints.
The Protocol
Before adopting any practice from another era or scale: (1) Identify the practice and its source context. (2) List the contextual conditions that made it optimal: organizational size, technical infrastructure, team structure, market conditions, cultural norms. (3) For each condition: does it hold in your context? (4) Where conditions differ: adapt the practice to match your context, or choose a different practice. (5) Conditions that hold → the practice likely transfers. Conditions that differ → the practice needs modification or rejection.