Originally published 1 April 2025
What Happens When Capability Is Matched With the Right Structure and Advocacy
Allan had been unemployed for several years.
Not because he didn’t want to work.
Not because he lacked ability.
But because every attempt to re-enter the workforce collapsed under pressure.
Allan has dyslexia and ADHD. Traditional recruitment processes, vague expectations, and unspoken workplace rules made it almost impossible for him to show what he could actually do.
On paper, he looked like a risk.
In reality, he was an untapped asset.
The Problem Wasn’t Skill. It Was Friction.
Allan is practical, hands-on, and reliable when tasks are clear.
But he struggled with:
- written instructions
- fast-paced onboarding without structure
- remembering multi-step processes when they were explained verbally once
- environments where mistakes were treated as personal failure instead of system failure
After years out of work, confidence wasn’t the issue.
Cognitive load was.
What Mentoring Changed
Ability Pathways didn’t try to “fix” Allan.
His mentor focused on removing friction.
That meant:
- identifying work that suited Allan’s strengths
- preparing him for the real expectations of a workplace
- breaking tasks into repeatable, visual systems
- rehearsing communication so he could advocate for his needs clearly
- translating “support needs” into language an employer could actually use
This wasn’t therapy.
It was practical, employment-focused mentoring.
The goal wasn’t to protect Allan from work — it was to help him succeed inside it.
The Role: Maintenance That Makes Sense
Allan was introduced to an air conditioning company servicing commercial properties.
The role involved:
- cleaning and maintaining air-conditioning units
- replacing and cleaning filters
- working on-site at commercial buildings
- following clear, repeatable maintenance routines
The work was physical, structured, and outcome-focused — a strong match for Allan.
But the real difference came from how the role was set up.
Putting Needs on the Table — Properly
Instead of vague disclosures or apologies, Allan’s mentor helped clearly articulate what Allan needed to do his job well.
That included:
- visual task checklists instead of dense written instructions
- consistent routines across sites
- clear start-and-finish definitions for tasks
- direct communication rather than implied expectations
- patience during early learning — without lowering standards
These weren’t “special favours”.
They were smart adjustments.
What the Company Did Differently
The company listened — and then acted.
They:
- adjusted onboarding to be more hands-on
- provided visual references for tasks
- checked understanding without condescension
- focused on outcomes, not paperwork
- gave Allan space to settle into routine
The result wasn’t reduced productivity.
It was increased reliability.
The Outcome: A Valued Employee
Allan didn’t just “get a job”.
He became a dependable part of the team.
His work is consistent.
His attention to detail is strong.
And once routines were embedded, performance followed.
As the company’s CEO, Brad Henshaw, put it:
“Allan has become a great employee. Once we understood how to support him properly, his reliability and work ethic really stood out. He takes pride in his work, and we’re very glad to have him on the team.”
That’s what happens when ability is given the right conditions.
This Is What Good Disability Employment Actually Looks Like
This story isn’t about lowering expectations.
It’s about designing work properly.
Allan didn’t need:
- endless pre-employment training
- confidence workshops
- or another assessment
He needed:
- the right role
- clear systems
- honest communication
- and support that translated needs into action
That's mentoring.
The Bottom Line
People with dyslexia and ADHD don’t fail at work because they can’t work.
They fail when:
- expectations are implicit
- systems rely too heavily on text
- mistakes are punished instead of designed out
- support stops at insight instead of execution
When those things change, outcomes change.
Allan’s story proves that.