Communication Policy
The rule is simple: discussion happens where the work lives, and the channel matches the content.
| Channel | Use it for |
|---|---|
| Slack | Contractor and internal engineering day-to-day: team channels, sprint coordination, technical discussion. |
| Discord | The CueLABS™ community — intern day-to-day, cohort coordination and open-source collaboration. |
| Linear / GitHub Projects | The work itself — issues, status, decisions about specific tasks. |
Email (@cuesoft.io groups) |
High-stakes communication: agreements, approvals, access requests, anything formal or sensitive. Per-engagement groups (e.g. cuehire-<client>@cuesoft.io) keep continuity when personnel change. |
| CueTA™ cohort communication, and discussion with client representatives in per-engagement groups — never credentials, never formal approvals. | |
| Meetings | Standups, sprint planning, monthly client reviews, escalations — with notes written back to the channel where the work lives. |
Expectations:
- Async by default; respect timezones between Lagos and the US.
- Respond within a reasonable working-day window; mark true urgencies as such, sparingly.
- Decisions made in calls or DMs get written into the tracker or channel — context trapped in a private thread is context lost.