Training Is Not a Natural Disaster
Someone told me she was stuck in trainings all day.
Multiple trainings.
All day.
My first response was basically:
“God have mercy on your soul.”
Then I remembered something.
Years ago, at a sports company, my product owner tried to put me into an eight-hour training session about sports betting.
I declined.
I already had people who knew the domain. That was part of how the team worked.
But the part that came back to me during this conversation was how surprising the refusal apparently was.
The training was scheduled.
Everybody else seemed to treat that fact as sufficient.
I still wanted to know whether it was worth a day.
She Was Furious
My product owner did not enjoy this decision.
At all.
There was another layer.
Her boyfriend was the trainer.
I suspected that mattered.
She denied it when I called it out.
Maybe she was right.
Maybe it had nothing to do with her reaction.
I remain unconvinced.
Because now my refusal was not merely:
“This training is not worth my day.”
It could also be heard as:
“This thing your boyfriend is teaching is not worth my day.”
Workplace systems become much more interesting once personal relationships enter the dependency graph.
The Trainer Problem
There was another practical issue.
I could barely understand the guy.
He was British from somewhere.
Fast.
Mumbly.
Some accent my ears never properly resolved.
I would listen and think:
“I know this is English.”
Beyond that, confidence dropped sharply.
So now the proposal was:
Spend an entire workday listening to material I did not think I needed, delivered by someone I struggled to understand.
No.
Still no.
The Strange Power of Scheduling
Organizations do this constantly.
A calendar invitation appears.
Suddenly a block of your life has acquired authority.
Nobody asks whether the meeting is useful.
Nobody asks whether the training is relevant.
Nobody asks whether the audience already knows the material.
It is scheduled.
Therefore it is real.
The calendar has spoken.
This is bizarre.
Scheduling something is not evidence that the thing deserves attendance.
It is evidence that somebody knows how to use Outlook.
Training as Weather
People talk about training the way they talk about rain.
“I have training all day.”
Ah.
Unfortunate atmospheric condition.
Nothing can be done.
Bring an umbrella.
But training is not weather.
Someone chose it.
Someone scheduled it.
Someone decided who should attend.
The attendees may or may not have meaningful agency depending on the organization.
But the event itself is not natural law.
This Is Not Anti-Learning
I like learning.
That is almost the problem.
I learn constantly.
I will lose entire evenings because one obscure technical question became interesting.
I will read documentation nobody asked me to read.
I will dig into APIs that are barely documented because I saw one hint that something was possible.
What I dislike is the assumption that formal training automatically equals useful learning.
Those are not synonyms.
The Cost
Eight hours is expensive.
Not financially.
Cognitively.
You are asking for a working day.
If the value is high, fine.
If the value is low, the price is absurd.
This should not be controversial.
Yet somehow “I don't think this is worth eight hours” can be treated as insubordination instead of ordinary resource allocation.
Back to the Present
So when someone told me she was in trainings all day, my brain immediately remembered that old scene.
She kept chatting through the training anyway.
Which raised another question:
“What have you been doing this whole time?”
Apparently the training had not achieved total cognitive capture.
Good for her.
Maybe the Universe granted bandwidth.
Or maybe, as I have long suspected, training is not a natural disaster after all.