I Didn’t Succeed Despite My Circumstances. I Succeeded.
This article was originally published on LinkedIn on January 21, 2026.
This isn’t a story about overcoming odds. It’s about how we explain success—and why those explanations matter.
In higher education, we often tell success stories that follow a similar pattern.
A person faces significant constraints. They persist anyway. Their success is framed as exceptional—proof of grit, resilience, or determination.
The intention is usually affirming. The effect is often distorting.
Because despite still centers on deficit. It reinforces the idea that certain starting points are disqualifying—and that success, when it occurs, is an exception rather than a legitimate outcome.
I want to offer a different framing.
I didn’t succeed despite my circumstances. I succeeded. Period.
That statement isn’t a denial of context. It’s a correction of interpretation.
A High-Friction Pathway Is Still a Valid Pathway
My educational and professional trajectory unfolded through what I now understand as a high-friction pathway.
Not dramatic. Not heroic. Structurally demanding.
It involved multiple institutions, multiple states, sustained work alongside study, chronic health and disability considerations, financial constraint, transfer transitions, and significant personal loss. At no point was there excess margin—financial, temporal, physical, or emotional.
That matters because high-friction systems do something very specific: they reduce forgiveness for error.
In those environments, progress depends less on intensity and more on judgment—the ability to read systems accurately, anticipate consequences, and make decisions that preserve momentum under constraint.
That kind of learning doesn’t come from grit alone. It comes from operating in systems that do not absorb variation easily.
What Actually Made the Pathway Viable
There’s an important part of this story that resists deficit framing without turning into a personal legend.
I was able to sustain my undergraduate education because a department recognized my strengths and designed a role aligned with them. That role created stability, meaningful contribution, and a gateway to graduate education.
Later, I secured a graduate assistantship in a different area—again, not as charity, but as legitimate work that converted capacity into continuity. When I moved into doctoral study, I intentionally sought a program structured to cover costs, understanding that design matters as much as aspiration.
This wasn’t a rescue.
It was opportunity recognition paired with supportive environments.
Three things mattered—together:
I had real, usable capacities.
Someone recognized and valued those capacities.
The environment was flexible enough to act on that recognition.
Miss any one of those, and the pathway collapses.
That distinction matters.
Support that is sentimental fades. Support that is structural endures.
Why This Shaped My Scholarship
This mental map is clearly evident in my dissertation and subsequent research.
I didn’t study student deficits. I studied campus climates, conditions, and assets—the environmental signals that shape mental health, belonging, agency, and learning.
The questions that mattered to me were practical:
What do institutions actually signal as valuable?
How do environments shape whether responsibility feels manageable or overwhelming?
When does support translate into functioning—and when does it unintentionally stall it?
That focus wasn’t accidental. It reflected a lived insight: Capacity is widely distributed. Opportunity recognition is not.
Institutions don’t just support individuals. They decide—often implicitly—which forms of capacity count.
Why It Shows Up in the Awards I Value Most
The awards I’m most proud of aren’t about visibility or ambition.
They’re about contribution to the field, student advocacy, and stewardship.
Each reflects the same underlying commitment: making systems more legible, more coherent, and better able to convert human capacity into sustained success.
Stewardship, in particular, isn’t performative work. It’s alignment work—holding responsibility for people, resources, and decisions over time, especially when the margin is thin.
Those recognitions didn’t affirm endurance. They affirmed judgment.
Why My Leadership Is Sometimes Misread
I’m aware of how my leadership can be perceived.
I’m often described as a workaholic. That isn’t untrue.
I can come across as matter-of-fact. I hold high expectations. At times, I’m perceived as lacking empathy—especially when someone cannot succeed in a particular role, structure, or moment.
I don’t dismiss those perceptions. But I want to clarify what sits underneath them.
My mental map is shaped less by intensity than by responsibility under constraint.
When you’ve spent long stretches operating without margin, you learn quickly that energy, time, and attention are finite. You also learn that saying yes indiscriminately isn’t kindness—it’s avoidance. It defers tradeoffs until they land on someone else—or until they burn you out.
That’s why I rely on a simple principle: Say yes when you can, and no when you have to.
Both are acts of responsibility.
Why I Focus on What People Will Do—Not What Labels Predict
When I’m thinking about solutions—whether in student support, staff supervision, or organizational design—I’m far less interested in what research tells me to expect of someone based on a label.
That doesn’t mean I disregard research. I see it as a starting point—a set of considerations that helps me notice patterns, risks, and possibilities. Research gives me things to attend to, questions to ask, and conditions to watch for.
But it does not give me a prescriptive answer.
Because labels don’t act—people do.
What matters more is:
What is this person actually able and willing to do in this context?
Why does this approach not work here?
Which constraints are structural, and which are situational?
Where does effort translate into progress—and where does it dissipate?
This can read as insufficiently empathetic.
But it’s grounded in a different understanding of care.
Support has to be workable to be supportive. When constraints aren’t named, someone else ends up carrying them.
I care deeply about support. I care just as deeply about whether support functions.
Risk, Limits, and Responsibility
I was recently reminded of something Thomas Berta once said: “You can’t lose if you can’t lose.”
I recognize the truth underneath it.
I know what I’m willing to risk. I know when I’m willing to risk it. And I try to be mindful about which risks I ask others to carry.
That awareness isn’t caution for its own sake. It’s responsibility shaped by experience.
Support That Works Isn’t Always Gentle
I support when and how I can—even when that support is misunderstood.
Sometimes support looks like flexibility. Sometimes it looks like a redesign. Sometimes it looks like naming a limit, honestly, rather than preserving false hope.
And sometimes support means acknowledging that a particular structure, role, or expectation isn’t workable right now—and that continuing to pretend otherwise will do more harm than clarity ever could.
That kind of honesty can feel abrupt in cultures accustomed to reassurance-first responses. But it’s rooted in the same commitment that runs through my scholarship and leadership:
Design environments that allow people to function, not just be affirmed.
Final Word
I lead this way because I understand how fragile success can be when systems are unclear, incoherent, or unwilling to name limits.
I care deeply about people. That’s precisely why I care so much about whether what we’re doing actually works.
That’s not hardness. That’s stewardship.
© 2026 Joshua J. Mitchell. All rights reserved.
