Leadership When Every Option Hurts

If you’ve ever waited for a decision to feel “right,” you’ve probably spent time leading through the grey.

One of the hardest truths about leadership is that some decisions don’t come with a good option. They come with a least-harmful one.

When I made a deeply difficult, life-impacting decision recently, it wasn’t because I felt confident or because I had all the information I wished I had. It wasn’t driven by certainty or calm.

It was driven by the understanding that waiting would not bring clarity—only more risk.

At some point, leadership requires you to stop collecting data and start weighing consequences. You accept that incomplete information is part of the reality, not a failure of preparation.

This is what leadership looks like when every option hurts. You stop looking for the decision that feels good and focus instead on the one that reduces future harm.

I didn’t move forward because the decision felt clean. I moved forward because standing still was quietly causing more damage than choosing a direction.

This is why structure, systems, and governance matter. They exist for moments like this—when emotions are high, information is incomplete, and the cost of inaction outweighs the discomfort of action.

Whether you’re leading a family, a team, or an organization, the question rarely is:
Do I feel confident?
Do I have perfect information?

It’s:
Does this decision create the best chance for stability, safety, and improvement—even if it comes at a personal cost?

Leadership in the grey isn’t about certainty or perfection. It’s about responsibility—and the courage to carry it when no one is comfortable.

Empathy Is Not the Same as Emotional Decision-Making

One of the hardest parts of leading through the grey is learning where emotion belongs—and where it doesn’t.

There’s a quiet belief many of us carry: if a decision feels painful, it must be wrong. If someone we care about is upset, we assume we’ve failed.

That belief keeps leaders stuck.

When I made a deeply personal, life-impacting decision recently, emotion was everywhere. Fear, guilt, sadness, doubt. None of those emotions were wrong—but none of them could be allowed to decide for me.

I had to separate empathy from emotional decision-making.

Empathy meant acknowledging the pain the decision caused.
It meant staying present with anger and hurt.
It meant not dismissing how hard this was for someone I love.

But emotional decision-making would have meant prioritizing relief—mine or his—over stability. It would have meant backing away from a necessary decision because sitting with the discomfort was too hard.

That distinction matters.

We ask leaders to do this all the time at work. To enforce a process that isn’t popular. To address a financial issue before it becomes a crisis. To make a structural change even when people are unhappy about it.

Avoiding those decisions often feels kinder in the moment. In reality, it usually transfers harm forward.

Empathy belongs in how we communicate decisions.
It belongs in how we support people through them.
It does not belong in whether we act when responsibility calls.

Leading through the grey means holding compassion in one hand and accountability in the other—and refusing to confuse the two.

Sometimes the most empathetic thing you can do is make the decision anyway.

When There Is No Right or Wrong Decision—Only Responsibility

I’ve been quieter than usual this past month. Not disengaged—just living inside a decision that required more presence than words.

Over the years, I’ve written about leading through the grey—those moments when decisions aren’t clean and certainty isn’t available. That grey space doesn’t belong only to leadership roles at work. It exists just as clearly in personal life.

Recently, I had to make a deeply difficult, life-impacting decision to increase the level of care for someone I love very much.

At first, the fear was about timing. I worried I had acted too quickly. I questioned whether fear had pushed me into overreacting. But when I forced myself to look honestly at the alternative—the cost of underreacting—the answer became clearer, even if it didn’t become easier.

I could live with the possibility that I acted too soon.
I could not live with the outcomes that might come from waiting too long.

There was also a quieter fantasy I had to let go of: the hope that one day he would be grateful. That he would be happy I made this decision. That he would look back and thank me for it.

That’s not realistic. I know he’s upset. I know he may be for a long time—maybe years, maybe forever.

And that forced another reckoning: this decision can’t be about me.

Leadership in the grey often requires stepping out of our own heads—releasing the need to be understood, validated, or appreciated. It asks us to own our decisions fully, even in the face of hurt and pain, and remain steady when the people we’re protecting are angry with us.

This wasn’t the perfect decision. A “just right” wasn’t available. It was the least-worst option—the one that offered the most structure, safety, and possibility for benefit, even if it came at personal cost.

That’s what leading through the grey actually looks like. Not certainty. Not comfort. But responsibility—and the courage to stand in it.

CargoSphere Doesn’t Replace Contract Understanding — It Exposes the Gaps

CargoSphere is often positioned as a contract management tool or a centralized rate repository.

And in many organizations, that’s exactly how it’s used.

Contracts are loaded. Rates become searchable. Pricing feels more organized. On the surface, things improve.

Where I see challenges emerge is what happens after the contracts are in the system.

