Two small things that weren’t broken, and why ‘it’s automated’ isn’t the same as knowing it works.
How my thinking has developed from fixing individual issues to looking at the service around them.
Why the first description of a problem is the starting point, not always the diagnosis.
What I’ve learned from being the engineer responsible for customer support on-site.
What working across multiple customer environments has taught me about support, communication and service.
What I try to include when handing a technical issue to another team.
Why resolving an incident can be useful while still leaving a wider problem worth looking at.
Why turning a vague support issue into something you can actually investigate matters.
What my Army career taught me about responsibility, preparation, leadership and working in IT.