Support & systems administration
The early years built the habits that still matter: reproduce the problem, inspect the environment, understand dependencies, and fix the cause rather than the symptom.
About
Most of my career has been spent in the space between technology and operations: the point where a business knows something is inefficient, unreliable or harder than it should be, but the solution does not fit neatly into one product or job description.
I began my IT career in May 2005 in hands-on support and systems administration. Over time, that work expanded into SQL Server, enterprise reporting, SharePoint, infrastructure, automation, technical project delivery, business continuity, governance and custom software development. The titles changed; the underlying role did not. I was usually expected to understand how the pieces connected, find the actual cause of the problem and make the result usable by people who did not want a lecture on the machinery underneath it.
I have worked inside large enterprise environments, with legal and professional-services firms, in tourism, with property-management organizations and with smaller businesses where one person may be responsible for an entire technology estate. Those environments demand different tools, but reward the same habits: listen carefully, verify assumptions, document decisions, protect the organization from avoidable risk and do not build something more complicated than the team can realistically support.
Today, RTH Tech Services Inc. is the vehicle through which I take on selected consulting and development work. I am most useful when a problem crosses boundaries — data and workflow, reporting and business interpretation, infrastructure and access, or technology and the people who have to live with it afterward.
The career through-line
My background is broad, but it is not random. Each stage added another part of the same core capability: understanding operational systems well enough to improve them responsibly.
The early years built the habits that still matter: reproduce the problem, inspect the environment, understand dependencies, and fix the cause rather than the symptom.
Database analysis grew into SQL Server, SSRS and the work of turning business questions into reliable definitions, queries and reporting people can trust.
Enterprise IT added formal change, risk, resilience, stakeholder coordination, documentation, testing and the reality that technically correct is not always operationally successful.
Independent consulting brought the pieces together: clarify the need, choose a supportable architecture, build the solution, explain it clearly and remain accountable for how it behaves.
Where I have worked
Employer and client names provide context, but the useful part is what those environments required: accuracy, judgement, adaptability and systems that keep working after delivery.
Enterprise IT operations, technical project delivery, governance, resilience, business continuity and work involving formal processes and cross-functional stakeholders.
Legal and professional-services reporting, SQL, matter data, financial analysis, document workflows, collaboration and legal technology where accuracy and confidentiality are non-negotiable.
Database analysis and operational information in a destination organization, where useful data had to connect directly to day-to-day business needs.
Practical Microsoft 365, infrastructure, records, automation, hardware and vendor work designed to remain manageable for small teams and non-technical users.
Selected experience
Selected roles & credentials
These entries provide selected role context and professional foundations, including historical certifications and education.
Database analysis, operational information and data quality in a destination and tourism organization.
Enterprise operations, technical project delivery, formal change, resilience, business continuity, governance and documentation.
SQL, SSRS, reporting, legal technology, workflow and Microsoft 365 in environments where clarity and accuracy matter.
Selected consulting, systems analysis, reporting, automation, Microsoft 365 and custom internal software.
Working principles
Every engagement starts with understanding the actual operational problem, not just the requested feature, so the solution addresses root causes.
The right-sized solution for the organization — not the most impressive architecture, and not enterprise tooling the team can't realistically maintain.
Requirements, assumptions, changes and operational decisions are documented so the solution can be understood later rather than reconstructed from folklore.
Documentation and governance are part of delivery, not an afterthought — systems should remain supportable after the engagement ends.
Technical detail matters, but it has to be translated into risks, options, decisions and next actions that the audience can actually use.