Digitizing a contract does not mean you understand it.

CargoSphere can make rates visible, but it cannot interpret the nuances of a contract for you. If the underlying agreement isn’t well understood, those gaps show up quickly — especially once teams move beyond basic rate lookup and into mapping and autorating.

This is where implementations tend to struggle.

If teams don’t fully understand how charges are structured in the contract — how accessorials apply, how conditions interact, or how tiering and minimums actually work — mapping becomes guesswork. And once those mappings are in place, they don’t just sit quietly in the background.

They flow.

They flow into autorating logic.
They influence rate search results.
They shape margin expectations and downstream financial outcomes.

When a charge is misunderstood or poorly mapped, the system doesn’t catch it. It enforces it — consistently and at scale.

At that point, the symptoms start to appear. Pricing results feel off. Autorating is no longer trusted. Sales begins to question the tool. Operations works around it. Finance struggles to reconcile outcomes that don’t align with expectations.

CargoSphere often takes the blame. But in reality, the platform is doing exactly what it was configured to do.

This is why successful CargoSphere usage requires more than loading contracts into a system.

It requires deep contract comprehension and intentional translation of contract language into system logic. Contract management isn’t just about storage — it’s about interpretation. And interpretation is a governance responsibility.

When organizations treat CargoSphere as a repository, they underutilize it. When they treat it as a decision engine without truly understanding the contracts feeding it, they create risk.

Automation doesn’t fix ambiguity.
It accelerates it.

Before relying heavily on autorating or expanding rate usage, it’s worth pausing to ask:

👉 Do we truly understand what’s in our contracts — and how those terms are being translated into system behavior?

Because once rates are live, they stop being documents.

They become decisions.

If Your Data Is Debated in Meetings, You Have a Governance Problem

When leaders say they have a “data problem,” what they usually mean is this:

The numbers don’t agree.
The reports don’t match.
And no one trusts which version is right.

That is not a reporting issue.
It’s a data governance failure.

Here’s the pattern I see repeatedly.

Operations, Sales, and Finance are all looking at the same activity — but through different definitions. Each function answers a different question, so each one builds its own logic. Over time, those logics drift.

Take a simple but critical example: shipments.

Operations often defines a shipment based on physical movement and execution.
Sales often defines it based on customer commitment.
Finance defines it based on revenue recognition and accountability.

All of those perspectives are valid.

The mistake is pretending they’re interchangeable.

They’re not.

Operational reporting exists to measure efficiency.
Sales reporting exists to measure pipeline health and conversion.
Financial reporting must withstand audit, regulatory, and statutory scrutiny.

Different purposes require different lenses — but governance requires one agreed foundation.

And this is where things often get exponentially more complicated.

Many organizations now have “data people” embedded in each discipline — someone in Sales, Operations, and Finance who is very good at pulling reports and interpreting data through their functional lens.

These people are smart.
They are capable.
And they are doing exactly what their function needs.

But data governance requires stepping back from myopic, singular views — even highly competent ones.

Because governance is not about who can pull the best report.
It’s about who has the authority to decide which definition anchors the organization.

That’s why governance always starts in the same place: ownership.

Who owns the data?
Who is responsible for reporting?
Who resolves conflicts when definitions differ?

Until those questions are answered, alignment is impossible.

In many organizations, data ownership ultimately resides in Finance — usually because financial definitions must hold up to audit, regulatory, and statutory requirements. That doesn’t make Finance “better” at data. It makes Finance accountable for external truth.

Some organizations take this a step further and build a dedicated data or analytics team. When done well, this is a strong move.

A separate data team creates natural separation from individual disciplines. It allows data to operate within a formal governance structure instead of being pulled in competing directions by functional priorities.

Once ownership is clear, then the work moves into defining the core metrics that matter most — the definitions that drive money, volume, and accountability. Not every metric. Not every edge case. Just the ones that anchor decision-making.

Without this foundation:

  • processes fragment
  • data lineage breaks
  • dashboards contradict each other
  • and Finance gets blamed for outcomes it didn’t create

Here’s the part many leaders underestimate:

Solutions don’t require massive transformation programs or endless rework.
They do require structure — and the backbone to enforce it.

Effective data governance is surprisingly straightforward:

  • establish clear data and reporting ownership
  • agree on a small set of core definitions
  • embed them into systems and processes
  • centralize reporting around one dataset
  • allow multiple analytical views without redefining reality

And finally — leadership has to stand behind the decisions.

That means saying no to requests that break definitions, resisting one-off exceptions, and accepting short-term discomfort to protect long-term clarity.

