Andrea Jones walks through a six-part communication template: message, purpose, channel, audience, owner, and timing. She shows how embedding it into agile sprints, like Execute Agility's bi-weekly reviews, makes teams "knock over the dominoes" as projects move forward.
Hi, I'm Andrea Jones, and anyone who knows me probably knows that I really like to take things that are otherwise subjective and squishy and maybe hazy and put some structure and some process around them. Makes them a little bit more straightforward, easier to understand, easier to implement. And one such area is truly around communication in a project. So first, I want to say I get it. You can't always tell everyone everything all the time. But what you can do is follow a bit of a process around communication. So in this article, we have a small template that tells you how to write a basic, straightforward communication plan. And then once you've written the plan, which includes what you're trying to say, What it's supposed to accomplish, the channel you're putting it out on, right? Is it a YouTube video? Is it an email? Is it on the newsletter? Are there posters? Are you just saying it verbally, or is it a meeting announcement? Who you're going to have be listening to it, the audience, who is giving that message, who might be developing it, possibly separate from the person giving the message, especially if it's Maybe supervisor waterfall communication. And finally, the timing of those things. And if you put that in a plan up front in a project, you can just knock over the dominoes as you go. If you're using Execute Agility, you absolutely can use the every other week end-of-sprint reviews to be your primary communication channel. And the process itself has the messages built into the review templates. Either way, put a little structure, a little expectations out there, and follow them. That's the easiest way to continue to communicate in a project. Thanks for watching.
