For years, ERP projects had some usual suspects when timelines slipped. Configuration took longer than expected. Integrations turned out uglier than the slide deck promised. Data migration became its own side quest. Testing found things no one mentioned in discovery. Everybody nodded like this was just the natural order of the ERP universe. Now AI is starting to mess with that old pattern. Suddenly, we can draft requirements faster. Generate test cases faster. Accelerate code

I read a quote this weekend that stopped me cold: “80 mph feels different in the driver’s seat than it does in the passenger seat.” Man. That’ll preach. Because that is not just a quote about cars. That is leadership, it's every tense steering committee, every late-night cutover decision, every executive conversation where you’re trying to stay calm while twenty variables are moving at once and half the room only sees two of them. And maybe the reason it hit me so hard is bec

If you have spent any time around manufacturing implementations in Dynamics 365 Finance & Operations, you have probably heard some version of this: "Planning is a mess." "The system keeps suggesting the wrong thing." "Production orders are late again." "Inventory says we have it, but we don’t." "MRP is broken." And every time I hear that, I usually have the same first thought: Are we sure this is a planning problem? Or is this a master data problem wearing a planning costume?

The rant “Just update the PO.” Those four words have launched more chaos than any server outage I can remember. Because a purchase order is not a draft email. It is a contract, a planning signal, a receiving roadmap, and an invoice matching anchor. When you casually edit it after the fact, you are not “keeping it current.” You are rewriting history, and every downstream team pays for it in a different way. In manufacturing, this gets ugly fast. Change a date and master planni