Communicating Project Updates To Teams

“Storytelling” gets thrown around A LOT in change comms. But it can be hard to know where to begin. One of the simplest places to start is the humble project update. 🧠 People remember stories up to 22 times more than facts alone. (I know, the irony that is a fact is not lost on me.) Let's take a standard project update as a 'before' example: “Phase 2 of the Optimise Programme is now complete. A new automated process has been implemented to improve data accuracy and reduce manual input.” Factually accurate but dull as sh*t. I practically fell asleep writing it. Here's the same message, but with a story – and a human: “It used to take me hours – now it’s sorted in the time it takes to make a coffee.” Roger, Team member, Finance Ops. Same project. Same outcome. But now it actually means something to the people reading it. So if you want to make your project updates more effective... start here: 1. Find the friction (or 'the villain', as I like to call it). What wasn’t working before? 2. Find a human voice. Ask someone involved (ideally an employee) to describe the difference. 3. Frame the change. Make it about real people, not phases, platforms or processes. Storytelling isn't about writing a novel... Just start with one real voice. That's it. Because a single quote beats a five-point milestone update. 👊 Find this useful? Give me half a day and I'll turn your change team into proper writers. -------- Sign up to ‘The Comms Nerd’ email, unlocking the neuroscience behind words, storytelling and behaviour change: https://lnkd.in/eDsS55KQ Download my free Change Comms Checklist for change colleagues: https://lnkd.in/eJQX_ZKy DM me to find out more about my comms, narrative & writing programmes and The Change Writing Workshop.

Your greatest advantage is not more time; it is the courage to decide what matters most. A powerful project manager does not treat every task as equally urgent. They identify the work that creates the highest value, protect critical resources, and act before small problems become major delays. You can lead several projects successfully when you create one trusted system. The moment your teams can see priorities, dependencies, risks, and progress in one place, confusion loses its power. Visibility creates confidence, and confidence creates momentum. 🎯 Build One Portfolio View Create a master list showing each project’s objective, sponsor, priority, budget, deadline, health status, and expected benefit. Review the portfolio as one connected system—not as separate islands. ⚡ Prioritize Ruthlessly Rank projects according to strategic value, urgency, risk, customer impact, and resource demand. When two projects compete for the same people, equipment, or budget, make the conflict visible and decide quickly. 📅 Integrate Schedules and Dependencies Use one master schedule to expose milestone conflicts and cross-project dependencies. Add capacity planning so overloaded employees are identified before performance drops. 📊 Manage Through a Dashboard Track schedule variance, cost variance, milestone completion, workload, risks, issues, and change requests. PMI’s 2026 research reports that approximately one-third of complex projects fail, while professionals who manage complexity effectively can increase the likelihood of success fivefold. 🔄 Review, Rebalance, and Escalate Hold a short weekly portfolio review. Do not discuss every minor detail. Focus on delayed milestones, budget pressure, resource conflicts, critical risks, and decisions requiring executive support. Reassign resources, revise priorities, or pause low-value work when necessary. 🚀 Turn Control into Competitive Advantage High-quality Project Management Templates & Dashboard give you a structured way to plan, prioritize, monitor, and report multiple projects without rebuilding every document from scratch. Gain faster visibility, stronger governance, and more professional reporting. Get the complete solution here: https://lnkd.in/dCGqF98z #ProjectManagement #MultipleProjects #PortfolioManagement #PMO #ProjectManager #ResourceManagement #ProjectDashboard #Leadership #Productivity #RiskManagement Disclaimer: Sometimes images may contain some errors in designing process, so please focus on content of this post and ignore the design errors. Thanks 🙏🙏🙏

How I Keep My Projects Visible (Without Being Pushy) as a Program Manager at Amazon Out of sight = out of mind. And if leadership doesn’t see your work, it might as well not exist. But constant pings can backfire. Here’s how I keep my programs visible…without being the annoying follow-up person: 1/ I give consistent, lightweight updates ↳ I send a weekly 3-bullet recap ↳ No one has to ask “What’s going on with that project?” Example: I drop a Friday update in our team Slack: “Program X update → 1. On track, 2. Waiting on review, 3. Launch planned for 6/7.” Takes 90 seconds…keeps everyone looped in. 2/ I show momentum, not just status ↳ “We fixed X” hits harder than “On track” ↳ Progress > process Example: Instead of saying “dev work continues,” I write “finalized backend logic, tested 3 edge cases, fixed validation bug.” Feels real. 3/ I speak in outcomes, not effort ↳ Leaders don’t care how hard you’re working ↳ They care what’s changing Example: “Reduced processing time by 48%” lands better than “held 4 syncs and updated timelines.” 4/ I give credit publicly ↳ I tag contributors in wins ↳ Visibility shared is visibility returned Example: I posted a launch update tagging the SDE who carried it across the line. That update got 3 exec reactions…and now she tags me back in her progress threads. 5/ I never escalate before communicating ↳ I message the owner first ↳ Then loop in leadership if needed Example: Before flagging a delay to leadership, I always check in with the owner privately. That respect builds long-term trust. The key to visibility isn’t noise…it’s clarity. What’s one way you keep your work visible without oversharing?

