Human in the Loop Systems is built around a fairly simple idea: technology should earn its keep.
I help organisations make better use of what they already have, reduce friction, and turn messy systems, information, and processes into something more useful. Sometimes that means Microsoft 365, identity, governance, and automation. Sometimes it means data, context, AI, connected systems, or a project that needs shaping properly before anyone disappears into implementation theatre.
What ties it all together is not a product or a platform. It is the work of making technology useful, governable, and workable for real people.
What I bring
I bring a mix that is harder to find than it probably ought to be: technical depth, broad systems thinking, delivery experience, and a strong interest in how information is structured and used.
That includes work across Microsoft 365, Entra, Azure, automation, information architecture, governance, data flows, service improvement, and AI enablement. I am as interested in how things fit together as in the individual tools themselves. In practice, that means I am often most useful where there is complexity, underused capability, unclear structure, or a sense that something ought to be possible but has not yet been turned into a practical result.
I am not especially interested in technology as performance. I am interested in technology that helps.
Experience in brief
I have been around long enough to have seen several generations of systems, promises, and revolutions come and go. That turns out to be useful.
My background spans software, data, delivery, Microsoft platforms, information architecture, and technical leadership. I have worked in large-scale product and programme environments, in operational settings where systems have to survive contact with reality, and in roles where the job was not just to understand the technology, but to help people adopt it, manage it, and get value from it.
More recently, a lot of that experience has converged around Microsoft 365, governance, automation, reporting, AI, and the structure around intelligent systems: context, knowledge, routing, decision-making, and the practical business use of information.
The thread through it all is fairly consistent: understand the system, understand the people, shape the structure, and get to something that works.
How I work
I tend to work across boundaries.
Between strategy and implementation. Between technical detail and human reality. Between the attractive idea and the thing that can actually be delivered and lived with afterwards.
I learn quickly, ask awkward questions when needed, and prefer clarity over performance. I am generally more interested in whether something is useful than whether it sounds impressive in a slide deck. I like shaping things properly, reducing waste, and leaving behind something people can understand, manage, and improve over time.
That also means I am wary of hype. AI is useful. Automation is useful. Cloud platforms are useful. None of them are magic, and all of them benefit from structure, context, and a bit of adult supervision.
What matters to me
A few things matter consistently in the work.
- Good systems should reduce friction, not create theatre.
- Information should be organised in ways that support decisions, not just compliance exercises.
- Automation should remove dull work, not hide muddle.
- AI is most useful when it is grounded in real context, shaped around actual knowledge, and used with sensible oversight.
- And technology, in the end, should help people do something better.
Beyond the usual consultancy script
I am curious by nature, and a lot of my best work comes from following that curiosity into practical territory.
That includes exploring AI systems, context engineering, knowledge structures, local and cloud orchestration, connected devices, and lightweight automation. Some of that runs on enterprise platforms. Some of it runs on a Raspberry Pi. The point is not the badge on the box. The point is choosing the right level of complexity for the job and making it work reliably.
I have little interest in pretending every problem needs a grand transformation programme. Sometimes the answer is strategic. Sometimes it is architectural. Sometimes it is a well-placed bit of automation and a clearer structure around information. Knowing the difference matters.
If that sounds useful
If you have underused systems, repetitive manual work, messy information flows, or a sense that there is more value in your current setup than you are getting from it, there is probably a worthwhile conversation to be had.
I am usually at my best where there is complexity to simplify, capability to unlock, or an opportunity to make technology work a bit more like it should have done in the first place.