The other side of transformation

The other side of transformation


A new system can be technically sound, delivered on time and supported by training, yet still make surprisingly little difference to how people actually work.

Spreadsheets survive. Workarounds appear. Familiar processes find their way into the new environment. The implementation may be complete, but the transformation is not.

That distinction matters as technology plays a larger role in everyday work. AI is changing how information is processed and decisions are made, while many of the systems, tools and ways of working around us are shifting at the same time.

But what technology makes possible and what an organisation is ready to do are not always the same thing.

To explore that question, I spoke with Joel Spenner, CEO of Spenner Performance Services, a change management and performance consultancy whose work focuses on organisational change, adoption and workforce readiness.

When does technology become transformation?

A system can go live, people can complete the training and the project can be considered successfully delivered without necessarily changing how the organisation works. What has to happen before implementation becomes real transformation?

“Technology becomes transformation when it stops being something people have been given and becomes part of how they actually work.

That means consistent adoption, but adoption alone is not enough. New behaviours have to replace old habits, the organisation has to be ready to support those behaviours, and the technology has to deliver the value it was introduced to create.

It also cannot end at go-live. People learn what works, what does not and where the system or process still needs to adapt. Real transformation comes when adoption, behavioural change, organisational readiness and value begin to reinforce one another over time.”

Why do old habits survive?

Even after new technology is introduced, people often keep spreadsheets, workarounds and familiar routines alive. You have also pointed out that a new system can suddenly make someone who was highly experienced feel like a beginner again. What is really happening when people fall back into the old way, and how often do organisations mistake that for resistance?

“What looks like resistance is often something much more practical.

People return to what they know because it feels easier and requires less cognitive effort. A spreadsheet or workaround may not be the best solution overall, but in the moment it can still feel like the quickest or safest way to get the job done.

There is also a loss of confidence that can come with change. Someone who knew exactly how to navigate the old environment can suddenly feel inexperienced in the new one. If the training is not enough, or if the benefits of the change are not visible in the reality of their work, returning to familiar methods becomes understandable.

Organisations can be too quick to call that resistance. Often, the deeper issue is that the change has not been sufficiently connected to the reality of the people doing the work.

When leadership involves the people responsible for the success of the change effort in developing the strategy, you transform resistance into enablement. People rarely resist change that they helped to create.”

What does leadership have to get right?

Change asks people to learn, make mistakes and sometimes accept that they will initially be less effective at something they used to do well. What should leaders be doing during that transition, and what role do trust and honest dialogue play in whether people actually move with the change?

“Leaders have to make the competence dip safe.

People need to understand where the change is going and why, but they also need support while they adapt. Leaders have to communicate consistently, model the behaviours they expect from others and recognise that there will be a period when people are learning and may not perform with the same confidence they had before.

That is where trust and honest dialogue matter. People need to be able to say that they are struggling, ask questions and raise concerns without feeling judged for doing so.

Trust and dialogue are what turn compliance into commitment. When people feel safe admitting difficulty, the pull of the old way starts to weaken. Change becomes something they participate in rather than something being imposed on them.”

Is AI different?

AI feels different from many previous technology shifts because it can affect not only the tools people use, but how decisions are made, where expertise sits and how people think about their own role. At the same time, it is arriving while many other technologies and ways of working are shifting around us. Does AI fundamentally change the human side of transformation, or are we seeing the same organisational questions in a new form?

“AI amplifies many of the same dynamics, but the fundamental human questions remain remarkably similar.

Organisations still have to think about adoption, behavioural change, leadership, readiness and whether the technology is actually creating value. What changes with AI is the intensity of some of those questions.

AI can influence decisions that previously relied on human judgement. It can redefine roles, shift where expertise sits and force people to think differently about what they contribute.

So the underlying organisational challenge may be familiar, but the stakes around expertise and professional identity can be higher. That makes strong leadership and organisational readiness even more important.”

What does success actually look like?

Go-live dates, training completion and system usage are relatively easy to measure. Whether people are genuinely working differently is harder. If you returned to an organisation six months after a major implementation, what would tell you that the transformation had actually worked?

“I would look first at whether the new way of working has become self-sustaining.

