Selected Work

What I was hired to fix, and what changed

Client work is confidential, and I treat that as a working condition. No names, no logos, no deliverables to download, nothing a competitor could trace back to a curriculum or a configuration. Your project would get the same treatment. What I can give you is the part that actually transfers: the situation, the decision, and the outcome.

LMS Implementation

Legacy LMS to SAP SuccessFactors migration, global medical device manufacturer

Situation
A decade of training history sat in a legacy enterprise LMS serving 1,000–5,000 employees across 5–10 countries under FDA and ISO oversight. The records could not simply be abandoned.
What I did
Directed the full migration to SuccessFactors Learning, then two sequential implementations across distinct U.S. and global business groups: data migration, parallel operation, curriculum equivalency mapping and reporting continuity.
Result
Both business groups live with training-record integrity intact. Represented Training in subsequent FDA and ISO audits with zero findings related to training records or LMS data.

Legacy platform migration · SAP SuccessFactors Learning · Employee Central · FDA / ISO

LMS Implementation

Multi-region SuccessFactors Learning rollout, U.S. and Latin America

Situation
A client needed SuccessFactors Learning stood up across U.S. and Latin American operations, with requirements that did not match between regions and no budget for onsite consulting.
What I did
Led the implementation end to end and remotely, reconciling multi-region requirements, localizing configuration, running stakeholder alignment on a fixed communication cadence, and carrying it through SIT, UAT and go-live.
Result
Delivered on schedule with no onsite presence. Followed with post-go-live optimization recommendations covering learner adoption and administrative efficiency.

SAP SuccessFactors Learning · Multi-region configuration · Remote delivery

Localization

Ten-language localization program for global technical training

Situation
Technical and compliance training had to reach employees across 5–10 countries and every major language in those markets, without producing ten disconnected versions that drifted apart on every update.
What I did
Brought Articulate 360 in company-wide and wrote the governance policies and course standards that defined eLearning quality across all programs. Then built the localization architecture on top of that standard, covering 10 languages in the organization's major markets.
Result
One source course, ten maintainable locales, consistent quality across every region. All content meeting WCAG 2.1 AA.

Articulate 360 · DeepL · WCAG 2.1 AA · EN 301 549

Governance & Audit

Audit-ready LMS governance framework

Situation
A regulated environment where an FDA or ISO auditor could ask for any employee's complete training history and expect it to reconcile. That meant 50+ programs and a team of 6–10 designers producing content continuously.
What I did
Established configuration standards, documentation practice and governance policy covering how courses are built, versioned, assigned and retired: the operational discipline that makes records defensible.
Result
Zero compliance findings related to training records or LMS data integrity across FDA and ISO audits. Reduced audit findings and increased LMS adoption across global business groups.

Governance frameworks · FDA / ISO · Configuration standards

How I handle confidentiality

Discretion is part of what you are buying

A consultant who shows you another client's course library will show yours to somebody else. In regulated environments especially, the discipline that keeps other people's work off this page is the discipline that will protect yours.

Your intellectual property stays yours

Course content, configuration decisions, curriculum design and brand assets belong to you and leave with you. What I publish about an engagement is the shape of the problem and how it was solved: never the artifacts, and never anything a competitor could reuse. Nothing identifying goes out without your written permission.

Your data never goes to the cloud

Migration and reconciliation work sometimes means client records have to pass through my hands. When it does, they sit on secure, protected local drives: never a consumer cloud service, never a personal sync folder, never somebody else's data center.

Nothing is retained by default

Source files, configuration documentation and governance artifacts are handed over at close of engagement. Where you ask me to keep them so a future update stays possible, they are held under the same protections as live work, and only because you asked.

Recognize your own situation in any of these?

Client work stays confidential, but the thinking behind it does not. Describe what you are facing and I will tell you how I would approach it.

Start a Conversation