01
Leadership case
Experience and operating scope
Responsibilities, leadership reach and evidence of decisions carried through to operational ownership.
Read the leadership caseOperational Judgement
Senior IT Infrastructure & Cybersecurity Manager
I turn complex infrastructure and cybersecurity responsibility into resilient services, controlled change and evidence leaders can trust.
- Infrastructure resilience
- Operational cybersecurity
- Identity and assurance
- People, suppliers and programmes
Based in United Kingdom Open to senior infrastructure, security and technology leadership opportunities
- 50
- Published essays
- 3
- Case studies
- 6
- Evidence areas
A working body of evidence across strategy, delivery and operational judgement.
Choose your route
Understand the experience in minutes.
Start with scope, inspect the decisions, then use the archive to test the depth behind the claims.
02
Decision evidence
Case studies from real work
Anonymised examples focused on the call made, the trade-off managed and what changed afterwards.
Review the case studies03
Working judgement
A searchable field journal
50 concise pieces across infrastructure, cybersecurity, identity, delivery and leadership.
Explore the writingSelected work
Decisions with operational consequences.
Public-safe case studies showing ownership, judgement and outcome without exposing sensitive detail.
All case studies01
Asset management became a governance problem before it became a tooling problem
Asset management only became useful when ownership, lifecycle state, auditability and cost responsibility were treated as governance questions instead of a software procurement exercise.
- Decision owned
- Treated asset management as a governance and accountability design problem before selecting tooling.
- Outcome
- Moved fragmented recall toward a structured record with clearer ownership, lifecycle expectations and stronger finance and IT alignment.
02
Service continuity during a telephony migration
The telephony question was not only what to replace, but how to keep communication dependable while legacy expectations, supplier realities and future-readiness all pulled in different directions.
- Decision owned
- Framed the telephony migration as a continuity and operating-model decision first, and a technology refresh second.
- Outcome
- Shifted migration and supplier discussions toward dependable service, support ownership and a more sustainable operating state.
03
Visitor systems as operational accountability
Moving from paper sign-in to digital records only mattered because visitor handling was treated as an accountability and operational-confidence problem rather than a reception convenience project.
- Decision owned
- Treated the visitor system as an operational-accountability control rather than a reception upgrade.
- Outcome
- Improved record visibility and reporting usability, making exceptions clearer and the sign-in process more purposeful.
Latest signals
Recent writing
Read-only auditing changed how I separate evidence from action
A strict no-change constraint can improve technical judgement by separating verified findings, limitations, recommendations, owner decisions and later implementation.
A penetration test is not finished when the scanner stops
Assessment execution, evidence processing, finding readiness, triage, remediation and retesting are separate states. Calling all of them complete hides risk.
Contractor readiness begins before the engineer arrives
A supplier visit tests the quality of the preparation around it: scope, access, safety, prerequisites, change authority, acceptance and cross-team ownership.
External collaboration needs a boundary, not a blanket ban
External collaboration is safer when identity, application and data boundaries are explicit. A blanket ban often replaces governed access with unmanaged workarounds.
Filtering coverage is an assurance problem, not an installation count
A successful software deployment does not prove that filtering is configured, enforcing policy and reporting across every device population that depends on it.
A spare switch is not resilience until it is ready to take over
Spare hardware becomes a recovery capability only when compatibility, firmware, management, supporting components, documentation and validation have already been addressed.