The Boardroom Conversation: From Regulatory Awareness to Strategic Governance
Part 3 of a series in collaboration with Lucia Italiano (LI Advisory Studio)
Read Part 1: “The Digital Euro Isn’t a Compliance Project. It’s a Market-Shaping Moment” and Part 2: “The Executive Dilemma: Why Readiness Begins with Sequencing, Not Compliance.”
I sat in a board meeting not long ago where a twenty-minute briefing on digital euro readiness ended, almost without exception, in nodding. The presenter was thorough. The slides were accurate. Board members asked the clarifying questions that are on everyone’s mind at the moment (i.e. the ECB timeline, about the holding limit, about how Wero was performing in other markets). The chair thanked the presenter, the meeting moved to the next item, and nothing was decided.
Nobody in that room would describe the briefing as a failure. By the usual measure, it went well: people listened, nobody was confused, no reasonable question went unanswered. But I’ve started judging board sessions on this topic by a different standard, and by that standard it wasn’t a success. It was awareness, performed competently. Governance never actually showed up.
This piece is about that gap: the one between a board that is informed and a board that can genuinely govern.
Awareness Is Not Governance
Most boards I sit across from now can recite the upcoming calendar of deadlines. They know the pilot schedule, they know roughly where the holding limit discussion stands, they’ve absorbed the point that several structural shifts are converging in the same window. That’s real progress from eighteen months ago, when half the conversation was spent simply establishing whether the topic mattered.
But regulatory fluency at board level was never the hard part, and conflating it with governance is, I think, the single most common mistake I see boards make on this subject. Boards must demonstrate the capacity to decide who owns the delivery model, what the organisation’s risk appetite actually is for a given architecture choice, or what resourcing a readiness-decision requires. Those are governance questions, and they don’t get answered by a good generic briefing, however well delivered.
The distinction matters because it changes what a board should actually be asking for. A board that wants awareness asks for updates. A board that wants governance asks for decisions, and structures its own agenda to make room for making them.
What a Board Paper That Asks for a Decision Actually Looks Like
I’ve started reviewing board papers on this topic with a simple test in mind: does this document end in information, or does it end in a decision requested? Most of the ones I see still end in information.
A paper built for awareness typically reads: here is the regulatory context, here is our current posture, here is what we’re monitoring. It’s accurate, it’s genuinely useful, and it asks nothing of the board except attention.
A paper built for governance reads differently, and the difference is structural, not stylistic. It states the decision required, in one sentence, near the top rather than buried in a recommendation. When asking for delegation, it names who would have the authority to make that decision if the board delegates it. It states what resourcing the decision implies, specifically, not as a rounding error inside a larger budget line. And it names a trigger – a specific event or date – that brings the topic back to the board regardless of whether anything has formally changed.
I worked recently with a board that rewrote its template around exactly this structure. The content didn’t change much. What changed was that every paper on this topic now ends with a line the chair reads out loud: “The decision requested today is….”.
The first time they used it, the room went quiet for a moment before anyone answered. That pause, in my experience, is usually the sign the template is doing its job.
It’s worth being honest about why that pause happens. A paper that asks for information can be received passively: everyone in the room can nod along without personally owning anything that follows. A paper that asks for a decision removes that option. Someone has to say yes, no, or not yet, on the record, and that small act of attribution is precisely what most board papers on this topic have been quietly designed to avoid, whether anyone intended it that way or not.
A Second Example, Further Along
I saw the other end of this same spectrum with a different board, further along in its readiness work, reviewing a paper that recommended committing to a specific settlement architecture ahead of final confirmation. The paper didn’t ask the board to approve the technical choice itself. That was, rightly, a management decision. It asked the board to approve something narrower and more useful: the amount of budget the organisation was willing to commit before the standards were finalised, and the conditions under which that commitment would be revisited if the standards landed differently than expected.
That’s a materially different governance act than approving a technology choice, and it’s the one boards are actually equipped to make well. Boards are rarely the right body to adjudicate a settlement architecture. They are exactly the right body to decide how much risk the organisation is willing to carry while that architecture is still being finalised, and under what conditions that risk tolerance changes. Merging the two is, I think, part of why so many boards end up deferring on this topic altogether: they correctly sense they’re not equipped to approve the technical detail, and incorrectly conclude that means there’s nothing for them to decide at all.
Three Tests for Whether a Board Can Actually Govern This
There is a short diagnostic I use to evaluate every board session on this topic now. It’s made of three questions:
First: can everyone in the room name who has the authority to approve a trade-off, specifically for this topic, without checking a document first? If the honest answer involves a pause and a guess, the authority hasn’t actually been delegated. It’s been implied, which is not the same thing, and implied authority tends to evaporate exactly when a fast decision is needed.
Second: did the last paper on this subject end in a decision requested, or a status reported? I’ve started asking board secretaries to pull the last couple of papers on digital euro readiness before I run a session. In the organisations where governance is genuinely working, at least one ends in an explicit ask. In the organisations where it isn’t, they all read like updates, however well-produced.
Third: is there a defined trigger that brings this back to the board before the next scheduled cycle, or does it only resurface because the quarterly calendar says so? A board that only revisits a fast-moving topic on a fixed quarterly rhythm is, in effect, choosing to be surprised by anything that moves faster than that rhythm. And on this particular topic, several things currently do.
Why the Gap Is Expensive
None of this is abstract. The organisations evaluated as infrastructure providers, and the ones positioning for a seat in the standards conversation, are being assessed partly on exactly this capability: can their governance keep pace with a framework that’s still being finalised. A board that can only respond on a quarterly cycle to a process moving faster than that is not well positioned for that conversation, regardless of how technically sound its underlying readiness actually is.
I see the same pattern in investor and regulator engagement more broadly. The question increasingly asked isn’t “what’s your position on the digital euro.” It’s “walk me through how and how quickly crucial decisions are made.” Organisations that can answer that specifically, naming a person, a trigger, a resourcing line, read as governed. Organisations that answer with a summary of the regulatory landscape, however accurate, read as aware but not yet in control of the decision.
There’s a quieter cost too, one that rarely shows up until much later. A board that has never practised making a real decision, under genuine uncertainty, with the trade-offs named out loud, will not suddenly develop that capability. Governance, like most disciplines, is built through repetition on smaller stakes. Boards that treat every update as low-stakes information, right up until the one that isn’t, are effectively choosing to attempt their first real decision on this topic at the moment it matters most.
“From the delivery side, the tell I look for is almost identical to Daniela’s second test. If the only paper that’s ever reached the board is a status update, the actual decision was almost certainly made somewhere below it, informally, by whoever had the most convincing voice in the room that week. The board just ratified it after the fact, without realising that’s what it was doing.”
Lucia
The Pattern Boards Get Right
Across the boards I’ve seen genuinely close this gap, the same few habits tend to show up:
- Every paper on a live, fast-moving topic states the decision requested in a single sentence, not buried in a recommendation.
- Authority to approve specific categories of trade-off is named in advance, not improvised in the room when the question arrives.
- A defined trigger reopens the topic between scheduled cycles, so the board isn’t relying on the calendar to decide when it needs to pay attention again.
None of these require a larger governance function. They require a board willing and capable to rewrite its own habits. This, in my experience, is a harder ask than it sounds, and a far better use of a board’s time than another well-delivered briefing.
What Comes Next
In the final piece in this series, we’ll go further still, into what a genuinely useful digital euro readiness assessment looks like in practice, and why so many of the ones currently being offered in the market are compliance checklists wearing an advisory cover.
If the last paper your board received on this topic ended in a summary rather than a decision, that’s usually the first thing worth changing. We’d like to hear from you.