5 ms·

This was great. I wrote some thoughts on a subset of what is discussed in this article, the knowledge moat: How to Make a Good Secret Sauce: https://medium.c

This was great. I wrote some thoughts on a subset of what is discussed in this article, the knowledge moat: How to Make a Good Secret Sauce: https://medium.com/swlh/how-to-make-a-good-secret-sauce-8773cd0216ce?source=friends_link&sk=0e8451d9e935ca23dc4838ecdc5148fe https://medium.com/swlh/how-to-make-a-good-secret-sauce-8773... And follow up: Product Market Crossfit: https://medium.com/@b.essiambre/product-market-crossfit-c09b019188f3?source=friends_link&sk=5a57eddd18dd948ebb512afb40a21667 https://medium.com/@b.essiambre/product-market-crossfit-c09b... I'm not sure I do a good job of laying out my thoughts. I'm interested in feedback.

petra 7y ago
I like the idea of complex knowledge being protected in code. But what happens when a key employee leaves for a competitor ?
- BenoitEssiambre 7y ago
  Well, key employees are a weakness of knowledge moats since some of the knowledge gets embedded in them. This might explain why people are paid well in knowledge industries, to prevent them from leaving. The part of the knowledge that is embedded in code usually doesn't leave with employees. This might be an important advantage for software companies, a lot of the expertise gets embedded in the software platforms.