Hey everyone, I added 12 new tools in the Tools and Frameworks classroom. These are all Excel spreadsheets with instructions on how to use them.

Hey everybody! I guess I can actually do an intro. I'm Wesley. This is a pic of my workspace and my two best friends. Yes, I have a cutout of a colleague in front of me. That way, I don't feel like I'm talking to nobody, when I'm doing a recording. I did about 10 years in the army. Since then (15 years ago... holy shit) I earned 2 masters and too many certifications. Not because I'm super smart, I just like going to school and meeting people. I love facilitating and training teams. I happen to be good at building programs, scaling teams and executing on ideas. I have worked all over the globe on the executing the strategic plans of the good idea fairies. I firmly believe having a strategic plan without the skills to execute is a waste of everyone's time. BUT most importantly I have two dogs, a 10-year-old Yorkie-poo and a 4-year-old staffy pit. They are my best friends!

When you roll out a change, whether it's a new process, a new tool or a new way of running your team, most of us spend all our energy explaining what's different. The problem is that when people hear "change," their brains fill in the blanks with worst-case guesses. Will my job look different? Will I lose the stuff I'm good at? Is this the first of ten more changes? The fix is simple. Before you explain what's new, spell out what's staying the same. - "Your role and your team aren't changing." - "We're still serving the same customers the same way." - "The way you submit time off stays exactly as it is." This does two things. 1. It shrinks the change down to its real size, so people stop reacting to the imaginary version. 2. It gives them solid ground to stand on while they deal with the part that really is new. Try it today. Think of one change you're planning or dealing with right now. Write down three things that WON'T change, and lead with those next time you talk about it. Drop your change in the comments (keep it vague if you need to) and I'll help you figure out what belongs on your "staying the same" list. And if you want to go deeper, join us live Tuesday at 10am. We're working through PM Fundamentals and opening it up to whatever you're working on.

First live session of PM Fundamentals just posted, covering project foundations (modules 1-4). Check it out in the classroom. We're meeting every Tuesday at 10am, more coming each week.

Hey everybody, just a reminder that we're going to have the PM Fundamentals starting at 10 am. Today we'll discuss projects, programs, and portfolios, then the Iron Triangle. We'll go over a good business case and wrap it up with Agile and Waterfall methodologies.