Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I think you are using a non-standard definition of institutional knowledge that begs the question in the rest of your posts.

The standard phrase "institutional knowledge" merely refers to knowledge and skills that are carried by members of the organization. This is often much more than what is formally codified into the processes and training materials. As such, it can lead to loss of capability when there is too much turnover.

You seem to be conflating it with some other kind of bureaucratic conservatism or group-think. While that is a common dysfunction of long-running organizations, I think it is an orthogonal characteristic.



> The standard phrase "institutional knowledge" merely refers to knowledge and skills that are carried by members of the organization.

Yes, that't is my definition. But, that knowledge has very real practical effects and influence on the org, from the weight (those with it usually are in position of seniority/power) and momentum that knowledge carries, especially when approaching new problems, or reconsidering old problems. The mechanism for that can be anywhere from "this is industry standard" to "the director says we should focus on this approach", with the ever present "lets not risk it".

> While that is a common dysfunction of long-running organizations, I think it is an orthogonal characteristic.

I agree that it's logically orthogonal, but not practically. I think the actual killer of orgs is the sum of all the small scale risk avoidance. I think risk is most easily avoided by adhering to the institutional knowledge (what was done and what is known). Innovation eventually becomes a completely foreign concept.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: