Chapter from: "Mapping Workflows and Managing Knowledge: Capturing Formal and Tactic Knowledge to Improve Performance"
Published by:
Business Expert Press
Length: 38 pages
Share a link:
https://casecent.re/p/116426
Write a review
|
No reviews for this item
This product has not been used yet
Abstract
This chapter is excerpted from ‘Mapping Workflows and Managing Knowledge: Capturing Formal and Tactic Knowledge to Improve Performance'. This is a book that does what the title says, and is different from most business process mapping information in three key ways. First, it lets users capture all the knowledge that goes into a workflow in any kind of organization, including the most difficult kind of all, the tacit knowledge people bring to the job and carry in their heads. Second, it is simple, powerful, flexible, and easy to learn. Third, it does not require installing, learning, and applying a complicated program (sometimes requiring reorganization to support the software rather than the software supporting the organization). It was developed by the author in a fifteen-year long program of studying, analyzing, and improving avionics maintenance processes for the US Navy and the Royal Canadian Air Force, and then applied to organizations of all kinds ever since, for more than two decades. It has been taught and applied by the author and others in many short courses. It works.
About
Abstract
This chapter is excerpted from ‘Mapping Workflows and Managing Knowledge: Capturing Formal and Tactic Knowledge to Improve Performance'. This is a book that does what the title says, and is different from most business process mapping information in three key ways. First, it lets users capture all the knowledge that goes into a workflow in any kind of organization, including the most difficult kind of all, the tacit knowledge people bring to the job and carry in their heads. Second, it is simple, powerful, flexible, and easy to learn. Third, it does not require installing, learning, and applying a complicated program (sometimes requiring reorganization to support the software rather than the software supporting the organization). It was developed by the author in a fifteen-year long program of studying, analyzing, and improving avionics maintenance processes for the US Navy and the Royal Canadian Air Force, and then applied to organizations of all kinds ever since, for more than two decades. It has been taught and applied by the author and others in many short courses. It works.