Governance fails not because it’s complex, but because enforcement feels uncomfortable.

But definitions shape processes.
Processes shape data.
And data shapes decisions.

If your organization is still debating numbers in meetings, the next dashboard won’t fix it.

The real question is this:

👉 Do we know who owns the data — and do we have the backbone to enforce governance once we step beyond functional silos?

Because without that, clarity will always be temporary.

Customer Exceptions Are Not Customer Service — They’re a Control Failure

Last week I wrote about how most systems don’t fail — leadership stops protecting them.

Customer exceptions are one of the clearest ways that erosion shows up.

In supply chain, customer service has long been positioned as a key differentiator — alongside technology. The belief runs deep: anyone can move your freight, but we do it with a smile. We answer emails no matter when they come in. We keep customers constantly updated. We pride ourselves on being “all about customer service.”

That mindset worked — for a time.

But just as technology has evolved, our definition of customer service has to evolve too.

If you have more than a handful of “customer exceptions,” your system isn’t flexible.
It’s already broken.

A customer exception is not a relationship strategy or a service differentiator. Technically, it is a process that bypasses standard controls. And every bypass has consequences.

What usually happens looks reasonable at first. A customer request escalates to Sales leadership. Sales leadership agrees — often in a leadership-to-leadership conversation — to “take care of the customer.”

The problem isn’t intent.
The problem is distance.

At that level, leaders rarely have detailed visibility into desk-level processes. They don’t see how a one-off request actually executes. So the exception feels small — even harmless.

This is exactly where organizations miss an opportunity.

Instead of approving the exception in isolation, this is the moment to pull in a middle manager — and empower them.

Middle managers sit in a uniquely valuable position. They understand the operational detail at the desk level and the broader strategic intent of the organization. They can evaluate whether a request is:

  • operationally viable
  • system sustainable
  • and capable of being delivered without breaking controls

More importantly, they can propose alternative solutions that meet the customer’s underlying need — not just the surface request.

That requires something many organizations struggle with:
allowing a middle manager to say no to someone more senior.

Not as resistance — but as strategy.

True customer service isn’t about giving customers whatever they ask for. That definition is far too limiting. It traps organizations into reactive behavior.

Real customer service is about delivering what customers actually need — often before they can articulate it themselves. Stability. Predictability. Transparency. Solutions that scale.

You don’t deliver that by stacking exceptions.

You deliver it by building exceptional systems, leveraging technology intentionally, and treating customer service as a qualified, informed function — not an endless accommodation engine.

Systems are very good at this. They enforce rules, create predictability, protect margin, and produce data that can be trusted. What systems can’t do is have uncomfortable conversations.

That’s still a leadership responsibility.

Customer exceptions persist because saying no feels disruptive. Holding the line ruffles feathers. And approving the workaround feels faster than redesigning the solution.

So exceptions get approved.

The downstream impact is predictable. Operations works around the system. Finance loses confidence in the data. Reporting becomes defensive. And eventually, the system gets blamed for behavior it was never designed to allow.

This is not a technology failure.
It’s a control design and enforcement failure.

Strong organizations treat exceptions as intentional decisions — clearly defined, formally approved, tightly governed, and deliberately rare. They protect their systems by empowering the people closest to the work to be strategic, not just compliant.

Before approving the next workaround, it’s worth pausing to ask:

👉 Is this request truly customer service — or is this the moment to involve the people who can design a solution that works for the customer and the system?

Because once exceptions become normal, clarity disappears.

Closing Out My Second Year as a Solopreneur — and Learning to Slow Down

I’m closing out my full second year as a solopreneur.

I’m also a single parent.
Divorced.
Raising a child who needs just a bit extra from the world — and from me.

I’ve always been a hard-working, type-A, go-go-go kind of person. That identity served me well for a long time.

But this year didn’t gently suggest that I slow down.

It slapped me in the face and made slowing down non-negotiable.

My son — who is a truly wonderful human being learning his way in this world — has had his struggles. And with every one of those struggles, there has been a mom there.

A mom to make sure he didn’t fall.
A mom to make sure he didn’t carry things that were never meant to be carried alone.
A mom committed to finding a way forward that allows him to heal and become the glorious person he is meant to be.

All while trying to grow a business.

And if we’re honest, there’s a keep-the-lights-on reality to running a business on your own.

You put your name out there.
You hope projects line up neatly.
You try to avoid gaps.

Spoiler alert: they rarely do.

You either have a lot of people interested in you — or none at all. That swing is real. And it’s part of finding your way.

What this year also forced me to confront is something deeper.

We all carry a picture of what our life should look like.
I know I did.

