0

New workshop for Analytics teams now live!

Header Logo
Newsletter Blog Contact
Workshops
Design Principles for Analytics
Log In
← Back to all posts

Training Isn’t Enablement

Jan 27, 2026
Connect

Most companies don’t have a skills problem.
They have a training illusion.

They train people. Then they expect capability.

The real problem

The symptom is easy to spot.

Business users start saying:

  • "That’s not what I asked for"

  • "It’s too late now"

  • "Not another workshop…"

That’s not feedback.
I think that’s trust collapsing.

The common response is:

Let’s train the data or business team.

But the real problem is not the lack of training.
The real problem is the absence of a role-based learning path that turns training into behavior.

Example for a French major retail group - Analytics and AI Enablement

Most training programs are:

  • too long
  • too generic
  • too disconnected from day-to-day work
  • and too spaced out to create momentum.

So teams learn (a bit).
But they don’t change.

Why this is expensive

1. You pay for the same training multiple times.

I’ve seen teams repeat the exact same course 3 times in 3 years because practice never followed.

2. You create certified beginners.

People leave the training motivated… then return to their backlog and forget 80% within weeks.

3. You burn your analytics ROI.

Tools, licenses, platforms, governance, none of it matters if the human layer doesn’t progress.

It’s an enablement failure.

A quick corporate example

A BI team is trained in dashboard design.
They love the session. Everyone feels aligned.

Then Monday comes.

No one applies the method, because:

  • the backlog is full

  • the dataset is messy

  • stakeholders keep pushing "quick wins"

  • and no one has authority to slow down and do it properly.

Nine months later, a new training is requested.
Not because the first one was bad.
Because it was isolated.

Training doesn’t create skills. Repetition + feedback does.

If you’re rethinking enablement in 2026, I can help you assess your data practices, enablement, and transformation.

In English and French, oui oui!

 Book a call here

 

Responses

Join the conversation
t("newsletters.loading")
Loading...
How many KPIs are too many?
*]:pointer-events-auto scroll-mt-(--header-height)" dir="auto" tabindex="-1"> *]:pointer-events-auto scroll-mt-[calc(var(--header-height)+min(200px,max(70px,20svh)))]" dir="auto" tabindex="-1"> It depends. (ahah!) KPIs are everywhere.Across dashboards.Across reports. We use them constantly.And yet, the questions remain. Are they truly KPIs? Are they actually key? Key for others… or just ...
The "slide" I’m presenting to a CDO next week
*]:pointer-events-auto scroll-mt-(--header-height)" dir="auto" tabindex="-1"> *]:pointer-events-auto scroll-mt-[calc(var(--header-height)+min(200px,max(70px,20svh)))]" dir="auto" tabindex="-1"> Data teams don’t have a dashboard or report problem.They have a meaning and methodology problem. They adjust: Colors Fonts Layouts Chart types But three months earlier, they interviewed the wrong...
Beautiful. Useless. Shipped + The Analytics Talent Spotlight
Most analytics teams are skilled.Few are positioned to solve business problems. The more dashboards we produce, the fewer decisions are made. The visible symptom: Strong technical delivery. Clean models. Fancy colors. Solid SQL. The real problem is posture Analytics is approached as a technical and functional activity, not as a problem-solving discipline connected to the business environment....

The Dashboard Design Brief

What you’ll get every Tuesday A series of sharp visuals that decode common mistakes in analytics and dashboard design. Fast to read. Easy to apply. Hard to forget.
Footer Logo
Privacy Policy Terms and Conditions
© 2026 Dataviz Clarity
Powered by Kajabi