u/Aevitium

I've been exploring organisational silos over the past few weeks, and one question keeps emerging:

If organisations need specialist functions, how do we ensure those functions still operate as one enterprise?

Removing silos isn't realistic. Specialisation creates expertise, accountability and scale.

The governance challenge is making sure those boundaries don't also become boundaries for information, ownership and decision-making.

This becomes particularly important when outcomes cross several functions. Putting multiple functional reports into the same board pack may create visibility, but it doesn't necessarily create a coherent enterprise view.

I've explored this through three forms of connectivity: information, accountability and decisions.

I'd be interested in how others approach this.

What mechanisms in your organisation genuinely connect functional perspectives before enterprise decisions are made?

Why do highly resilient organisations (on paper) still fail under pressure?

Most companies invest a massive amount of money into operational resilience, governance frameworks, and recovery plans. Yet, when a real crisis hits, these "perfect" frameworks often fall apart.

I was listening to a discussion on this topic recently, and one point really stuck out:

Resilience is not the presence of documentation. It is the behavior of the system under stress.

True resilience isn't about perfect paperwork; it's about how your people and systems behave when your initial assumptions fail. It shifts the entire focus:

• From governance as a static structure to decision-making under high pressure.
• From resilience as a framework to resilience as an organizational capability.
• From documenting accountability to understanding how people actually act when conditions change.

The real breakdown happens when priorities conflict, information is incomplete, and teams have to move fast. That’s when culture and leadership take over, completely rendering the documented process irrelevant.

For those managing risk or team structures: What do you think has the absolute greatest influence on a company's resilience when real pressure hits? Is it leadership, culture, or something else entirely?

(Note: This was inspired by a recent RiskMasters podcast episode with Frédéric Gielen if anyone wants the deeper dive/links, but I really want to hear Reddit's take on this friction between paper compliance vs. reality).

One observation keeps appearing in operational resilience.

Individual teams often recover successfully.

IT restores systems.

Operations resumes activity.

Suppliers recover.

Yet the customer-facing service is still unavailable.

The problem isn't individual recovery.

It's whether the organisation can reconnect all of those capabilities into a functioning end-to-end service.

I'm interested whether others working in resilience, continuity or risk management have experienced this.

Do organisations spend too much time measuring functional recovery instead of service recovery?

Newsletter here if anyone is interested: https://www.aevitium.com/so/1fP_vr3m6?languageTag=en

I've been researching why important risks often reach executive teams and boards only after organisations have already absorbed significant operational strain.

One conclusion surprised me.

Most discussions focus on culture, psychological safety or whether employees are willing to escalate.

I'm increasingly convinced that governance design deserves much more attention.

If teams are rewarded for resolving issues locally, then delaying escalation becomes a rational response rather than a behavioural failure.

That raises some interesting questions.

• Should escalation be based on impact or on trajectory?
• Should capacity constraints be treated as an escalation trigger?
• Does governance place too much emphasis on issue closure rather than decision quality?

I'm interested in hearing how others have seen this play out in practice.

No promotional link. Reddit responds much better to genuine discussion than promotion.