I had a picture of what my life would be like.
What I wanted my son’s life to be like.

And as much as we want something — and work toward it — we don’t always get what we want.

That truth is scary.

Because we follow the steps.
We do the “right” things.
We work toward those images with everything we have.

And sometimes those steps lead us somewhere else entirely.

That other place can challenge you in ways you never imagined:
Almost losing someone you love.
Feeling like your professional life is dying on the vine.
Wondering if everything you built is slipping away.

But here’s what this year taught me:

That place — as painful as it feels — is often a season, not the destination.

You still have to show up.
Even scared.
Especially scared.

Because there is always the possibility that things turn out — not just okay — but better than you expected.

Life is unexpected like that.

The destination we had in mind may not have been the best option for us after all.
So sometimes the universe redirects us — not to punish us, but to grow us.

This year taught me to slow down.
It taught me not to miss moments with my son.
It taught me to be fully present where I am actually needed — not just where I feel productive.

It also taught me something quieter, but just as important.

When things slowed, I had a choice:

  • Fill the space with endless Netflix and laundry
  • Or use it to refine my skills, sharpen my thinking, and become better at what I do

I chose the second — imperfectly, but intentionally.

And maybe the most unexpected lesson of all?

This year taught me to find ways to define myself outside of my work.

Not because the work doesn’t matter — it does.
But because I matter too.
And so does the life I’m building alongside it.

As this year comes to a close, I don’t feel behind.

I feel clearer.
More grounded.
More honest about what this season of life requires of me.

And oddly enough — that feels like real progress.

As we move toward a new year, I hope you’ll give yourself the space to pause.
Not to judge the year — but to listen to it.

Because every year teaches us something, whether we were ready for the lesson or not.

👉 What did this year teach you about who you are becoming — and how will that shape the way you move forward?

Sometimes growth doesn’t look like acceleration.
Sometimes it looks like understanding.

Finance Doesn’t Create Clarity — It Reveals Whether It Already Exists

When leaders say,

“We need better data,”

what they often mean is,

“The numbers aren’t giving us the answers we want.”

So Finance gets asked to fix it:

  • New reports
  • New dashboards
  • More reconciliations
  • More explanations

But here’s the uncomfortable truth:

Finance doesn’t create clarity.
It exposes whether clarity already exists.

Let me give a very real example.

Do you know how many conversations I’ve had just trying to define a “shipment”?

When does a shipment actually become a shipment?

That is a real question — and the answer often depends on who you ask:

  • Finance may define it based on revenue recognition
  • Operations may define it based on physical movement
  • Sales may define it based on customer commitment

All three perspectives are valid.
And all three answers are often different.

That difference does not invalidate how Operations or Sales need to see the data.

Operations needs shipment data to understand:

  • Throughput
  • Bottlenecks
  • Operational efficiency

Sales needs shipment data to understand:

  • Pipeline conversion
  • Customer success
  • Commercial performance

These views are valuable — and necessary.

But we need to name them for what they are.

They are operational reporting and sales reporting.
They are not financial reporting.

Financial reporting has to meet a different standard — one that holds up to:

  • External auditors
  • Regulatory and statutory filings
  • Tax reporting
  • Third-party scrutiny

That doesn’t make it “better.”
It makes it purpose-built.

The real problem arises when these differences go unnamed.

Because when definitions are unclear:

  • Processes fracture
  • Data drifts
  • Reports contradict each other

And Finance — often the function that owns reporting due to proficiency — ends up being blamed for inconsistencies it didn’t create.

To be clear, I am not arguing for separate, siloed reporting produced independently by Finance, Operations, and Sales.

I argue the opposite.

Reporting must be centralized.

We must:

  • Agree on core definitions
  • Acknowledge that nuance exists
  • Look at the same data in different ways to answer different questions

One dataset.
Clear definitions.
Multiple lenses.

Once those foundational decisions are made, leadership has to:

  • Accept the conclusions
  • Support them consistently
  • And back them all the way down to the desk

Because definitions shape processes.
Processes shape data.
And Finance is often the one asked to report the result.

So before asking for another dashboard or reconciliation, it’s worth asking:

👉 Which definition are we still debating — and what is that indecision costing us in trust and efficiency?

Because until definitions are aligned, clarity will always feel just out of reach.

Most Systems Don’t Fail — Leadership Just Stops Protecting Them

Every time a system “fails,” the conversation usually goes something like this:

“It’s too rigid.”
“It doesn’t really fit how we work.”
“We’ll just do this one thing outside the system.”

And slowly — almost invisibly — the system becomes the problem.

