What My PhD Actually Taught Me (And It Was Never Just About the Research)

People assume a PhD is about becoming an expert in a narrow field. You pick a topic, spend four years buried in it, defend your thesis, and walk away with a title in front of your name. That was how I thought about it when I started mine at Universiti Teknologi Malaysia back in 1989.

I was wrong. The research was almost the least important part.

What the PhD actually gave me, I only fully understood decades later, when I found myself building FAVORIOT from scratch. No corporate safety net. No budget approval processes. No team of fifty people to delegate to. Just a problem to solve, a market to convince, and a very steep learning curve. And somewhere in that pressure, I realised that every skill I was relying on, I had built it during those three years of doctoral work.

You Learn to Think, Not Just to Know

The biggest myth about a PhD is that it fills your head with knowledge. It does, but that is not the point. What it really trains is how you think. How to slow down when a problem looks unsolvable. How to question your own assumptions before anyone else does. How to look at a complex situation and break it into parts that can actually be examined.

Running a startup constantly throws you into situations where there is no clear answer. The market changes. A technology assumption turns out to be wrong. A partnership you counted on falls through. Most people freeze or react. The PhD habit of structured thinking means I almost always go back to basics: what do I actually know, what am I assuming, and what do I need to find out?

That thinking discipline has saved me more times than any specific technical knowledge I carry.

Working Alone Without Falling Apart

A PhD is a deeply solitary journey. Your supervisor guides you, but the work is yours. The thinking is yours. The doubt is yours. Nobody is going to sit with you at two in the morning when you cannot make sense of your own data.

Entrepreneurship feels exactly the same way in the early years. You make decisions that nobody else fully understands. You carry uncertainty that you cannot always share with your team because you are supposed to be the steady one. You have to be comfortable with ambiguity without becoming paralysed by it.

The PhD taught me how to keep working when I had no external validation. It taught me that the absence of certainty is not a reason to stop. You form a hypothesis, you test it, you adjust, and you keep going. That is the startup loop. That is also the research loop.

Finding Knowledge Instead of Waiting for It

Before the PhD, I consumed knowledge the way most students do: someone put it in front of me, and I absorbed it. The PhD changed that completely. You quickly discover that nobody is going to hand you what you need. You have to hunt for it. You learn to search literature strategically, to identify which sources actually matter, to read critically instead of passively.

At FAVORIOT, we operate in a field that moves fast. IoT, AIoT, edge computing, platform architecture, developer ecosystems. The landscape shifts every eighteen months. If I waited for someone to teach me what I needed to know, I would always be behind. The PhD habit of self-directed learning means I am always reading, always synthesising, always asking what the current evidence actually says rather than what the conventional wisdom assumes.

Making the Complicated Simple

The viva examination is the moment every doctoral candidate dreads. You stand in front of a panel of experts and defend work that you have spent years on. They will probe every weakness. They will ask you to justify every assumption. And they will not accept jargon as a substitute for understanding.

To survive a viva, you have to be able to explain your work clearly. Not just to people who already know the field, but to people who are testing whether you truly understand it, or whether you are hiding behind technical language.

That skill matters enormously in a startup context. I cannot afford to lose a potential customer, partner, or investor because I explained our platform in terms only an IoT engineer would recognise. I have to be able to take a genuinely complex system and present it in a way that is meaningful to a city mayor, a business owner, or a university faculty head. The PhD forced me to develop that translation ability.

Defending What You Believe Without Being Defensive

There is a particular kind of confidence that the PhD builds. Not arrogance, which is brittle. A well-grounded, evidence-based confidence that allows you to say: I believe this is right, and here is why. And then to genuinely listen to the counterargument rather than dismissing it.

In business, this matters in negotiation, in pitching, in product decisions, and in those moments when someone more powerful than you tells you that your idea will not work. The PhD trains you to distinguish between a challenge that reveals a real weakness and a challenge that is simply pressure. You learn to stand your ground when the evidence supports you, and to revise when it does not.

Evaluating Other People’s Work Without Ego

A less obvious skill the PhD builds is the ability to critically evaluate the work of others. Peer review, literature critique, comparative analysis of methodologies. You develop a framework for assessing quality, identifying gaps, and recognising when something looks impressive but is actually incomplete.

This translates directly into how I evaluate technology vendors, potential partners, and market claims. The IoT industry is full of noise. Announcements that overstate capability. Case studies that obscure the real cost. Research that is funded to reach a particular conclusion. The critical evaluation skills from doctoral training mean I read all of it with appropriate scepticism, and I draw my own conclusions.

The Scroll Was Never the Point

I do not display my PhD certificate in my office. Not because I am not proud of it, but because I stopped thinking of it as the output a long time ago. The output is how I think, how I work, how I handle uncertainty, and how I communicate. Those are the things the doctorate actually produced.

If you are a PhD holder wondering whether the years were worth it beyond the academic world, I would say this: you were trained for exactly the kind of work that startups and leadership roles demand. The certificate opened some doors, yes. But the habits it built have kept me going long after the doors were open.

So the real question is not whether your PhD is relevant to business. The question is whether you have recognised and applied everything it actually gave you.