What comes after Expert? Mastery.
I’ve been doing this work for 15+ years. Long enough to know what I’m good at, and more importantly, what I’m still learning. This field evolves constantly. The moment you think you’re done learning is the moment you become irrelevant.
But after decades of public speaking, operations and professional L&D work, I’ve earned real expertise. Yes, I’m naturally talented, and I’ve put in the time. Both matter.
How I Think. Show, Not Tell.
Three strands. One rope.
The combination is the credential.
Not a portfolio. Architecture. How I think – shown, not told. A résumé and personal statements built differently on purpose, using a framework I earned over a career.
Each document designed deliberately, not assembled.
Rooted in the same three strands:
Operations, Performance, and Technology.
Scroll to explore. Click any document to expand it. Open the full version from inside the preview.
Foundation
My career path: Retail → Corporate → Leadership → Organization Effectiveness.
Every pivot sharpened my ability to connect dots across functions and turn strategy into action.
I started at Chase Auto Finance. Customer service to the Leadership Development Program to five progressive roles in seven years. Chase taught me how large organizations work when done well. Everything I create now is built to meet or exceed that standard.
Then MedImpact Healthcare Systems for 16 years. I built a call center QA infrastructure from scratch. Learned LMS administration from the wrong side first—rescued a failing LMS, then reimplemented it properly with full content migration. Maintained 99%+ regulatory compliance for a decade in a heavily regulated pharmacy benefit management environment serving 1,700+ employees.
At Kruze Consulting, I put it all together. Built an LMS with 70-80% monthly engagement (replacing a platform with less than 10% return rate). Led AI transformation with 100% Phase 1 completion. Designed systems that scaled without me.
How I Work
My brother’s a mechanic. My mom was a professional cleaner.
Both taught me: use the right tool for the job, and know when to use which one.
My approach → → → →
- Begin with the end in mind – What are we trying to accomplish? Sometimes the answer isn’t training
- Make the complex simple – Bridge the gaps between L&D, tech, and operations to design ecosystems that actually get used
- Do it once, make it automatic – Build systems that scale, not one-off programs