Your stakeholders don't need more status reports They need confidence in the plan. It's easy to think that sending MORE status updates will earn stakeholder trust → Weekly updates → Color-coded dashboards → Bullet point highlights galore The truth is: information alone doesn't build confidence. Leadership does. Stakeholders aren't just asking "where are we?" They're asking "are we in control?" They're asking "are risks being monitored/managed?" They're asking "will we hit X target?" If you just report progress, you're replaceable. If you LEAD the plan (+ manage the risks and clearly own), you become essential. Here's how you can shift from "status updater" to confident execution leader: ✅ Tell the story, not just the facts Connect updates back to goals. Make it clear how today's progress ties back to business outcomes. Add metrics to support the tale you're telling. ✅ Own the risks out loud Don't wait for someone to discover problems. And don't hide things just because they may not happen (yet). Surface risks early, brainstorm mitigation, and have it ready. ✅ Frame the path forward Every update should answer 3 things. "What are you doing?" "What's next?" "What's needed/in the way?" When teams know what to do and know when and how to ask for help (and that you'll deliver), you'll execute at a whole new level. Think ahead. Solve problems. Navigate the ship. If stakeholders see you doing this, they won't need daily updates to feel safe. They'll trust that you can run the show. PS: what's one thing you've done to build deeper trust with stakeholders? 🤙

PMOs don’t fail because of tools. They fail because of silence. Think about it: • A risk raised too late, when it’s already burning. • A sponsor left in the dark until the project derails. • A portfolio report that shows data but hides the real story. And then we wonder why trust is lost. Here’s the truth: A PMO’s biggest problem is not process. It’s relevance. Updates don’t move projects forward. Decisions do. PMOs spend their days in endless meetings collecting updates, recycling the same slides, and they wonder why nobody listens. The truth: Your value isn't in tracking activity. Your value is in keeping work moving and enabling decisions. A PMO that understands cadence, status, prioritisation, and communication becomes strategically valuable. Because it's not about "being busy." It's about creating the right decision at the right time. Here's what changes everything: Ask yourself ❓Are your meetings aligned to decision moments? ❓Does your status page make it obvious what to decide? ❓Can you defend why one project matters more than another? ❓Do you have the language to handle tough sponsor conversations? If not, here’s what I've learned works👇 1️⃣ Cadence That Works - Daily → unblock teams - Weekly → risks & dependencies - Fortnight → steering (decisions only) - Monthly → portfolio review 2️⃣ Status 1-Pager - Translate one status report into a 3-line business impact summary. - RAG + forecast - 3 highlights, 3 risks with owners - 2 decisions with options - Budget & benefits variance 3️⃣ Prioritisation Model - Score projects 1–5: Value, Fit, Urgency, Effort, Risk - Weight criteria based on strategic context - Transparent ranking sparks conversation, reduces politics Note: Politics and dependencies will adjust pure scoring 4️⃣ Communication & Scripts - Keep a “story bank” of real wins and failures to share with leaders. - Map influence vs interest - Message format: headline → so what → action → deadline - Prepare scripts for: scope creep, date pressure, resource gaps 🧩 Pro tip: Cancel any meeting that has no decision on the agenda. You'll gain instant credibility and protect leadership's time. 💼 Practice: Take 3 active projects. Score them with the prioritisation model. Does the ranking match your sponsor's gut feel? If not, you've found a valuable conversation to have. Don't try to tackle all four at once - that's overwhelming for anyone.Choose whichever foundation resonates most and give it a proper try. ______ ✳️ This is part 2 of 3 on mastering PMO In Action. Missed part 1? Check here: https://lnkd.in/dR7-89zm 👉 Save this cheat sheet! 👉 Want the full 15-item PMO Upgrade Guide with templates and scripts? Download it here: https://lnkd.in/dWgE53x2 ______ 👉 Need help on your PMO transformation? I’m Pierpaolo. I help ambitious professionals transform their career using AI applied to PMO and project leadership. Book a call with me: https://lnkd.in/dTNUPQwT

