Tools need a context of use

Over and over you see people building tools for people other than themselves that are terrible. Similarly, the best tools are often built by practitioners. One way to interpret this is the YC-ism “build the thing you want.” Another way is for the tool builder to have a context of use while building the tool.

Processes and practices are like tools in this respect. Many people develop processes and practices in the abstract (see: McKinsey and academic management and finance.)

Another situation is that people develop a really specialized tool for their exact context (which is great) but then abstract it to be the right tool for every other context. Something something hammer something something nail. Western thinking seems particularly bad at context-dependent answers