This space is for progress you can point to. If you used a template and it helped, post it. If you watched a video, implemented and you finally understood, tell us. If something clicked and saved you time, share it. If you finished a task or hit a milestone, say so. Small & Big wins count. Clarity is a win.Momentum is a win.Taking action is a win. This is how PMs build proof. Your win today becomes someone else’s reason to start and your reason to go on. .

These two get mixed up constantly. Save this for the next time someone throws both terms around in a meeting. Quick check: Your Steering Committee is arguing over who can approve a major change. Which document would you check first? A. Project Charter B. Terms of Reference C. Project Plan Check Your Answer is correct at the bottom of the text Here's the clear version: A project charter is the document that formally gets the project off the ground. It sets out the high-level picture in one place: the objective, what is in scope and out, the key assumptions and risks, who is involved, and the budget and timeline at a high level where these are known. Its main job is to authorise the project and give everyone a shared starting point. When someone asks, "What is this project actually about, why are we doing it, and what have we agreed?" the charter helps answer that. A terms of reference is different. It usually sets out how a specific group involved in the project will work and govern its part of the project. That might be a Steering Committee, Project Board or working group. It covers things like the purpose of the group, who sits on it, what authority it has, what people are responsible for, how decisions get made, how often the group meets and what counts as a quorum. Less "what is this project?" More "who decides what, and how will this group operate?" So the charter defines and authorises the project at a high level. The ToR defines how a governance group works, who has authority and how decisions are made. An easy way to hold the difference: Charter = what, why and high-level agreement. Terms of Reference = who decides, what they are responsible for and how they operate. One important thing though: organisations do this differently. Some may not use a document called a Project Charter at all. You might see similar information sitting inside a Project Brief, PID, Business Case or another initiation document. The same applies to Terms of Reference. Some organisations use them heavily. Others barely use the term.

PMI published its first global standard for using AI in project, programme, and portfolio work this June. It's built around keeping a human in the loop at every stage, and it covers AI risk, ethics, and staying ahead of new rules like the EU AI Act. Here's my read: this is the point AI stops being a side tool and starts being something you have to account for. As more of your risk logs, status reports, and meeting notes get AI help, someone still owns what happens if it's wrong. That's landing on the PM, not the tool. We've spent years building RACIs for people. We might be building them for people plus AI next. Question: is your organisation already setting rules for AI use on projects, or is everyone quietly figuring it out on their own? Further reading: PMI — Publishes World's First Global Standard for AI in Project Work