Skip to content

Services

Engagements with a defined shape.

Most leaders are strong in strategy, technology, or change, rarely all three. I work the full arc: set the direction, build the solution, then run the change work that turns a launch into daily use.

  • Twenty-plus years across financial services, government, education, healthcare, utilities, manufacturing and nonprofit.
  • M.S. Instructional Technology; former lecturer in IT and Instructional Systems, Mississippi State University.
  • Design practice grounded in ADDIE; change practice grounded in ADKAR (Prosci's model).

Start here

Adoption Diagnostic

For
organizations with a rollout, pilot or platform that is not delivering, who want a clear answer before committing to a larger engagement.
The outcome
An evidenced answer to where adoption is stalling, and what to do first.
You get
interviews with sponsors, managers and users, a readiness and usage review mapped to ADKAR, and a prioritized action plan you can run with or without me.
Typical timeframe
2 weeks

AI transformation and strategy

Decide where AI belongs, pilot it so it can scale, set the rules for using it, and measure whether people use it.

Work like: Corporate AI Transformation Lead, Principal AI Transformation Lead, AI Strategy and Transformation.

How I think about it: Why AI pilots die at rollout, and what ADKAR fixes Sponsorship is not a kickoff email The training that nobody opens

AI Readiness and Use Policy

For
leaders being asked where AI belongs in their organization, who need an answer that holds: where to start, what to allow, and how to tell whether it is working.
The outcome
A decision on where AI belongs, a pilot that can scale, and adoption measured from week one.
You get
an assessment of where AI fits your work, a pilot designed to scale, rules for use that people can follow, and the measures that show whether people use it.
Typical timeframe
4 to 6 weeks

Proof A written AI use policy for a nonprofit, and the pilot that followed it, which succeeded.

AI Enablement Sprint

For
teams whose AI pilot hasn’t left the pilot.
The outcome
AI that people use on an ordinary Tuesday, not just in the demo, with evidence of daily use your sponsor can see.
You get
role-based training paths, a scoped enablement plan, and the adoption instrumentation to prove daily use.
Typical timeframe
4 to 6 weeks

Proof Weekly AI use on a 35-person team grew from 11% to 60% in six months. Regular users reported an average of two hours a week saved.

Change, training and adoption

The training, workshops, champion networks and ADKAR change work that get people using a new tool, with adoption measured.

Work like: Change Management Consultant, AI Enablement Training and Adoption Designer, Corporate AI Facilitator.

Change Adoption Program

For
leaders whose rollout landed but didn’t stick.
The outcome
Adoption that survives quarter two, when most rollouts quietly fade.
You get
an ADKAR-based adoption plan, manager enablement, and reinforcement that survives quarter two.
Typical timeframe
3 to 6 months

Proof 94% adoption on the Cornerstone rollout.

Learning Program Build

For
teams that need training people will actually use, designed and built end to end.
The outcome
Courses and programs designed for the moment of need, measured by what changes in the work.
You get
learner analysis, objectives at a performance level, the build itself, and evaluation built in from the start.
Typical timeframe
6 to 12 weeks per program

Proof 42 courses developed, producing 156 assets, for the Cornerstone rollout.

Technology advisory and solutions

Platform choice, integrations, reporting and tools built with AI, explained plainly so leaders can decide.

Work like: Enterprise Data and IT Strategy Consultant, Business Technology Advisor, Senior Solutions Consultant, Lead Presales Technology Consultant, Senior Adaptive Consultant, Colleague Modernization Engineer.

LMS Selection and Launch

For
organizations choosing, or rescuing, a learning platform.
The outcome
The right platform, launched into daily use, not just go-live.
You get
a structured vendor evaluation, implementation oversight, and a rollout designed for daily use, not just go-live.
Typical timeframe
3 to 6 months

Proof Cornerstone LMS, evaluation to adoption: 100% completion, 94% adoption, 8 days to productivity, 0 findings at federal audit.

Platform Selection and Integration

For
organizations choosing a platform, or connecting the ones they have: a learning platform to a CRM, one sign-on across both, reports that span them.
The outcome
One platform decision you can defend, connected to the systems people already work in.
You get
a structured vendor evaluation against your requirements, then the integration scoped, directed and configured: user provisioning, records sync, single sign-on and cross-platform reporting, tested, validated and put into production.
Typical timeframe
6 to 12 weeks

Proof Cornerstone to Salesforce: user provisioning sync, training records pushed to Salesforce, single sign-on across both and cross-platform reporting, tested, validated and put into production. The platform itself was chosen with a published ten-platform scorecard.

Business Tools Built with AI

For
teams with a process that lives in spreadsheets, inboxes and memory, who need a working tool rather than a platform project.
The outcome
A tool in weekly use, owned by your team, producing the numbers it was built to produce.
You get
a scoped build on Power Platform or the Anthropic and OpenAI APIs: the tool, its data, the reports or agents around it, and training for the people who will run it.
Typical timeframe
4 to 8 weeks

Proof 50+ apps and tools built with AI, including Power Platform solutions and AI agents, and live apps on the Anthropic and OpenAI APIs.

Every engagement is priced to its scope. The scoping call sets the scope, timeline and fee. Schools, colleges and universities: 20% off every engagement.

What clients say

The vendor evaluation framework Clea developed saved us months of research and countless hours of stakeholder alignment. Her compliance-first approach ensured we selected a platform that would scale with our growth trajectory while keeping us audit-ready from day one.

VP of Operations, executive sponsor, regulated consumer-finance firm

How an engagement begins

  1. You describe the problemYou don't need a finished brief. Tell me roughly what's going on.
  2. A personal replyI reply personally within one to two working days. If what you describe is not something I am right for, I will say so and name someone who is.
  3. A scoping callThe call sets the final scope, timeline and fee.

How an engagement runs

Every engagement moves through these five stages, in this order.

  1. AnalysisWho is learning, what is in their way, and what evidence says so. Before any solution is proposed.
  2. ProblemStated as an observable gap in performance, not a topic to cover. If training is not the answer, this is where it is said.
  3. DesignObjectives at a level that can be observed, the method chosen, and the decisions that followed from them. Built, not handed off.
  4. OutcomeWhat was delivered and what changed, with attribution stated honestly: what the work caused, and what it merely coincided with.
  5. EvaluationThe Kirkpatrick levels, each marked as measured, validated at acceptance, built in, or planned. A number without one of those labels is left out.

See the case studies →

Start with a scoping call.

A platform nobody uses. A change that won't stick. Tell me what isn't landing, and I'll tell you first whether training is the answer.