When you have worked with someone for a while it becomes easier to communicate as we can make assumptions about the nature of requests or intention behind statements they make.
However, in projects we are often thrown together with a new team of people and the need to become a cohesive delivery machine quickly is of paramount importance.
1/ Set expectations of the high level end game that the team is aiming to achieve. In 6prog projects this is easy as all of the freelancers hired can see the same outline and key deliverables.
2/ Regular meetings. We have a scrum every 48 hours. It’s so valuable to see if what was planned is actually achievable – and understood -before too much effort is undertaken. It means we can be more agile and change deliverables without major impact on timescales. Try out Teamretro to help your team retrospectives flow with ease.
3/ Commit verbal changes to writing. Within projects chat, simple status and notes can be made to confirm agreed steps within an engagement.
4/ Use the same language. Call a widget a widget and stick to it.
5/ Limit the number of locations where written conversations take place. I have found myself checking through multiple channels in slack, teams, WhatsApp, messages and then finally finding the relevant data was shared in another location to be the most troublesome ‘benefit’ of modern communications. There are so many practical comms channels, just choose a few and clarify for what purpose each is going to be used. 6prog will be using a Slack api for our projects soon!
6/ Utilise low cost collaborative project tools such as one Figura Associates demo’d to me recently. Figura have a free trial here
What is your tip for team communications?