IT Operations
Service ownership, support models, operational controls, roadmaps, prioritisation and transition into sustainable BAU.
Operations & Automation
Reliable operations first. Automate where it genuinely improves the service.
My approach to IT operations combines clear ownership, supportability, resilience and practical automation. Automation should remove repetitive work, reduce risk and improve consistency without creating a new layer of complexity that nobody owns.
Operating Philosophy
Automation supports the operating model; it does not replace it.
Strong operations start with knowing who owns a service, how it is supported, what happens when it fails and how change is controlled. Once those basics are understood, automation can make the service faster, more consistent and easier to operate.
Understand → Standardise → Automate → Monitor → Improve
Areas of Focus
Operational Resilience
Business continuity, incident response, recovery, dependency management and learning from operational events.
Identity & Access
Joiner, mover and leaver processes, access governance, deprovisioning and evidence across Active Directory and Microsoft 365.
Practical Automation
PowerShell and workflow automation for repetitive administration, reporting, access review and operational consistency.
Practical Work
Playbook
IT Operations Playbook
Operating models, service management, resilience, vendor management, roadmaps and business-led technology prioritisation.
View repository →Automation
Technology Automation
Practical automation and control patterns across identity, Microsoft 365, infrastructure, secure delivery and resilience.
View repository →IAM · PowerShell
IAM + User Offboarding
Identity lifecycle and user-offboarding guidance covering Active Directory, Microsoft 365, access review, evidence and PowerShell automation.
View repository →Operational Resilience
Major Incident & Operational Resilience
A practical incident-management model covering prioritised recovery, communication, business continuity and post-incident learning.
Read playbook →Documentation · BAU
Documentation as an Operational Control
Policies, SOPs, runbooks, as-built documentation and handover as practical controls for supportability, recovery and knowledge retention.
Read playbook →Windows · PowerShell
Win11 Classic Experience
Conservative PowerShell administration for familiar Windows 11 behaviour without generic debloat or weakening security controls.
View repository →Principle
Automate the repeatable. Keep ownership visible.
Good automation should leave the environment easier to understand and support. The objective is not to maximise scripts or workflows; it is to reduce manual effort and risk while preserving clear accountability, logging, documentation and recovery paths.