Internal Communications Flow

From Noolaham Foundation
Revision as of 05:19, 27 June 2020 by Natkeeran (talk | contribs) (Created page with "Noolaham Foundations seeks to build an open, positive, collaborative, respectful atmosphere for all staff and volunteers. Noolaham Foundation seeks to be a self-archiving, le...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

Noolaham Foundations seeks to build an open, positive, collaborative, respectful atmosphere for all staff and volunteers. Noolaham Foundation seeks to be a self-archiving, learning organization. Open communication and transparency are key to these goals.

All of Noolaham Foundation meetings must be pre-announced on respective process or project email threads, with reasonable notice period. Summary of all meetings should be shared via email or slack.

Sector Lead/Project Co-Ordinator and/or their Department Manager, and/or Chief Operating Officer must always be present at the meeting. The Chief Operating Officer must be present in all meetings where a job assignment/change or a priority establishment/change is needed. It is not mandatory for COO to attend technical advisory process/project meetings. However, the sector lead and/or department manager must be there and notify the summary of discussions in the slack thread or via email.

Use official channels for internal communications: Process/Project email threads, slack channels, wiki, document management system (Google Docs), website, and GitHub repository.

Do not use WhatsApp, use Slack instead. Avoid creating email threads outside of processes and project email threads. It is recommended that regular policy discussions happen face to face during the Governance Board meetings, rather than through drawn out email thread discussions. Staff can prepare background information.

For work related matters, volunteers should avoid communicating with staff outside of the following official meetings.