My principles

Why write them down

Integrity, loyalty, service, family and continuous learning: the short list I have kept through twenty years of projects, written down so that hard decisions are already half made before they arrive.. I wrote that half in humour and entirely in seriousness, because principles that are never stated tend to be discovered too late, usually in the middle of the situation where they were most needed.

Values that stay implicit are negotiable. Under pressure they quietly adapt to whatever the moment requires, and afterwards we tell ourselves the circumstances were exceptional. Written principles behave differently. They are decided in calm conditions, on purpose, so that the difficult decision is already half made before it arrives. That is their real function: not moral display, but pre-commitment.

What follows is not a universal code. It is the short list I have kept through twenty years of projects across Europe and Africa, through a career built in engineering and project controls, and through the ordinary business of raising a family while doing demanding work.

Integrity, especially when it is expensive

Integrity is cheap when it costs nothing. Its price appears when the truthful number damages the presentation, when the honest schedule contradicts what a client wants to hear, or when the correct contractual position is inconvenient for someone senior.

In project controls this is the whole profession. If the reported cost and the actual cost diverge, everything downstream becomes fiction: forecasts, decisions, negotiations, trust. I have learned that the discomfort of delivering an unwelcome fact early is always smaller than the cost of a discovered concealment later, and that the reputation gained by being reliably accurate outlasts any single project.

Integrity is also internal. It means the version of me that speaks in a steering committee and the version that speaks at home are the same person, holding the same standards.

Loyalty that goes both directions

Loyalty is often described as something owed upward, to an employer or a hierarchy. I understand it as something owed in every direction, and above all to the people who cannot enforce it.

It means defending an absent colleague when it would be easier to let a criticism stand. It means not sacrificing a junior engineer to protect a schedule that was unrealistic before they arrived. It means keeping a commitment to a friend after the reason for it has become inconvenient.

Loyalty is not blindness. Covering for repeated professional failure is not loyalty; it is complicity. The distinction I use is simple: loyal to people, honest about facts.

Serve before you are asked

Helping is the principle that has returned the most and been planned the least. Most opportunities in my career came through relationships built by doing something useful for someone with no expectation attached: an explanation, an introduction, a review of a document at an unreasonable hour, time given to a young professional trying to find their direction.

Service done for return is a transaction and people can feel it immediately. Service done because it is right creates something that cannot be purchased. It also keeps a senior career honest, because a person who still helps directly stays connected to the reality of the work rather than to its reporting.

Family is the first project

Every professional in a demanding sector eventually faces the arithmetic of time, and the arithmetic does not forgive. Careers are elastic; childhoods are not. A project that slips can be recovered with a revised plan. The years in which children need presence cannot be re-baselined.

So family is not the reward for a successful career, it is the first project, with its own non-negotiable milestones. This has cost me opportunities, and I would make the same choice again. What it produces is not sacrifice but stability: a place where I am not evaluated, which is exactly what makes it possible to take professional risks.

Keep learning, and stay humble about it

Expertise expires. The methods that made me effective ten years ago are not sufficient for the way projects are governed today, and the arrival of artificial intelligence in project management is a reminder that competence is a subscription rather than a possession.

So the principle is to remain a student in public: to ask the basic question in front of juniors, to accept correction from someone with less seniority and more current knowledge, to pursue formal study even when it is inconvenient. The willingness to say "I don't know, explain it to me" is not a weakness in a leader. It is the only reliable way to keep learning after the point where people stop correcting you.

Living with the list

Principles are not decorations, and they are not achieved. They are tested, repeatedly, in small moments that rarely look important while they are happening. I have broken every one of these at some point, which is precisely why I keep them written: not as proof of character, but as a way back.

Integrity, loyalty, service, family and continuous learning: the short list I have kept through twenty years of projects, written down so that hard decisions are already half made before they arrive.. The line is light. The intention behind it is not. A life is eventually the sum of the standards a person kept when nobody was checking, and those standards are worth choosing deliberately rather than discovering by accident.