Learning Leader · L&D Systems Builder

L&D is Infrastructure,
Not a Service Desk.

I've spent 20 years figuring out how to move people — to grow, to see what they're capable of, to cross from "I can't do this" to "I can teach this." The systems I build are the infrastructure for that, at scale.

26
Global team built
12x
Content growth in one year
31%
AI efficiency gain
3
LMS migrations

What I'm working on

Building in public

Moodle for Business L&D: Fixing What Educational Institutions Don't Need To

Building Moodle plugins and xAPI/LRS infrastructure for business learning environments, closing the gaps I hit at my last role that open-source and enterprise LMS vendors both miss. Documenting every decision as I go.

Writing

Learning, Upgraded

Practical writing on L&D systems, AI implementation, and what honest practice actually looks like. No platitudes about learning culture. Systems, tools, and the things that break when you scale.

Something I got wrong

The Certification Launch That Failed on Day One

I skipped SME sign-off because I was moving too fast. Had to stop multiple teams, redirect resources, and rebuild trust. The real lesson wasn't about process. It was about what happens when speed becomes identity.

How I've applied this thinking

Three stories that define the work.

Systems Design · AI Integration

Scaling Content 12x Without Breaking Quality

Built the intake, governance, and QA systems that took the library from 50 modules to 637 in a single year, without adding headcount at the same rate.

12x content growth in one year
Read the full story →
Team Architecture · Cross-Cultural Leadership

Building a 26-Person Team Across 3 Countries

Designed the org structure, career frameworks, and governance model before posting the first role. Grew from 0 to 26 across US, Canada, and France.

26 global team (0 → 26)
Read the full story →
Change Management · AI Governance

Integrating AI When Your Team Is Afraid

Led a three-phase AI integration that cut development cycle time 31%, and kept every team member through the transition.

31% faster cycle time
Read the full story →

Why teams hire me

The systems are what make the human moments possible at scale. Here's how I build them.

I build the system before I scale the team.

The 26-person global team worked because I designed the architecture, career frameworks, and governance model before posting a single role. Most leaders hire first and build later. That's why they hit walls at 10 people.

I deploy AI without losing the team.

We cut development cycle time 31% through deliberate AI integration, not mandates, not demos. I sat in check-ins, opened Claude and Copilot side by side, and we experimented together until we found what worked. Adoption followed.

I measure what organizations resist measuring.

Completion rates and quiz scores are comfortable. They're also useless for proving L&D value to a CFO. I build measurement systems that connect learning to behavior change and business outcomes, and I own it when the numbers aren't flattering.

I operate at director scope without the title lag.

$500K+ annual budget, 26 people across 3 continents, 3 LMS migrations, 3 countries' employment law. Most "Senior Manager" roles don't operate at this scope. I'm ready for the title to catch up.

What I believe

I build L&D systems because I love what happens when they work — someone crosses from "I can't do this" to "I can teach this to someone else." The systems just let that happen more often, with more people, more consistently.
— Eian Newland

What others say

"Eian built something I've rarely seen — a learning function that actually changed how the business operated. Not just courses. A real system. The team he built, the processes he designed, the way he tied everything to outcomes — it was director-level work, full stop."
— Cross-functional partner, Tekion Corporation
"I came in with no training background and Eian built a curriculum around where I actually was, not where he assumed I'd be. Six months later I was training other people. That's the thing about working with him — he designs for the person in front of him, not the average learner."
— Former direct report, Tekion Corporation

How I think

The systems are how I move people at scale. I've spent 20 years watching people go from anxious to capable — seniors learning eBay from scratch, professors figuring out online teaching during COVID, engineers building confidence with a new system on Day 30. The tools and systems I build are the infrastructure for that. The tools change. That moment doesn't.
I build systems before I hire people. The 26-person global team worked because I designed the architecture, career frameworks, and governance model before posting a single role.
I learn alongside my team, not ahead of them. When AI tools became viable, I didn't build a polished demo. I sat in check-ins, opened Microsoft Copilot and Claude side by side, and we experimented together until we found what worked.
I sit in tension instead of pretending it resolves. Speed vs depth. Scale vs craft. I manage these trade-offs better than I did three years ago, but I haven't eliminated them. The certification failure taught me that.
I say the uncomfortable thing. Most organizations structurally resist what L&D offers. I challenge that with data, not opinions. And I own it when I'm wrong.

Looking for a learning leader?

I build systems, not just training.

If your organization treats L&D as infrastructure and wants someone who can design the function from scratch, scale it globally, and integrate AI without losing the team, let's talk. The systems are the job. But the reason I build them is the people on the other side — and I never lose sight of that.