3 ms·
Totally. A company that doesn't want to pay attention to why they do things a certain way, and keep evolving it, doesn't care to grow, or stay in business. Too
by j45 14y ago
Totally. A company that doesn't want to pay attention to why they do things a certain way, and keep evolving it, doesn't care to grow, or stay in business.
Too often, excuses from a site like http://www.yourlogicalfallacyis.com http://www.yourlogicalfallacyis.com sums up why an organization doesn't maintain enough documentation of their business and the knowledge contained with it, and it's free to just walk out the door.
- philwelch 14y agoNow that's a little harsh. The fact is, every company where I've seen the internal wiki go stale is also a company that is otherwise incredibly successful. Though important processes were also documented by some additional formal process, and the wiki was a lower-priority thing anyway. Or at least, important wiki pages seemed to be better maintained.
- j45 14y agoDidn't mean to be. I've observed with clients while systemizing their businesses: In the long run in those who don't keep it a priority to document, improve and transfer their knowledge capital regularly, peak out, stall and fade. By failing to bake into the bread of their culture that understanding and sharing the why to do things a certain way.. maintaining their competitive advantage, they inevitably are exposed to becoming less effective, productive, efficient, ultimately welcoming a culture of accepting less and less. It's also probably worth noting that I'm not talking about creating a mistake manual, but rather a why manual that helps teach the mindset that creates the types of mindset required to make decisions to grow the business Businesses that become institutions do so with cultivating a a 50 to 100 year mindset, but few have a 10 year mindset to take what we do today and make sure it's happening while we find the next way to grow.
- philwelch 14y agoI don't think we disagree. Maybe you work with smaller and younger businesses than I've been employed in, because in my experience there's always SOME means of formal documentation, with the wiki as an optional layer on top of that. Or else, a really uneven wiki with some well maintained pages (generally the ones you actually need more often) and some stale data.