It often starts with good intentions.

We have Customer X and Customer Y who “don’t fit the process.”
So a special manual workaround gets created — just for them.

Then another.
And another.

All under the banner of customer service.

But here’s the truth most teams avoid saying out loud:

Systems don’t usually fail because of technology.
They fail because leadership stops enforcing decisions that feel uncomfortable.

Why does that happen?

Because saying no ruffles feathers.
Because holding the line disrupts the proverbial apple cart.
Because it’s easier in the moment to accommodate than to challenge.

And the more senior a leader becomes, the more complicated this gets.

As you move up, you become increasingly divorced from the daily operational details.
So when a tough decision lands on your desk, doubt creeps in:

What if I’m wrong?
What if I don’t fully understand the nuance?
What if this exposes a gap in my own knowledge — and now my performance is questioned?

So instead of holding the line, leaders step back.
Exceptions get approved.
Standards soften.
And systems quietly absorb the damage.

This is where organizations either stabilize — or slowly unravel.

Because leadership is not about always having the right answer.
It’s about building a structure where the right people are empowered to protect the system.

That’s where middle managers come in.

Middle managers sit in a uniquely powerful position:

  • Close enough to the work to understand operational reality
  • Senior enough to understand organizational strategy
  • Trusted enough to translate intent into execution

They are the ones who can hold the line — if they are allowed to.

Yet too often, we treat middle managers like traffic controllers instead of decision owners.
We expect them to keep things moving but don’t give them the authority to say no.

And without that authority, systems bend.

Meanwhile, we convince ourselves we’re “giving the customer what they want.”

But here’s the harder truth:

Customer service isn’t about giving customers what they want.
It’s about understanding what they actually need — and delivering that well.

Systems are very good at supporting real needs:

  • Consistency
  • Reliability
  • Scalability
  • Trust

What systems can’t do is have the uncomfortable conversation.

They can’t ask:

  • Why is this request necessary?
  • What problem is the customer really trying to solve?
  • Is this request compensating for a failure somewhere else?

Sometimes it feels like saying yes is the only way to meet the customer’s needs.

But what if those needs are shaped by their own broken systems?

What if there’s an opportunity to deliver value that fixes both sides — instead of layering another workaround on top?

You’ll never know if you always acquiesce and do exactly as you’re told.

What you will do — without question — is contribute to a system that slowly breaks under the weight of exceptions, manual effort, and silence.

Strong systems require protection:

  • Clear standards that don’t change customer by customer
  • Leaders willing to back their middle managers
  • The courage to tolerate short-term discomfort for long-term clarity

Efficiency isn’t about more tools.
It’s about leadership alignment — and the willingness to hold the line.

As you reset for the week, here’s a question worth sitting with:

👉 Which decision are we avoiding because it feels uncomfortable — and what is that avoidance costing our system every day?

That answer usually points directly to your biggest opportunity.

Leadership, Control, and Ego

When High Standards Quietly Turn Into Control

I’m writing this from personal experience.

I was the high achiever with internal standards so high that I believed only I could get it right.
Only I could lead the team the “right” way.
Only I could protect outcomes.

At the time, I thought this was excellence.
Drive.
Responsibility.

But experience — both professional and life — taught me something uncomfortable.

That wasn’t me becoming the best version of myself.
It was control.
And it was ego.

As an individual contributor, you’re measured by your output.
Your accuracy.
Your speed.
Your results.

But the moment you transition into leadership, the scorecard changes.

Leadership is no longer about your individual contribution — it’s about how your team performs.

That shift is where many high performers struggle.

Because holding on to ego feels safer than letting go of control.

Control often hides behind good intentions:

  • “I just care about the outcome”
  • “I have high standards”
  • “It’s faster if I do it myself”

But over time, control creates a fragile system — one that depends on a single person and quietly limits everyone else.

So what’s the alternative?

You can let go of some ego and allow others to shine brighter than you.
You can release control so people can step into their own excellence.
You can build a unit — not a hierarchy of dependence.

Or…

You can become tired.
Burned out.
An exceptional individual contributor trapped in a leadership role.

And just know — that choice often limits your own growth.

Leadership isn’t a solo sport where you are both captain and player.

It’s a cohesive unit made up of unique talents that, when aligned, create something greater than any one person could achieve alone.

Your talent as a leader is not doing everything well.

It’s getting everyone to work toward the same goal — with clarity, trust, and standards strong enough to stand without you hovering over them.

High standards still matter.
They just don’t have to live inside you.

Because real leadership isn’t about proving you can do it all.
It’s about creating something that thrives beyond you.