Are people using it consistently without having to be pushed? Have new workflows genuinely replaced the old habits? Is the organisation seeing the value it expected, whether that is greater efficiency, better decision-making or another intended outcome?

There is also a human signal. People begin to own the change. They help colleagues, teach each other and can talk openly about mistakes and what they have learned. They work confidently rather than simply following the new process because they have been told to.

Six months in, transformation has worked when the new way no longer depends on the project team to keep it alive. The value is visible, people are confident in how they work and the old workarounds have disappeared because they no longer serve a useful purpose.”

When change stops feeling like change

The clearest distinction is between introducing a new way of working and reaching the point where it simply becomes the way the work is done.

Technology can provide the capability. Training can explain it. Leadership can create the conditions for people to adopt it. But none of those, on their own, mean that an organisation has changed.

The more meaningful signals appear later: when people stop reaching instinctively for the old workaround, when they are comfortable admitting what they do not yet know, when they help others navigate the new way and when the benefits begin to show in the work itself.

That may become even more important as AI expands what organisations are capable of doing. Technology can move quickly. Building the confidence, trust and behaviours required to use it well takes something different.

The other side of transformation is reached when change stops feeling like change and simply becomes the way the work is done.

L’équipe que tout le monde voulait rejoindre

L’équipe que tout le monde voulait rejoindre


L’équipe que tout le monde voulait rejoindre

Certaines expériences professionnelles restent avec nous bien après avoir changé de poste, d’entreprise ou même de pays.

Pour moi, l’une d’entre elles remonte à mes années en France.

Nous étions l’une des équipes les plus performantes de la région. Les résultats étaient là dans des domaines très différents : entrées en relation, assurance, promotion immobilière, investissement. Les trophées s’accumulaient et il y avait peu de semaines sans une raison de lever un verre pour célébrer quelque chose.

Mais ce n’est pas vraiment pour cela que je m’en souviens.

Je m’en souviens parce que nous prenions énormément de plaisir à travailler ensemble.

Les gens avaient envie de rejoindre notre équipe. Il y avait une énergie particulière, au travail comme en dehors. Nos célébrations et même nos fêtes de Noël avaient fini par avoir leur petite réputation.

Au centre de cette équipe se trouvait Carlos Ribeiro Lopes.

Après une longue carrière dans le secteur bancaire et plusieurs responsabilités au Crédit Agricole Alsace Vosges, Carlos a récemment rejoint Groupama Grand Est comme Responsable du secteur de Sélestat, Marckolsheim et Villé.

Mais pour moi, il restera surtout le leader qui m’a fait découvrir une certaine manière de construire une équipe.

Avec les années, j’ai réalisé à quel point certains des principes que j’avais observés à l’époque me marquent encore aujourd’hui : faire confiance, laisser de l’autonomie, accepter que les gens soient différents, pouvoir se dire les choses, protéger son équipe et ne jamais oublier les personnes derrière les résultats.

À l’époque, je ne mettais pas nécessairement de mots dessus. Nous travaillions, nous gagnions, nous célébrions et nous recommencions.

Aujourd’hui, avec davantage de recul, je comprends mieux pourquoi cette expérience a autant influencé ma propre vision du leadership.

Alors, plusieurs années plus tard, j’ai proposé à Carlos de revenir ensemble sur cette période et sur ces principes qui, bien au-delà des résultats que nous obtenions à l’époque, continuent de me marquer aujourd’hui.

Pourquoi certaines équipes deviennent-elles plus que la somme de leurs talents ?

Nous étions très différents.

Nous n’avions ni les mêmes personnalités, ni exactement les mêmes compétences. Personne n’était excellent partout.

L’un était particulièrement fort en investissement, un autre en assurance, un autre dans la conquête de nouveaux clients. Et quand quelqu’un ne savait pas faire quelque chose, il savait généralement qui appeler.

Nos faiblesses individuelles devenaient beaucoup moins importantes parce que les forces des autres étaient juste à côté.

Carlos, quand vous repensez à cette équipe aujourd’hui, pourquoi pensez-vous que cela fonctionnait aussi bien ? Est-ce que vous aviez consciemment cherché cette complémentarité ou est-ce quelque chose qui s’est construit progressivement ?

