The first time my physics degree saved a meeting, nobody in the room knew that was what had happened.

I was working as a police intelligence officer at the time. Not the career trajectory most people map out after studying theoretical physics — but I'd taken the turn anyway and was making it work. Someone had put a report on the table. Strong language. Clear recommendation. The kind of document that gets nodded at and actioned without much friction.

Except the conclusion didn't follow from the data. The numbers were real. The interpretation wasn't. I'd been trained to see the difference, even if I couldn't have explained exactly why it bothered me in that moment.

I asked one question. The recommendation was shelved. Nobody connected it to the degree.

I did. Eventually.

The honest answer to "what do you do with a physics degree" is: more than you expect, in places you didn't plan for.

I didn't set out to move from intelligence work into ICT, and then into consulting across mine sites and airports and data centres and government agencies. That is not the linear career the university careers office described. But the thinking that came from studying physics — the specific cognitive habits drilled into me through years of working with incomplete information and needing to be precise about what I actually knew — that thinking came with me everywhere.

Not because I planned it that way. Because that's what happens when you learn to think in a particular way. The thinking doesn't stay in the container you developed it in.

Here's what that means in practice.

Physics forces you into a very particular relationship with uncertainty. You learn early that there is what is known, what is suspected, and what is assumed — and that conflating those three categories is where serious errors live. You learn to ask what would have to be true for a conclusion to hold before you accept it. You learn to follow an argument to its logical end and check whether it still stands.

I was doing that in police work when I caught the flawed report. I was doing it fifteen years later when a vendor was pitching a network solution that looked plausible on paper but didn't survive the question: what happens when this assumption breaks? I was doing it in a boardroom in the Middle East when a project plan with a compelling financial case turned out to have a risk model built on best-case assumptions being treated as certainties.

Different industries. Different problems. Same habit of mind.

The thing nobody tells you when you start a science qualification is that the subject matter is almost secondary.

Yes, you need to know the techniques. Yes, the protocols matter. Yes, the specific knowledge of your discipline is what gets you hired and what keeps you credible in the field. None of that is trivial.

But underneath the domain knowledge, your training is doing something else. It is shaping how you approach a problem before you've decided how to solve it. The instinct to check the methodology before trusting the result. The reflex to ask what the evidence would look like if your current assumption were wrong. The trained discomfort — and it is trained — with conclusions that arrived faster than the evidence warranted.

Those aren't physics habits. Or pathology habits. Or concrete testing habits. They're thinking habits. And they belong to you, not to the discipline you developed them in.

I have never once introduced myself as a physicist. Nobody in my professional life has ever hired me for physics. The degree sits in a folder somewhere and has never been asked for at an interview.

But thirty years into a career that has taken me across three continents and more industries than I intended, I can tell you with reasonable confidence that the way I think — the specific, trained, evidence-first way I approach a problem — has been the most consistent asset I've carried.

Not the credentials. Not the accumulated job titles. The thinking.

Your training is building the same thing. It probably doesn't feel like it right now — it feels like procedures and instruments and assessments and the pressure of the next deadline. But underneath all of that, something is being installed that will still be running decades from now, in rooms and industries and situations you currently can't imagine.

The question is whether you recognise it before it saves a meeting — or after.

Adam