Michael Shreeves
I struggle to leave a problem unsolved once I’ve noticed it. Somebody, somewhere, is doing this by hand right now.
Head of IT for a healthcare group, former CTO, and a developer for the twelve years before either. Cyber security, governance and compliance are the job now as much as the code ever was.
Dad to four, gamer, car enthusiast, and still writing code most evenings, once the kids are down.
More about me
The short version. Everything else has its own page.
About
Since 2008 I’ve mostly been the person in the room saying “we could just build that”.
Head of IT for a healthcare group, former CTO, and a developer for the twelve years before either title existed. Why the tools on this site exist, and what I do off the clock.
Read the full story →Problems I enjoy solving
Not a technology list. The stuff underneath it.
The spreadsheet that became load-bearing, the systems that won’t talk to each other. The patterns behind every tool below, recognised in the wild before they ever became a spec.
See all six →Experience
Twelve years writing the code, then the jobs that needed somebody who had.
The full role-by-role history from 2008: website developer to team lead to senior developer, co-founder & CTO, and now Head of IT.
Read the full career history →Skills
Broad on purpose.
Technology, product & delivery, and leadership & governance: the three areas that have to join up to fix anything.
See the full list →What I build
Every one of these started life as somebody’s least favourite
Tuesday.
A spreadsheet holding something important together. A subscription costing more than it saves. A job being done three times over because two systems refuse to speak to each other.
Only one of these is shipped. I’d rather say so than hide it, so the filter below shows everything, ideas included. The live one, Foundry, has its own write-up.
Nothing is called live until it is deployed, backed up, and I have restored from one of those backups. A tool with a link is running somewhere you can look at it; one without isn’t, yet. Full list, filterable the same way, also lives on its own shareable projects page.
The household one isn’t the joke of the set, whatever it looks like next to a clinical imaging viewer. A family tool holds family data (sometimes children’s) belonging to people who’ve never read a data-processing agreement and should not have to. That’s a higher bar than an internal business tool, not a lower one, and it gets held to it.
Guides & tips
Two ways to read what I’ve learned.
Pulled from the same list of things worth automating that built the tools above: longer background pieces on one side, quick one-idea checklists on the other.
Guides
Background, setup, and the edge cases.
Full write-ups on M365 & security, AI & Copilot, and automation. Each one ends with what goes wrong, not just the happy path.
View all guides →Tips
One idea, under two minutes.
Short, actionable checklists and snippets on IT and automation, with no padding.
View all tips →Latest
- If a mailbox script or signature tool stopped working this month, check EWS first
- Central email signatures in Microsoft 365: there's no API for it, so here are the routes that work
- Let AI draft the social post, then run five checks before you hit post
New here? Start with the map of the AI prompts, grouped by the job you're doing. There's also a feed.
Some of it
Things I’m glad I got to do.
- Cyber Essentials and Cyber Essentials Plus Took SEEDL through basic myself, and then supported Pure Unity Health from implementation to documentation.
- An NHS patient discharge system Scoped it and built it at Phew, working directly with the people who’d use it.
- Concept to live product Co-founded SEEDL and took its learning platform from an idea to something customers ran their training on.
- Seventy-plus clinics IT strategy, service delivery and compliance across a group in Primary Care and NHS-affiliated services.
The software wasn’t the hard part.
Technology beliefs
Eighteen years of this leaves you with opinions. Here are a few.
- Every spreadsheet is a system of record nobody signed up to own.
- If a process only works because one person remembers it, it isn't a process yet.
- A tool people route around solved the wrong problem, however well it was built.
- Nobody asks for fifteen minutes back each week. Everybody notices when they get it.
- A dashboard nobody checks is an expensive decoration.
- Most integrations fail because of the data, not the API.
- Security is a habit, not a certificate on the wall.
- In healthcare IT, compliance isn't paperwork around the job. It is the job.
- AI won't fix a bad process. It just helps you do the wrong thing faster.
- The best AI projects start with a problem, not a model.
Get in touch
Right then.
I like hearing about what other people are learning, wrestling with, or have actually solved, just as much as I like solving things myself.
So get in touch — whether that’s a problem that smells automatable and you want a second opinion, or you’ve found a better way to do something I’m still doing the long way round. Could be I help you. Could just as easily be the other way round.
Nothing for sale here. I do this because I like solving problems and I like people, plain and simple. Won’t be remotely offended if it drifts onto football or cars.