I would stop and ask yourself why you want a "communications process". I would look at all your processes (ie how you set strategy, produce goods and deliver services, what you do to enable that to happen), and define: (a) what has to be communicated to others at each step, and (b) what information has to be obtained from someone else to allow the person responsible for that step to carry it out. That is communication - and it happens all through normal operations. [It is easier to define when you use a deployment flowchart approach, since you can show who is involved in each task, including customers and suppliers] I don't believe that "communication" has to be a separate process.