After my last post on automating 60% of T/PM work… My inbox exploded. So here it is— The exact AI prompt stack I use weekly as a Technical Project & Program Manager> 1// Weekly status report “Act as a TPM. Summarize these updates into a crisp weekly report. Include: key progress, risks, blockers, next steps. Keep it leadership ready.” 2// Meeting Notes → Action Items “Convert these meeting notes into structured outputs: Decisions made, action items, owners, ETA, and open questions.” 3// Executive summary (30-sec read) “Summarize this project update for executives. Max 5 bullet points. Focus on outcomes, risks, & business impact.” 4// Stakeholder specific updates “Rewrite this update for: 1. Leadership (concise) 2. Engineering (detailed) 3. Business (outcome-focused)” 5// Risk identification “Analyze this project update and identify potential risks. Include likelihood, impact, and suggested mitigation steps.” 6// Dependency mapping “From this data, extract all dependencies. Highlight critical ones and potential delays they may introduce.” 7// Follow up messages (that get replies) “Draft a polite but firm follow-up message for a delayed task. Make it actionable and hard to ignore.” 8// Roadmap narrative “Turn these bullet points into a clear roadmap narrative. Explain why this matters, what’s changing, and expected outcomes.” 9// Conflict framing “Two stakeholders disagree on priorities. Frame both perspectives and suggest a neutral resolution approach.” 10// Pre meeting brief “Summarize everything I need before this meeting: Context, key discussion points, risks, and decisions required.” Real shift? T/PMs who use AI → focus on thinking T/PMs who don’t → stuck formatting updates I repeate ...AI will NOT replace T/PMs But T/PMs who use AI will replace those who do NOT. If you found this useful> Repost so other T/PMs can save hours every week —The Ordinary TPM

Every PM knows watermelon status reports are no good in project management. Those status reports where everything seems fine until it’s not. They usually happen when PMs try to keep things “positive” so they don’t upset stakeholders. But the truth is most stakeholders also don’t know what to do with brutal honesty. It’s a balance. I remember 7-year-old me who once wrote an essay about my family. Describing my dad as tall and slim. And my mom as short and fat. Ouch. 😅 Too much honesty can sting. Not enough transparency can destroy trust. So how do you strike the right balance when reporting project status? 1. Keep it short and necessary. Not every detail matters. Focus on what drives action or clarity. 2. Highlight wins. Celebrate progress and recognize the team. It keeps morale high. 3. Call out critical risks clearly. List them in order of urgency and impact. Greenwashing only delays pain. 4. Provide context and possible solutions. Stakeholders respect PMs who come with both problems and a path forward. 5. Be clear where support is needed. Don’t assume leadership will jump in. Tell them how they can help. 6. Set the rhythm. End every update with when the next one will come as predictability builds trust. A great PM doesn'’t just report what is. They focus on what matters with the right tone.

15 years into delivery leadership, I learned this the hard way: The executives who demand weekly status updates are the ones who don't understand the work. The ones who matter? They ask one question: 'What's blocking you?' I spent years perfecting 50-slide decks. Zero impact on outcomes. Then I flipped the script. Instead of reporting progress, I started flagging friction - budget constraints, cross-functional misalignment, resource bottlenecks. The moment I shifted from update cadence to obstacle removal, CXOs started calling me directly. Here's what changed: → Fewer meetings, clearer decisions → Stakeholder trust tripled (because I was solving their problems, not mine) → Delivery timelines improved 30% (no data loss chasing perfect communication) The best stakeholder managers aren't great communicators. They're great problem solvers who communicate strategically. Your status reports aren't your value. Your ability to unblock the business is. #DeliveryLeadership #StakeholderManagement #ExecutiveAlignment #Stakeholder #ExecutiveLeadership #ProjectDelivery #ProgramManagement #Crossfunctionalcollaboration #Leadershipmindset #ProjectManagement #ITOperations

