We obey other U. S. traffic rules too. We try to comply with I.R.S. rules if we understand them.
Some of the rules we make for ourselves; some are imposed upon us, outside our control.
In any enterprise, some business rules result from corporate or strategic policies or operating policies. These are INTERNALLY imposed rules.
Examples of EXTERNALLY imposed rules would be OSHA, EPA, IRS regulations, etc., that are outside the control of your enterprise, and also changing from time to time.
Similarly, you could think of a plethora of rules, both internally imposed (such as your own product design with a wide array of operable configurations and therefore, by implication inoperable configurations that your manufacturing division is incapable of building; and externally imposed rules such as EPA, OSHA etc.
Or, seemingly simple business processes which become a nightmare for your people to implement, because the processes, from time to time require additional expert knowledge to implement.
and querying a database NOT situated in close proximity....
and reading a document in a given word processor, while ensuring compliance to internally and externally imposed rules....
and dash off a well-written memo draft in a different word processor type for you to review....
you would love to see how Knowledge Processing and Information processing depend on each other, won't you.
Now, think of your own criteria. How many different problems like the above need to be solved in your organization immediately .
If you are unable to think of any, Knowledge Processing is NOT for you.
Otherwise Knowledge Processing IS for you.