|
Read time: 5 minutes Hey Subscriber First Name, This week: the voice in your head that ruins more projects than any missed deadline, a communication framework stolen from a trillion-dollar industry, and a free cheat sheet that'll give you 2 hours back every week. Let me start with something I don't think we talk about enough. There's a voice in your head. It's not the one that reminds you to send the status update or chase the action log. It's the other one. The one that says things like: "No one reads my updates." "I spend hours on decks that nobody opens." "I escalate issues and they just die in senior meetings." "The goalpost moves every meeting but the deadline doesn't." You've had at least one of those thoughts this month. Probably this week. So has every other project manager, leader, and entrepreneur reading this right now. That voice is universal. It's not a sign you're failing. It's a sign you care about doing the work well and you can feel the gap between the effort you're putting in and the impact it's having. So let's talk about that gap. Because it's not a performance problem. It's a communication problem. And the research backs it up. The numbers are brutal. PMI estimates that US$75 million of every US$1 billion spent on projects is at risk due to ineffective communication. Not bad planning. Not technical failures. Communication. And project managers spend 75 to 90% of their time communicating. That's almost the entire job. So if communication is most of what you do and it's also the thing most likely to sink your project, why does it still feel like nobody's listening? Because you're reporting. You're not telling a story. Here's what I mean. Most project updates read like a list of facts. Milestone hit. Risk raised. Budget on track. RAG status green. It ticks the box. But it doesn't land. Nobody walks out of that meeting thinking differently. People retain information far better when it's delivered as a story. Research published in the Quarterly Journal of Economics found that the impact of statistics on beliefs fades by 73% within a day, while the impact of a story fades by only 32%. That's a massive difference. It means more than half of your carefully prepared data points are gone from your audience's memory by the next morning, but the story you told is still sitting with them. But the decision to support your project, to fight for your budget, to back you when things get difficult, that doesn't come from a RAG status. It comes from the story. So let's look outside our industry for a moment. There's a discipline that has spent decades figuring out how to communicate with people in a way that moves them to act. It's called marketing. And it's a $1.14 trillion industry. The best marketers in the world don't start with what they want to say. They start with who they're talking to, what that person cares about, and what story will make them feel something. Then they deliver. That's why you remember certain adverts from years ago but can't recall last week's project update. Seth Godin puts it simply in This is Marketing: "Each person has a narrative in their head, used to navigate the world. The extraordinary thing is that every person's narrative is different." Your audience isn't ignoring your update because they don't care. They're ignoring it because it doesn't connect to the narrative already running in their head. Marketing has known this for decades. They've built entire frameworks around it. AIDA (Attention, Interest, Desire, Action) has been used since the 1900s. StoryBrand by Donald Miller teaches businesses to make the customer the hero. PAS (Problem, Agitate, Solve) is behind almost every piece of copywriting you've ever read. These aren't gimmicks. They're proven, repeatable systems for making people listen and act. So I studied them and asked: why don't we have something like this in project management? I took the best of what marketers do and adapted it for how PMs communicate. I call it the CRAFT Framework. The CRAFT Framework C - Cut to who matters. Marketers never write for everyone. Neither should you. Identify the three to five people who actually need to hear this. Your project director. Your senior stakeholder. Your team lead. Everyone else is secondary. R - Read their world. What is this person worried about right now? What does success look like from their seat? Your project might be about delivering a platform migration, but your senior stakeholder's story might be about proving the investment was worth it. If you don't understand their world, your message won't land in it. A - Angle from their story. Most PMs communicate outside-in: what we did, how we did it, then maybe why it matters. Flip it. Start with why it matters to them. When your opening line connects to something your audience already cares about, everything after it lands differently. F - Frame it as narrative. Facts inform. Stories move people. Instead of "milestone delivered on time," try "the team hit a wall on Thursday, found a way through by Friday, and the deliverable shipped on schedule." That's the real story of your project. If you don't tell it, nobody will. T - Tell them what you need. What do you need from this person? A decision? A resource? Their support? Say it. One ask. Front and centre. If they walk away without knowing what you need, the communication failed. Let me show you the difference. Without CRAFT: "Project is on track. Migration completed for Phase 2. Two risks flagged. Budget at 92%. RAG status green." Your project director skims it, nods, and forgets it before their next meeting. With CRAFT: "Sarah, I know you need to show the programme is delivering. Here's where we are. Phase 2 of the migration is done. The team hit a blocker mid-week that could have pushed us back three weeks. Instead, they found a workaround in 48 hours and shipped on schedule. We're sitting at 92% of budget with two risks on the radar, both manageable if we act now. The one thing I need from you is ten minutes at Thursday's steering committee to help us clear those two risks before they become blockers." Same project. Same week. The first one reports. The second one lands. CRAFT works for status updates, steering committees, emails to senior leadership, one-to-ones with your team, and any situation where you need someone to listen, understand, and act. MAKING IT HAPPEN: Your Weekly Strategy Pick one communication you're sending this week, a status update, a steering committee paper, an email to a key decision-maker, and run it through CRAFT before you hit send. Cut to who matters. Read their world. Angle from their story. Frame it as narrative. Tell them what you need. One communication. Five steps. See what changes. CRAFT + AI: Your Ready-Made Prompt Think of this as training wheels - it'll get you moving, but the real growth comes when you can do this naturally without the prompt. Copy this, fill in the brackets, and paste it into any AI chatbot: "Act as a senior project communication advisor. I'm writing a [status update / steering committee paper / stakeholder email] for [audience]. Their main concern right now is [their concern]. Rewrite my draft using the CRAFT framework. CRAFT stands for: C - Cut to who matters: identify the three to five people who need to hear this and focus the message on them. R - Read their world: understand what they're worried about and what success looks like from their seat. A - Angle from their story: lead with why it matters to them, not what we did. F - Frame it as narrative: turn facts into a story with tension, resolution, and impact. T - Tell them what you need: end with one clear ask they can act on.
Context: [paste your draft or bullet points]. Present as: a concise, story-driven communication no longer than [length]. Keep the tone professional but human." New this week: AI Meeting Prompts - a free cheat sheet to help you get the most out of your meetings and save up to 2 hours each week. If this landed with you, forward it to someone who's trying to grow in their role. That's how this community grows. bilaljamil.com | Newsletter archive | Hit reply to share your thoughts Take care and speak soon, Bilal
|
