She Writes Change

Customer journey mapping, be it internal of external customers, is more than a fully CX exercise. It's an excellent project planning tool that spots problems before a line of code is even written. 𝐇𝐨𝐰 𝐢𝐭 𝐰𝐨𝐫𝐤𝐬 Map out every touchpoint your customer will have with what you're building. Do this upfront, before you've committed budget. This will let you see and structure processes and features early on, making sure you also spot issues that could blindside you after l

Post-Mortems or Lessons Learned are useful if run properly, of course, BUT they won't save your project. We've normalised learning lessons after delivery, after the damage, after the failure. But what if there was a better way?

The most expensive thing in your project isn't what you think. It's a the endless one-hour meetings with either the wrong people, or the wrong agenda. And I've seen this everywhere, hell, I've definitely been guilty of it myself in the past!

Stop asking for "Lessons Learned". Start asking for "Lessons Applied". How many times have you sat in a post project meeting review, listing out all the "Lessons Learned", only see them filed away in a document that's never read again?

Stop annoying your sponsors: 𝐌𝐚𝐬𝐭𝐞𝐫 𝐭𝐡𝐞 𝐀𝐫𝐭 𝐨𝐟 "𝐈𝐧𝐭𝐞𝐥𝐥𝐢𝐠𝐞𝐧𝐭 𝐄𝐬𝐜𝐚𝐥𝐚𝐭𝐢𝐨𝐧". Escalate too often, and you look incapable. Escalate too late, and you become a liability. Sound familiar? Before even thinking about your sponsor, ask: "Can my team and I solve this without external help?" and "Is this issue significant enough to warrant executive attention?" This shows you respect your own authority and your sponsor's time.

Your project dashboard is a sea of green but you know something's off.  Your status updates say everything is on track, your weekly reports are all positive. But you know that it's not accurate. 𝐖𝐞𝐥𝐜𝐨𝐦𝐞 𝐭𝐨 𝐆𝐫𝐞𝐞𝐧 𝐋𝐢𝐠𝐡𝐭 𝐒𝐲𝐧𝐝𝐫𝐨𝐦𝐞!

You've integrated all your project dashboards into one view. So why is your Steering Committee still confused? I've seen organisations invest heavily in Project software and unified dashboards, integrating every project management tool, all to create the perfect "single pane of glass" view. Then they sit in Steering meetings where executives still ask the same questions: "Are we on track?". "What does this really mean for the business?". "Should we be worried?".

Whilst AI can handle more of the technical and admin work, the uniquely human aspects of project management become MORE critical to success, not less.

Launching a new digital product across 12,000 retail locations taught me that scale isn't about size, it's about psychology. You can't just double the resources for double the locations. The real challenges are human. Here's what I learnt about scale:

𝐅𝐫𝐚𝐦𝐞 𝐲𝐨𝐮𝐫 𝐀𝐈 𝐭𝐡𝐢𝐧𝐤𝐢𝐧𝐠: It’s a business tool, not a side experiment so apply the same strategic intent, and ROI focus you would to any core investment

The reality is that the rigid application of either Agile or Waterfall rarely fits the messy reality of complex delivery.