Les réussites individuelles et collectives se sont construites sur plusieurs piliers.

Le premier, qui est la base de tout, était de connaître chaque individualité, ses forces, ses points d’amélioration, mais surtout ses motivations.

Après ce constat, le deuxième pilier était de construire collectivement un projet auquel tout le monde adhère avec ses motivations et ses qualités. Les points d’amélioration restaient du domaine du manager : c’était à moi d’aider chaque personne à progresser en m’appuyant sur les qualités et les réussites déjà acquises, ce qui me permettait de mettre en œuvre le troisième pilier.

La culture de la réussite et de la performance basée sur les valeurs humaines et leurs contributions au collectif, qui grandissait au fil du temps pour atteindre le sommet.

Jusqu’où faut-il faire confiance ?

Il y avait beaucoup de liberté.

Carlos nous faisait confiance pour faire notre travail. Nous savions ce qui était attendu de nous, mais nous avions de l’espace pour trouver notre manière d’y arriver.

Cela ne voulait pas dire qu’il était absent.

Quand quelqu’un avait besoin d’aide, il était là. Quand une situation devenait difficile, il intervenait. Mais le point de départ était la confiance, pas le contrôle.

C’est probablement l’une des leçons de leadership qui m’est le plus restée.

Comment trouvez-vous cet équilibre ? Comment un leader sait-il quand laisser faire et quand intervenir ?

Pour faire confiance, il faut connaître les valeurs et qualités humaines et apporter son soutien en fonction des besoins, savoir gérer les efforts, savoir surtout valoriser les réussites individuelles, mais surtout collectives.

Pour savoir quand et comment intervenir, il faut très bien connaître chaque personne, savoir analyser ses états d’âme, ses préoccupations et savoir laisser souffler quand il faut.

Tout repose sur l’analyse comportementale de chaque personne et sur le fait de savoir trouver les bons mots au bon moment. Savoir être proche sans être opprimant et savoir donner de l’autonomie sans être absent.

La clé de la réussite repose sur la disponibilité pour chaque personne quand elle en a le plus besoin, en pensant toujours à la réflexion d’un grand homme d’affaires qui résume son management par cette phrase :

« Les premières personnes qui rentrent dans un établissement, quel qu’il soit, ce sont les collaborateurs et non les clients. Alors traite tes collaborateurs comme tu souhaites qu’ils traitent tes clients. »

Une bonne équipe doit-elle toujours être d’accord ?

Nous ne l’étions certainement pas.

Les personnalités étaient fortes et nous étions directs. Les désaccords existaient, parfois franchement, mais ils remettaient rarement en cause la relation entre les personnes.

On pouvait ne pas être d’accord, se le dire et continuer ensuite à avancer ensemble.

Avec le recul, je me demande si une partie de notre efficacité ne venait pas précisément de là. Nous passions peu de temps à gérer ce qui n’avait pas été dit.

Comment crée-t-on suffisamment de confiance dans une équipe pour que les gens puissent se dire les choses sans que chaque désaccord devienne un problème personnel ?

Le sujet est très complexe et difficile, car il repose sur la capacité et la volonté à se dire les choses. Le manager ne doit surtout pas accepter d’être un bureau des pleurs ou des réclamations.

Quand il y a des tensions, des différends, des non-dits, le rôle du manager n’est pas de les régler mais de faire en sorte que les personnes les règlent entre elles.

Pour cela, on revient au premier pilier : connaître suffisamment chaque personne pour qu’elle fasse confiance à son manager pour en parler, puis faire confiance à ses collègues pour évoquer les irritants et accepter de les résoudre, en sachant que cela peut remettre en cause certains comportements ou attitudes personnelles.

Ce qui aide énormément, c’est que le collaborateur ait assez confiance en son manager pour évoquer les erreurs, les manquements, sans craindre d’être réprimandé. Le bon manager écoute, analyse, règle le problème et explique toutes les conséquences pour le client et pour l’entreprise, et s’assure que la personne ait appris.

Un bon manager est celui qui est respecté, pas celui qui est craint.

