Projects involve communication within and outside of the project team. The Project Manager is responsible for ensuring that the right communication happens.
Stakeholders (such as a client or key internal stakeholders) should generally address communication regarding the project to both the PM and Strategist. The team will also regularly interact with stakeholders via email or Slack.
The Project Manager is responsible for making sure that all inbound communication is answered promptly. For any communication that does not require a response from the strategist, the PM should respond within 24 business hours. They should request a follow-up from the Strategist for any questions/comments that are in the Strategist’s realm.
To provide prompter responses, the Strategist may also reply first if they see an email first. But it is formally the responsibility of the PM to ensure that a response gets sent.
Communication with non-project Stakeholders should be handled with a mixture of phone calls, emails, Basecamp communication, and sometimes client-specific communication platforms.
Every week, the PM should send two updates:
- An internal weekly update for the team via Asana
- For client projects, a client update via email or the stakeholders chosen communication method
The update should inform the relevant parties of the high-level project statuses and how we are tracking against our budgets and timelines. See
Hello Client Name, Hope you had a great week! Other miscellaneous chatter here. Last week, we... * Did a thing * Did another thing This week, we... * Will do a thing * Will handle that other thing Budget/Timeline Update [As appropritate to the project itself] We are at X hours out of our Y hour budget. The project is on schedule. The schedule is broken out below...
A good cadence for these is that the project manager should do a pass of all their projects on Friday, send the internal updates, and assemble the Client updates as a draft in Google Docs. They should share them with the relevant Strategists for review. Strategists should review the updates on Monday and provide any feedback so the updates can go to the client in the afternoon.
Basecamp/Asana Project Access
For internal projects, communication with stakeholders may also occur in Asana. For client projects this is not yet a practice we have, but we are working on a methodology to facilitate it.
We are still exploring the client access features of Asana. You can add the client as full members of the project, but that exposes all information and internal communication. For some clients this might be fine but most of the time it will make the team uncomfortable to know that anything they type in the project may be read by the client.
Some clients prefer to communicate on platforms like Slack, Trello, or Jira. For one-off projects we should almost never use client platforms for communication. Our project management rhythm is very precise and adding more platforms throws it off and creates more confusion than it prevents.
A benefit of Core Coverage is that we are willing to have our PM and Strategist also work within the client’s tools. This should never replace our tools, but should be alongside it.
The extent to which we will use their systems is dependent on the specific case and how the client is using it. If they have a fantastic Jira system set up that handles all their work really efficiently, we don’t mind putting our whole team in there. If they have a janky system that is rarely updated, we don’t want to get mixed up with it, since it could cause confusion.
When we do this, it does incur additional project management cost, as our Strategist and PM have to shuttle between different systems throughout the work day. This is often worth it for clients, as it saves them time having to be in Basecamp or translating an email. As a Strategist or PM please make sure that you communicate to clients the impact of working with their system, but also that we are happy to adapt to whatever works best and easiest for them and their team.