The Second Year: Systems, Self-Advocacy, and Small Wins

They say time flies when you’re having fun, and I can certainly vouch for that; but it’s equally true when you’re simply busy. This year has been a whirlwind, packed with tasks to tackle, topics to dig deeper into, and systems to break (always with the aim of making them better). Yet, every one of these “somethings” has been a learning opportunity, and that’s what I embrace most days. Sometimes it’s genuinely frustrating, especially when things don’t quite go to plan. It’s important, though, to keep sight of the real goal: am I learning something new? If the answer is “yes”, then that counts as a win in my book.

Year one was about finding my feet, making an impression, and showing I could get things done. I’d say I managed that well. I focused on replacing processes that had outlived their usefulness, systems that relied more on manual effort and good intentions than on scalable design. As someone once said, “hope is not a strategy,” and that mindset guided a shift from Meraki to Intune, which became key to simplifying the deployment of all the devices, iPads and Laptops alike. We moved from a multi-step setup involving CSV uploads and lengthy guides to a streamlined, directory-synced approach that just works. Year two, then, was about tying up loose ends, refining what was already built, and finding ways to make things that bit more brilliant

The year kicked off with replacing the seven-year-old printers. One of them finally gave up the ghost (rest in peace, Graham). The new printers were an instant hit, which is unsurprising, as I’d used the same model in my previous school. They came complete with modern conveniences like scanning straight to OneDrive and, amusingly, manual stapling on the printer itself, consigning the humble stapler to history. Next up was upgrading to the modern 3CX phone system: a massive leap from our outdated setup. Now, features like voicemails sent direct to inboxes and a companion app make missing important calls a thing of the past. Then came the dreaded MIS migration, a reminder that leaving things to chance seldom ends well.

The year’s headline project was all about consistency and future-proofing: standardising student iPads across the school. We moved from a varied mix of five generations to just two, 10th gen for outgoing Year 12s and 11th gen for newcomers, both managed via Intune for the first time. It was a big step toward simplifying support and ensuring a smoother experience for students and staff alike. Alongside that, we refreshed the teaching laptops with new devices, replacing models that had served us well but were beginning to show their age. Thanks to some brilliant colleagues, the rollout was seamless. Of course, they’re still laptops, so we’ll see how they hold up over time, but for now, they’re a welcome upgrade.

Big projects are rewarding, but I often find the smaller ones more satisfying, the quiet tweaks that make everyday life smoother for everyone (myself included). Whether it’s resolving quirks in the print credit system, designing fresh wallpapers to brighten screens, setting up Microsoft SSO across platforms, or finding a more reliable way to print student ID cards with clearer photos, these tasks add up. They may not grab headlines, but they keep things running, and keep me curious.

From the highs of eureka moments to the lows when burnout seemed all too real, these two years at The NCS (and by extension, the Trust), and nearly five years in educational IT, have taken me from a knowledgeable but clueless apprentice to a slightly less clueless technician, ever ready for the next challenge. I’ve had a few realisations along the way, including but not limited to:

• Thinking “yes” was the default. Now I know that “no” can be just as constructive, especially when it means protecting time, energy, and the ability to keep showing up with my best.

• Taking time to acknowledge my wins before moving on, especially when others recognise them too. It’s not just “doing my job”: celebrating successes matters.

• People often fail upwards, but it’s pointless to compare yourself to them.

• Most meetings are a waste of time: a few emails would usually suffice.

• The importance of advocating for myself, as few others will.

• A tough day can be salvaged by a few great colleagues.

  
  

On that note, I’ll close by saying this: when given the space to work thoughtfully and creatively, I tend to find solutions that stick. I take pride in improving what’s there and building what’s needed, a strength that’s been recognised by colleagues I deeply respect, and for that I’m grateful. The future will no doubt bring its share of challenges, learning curves, and unexpected wins. And if I’ve learned anything, it’s that knowing when to pause, prioritise, or say “not this time” is just as important as knowing how to fix what’s in front of me.