Qui porte la responsabilité quand quelque chose ne fonctionne pas ?

Il y a un principe de son leadership qui m’est resté plus que beaucoup d’autres.

Carlos nous protégeait.

Quand nous réussissions, c’était notre succès.

Quand quelque chose tournait mal, c’était sa responsabilité.

À l’époque, je trouvais probablement cela normal. Avec le temps, j’ai compris que cela ne l’était pas nécessairement.

Et je me demande si une partie de la confiance et de l’autonomie dont nous disposions ne venait pas précisément de là. Nous savions que nous étions responsables de nos résultats, mais aussi que notre leader ne disparaîtrait pas au premier problème.

Est-ce que cette manière de protéger l’équipe était consciente ? Jusqu’où un leader doit-il prendre la responsabilité de ce qui se passe dans son équipe ?

Le manager est toujours le premier responsable d’un dysfonctionnement.

J’ai toujours considéré que si un collaborateur honnête et engagé commet une erreur, c’est parce qu’il ne sait pas faire, donc j’ai failli à mon rôle de formateur, d’accompagnateur.

Mon rôle est de le protéger face aux conséquences. Cependant, l’exigence arrive après.

Car s’il sait, s’il a eu le temps de bien faire et qu’il répète les erreurs, alors l’exigence doit prendre le pas et il faut recadrer la situation, avec, s’il le faut, une remise en question de la continuité sur le poste.

Peut-on demander beaucoup sans oublier la personne ?

Je garde aussi de cette période un souvenir beaucoup plus personnel.

Un jour, Carlos avait compris que je n’allais pas bien.

Il a annulé mes rendez-vous et pris le temps de s’asseoir avec moi et de parler.

Des années plus tard, je ne me souviens plus exactement de ce qu’il m’a dit. Mais je me souviens parfaitement d’avoir compris que, ce jour-là, la personne comptait davantage que le résultat.

Ce sont des gestes que l’on ne retrouve dans aucun tableau de performance. Pourtant, ce sont parfois ceux dont on se souvient le plus longtemps.

Et peut-être aussi ceux qui expliquent pourquoi, lorsque l’équipe avait besoin que l’on donne davantage, nous étions prêts à le faire.

Peut-on demander beaucoup aux gens précisément parce qu’ils savent que, lorsque cela compte vraiment, leur leader sera là pour eux ? Quelle place donnez-vous à cette dimension humaine dans la performance d’une équipe ?

La dimension humaine est le pilier principal, je dirais même le seul, pour construire un niveau de performance élevé mais surtout durable.

Il est facile d’obtenir d’excellents résultats. La véritable difficulté réside dans la capacité à les obtenir de façon régulière, voire permanente.

Et qu’en reste-t-il des années plus tard ?

Cette histoire n’était évidemment pas seulement la mienne ou celle de Carlos.

J’ai donc retrouvé quelques-uns de ceux qui l’avaient vécue avec nous et leur ai posé une seule question :

Qu’est-ce qui faisait, selon vous, que cette équipe fonctionnait ?

Robin Guerin

On était avant tout un sacré collectif, avec chacun nos forces respectives, mais qui se sont archi bien complétées ! Un hasard ? Sans doute un peu, mais on a su le cultiver et l’enrichir avec le temps.

On a su intégrer aussi les nouveaux éléments, qui se sont fondus rapidement dans notre groupe. Ça n’aurait peut-être pas fonctionné avec n’importe qui non plus… Qui sait ?

Mais je pense que le principal artisan de tout cela, c’était Carlos, qui a su composer avec chacun de nos caractères pour en tirer le meilleur. Il a absorbé la pression pour nous laisser faire ce que l’on savait faire de mieux.

Les résultats sont arrivés tout naturellement, ce qui a engendré beaucoup de confiance. On a gagné des challenges, on est partis en vacances, on a gagné des sous. Bref, on ne pouvait plus nous arrêter, on était les meilleurs à ce moment-là.

On était contents de venir travailler le matin, de se retrouver et d’aller manger ensemble le midi. Il y avait une petite vie de famille et une ambiance de dingue.

