Communicating Internally

Urgent Communications

Urgent communications need to be communicated speedily and clear. This document might help you get in contact with a Codeweavers individual if there’s an urgent matter.

Anything urgent, don’t wait on an email or Slack, if you can talk in person or by phone. If the person you need to speak to isn’t available consider if there is someone else you can talk to.

Methods of communicating internally

Email

• If you have just started with us, our infrastructure team will have set you up with a business email account.

• You hopefully have added your Codeweavers email signature ????. 

• If you see an email from Codeweavers please avoid putting it in the trash (unless it really isn’t relevant to you)! 

• Try and keep up to date with your emails, there maybe something important in your inbox!

• Consider that some people in the business may not use Slack so it’s always worth sending them a quick email if you haven’t had a response through Slack. 

Slack

• When posting on Slack, please remember that you can’t search through historic posts so it’s not the right channel to use if you want someone to refer back to your post.

• There are many Slack channels you can join at Codeweavers. 

• If you are creating a channel consider why  you are doing it and who should be involved. 

• Using @channel. If you want everyone in a particular channel to be notified and see your post please add @channel. Only use at @channel if it’s really important. Think about it like this, if you have an announcement do you shout about it across the office as that is what you are basically doing in Slack.

• Consider what the topic of your post/announcement and add it to the relevant channel.

• Announcement channel. Only post in this channel if you have a post that is relevant for the whole company and everyone needs to know about it.

• Direct messaging. Is great when you need to send a message to an individual or multiple people without having to create a group.

Internal Blog

• The internal blog is a place where everyone in the business can see what we are working on and to view details of started, ongoing and completed projects.

• The aim of the internal blog is to be the go-to place for info on any project, service or business update. If you or your team are working on an update, MMF or Epic, come and have a chat with the design and marketing team so we can add it onto the blog.

• When you want to add a post to the internal blog, please complete the following template here.

• Once we have got into the swing of adding projects to the internal blog we will be exploring other areas such as adding a technical space, an area HR, guilds etc.

Business Updates

• Business updates happen every quarter. It's your opportunity to find out what’s going on at Codeweavers from the Directors. It’s really important to attend business updates to understand the bigger picture.

Demos

• Demos take place on a weekly basis on a Friday. If there’s company/team updates these get mentioned along with the different projects people have been working on. If you would like to demo anything you can add your update here. Alternatively you can search through previous demos to.

In person

• If you want to get a speedy answer from someone there and then in person is also the way. 

• If it’s not urgent, the person you are speaking to might not appreciate being interrupted if they are in the middle of something important. Consider what they are doing and the urgency.

• If you are unsure who the person is you need to speak to Natural HR is very handy to put names to faces!

Standup

• Many of the teams have daily or weekly standups. Feel free to get involved in the ones you think are relevant to you or create your own!

Phone

• If someone is on the road, it maybe sales staff or someone from your team on the road to a meeting if you need them give them a bell. Try not to ring people when they are on holiday or outside of their working hours. You can find members of the business phones numbers here.

Conference call

• If you need to speak to a few members of the team who aren’t in the office, setup a conference call via JoinMe. You can find the details to login in KeePass.

Zendesk

• If you are involved in a ticket or have spotted an issue with a Codeweavers email support@codeweavers.net and this will go straight into our ticketing system Zendesk.

Communicating Projects Internally

Quoting a project - Sales and Account Managers

• When quoting for a project, let the design and marketing team know so we can see how we can help. It also makes us aware of things to come that we may need to communicate.

Starting a project - Product Owners

• When starting a project please let the design and marketing team know so we can plan the launch of the project (if required). We need to know who is involved in the project, the project details and how long it will roughly take.

Project soon to be live - Product Owners

• Let the design and marketing team know so we can update the relevant individuals. We can also put our plans in place for any external communications.

Project is live

• Who needs to be informed externally

Emailing Internally

• Email signature - automated

• Email Signature - manually inputted

• The do’s and don’ts

• Use of Imagery

Product Communications Internally

• Product communications overview

• Methods of communication 

• Product launch

• Product update