IT Operations
Service ownership, support models, operational controls, roadmaps, prioritisation and transition into sustainable BAU.
Operations & Automation
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
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.
Clarify the service, owner, process, dependencies, risk and support model.
Reduce unnecessary variation and make the process clear enough to repeat.
Remove repetitive work where automation improves consistency, speed or control.
Log outcomes, detect failure and keep operational ownership visible.
Use incidents, exceptions and feedback to refine the service over time.
Areas of Focus
Service ownership, support models, operational controls, roadmaps, prioritisation and transition into sustainable BAU.
Business continuity, incident response, recovery, dependency management and learning from operational events.
Joiner, mover and leaver processes, access governance, deprovisioning and evidence across Active Directory and Microsoft 365.
PowerShell and workflow automation for repetitive administration, reporting, access review and operational consistency.
Automation Principles
A script or workflow should still have a clear owner, support path and recovery process.
Logging, alerts and clear outcomes matter as much as the automation itself.
Automation that only one person understands can create a new operational dependency.
Practical Work
The material below focuses on repeatable operational patterns rather than organisation-specific implementation detail.
Playbook
Operating models, service management, resilience, vendor management, roadmaps and business-led technology prioritisation.
View repository →Automation
Practical automation and control patterns across identity, Microsoft 365, infrastructure, secure delivery and resilience.
View repository →IAM · PowerShell
Identity lifecycle and user-offboarding guidance covering Active Directory, Microsoft 365, access review, evidence and PowerShell automation.
View repository →Operational Resilience
A practical incident-management model covering prioritised recovery, communication, business continuity and post-incident learning.
Read playbook →Documentation · BAU
Policies, SOPs, runbooks, as-built documentation and handover as practical controls for supportability, recovery and knowledge retention.
Read playbook →Windows · PowerShell
Conservative PowerShell administration for familiar Windows 11 behaviour without generic debloat or weakening security controls.
View repository →Principle
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.