A few days ago, I was on a call where we were discussing the status of each person's projects and ideas. One individual was visibly upset because their project wasn't progressing as quickly as they had hoped. The reason? The people they were relying on weren't being as reactive as needed. The facilitator had a brilliant approach to this situation. Instead of letting the person dwell on the lack of support, they suggested looking at the story from a different angle: rather than waiting for others to take action, why not drive the action yourself? Don't just stop at proposing ideas; take the lead and make them happen. And this is especially important when the project is important for you, but for the other party it’s just one more thing to do on their plate, and maybe not even a top priority. When you’re telling yourself the story of “they don’t care about this important project”, don’t forget to consider the story from their shoes as well. Also, way too often we tend to...
I was working with one of my peers on a new project that she was taking over - and she was really confused about the project charter, status report, and the workflows they were trying to build with the project in order to achieve its goals. So I spent some time to explain her how all these terms and concepts work together in order to ensure she focuses on the right things with the right people. So if you’re new to project management, you might hear terms like "documentation," "processes," and "deliverables" thrown around. They can sound confusing at first, but don’t worry—they’re just different pieces of the puzzle that help make a project successful. Let’s break them down in plain language so you can see how they’re different and why they matter. What is Project Management Documentation? Think of project management documentation as the paperwork or files that act like a guidebook for your project. These are the written plans, notes, and records that tell ...