Par contre, je suis certain que cela ne se provoque pas. C’est très difficile de créer cela de toutes pièces, l’alchimie est parfois très dure à trouver. Ce que l’on a fait est génial, et c’est pour cela que cela reste exceptionnel de le vivre dans une carrière. Malheureusement, toutes les bonnes choses ont une fin…

Finalement, pour conclure, le manager a un rôle déterminant, mais il faut aussi que le terrain ne soit pas trop miné dès le départ.

Comme point de départ à tout cela : je pense que cela a réellement débuté le soir de la soirée de Noël, au resto brésilien, où on a fini la fiesta au bout de la nuit alors qu’il fallait aller bosser le lendemain… Incroyable souvenir, et le début d’une grande aventure.

On est plus que des collègues maintenant, on est des amis. 

Matthieu Boccardo

Mon regard est particulier puisque j’étais le stagiaire de l’époque pendant trois mois. Si l’équipe fonctionnait si bien, c’est parce qu’il y avait un équilibre rare entre rigueur pro et convivialité. Vous m’avez intégré comme un membre à part entière de la team dès le premier jour.

C’est cette culture d’équipe hyper soudée qui a boosté mes débuts et dont je m’inspire encore aujourd’hui.

Et si c’était à refaire ?

Beaucoup d’années ont passé depuis.

Nous avons tous suivi des chemins différents. Carlos a continué à diriger des équipes. De mon côté, cette expérience m’a accompagné à travers plusieurs pays, entreprises et responsabilités.

Et une dernière question pour Carlos :

Si vous deviez reconstruire demain une équipe comme celle-là, avec tout ce que vous savez aujourd’hui, qu’est-ce que vous referiez exactement de la même manière ?

Je ne changerais quasiment rien sur la méthode. Avec le recul et les autres expériences, j’aurais pu mieux gérer mes émotions et comprendre que certaines personnes ne sont pas forcément prêtes et n’ont pas forcément les mêmes ambitions collectives.

Ce qui me frappe en lisant les réponses de Carlos, Robin et Matthieu, c’est que nous ne nous sommes pas concertés.

Et pourtant, dix ans plus tard, nous racontons au fond la même histoire.

Carlos n’est plus notre leader depuis longtemps et cette équipe n’existe plus. Mais quelque chose de ce qu’il avait construit est resté : dans les relations entre nous, dans la manière dont chacun se souvient de cette période et, pour ma part, dans ma façon de penser le leadership aujourd’hui.

On parle beaucoup de ce qu’un leader obtient de son équipe lorsqu’il la dirige.

Peut-être que la vraie mesure de son impact est ce qu’il en reste des années plus tard.

When risk becomes a business partner

When risk becomes a business partner


When Risk Becomes a Business Partner

I have known Adrianna Fabijanska for quite a few years now.

One of the things I have always valued about her is her curiosity. She is one of the sharpest people I know in her field, but she is also constantly asking what is changing, why it matters and whether the way we think about something still holds.

Over the years, we have discussed compliance, markets, tokenisation, emerging technologies and broader questions where the right answer is not immediately obvious.

Adrianna is now CEO & Founder of Meridian Risk Intelligence Ltd, after a career spanning financial crime compliance, global advisory, assurance and risk. She was most recently Global Head of Financial Crime Compliance - Investment Banking and Global MLRO for Investment Banking at ING, a global systemically important bank. Earlier, she held senior international compliance roles, led regulatory remediation and transformation programmes and served as a regulator, including sitting on the supervisory boards of strategic entities in energy and markets infrastructure.

Today, Meridian Risk Intelligence Ltd advises asset managers, banks and other financial institutions at the intersection of compliance risk and emerging risks. Its work includes the design and delivery of financial crime and compliance enhancement programmes, digital and crypto assets, AI and geopolitics.

My own perspective is shaped by 15 years in business development across different products, markets and complex situations. That experience has left me with a fairly simple belief: when business and risk are genuinely aligned, there is very little that cannot at least be explored.

With Adrianna now building Meridian Risk Intelligence Ltd and experiencing the commercial side more directly, it felt like a natural moment to bring those two perspectives together around one key question: when does risk become a business partner?

What does being a business partner actually mean?

We use the term business partner rather easily.

