You’ve worked across contracts, bids, business development, and now operations. Looking back, how did you end up on this path? Was it planned, or did it just evolve along the way?
It evolved rather than being fully planned, but looking back there is a clear logic to it.
I started from a technical and project delivery background, then became increasingly interested in the decisions that shape projects before delivery begins: contract structure, risk allocation, commercial strategy, client positioning and whether the proposed delivery model is genuinely executable.
That naturally took me into contracts, bids and business development, and later into operations, where those upstream assumptions are ultimately tested.
When I assess an opportunity today, I assess it holistically: our probability of winning, our ability to mobilise and deliver, the depth of capability behind the solution, the credibility of the resource model, the sustainability of the commercial position, and whether the key bid assumptions will remain valid once the project is live.
That operational perspective helps ground the proposition in delivery reality and avoids commitments that may look attractive at bid stage but become difficult to sustain in execution.
So my career was not predefined. It evolved from managing individual projects to shaping the commercial, operational and strategic decisions that influence how the wider business performs.
You’ve seen projects from both sides: winning the work and then actually delivering it. What have you learned about the gap between a great proposal and a great project?
The biggest lesson is that a proposal does more than win work. It sets the operating conditions for the project that follows.
Every commitment made during a bid becomes real after award: mobilisation dates become delivery pressures, lean staffing becomes workload, pricing assumptions become margin obligations, and methodology commitments become client expectations.
The gap appears when a proposal is optimised mainly to win rather than to be executed. That is why I believe strong proposals should be built backwards from delivery, with the organisation, resource model, programme and commercial structure all tested against what the project will actually require.
A successful bid is not simply one that wins the award. It is one that creates a credible, executable platform for delivery - commercially sound, operationally realistic and resilient under real project pressure.
When you’re sitting with a client for the first time, what are you really trying to understand beyond what’s written in the brief?
The brief tells me what the client wants to procure. I am trying to understand what they are really trying to achieve, what is creating pressure, and what could prevent success.
I focus on three things: the real delivery challenge, how decisions are made within the client organisation, and what success means to the key stakeholders.
For example, a project may appear to have a reporting problem, when the real issue is that management does not trust the information enough to make timely decisions. In that case, producing more reports does not solve the problem.
So I see the first client meeting less as a sales exercise and more as a diagnosis. Strong leadership starts with understanding the real problem early enough to shape the right strategy, align the right people, and focus the organisation on the decisions that will have the greatest impact on delivery.
Everyone wants to win a major opportunity, but what do you think actually makes a client choose one consultant over another?
At the level of major PMC opportunities, most serious competitors can demonstrate relevant experience, systems and technical capability. Those things get you into the competition, but they do not always differentiate you.
What the client is really buying is confidence - confidence that you understand the challenge, that the proposed team is credible, that you can mobilise effectively, and that you will make sound decisions when the project becomes difficult.
Price matters, especially in today’s market, but value is not simply about being cheaper. It is about showing that the delivery model is efficient, the team is right-sized, and the wider organisation can reduce risk and support better outcomes.
The strongest differentiation often comes from insight. If you can identify a risk, challenge an assumption, or propose a better way of delivering the scope, you move the conversation beyond compliance and price.
Winning major work is ultimately about reducing uncertainty for the client and giving them confidence that your organisation can convert capability into reliable delivery.
You now oversee multiple major PMC projects. When things get complicated - changing priorities, commercial pressure, delivery challenges - how do you know what needs your attention first?
The first principle is not to confuse noise with importance.
Across multiple projects, there will always be competing issues, so I prioritise based on consequence: client impact, programme impact, commercial exposure, urgency, and whether the project team can resolve the issue without escalation.
I also consider reversibility. Some issues can be corrected later with limited impact, while others, such as a missed contractual notice, a critical mobilisation delay, or the wrong senior appointment, can create consequences that are much harder to recover from.
I also look for patterns across the portfolio. One issue may be project-specific, but the same issue appearing across several projects can signal a wider operational problem that needs a different level of intervention.
My role is not to solve every issue personally. It is to create visibility, focus attention where intervention will genuinely change the outcome, and make sure accountability remains at the right level.
The PMC market is changing quickly. What are clients asking for today that they weren’t asking for a few years ago?
The biggest change is that clients are becoming much more demanding about the relationship between cost and value.
They still expect strong PMC fundamentals, but increasingly they want leaner teams, better use of data, stronger forecasting, earlier visibility of risk, and access to specialist capability without carrying unnecessary permanent cost.
Clients are also challenging the traditional manpower-heavy model. They want to understand what each layer of the organisation is actually contributing and whether the consultant is improving decisions, not simply adding resources.
At the same time, commercial pressure has intensified. Local competitors are stronger, benchmarking is more aggressive, and international firms have to demonstrate clearly how their wider network, systems and expertise translate into measurable local value.
In Saudi Arabia, localisation and capability transfer are also becoming more important.
So I see the market moving from supplying resources to providing integrated capability, better decisions and measurable outcomes.
After working across so many sides of the business, what’s one thing you understand about successful project delivery now that you wish you knew earlier in your career?
The biggest lesson is that many delivery problems are actually created much earlier.
What looks like a staffing issue may come from an unrealistic mobilisation commitment. What looks like a margin problem may come from an aggressive pricing assumption. What looks like a governance issue may simply reflect unclear accountability from the start.
Earlier in my career, I focused heavily on execution: good processes, systems, controls and technical capability. I now see successful delivery as starting much earlier, during positioning, bidding, contracting and mobilisation.
Strong leadership is not about controlling every detail. It is about creating the conditions for good decisions: capable people, clear accountability, reliable information and the confidence to escalate issues early.
Complex projects will always face problems. The difference is whether the organisation sees them early enough, makes decisions quickly enough, and acts before they become structural.
.png)
