The Right Moment to Start Paying Attention

I’ve always seen systems clearly — the moving parts, the logic, the way information flows from one decision to the next. Whether it was video games or business processes, I’ve just naturally understood how things fit together. Over the years, I’ve watched organisations build processes that range from elegant to chaotic, and I’ve learned to spot the difference quickly. That clarity was pushed to its limit back in 2021, when I took over the rollout of a new ERP system with only two months before launch. Suddenly the reasons behind “bad processes” became obvious: pressure, deadlines, and the reality that businesses have to keep running even while the supporting systems are still being built. The system went live, held together, and has since processed over £30 million in revenue — and is growing rapidly. That growth is precisely why better data, reporting, and automation matter. It’s also what nudged me deeper into the world of data, long before I had a name for what I was learning. Why I’m Writing Now In the last year, the company’s appetite for data has gone from healthy to ravenous. To support that — and to grow alongside it — I started a Level 4 Data Analytics apprenticeship. I’d built dashboards and KPI packs before, but now I’m learning the methods and thinking that underpin them. I’m also nearly 44. I’m aware that the gap between where I am and where I want to be doesn’t close by itself — and that the window to close it isn’t permanently open. That’s not anxiety, it’s clarity. And clarity, for me, tends to produce action. The timing feels deliberate, even if it wasn’t entirely planned. The organisation is growing fast, the appetite for data is real, and I’m in a position I don’t want to waste. This blog is partly about making sure I’m building the right things — not just keeping up. As I explore new tools and ideas, I realised I needed somewhere to document the journey — not to teach, but to track my own progress and see how my thinking evolves over time. Balancing Learning With Keeping the Wheels Turning My day job as a Business Process Systems Manager is about stability and clarity. If I introduce a half‑baked automation or build a dataset that answers the wrong question, it doesn’t just waste time — it disrupts the operation. And when a process has been done the same way for years, convincing people (and sometimes myself) that change is worth the effort can be a challenge. Working with ERP and CRM data can also feel a bit like being one of the goblins in Gringotts: you know where all the vaults are, what’s hidden inside them, and how to guide people safely to what they need. I know where the data lives, what it means, and how it flows through the organisation — and now I’m learning how to serve it back in cleaner, clearer, more digestible ways. That shift from guardian to translator is a big part of this journey. What This Isn’t It’s not a tutorial site. It’s not guru content. It’s not hype, shortcuts, or “10 tips to…” It’s simply me reflecting on what I’m learning, how it connects to real work, and the messy, practical realities of improving systems from the inside. Who This Might Help Maybe someone trying to push themselves in a new direction. Maybe someone who enjoys thoughtful, reflective writing about work. Maybe someone who wants to understand how another person thinks about systems, change, and progress. And if nobody ever reads it? I’m still better for having written it. Where This Goes I don’t know yet — and that’s the point. I have a rough direction: better tools, cleaner thinking, work that creates more value. But the specifics are still forming, and I’d rather document the process honestly than pretend I have it mapped out. If you’re somewhere similar — figuring it out while keeping things running — maybe this will be worth reading. If not, I’ll still have the record.