My best experiences with risk have never been about getting an easy yes. They have been about someone willing to understand what the business is trying to achieve before reaching a conclusion.

So I asked Adrianna where she sees the difference between assessing an opportunity and helping shape one.

“The difference is timing and intent. Assessment happens once a proposition already exists: the structure is chosen and expectations have already been set. The risk role at that point is close to binary.

Shaping happens earlier, while the problem is still open. That is where a risk professional can influence the structure, the controls that are designed in rather than bolted on, and the information needed before commitment rather than after.

But early involvement does not mean co-ownership of the commercial outcome. The second line, and the MLRO above all, carries an independent judgement that must survive the relationship intact.

For me, the principle is simple: risk can be fully invested in helping the business find a good answer, and entirely uninvested in whether that answer is yes. That is what makes the partnership credible.”

That distinction matters. Partnership is not about making risk more likely to say yes. It is about making its perspective useful without weakening the independence that gives it value.

Should risk get closer to the commercial context?

If timing is the first part of the equation, proximity is the next. Once risk is involved, how close should it get to the underlying commercial context?

I have seen how easily nuance disappears as information moves from one person to another. A situation described second-hand is rarely quite the same as hearing the context directly.

So I asked Adrianna whether proximity actually improves risk judgement, and where the boundary should sit.

“Very much so. Poor risk decisions are often caused not by poor judgement but by poor information. Commercial context can pass through several layers, and important nuance can disappear before it reaches risk.

Hearing the context directly allows me to ask the questions that matter and to hear how they are answered. Hesitation, over-explanation and precision each tell you something a written summary cannot.

Risk functions talk a great deal about wanting a seat at the table. The less-discussed truth is that you also need a business that wants risk there - as a matter of governance, not goodwill.

At the same time, proximity must never become advocacy. Risk is there to listen, question and form a view, not to become the commercial champion. Risk attends and challenges; business owns and decides.

Closer, yes. Captured, never.”

That is the balance: better information without blurred accountability.

What happens when there is no playbook?

That balance becomes harder when the subject itself is new.

This becomes particularly interesting in areas where the answer is not obvious. Tokenisation is one example. Digital assets and AI give us plenty more to discuss.

New markets and technologies rarely arrive with years of precedent behind them. That creates opportunity, but also uncertainty.

Adrianna starts by questioning the word new itself.

“I begin by refusing to treat ‘new’ as a risk category. ‘New’ describes the market, not the risk. Strip away the novelty and most of the underlying questions are familiar: who is the counterparty, where does value come from and go, who controls it, and can we evidence what is happening?

The next step is separating what is genuinely unknown from what is merely uncomfortable. Uncertainty that can be reduced through more information, expertise or a bounded pilot is a reason to keep working. Risk that cannot be reduced, contained or monitored is a reason to stop.

I use three tests: can I explain the risk and its mitigation to a regulator in plain language? Would we detect it going wrong ourselves? And is the residual risk within an appetite the board has actually approved?

If those tests hold, uncertainty becomes a design brief. If they do not, the answer may be not yet, which is very different from no.

Intellectual honesty about uncertainty is itself a control.”

I like that idea because it reaches beyond compliance. Uncertainty does not automatically mean stopping. Sometimes the better response is to define what remains unknown, what can be reduced and what would need to be true before moving forward.

Is “no” sometimes where the interesting work starts?

Of course, sometimes the answer is still no. Not every opportunity should happen.

But there is an important difference between we can’t do this and we can’t do it this way. The second leaves room to understand whether the problem is the opportunity itself or the way it has been designed.

That does not mean risk should become the architect of the solution.

“The moment risk starts redesigning the transaction, risk becomes its author, and nobody can independently challenge their own design.

Risk can define the concern and the outcome that needs to be achieved; the business owns the redesign. Risk can say what would need to be true, not how the proposition should be structured.

Some decisions also have to remain outside the commercial conversation altogether, particularly around suspicious activity reporting, certain exit and sanctions decisions, and the handling of law-enforcement or regulatory enquiries. A partnership, however strong, cannot become a channel through which those decisions are influenced. In my own MLRO roles those decisions sat outside any commercial relationship, including the ones I valued most, and that is exactly how it should be.