Our contract manufacturer was rapidly falling behind schedule. The breakthrough was a wall, some Post-it Notes, and a phone camera. My client was moving an FDA-approved device into manufacturing. A $100M payment hung on hitting formal milestones. Every week, we reworked a 1,000-line project plan, only to wait days for our CM to approve the changes. The update process itself was unworkable for the CM's project manager. Every change meant chasing sign-offs across departments. So I offered him something smaller than what he already did. ✔️A board at his plant with all the tasks. ✔️ To do, in progress, done. ✔️ Move a note, take a photo. ✔️Text it to me. No more status emails. It was faster than the schedule updates he already wrote. It needed no sign-offs. All the time wasted on schedule updates and on talking about schedule updates now went into project work. Focusing both teams on driving the critical tasks and not worrying about when they would be done is how the team started crossing tasks off the list. My client met its manufacturing transfer goal. Milestone payment achieved. The CM kept the method and rolled it out to all their clients. Adoption isn't a willpower problem. People adopt the new way when it costs them less and gets them more than the old way. Processes with wasted work drain your team and slow the project. 💬 What waste could you remove from your process? Follow ➕ Chris Danek for more on medtech development and startups.

🚨 𝗦𝘁𝗿𝘂𝗴𝗴𝗹𝗶𝗻𝗴 𝗽𝗿𝗼𝗷𝗲𝗰𝘁𝘀 𝗼𝗳𝘁𝗲𝗻 𝘁𝗿𝗮𝗰𝗲 𝗯𝗮𝗰𝗸 𝘁𝗼 𝗮 𝗰𝗼𝗺𝗺𝗼𝗻 𝗿𝗼𝗼𝘁 𝗰𝗮𝘂𝘀𝗲: 𝗪𝗲𝗮𝗸 (𝗼𝗿 𝗮𝗯𝘀𝗲𝗻𝘁) 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗿𝘂𝗹𝗲𝘀. When 𝘦𝘷𝘦𝘳𝘺𝘵𝘩𝘪𝘯𝘨 feels urgent, nothing moves forward with clarity or logic. That’s why strong programs and PMOs anchor around a 𝗽𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗿𝘂𝗯𝗿𝗶𝗰, built early, not reactively. A clear rubric gives you: ✅ Consistency in chaos ✅ Fact-based decision-making ✅ Faster, defensible tradeoffs when pressure hits Here’s how to build one that sticks 📈 𝗦𝘁𝗮𝗿𝘁 𝘄𝗶𝘁𝗵 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗶𝗺𝗽𝗮𝗰𝘁, 𝗺𝗮𝗴𝗻𝗶𝘁𝘂𝗱𝗲, 𝗮𝗻𝗱 𝗽𝗿𝗼𝗯𝗮𝗯𝗶𝗹𝗶𝘁𝘆. • Does it affect multiple business units? • Can you quantify the financial or operational impact? • Is there a feasible workaround?    ♻️ 𝗥𝗲𝘃𝗶𝘀𝗶𝘁 𝗰𝗼𝗻𝘀𝘁𝗮𝗻𝘁𝗹𝘆. 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗻𝗼𝘁 𝗮 𝗼𝗻𝗲-𝗮𝗻𝗱-𝗱𝗼𝗻𝗲 𝗲𝘅𝗲𝗿𝗰𝗶𝘀𝗲. • When markets shift, priorities shift. • When new information is presented, reassess the severity. • Force rank within each prioritization level.    ⚓ 𝗖𝗵𝗮𝗹𝗹𝗲𝗻𝗴𝗲 𝘁𝗵𝗲 𝗯𝗹𝗶𝗻𝗱 𝘀𝗽𝗼𝘁𝘀. 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘇𝗮𝘁𝗶𝗼𝗻 𝗶𝘀 𝗼𝗻𝗹𝘆 𝗮𝘀 𝘀𝘁𝗿𝗼𝗻𝗴 𝗮𝘀 𝘁𝗵𝗲 𝗱𝗲𝗯𝗮𝘁𝗲 𝗯𝗲𝗵𝗶𝗻𝗱 𝗶𝘁. • Map upstream/downstream impacts. • Recommend tradeoffs, not just surface issues. • Document the decision 𝘢𝘯𝘥 the why behind it.    Projects don’t fail because teams don’t care. They fail because they care about 𝗲𝘃𝗲𝗿𝘆𝘁𝗵𝗶𝗻𝗴 equally. Build your rubric. Anchor your focus. Deliver with purpose. 👉 If your projects feel like they’re spinning, start by redefining what truly matters. Build your prioritization rubric before you need it.