Most people spend all their energy listing what's in, and skip what's out. That's backwards. Nearly every scope fight starts with something one person assumed was included. Naming what's OUT is how you prevent that fight before it starts. Rough guide: for every few things you list as in scope, name at least one clearly out of scope. Four examples, and a caveat before you read them: these are just examples, not rules. On your project, some of what I've marked "out" below could easily be "in." The split isn't fixed, it's agreed. The point is writing it down and agreeing it up front, whatever the split ends up being for you. Systems upgrade project: in scope is migrating existing data into the new system. Out of scope is rewriting the reports that sit on top of that data. Software development project: in scope is building the agreed features for this release. Out of scope is fixing bugs in older parts of the system, that's handled separately. Construction project: in scope is building the structure to the agreed drawings. Out of scope is fitting out the interior once the structure is up. Manufacturing project: in scope is installing and testing the new equipment. Out of scope is training the operators who'll run it day to day. Question: what's the one thing you wish you had marked "out" on a past project?

🚨⬇️⬇️⬇️🚨 Welcome. This is a community, so let's start it like one. Do this one thing before you explore anything else. Your first step: start one challenge, then say hello in the comments. Pick the one that sounds like you: → Already in a project role and it feels messy? Start "From PM Chaos to PM Calm." [link] You'll learn exactly what to do in the situations that trip up new PMs. → Trying to land your first PM role? Start "Your First Project." [link] You'll walk through a real first project, step by step, so you finally see how it's done. Then do two quick things in the comments below: 1. Tell us which challenge you started and one thing you're hoping to figure out. 2. Reply to one other person who started the same one. Just a "me too" or a quick tip is enough. That's it. That's how the room comes alive, and how you meet the people who get exactly where you are. You don't need to feel ready. You don't need to read every post. You don't need to have it all figured out. Just open the first lesson, say hello, and reply to one person. Takes about 2 minutes. Honest truth: the members who take one small step on day one are the ones who get results and make friends here. The ones who plan to come back later usually don't. So do it now, while you're here. We're glad you came. Welcome to PM Blueprint! If you aren't already, make sure you're following/subscribed to me for my latest content to help you on your journey: → Main Channel: http://www.youtube.com/@pmblueprint_1 → Instagram: https://www.instagram.com/build.with.ola?igsh=emhoOTJlaHp6YnVm

The fastest way to get better at this job is to learn from someone who's already been there. So let's pool what we know. 👇 Share a win or a lesson. Something like: 1. A moment at work you handled well. A tough stakeholder, a messy meeting, a scope change, a save under pressure. What happened, and what you did. 2. One thing that just works for you. How you learned to speak up in meetings, how you keep a project on track, how you say no without the drama. A few ground rules to keep this a good space: - Keep it anonymous. No company names, no client names, no real names of people you work with. "A senior stakeholder" is perfect. - Focus on what you did and what worked, not on venting. This is a wins room, not a moaning room. - Keep it real and specific. The small, practical stuff helps the most. Then read a few and like the ones you'll actually use. If someone's story helps you, tell them. That's how this room gets good. No perfect answers needed. We're all still learning. Your everyday fix might be the exact thing someone else needs this week. 🙌