The answer, of course, is that knowledge also arises from doing an Activity - both knowledge of how to do the Activity efficiently and effectively, and also ancillary knowledge gained during execution. Both these forms of knowledge may be as important to your organization and to its clients as delivery of the expected outputs.
However, most organizations make a poor job of capturing, maintaining and re-using this knowledge, for several reasons. This is mainly because context is critical - without this, you get information (which just has a maintenance cost) rather than knowledge (which also has a business value).
The way forward is to ensure that you define, execute and manage Activities in such a way that knowledge, both execution-related and ancillary, is automatically captured and maintained. This is what HIM process modelling provides.
A HIM Activity has well-defined inputs and deliverables, but these can be updated during execution. The final Activity along with all its inputs/outputs are preserved as part of the Plan, which not only provides a human-friendly audit trail that forms a useful part of the knowledge base of the organization(s) concerned but can also be used as a template for future work.
A HIM Activity is a place to record not only the outputs expected by management, but also the way you produced them and any supporting artefacts - all in its proper context. This is a very different thing from the pure task-based approach of traditional project planning and workflow definition.
More about Activities in the next post. In the meantime, if you would like to try HumanEdj, visit http://rolemodellers.com/get_started to register for an account on the demo Web instance.