Those safeguards do not undermine partnership. They are what allow it to exist, because independence has to be protected by design rather than by personality.

The same principle applies when business and risk disagree. Both sides should arrive with reasons rather than positions, and the challenge should be directed at the proposition rather than the person. Quiet compromise is where independence dies.

And independence does not mean assuming risk is always right. I have been wrong. A partner who tells me that a control I have proposed makes no operational sense is doing me a favour.”

That last point matters. Good partnership does not eliminate disagreement. It makes disagreement useful.

What should business development understand better about risk?

If business expects that kind of partnership from risk, the expectation has to work in both directions.

So what should those of us in business development understand better?

“First, when risk says no, it is rarely only about one specific case. Risk is also thinking about what would need to be explained to a regulator, a court, a correspondent bank or a board if things go wrong.

Second, the downside is asymmetric. A hundred good decisions earn little visible recognition; one bad decision can cost a licence, a relationship or a reputation built over decades.

Third, information delivered late is itself a risk. Bring the ambiguous facts early and unpolished. I would rather hear in week one that something looks odd than discover it in week eight once expectations have already been created.

And documentation matters. It is the memory of the decision and protects the business at least as much as it protects risk. Written compliance is not operating compliance, but operating judgement that was never written down does not exist when it is tested.”

That is probably the most practical lesson for the business side. Our instinct can be to bring something forward once it looks sufficiently developed. But the uncomfortable or unclear parts may be exactly what need to surface first.

What changes when you sit in both worlds?

This is where Meridian Risk Intelligence Ltd makes the discussion particularly interesting.

Adrianna is now building relationships and making commercial decisions herself, while bringing years of experience looking at complex questions through a risk lens.

So has being closer to the commercial side changed her view?

“Reinforced, but with a sharper edge. Building Meridian Risk Intelligence Ltd, I now feel the weight of a pipeline, the cost of a delayed decision and the pull of a commercial opportunity - and a sharper appreciation of why the second line’s independence must be structural rather than personal, so that it never depends on who is in the room. That has given me a far deeper respect for what business development colleagues carry.

It has also made me more convinced, not less, that independent risk thinking can be a commercial asset rather than an overhead. What organisations need is someone who understands the business well enough to say no in a way that opens a different door.

For me, that comes back to mutual literacy: risk that understands commerce, and business that understands risk.

That literacy has to work both ways. Just as business needs to understand risk, the risk function needs to understand how the business makes money, how its products work and what it is trying to achieve. That is what allows risk to challenge in a language the business can act on.

Looking back, the independence required by the roles I held did not constrain partnership. It was what made it possible, because the business could trust that my yes meant something.

But above all, it takes people. Partnership is not a framework or a governance chart. It is a relationship built through many conversations, some of them awkward, over years.”

Where does that leave us?

What strikes me after this conversation is how little of it is really about compliance in the narrow sense. It is about whether two different perspectives can meet early enough, and understand each other well enough, for the difference between them to become useful.

Timing matters. Boundaries matter. And partnership has to work both ways.

That is why Adrianna’s idea of mutual literacy resonates with me. Business and risk do not need to think alike. They need to understand each other well enough to challenge each other intelligently.

Looking across 15 years, I can think of many situations, across different firms and markets, where a risk partner who thinks the way Adrianna does would have made the decision better. Not because the answer would have been easier, but because the thinking around it would have been.

That, to me, is the real value of a strong risk partner. They do not remove the complexity or guarantee the answer you want. They make the thinking around it better.

Find your risk partner early, and earn the right to keep them close.

A note on scope and independence. This conversation is about how business development and risk work together as a matter of general professional practice. It does not draw on or comment on any specific transaction, client, counterparty, escalation, suspicious activity report, exit decision, sanctions matter or regulatory engagement either of us has worked on. The MLRO role carries its own independent responsibilities, protected by governance rather than relationships, and nothing in this article should be read as suggesting that this independence can be influenced by proximity to the business. The views expressed are personal and do not represent any current or former employer or organisation.

Intelligence, investigations and the wider MLRO remit raise a distinct set of questions, which the authors may return to separately.>