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

The team, the sponsors, and the stakeholder are all there. Scope, goals, and timelines are aligned. But the most critical voice is missing: the end-user.  Not the internal client. Not the budget holder. But the person who really matters, whose life or work we are supposed to be improving. When the customer isn't represented from day one, we risk delivering a project that's on time, on budget, BUT isn't fit for purpose.

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 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?".

So when I talk about the business risk of siloed delivery, I'm talking from real experience. And I've seen it in so many other places too. Disconnected projects undermine what could be powerful business outcomes, it puts pressure on people already overloaded with change.

As a project delivery and turnaround specialist, I've learned that the difference between project success and failure isn't about how fast you can put out fires.  It's about preventing them from starting in the first place.

The difference between strategy and success is delivery. Without it, every brilliant idea remains just that - an idea. Brilliant ideas don't deliver outcomes, unfortunately. It's project management that ultimately makes those ideas a reality.