Independent advisor · Structural governance

Naming where authority and consequence have come apart.

My work is with leadership teams, executives, and individual employees on authority and decision rights — who gets to decide what, when, why — and what happens downstream when coherence is not held.

I’m the person you call when things feel off, are hard to name, and the fix isn't working. Usually by then, the potential consequences feel very real too. In that moment, clarity is what helps.

What makes for smooth operations does not live in your org chart, SOPs, the dashboards, or which software you use.

It's how clear the authority structure is, and whether that's held in practice, versus something that exists on paper.

When structure is unclear — and I am not referring to your org chart here — someone, somewhere, is holding up the organization by hand. (Often multiple someones.)

  • That can be a COO or a VP — with a CEO who's not seeing the whole picture.
  • That can be an EA or IC — with a manager distanced from day-to-day operational complexity.
  • It is sometimes a whole team, department, or a division that's closing cross-functional gaps that aren't theirs to close alone.
  • Or anyone in between.

Over time it leads to burnout and morale issues, and your best people leaving with legacy knowledge you cannot replace with a new hire.

When the same problems keep surfacing, internal efforts to correct them get more intense.

Instead of resolving the issue, the increasing pressure simply asks for heroics, and burns out your best people.

The issue isn’t effort or commitment. It's not communication or tooling either.

Determining the actual root cause — the underlying conditions creating the environment — is critical before we can determine what kind of correction is actually possible, or even survivable.

By "survivable" I mean the correction is:

  • politically neutral enough to be accepted
  • sharp enough to make a difference
  • feasible within your current operating constraints

My work is diagnostic before it is corrective because until we determine what situation is actually present, any recommendations or forward motion can increase risk.

Determining what not to do is a first-class result.

Organizational dysfunction does not require malice or incompetence — and it's not a moral failing either.

Your organization, your leadership team, and your staff are not uniquely defective because your fixes failed and you didn't catch it sooner. It's understandable to look at capacity, communication, and tooling first.

But when the usual fixes do not resolve it — especially under pressure?  That's a sign of separation between where authority lives, and where consequence lands.

There are 3 things you need to know about structural drift:

  1. It does not correct on its own. If you found yourself on this page, I encourage you to take the signal that got you here seriously.
  2. Your most conscientious employees will absorb the ambiguity until they cannot anymore — and that is often when things start failing in more painful ways.
  3. Misdiagnoses and delay compound the risks. The longer things go, the harder it is to correct.

Throughput ≠ Capacity

When individuals are responsible for filling gaps, holding context, translating across functions — things they don't have authority for — that buffering becomes invisible infrastructure.

Sometimes organizations mistake that containment for capacity.

It isn't. It's the system spending its energy holding itself together in a broken loop.

When — not if — that fails, it reads as performance failure and is blamed on individuals, rather than unclear structure or ambiguous authority.

That misdiagnosis compounds risk by hardening incorrect thinking into "the way we do business."

The longer this goes on, the harder it is to correct without backlash. Distortion continues until it becomes genuine dysfunction.

Naming root cause and 2nd- and 3rd-order effects is hard to do when you are inside the system.

There are always aspects you don't know, or can't see yet.

Even if you do know what's off in your organization, political or social pressure may make naming the dysfunction risky.

Two things are reliably true:

  1. Structural coherence benefits from a mirror.
  2. Systems reject what they cannot metabolize.

I can help you navigate both, regardless of your title or authority.

Decisions stay open longer than they should. They route sideways, get revisited without new information, or collapse back to the top under pressure.

Responsibility lands on people who do not have the authority to resolve what they are being held accountable for. The most conscientious people absorb the ambiguity. Their stabilizing work becomes invisible, then expected, then load-bearing.

From above, throughput may look acceptable. From inside, it is being held together manually — by people tracking what the system does not, filling gaps the structure left, and compensating for decisions that were never made cleanly.

Urgency becomes the operating model. Capacity gets redirected into containment — clarifying, chasing, patching, re-deciding — and that containment reads, from a distance, as execution failure.

When things go wrong, the first explanations are often related to communication, commitment, performance, tooling, the wrong hire, the last consultant. Some of those things may be partially true. They are often not the root cause.

When structure is not holding, everything downstream is being distorted by that.

If my writing feels familiar before it feels explanatory, that is intentional.

Structural coherence is felt. Structural thinking can be taught, but it takes time to see the patterns and can be hard to diagnose from inside your own organization.

Learn more here:

The Methodology page describes how I assess what is present and what can change.

The Services page describes the engagement structure and what each tier is for.

If you want a clearer read on the kinds of situations I write and think about, join the email list below.