‘A known enemy is already half disarmed’ - Louis Pasteur
There’s a moment in most complex environments where something shifts: not visibly. not dramatically, but just enough that, if you’re paying attention, you feel it.
It’s the point where patterns stop being abstract… and start pointing to something real. That moment came not through a single conversation, but through several:
Different managers
Different contexts
Different pieces of work.
And yet, the same thing kept coming up quietly, almost as an aside.
‘Yes, we’re aware of that…’
It wasn’t raised as a risk. It wasn’t escalated as a concern. It surfaced more as background noise: ‘Yes, we know about that…’, ‘That’s coming up…’, ‘We’ll need to deal with it…’
Individually, these comments didn’t stand out. Collectively, they told a very different story: There was a licence due for renewal/expiry in three months.
At one point, it had been essential because it supported a core product used throughout the business. But that product had since been transformed. Rebuilt. Replaced. On the surface, it looked like the organisation had moved on.
In reality, it hadn’t.
What Gets Left Behind
Transformation often focuses on what’s new:
New platforms
New capabilities
New ways of working
So, when you consider transformation, remember: what’s left behind - these unaddressed dependencies - can create operational risks as significant as any new system or process. Because rarely does everything move at the same pace.
In this case, several systems - and some important operational capabilities - still depended on that licence. Because over time, dependencies had become:
Embedded
Assumed
And eventually, invisible
Until something forced them back into view.
The Gap Between Knowing and Acting
By this point, it was clear that multiple people knew about the licence but no one had fully stepped up to resolve it.
This is where organisations can get caught in a very specific gap: not a gap in knowledge…
A gap in ownership.
Because when something spans teams and touches multiple systems, products, and priorities, it can quietly become everyone’s problem.
And in doing so, it becomes no one’s responsibility.
Why This Happens (More Often Than We Admit)
There are a few patterns that tend to show up in situations like this:
The original context is no longer current
The ownership model hasn’t evolved with the architecture
The work required cuts across multiple teams
And the effort to resolve it feels… inconvenient
Not impossible, just complex enough to delay.
It’s acknowledged. It’s remembered. But unless someone mobilises action, this important issue remains unresolved - and the risk of inaction grows closer.
And time continues to move.
Reframing the Conversation
At this point, there were two possible ways to approach the situation:
Treat it as a technical clean-up or recognise it for what it actually was:
A time-bound business continuity risk
The distinction matters because technical problems can be deprioritised but business risks can’t. So the conversation shifted.
Not:
‘We have a licence expiring’
But:
‘In three months, parts of the business will lose access to capabilities they still rely on’
And:
‘We have a limited window to either remove that dependency - or accept a significant cost increase for questionable value’.
That reframing ensured the issue was treated as a business-critical risk, leading to clear prioritisation and action.
The Decision Landscape
Once surfaced clearly, the options became more explicit:
Renew the licence
At a significantly increased cost
With a cost-to-value ratio that no longer made sense
Detangle the dependencies
Across multiple systems
Within a fixed timeframe
With no pre-existing coordinated plan
Neither option was trivial.
Only one option matched the organisation’s strategic direction, highlighting the importance of aligning technical choices with business goals.
From Awareness to Accountability
‘It is in your moments of decision that your destiny is shaped’ - Tony Robbins
At this point, the role of leadership isn’t to solve the problem immediately, it’s to create clarity and secure alignment. So the next step was to bring this into the right forum:
Executive leadership
Not with technical detail
Not with a fully formed solution
But with a clear articulation of:
The risk
The timeframe
The decision required
And the consequences of inaction
What followed was exactly what was needed:
Sponsorship
Priority
Urgency
And just as importantly:
Permission to act decisively.
The Moment Ownership Becomes Real
There’s a subtle but important shift that happens when something moves from:
‘Something we know about’ to ‘Something we are now responsible for delivering’.
You can feel it. The conversations change, the focus sharpens, the edges of the problem become clearer. Because now, it’s not theoretical, It’s real work with a real deadline.
But Clarity Isn’t the Same as Simplicity. At this stage, we had:
Visibility of the issue
Executive alignment
A clear direction of intent
What we didn’t yet have was:
A defined path forward
A structured plan
Or a clear understanding of how deeply embedded the problem actually was
Because the next step wasn’t just to act, it was to understand what we were truly dealing with.
This deliberate assessment of the problem laid the foundation for a solution optimised for business continuity, not just technical completion.
A Thought to Leave You With
In many organisations, the biggest risks aren’t hidden. They’re known, discussed, even accepted. But without clear ownership, they sit in a kind of operational limbo: visible, but unmoved. Until time runs out.
Awareness creates comfort.
Ownership creates action.
In summary: leaders identify risks, assign clear ownership, and transform organisational awareness into decisive action. That is when knowledge becomes results.