Mid-Week Reflection: The System Rewards Persistence, Not Need

Many systems are designed to respond to need.

At least, that’s the intention.

Eligibility rules are written.
Applications are submitted.
Decisions are made.

On paper, support is supposed to follow need.

But in practice, something else often determines who gets through.

Persistence.

What Persistence Looks Like

Persistence isn’t usually named as a requirement.

But it shows up everywhere.

Calling multiple times to reach the right person.
Following up when something goes unanswered.
Resubmitting documents that were already provided.
Appealing decisions.
Waiting on hold.
Showing up again.

And again.

And again.

What Systems Actually Respond To

Need is often static.

Someone qualifies or they don’t.
Their circumstances meet the criteria — or they don’t.

But persistence is dynamic.

It determines whether an application is completed.
Whether a missing document is corrected.
Whether a denial is challenged.
Whether a problem is resolved.

Over time, persistence becomes the mechanism that moves people forward.

Not necessarily need.

What Persistence Requires

Persistence takes:

Time.
Energy.
Stability.
Support.
Information.

It requires the ability to stay engaged with a system that may be confusing, slow, or unresponsive.

It requires capacity.

And not everyone has that capacity — especially in the moments when they need support most.

When Persistence Becomes the Gatekeeper

When systems rely on repeated follow-up, escalation, and self-advocacy to function, they quietly shift the burden onto the person seeking support.

The question stops being:

Do you qualify?

And becomes:

Can you keep going?

What I See in Practice

I see this all the time.

People who qualify for support — clearly, by the rules — but get stuck in the process.

A form needs to be corrected, but the instructions aren’t clear.
A document is missing, but no one explains what’s needed.
A call drops.
A message goes unanswered.
A deadline passes while someone is trying to get clarity.

Each step is small.

But together, they require persistence.

Some people can push through.

Others can’t — not because they don’t need support, but because they don’t have the capacity to keep navigating the system.

What This Reflection Is Naming

When persistence becomes the deciding factor, systems stop distributing support based on need.

They begin distributing it based on who can endure the process.

That is not a neutral shift.

Persistence is not a proxy for need.

But in many systems, it functions as one.

If you’ve ever felt like getting help required more energy than you had available, you’re not imagining it.

Much of my work involves helping people move through systems that depend on persistence — especially when persistence is hardest to sustain.

You can learn more about how I help here.