Low-Tech Strategy
Updated 2026-08-10
INTRODUCTION
English translation pending.
CORE DEFINITION
Deliberately selecting low-tech or no-tech solutions instead of over-engineered ones. The core claim is that technology is never the goal; solving the real problem is. Sometimes paper and pen beat software, and face-to-face conversation beats video meetings, so the simplest adequate tool should always be tried first and upgraded only when it fails.
SCAFFOLDING EFFECT
Reduce cognitive load
- Tool discipline: ask whether each technology truly serves the problem or only flatters the maker's ego - Simplicity first: try paper, whiteboards, or face-to-face talk before buying any software - Escalation gate: upgrade technical sophistication only after the simple option demonstrably fails
Anchor fast decisions
Choosing low-tech removes the hidden costs of complex tools: learning curves, maintenance, dependencies, and failure modes. Simpler tools have fewer parts that can break and less cognitive overhead, so effort flows directly into the problem itself. Complexity is justified only when the simple option demonstrably cannot meet the requirement.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Low_technologyverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS