One thing my career has taught me is that problems rarely belong to one discipline.

A technology project can have a business problem behind it. A healthcare challenge can involve technology, people, funding and regulation. An education service can have a market-access problem rather than an educational one. Even an operational problem can sometimes be traced back to communication, process design or a decision made much earlier.

Working across technology, healthcare, business development, facilities management and education has therefore changed the way I approach problems. I have learned not to rush towards a solution before understanding what is actually wrong.

**

Start With the Problem, Not the Solution

**

One of the easiest mistakes in business and technology is falling in love with a solution before properly defining the problem.

A company may ask for a new platform when what it really needs is a better process. A team may request additional staff when the real issue is poor workflow. A business may want to enter a new market when the underlying problem is that its existing proposition has not been properly tested.

The first question I ask is usually simple:

What problem are we actually trying to solve?

Getting that answer right can prevent organisations from spending considerable time and resources solving the wrong problem.

**

Look Beyond the Symptoms

**

A visible problem is not always the root problem.

If customers are leaving, for example, the immediate assumption might be that pricing is too high. But the underlying issue could be poor service, an ineffective product, difficult onboarding or a competitor offering a better experience.

This is where structured analysis becomes useful. Root-cause analysis, stakeholder discussions, data and research can help separate what is happening from why it is happening.

I have found this particularly important when working across technology and healthcare, where a problem can have technical, operational and human dimensions at the same time.

**

People Are Part of the Solution

**

A technically sound solution can still fail if it does not work for the people expected to use it.

This is particularly visible in healthcare and organisational technology. The people designing a system may understand its technical capabilities perfectly, but the end users experience it through their daily responsibilities, pressures and existing workflows.

That is why I place considerable value on listening to stakeholders before making major decisions. Different people see different parts of the same problem, and those perspectives can reveal issues that are invisible from a single viewpoint.

**

Context Changes the Answer

**

A solution that works well in one organisation, industry or country may not work in another.

Market conditions, regulations, infrastructure, organisational culture, available skills and customer expectations all influence what is practical.

This is one reason I am cautious about applying solutions simply because they have worked somewhere else. Good problem solving requires understanding the environment in which the solution will operate.

**

Research Makes Decisions Stronger

**

Experience is valuable, but experience alone can also create blind spots.

Research provides an opportunity to test assumptions, compare alternatives and understand patterns that may not be immediately visible. My work has involved qualitative and quantitative research, stakeholder analysis, data analysis and Design Science Research, and these methods continue to influence how I approach professional challenges.

The objective is not to make every business decision academic. It is to make important decisions better informed.

**

The Best Solutions Often Cross Disciplines

**

Some of the most interesting problems sit between traditional areas of expertise.

Digital health is a good example. It requires technology, healthcare knowledge, business thinking, security, regulation and an understanding of the people using the service. Looking at only one of these dimensions can produce an incomplete solution.

That is why I have come to value interdisciplinary thinking throughout my career. Different disciplines bring different ways of seeing the same problem, and combining those perspectives can produce better questions—and eventually better solutions.

**

What I Carry From One Industry to Another

I do not expect every industry to operate in the same way. What I carry from one professional environment to another are the principles: understand the problem, investigate the cause, listen to the people involved, consider the context, test assumptions and measure whether the solution actually works.

The technology, terminology and business model may change. The need to solve the right problem does not.

For me, that is one of the greatest advantages of working across different industries: you begin to recognise patterns that are not always visible when you look at a problem from only one professional perspective.