I agree that policy and procedure writing needs all of these skills. But most of the policies and procedures I see (and have to improve) have defects in clarity, complexity, and cohesion.

Experience has taught me that policy and procedure writing should follow Plain Language principles. This means using:

- Simple words and sentences wherever possible
- A reading level appropriate to the intended audience
- High cohesion
- Active voice, unless passive voice serves a verifiable need
- Short paragraphs
- Bullet and number lists instead of comma separated lists
- Tables and other visual formatting techniques
- NO undefined acronyms

Courses can teach these concepts and skills to those who need courses. I think most technical writers can learn them through self-study and a LOT of practice. I have used Plain Language for over thirty years and only recently learned it is an international movement.

Also, combining Plain Language with Information Mapping can provide even better results.