When I hear certain dogmas about performance and productivity, including those tied to the concept of philocognitives, I laugh.
So, I thought we’d explore this and have a good laugh together ;)
For those discovering the term "Philo...", it’s basically a way of talking about gifted individuals, but with a new label because, well, we got a bit bored with the lack of novelty in the world of labels.
Quite often, you hear...
“Listen up, everyone!”: You mustn’t procrastinate to be efficient.
“Stop slacking off!”
And then you feel bad when you slack off—how nice.
The first problem is... These concepts aren’t defined.
Without a clear definition of procrastination and without linking it to performance in a concrete, tangible, and specific way, we can only approach these concepts and their connection from a general perspective.
Which aspects of procrastination are we talking about? Efficient at what level?
You get the idea...
It all remains conveniently vague.
Being vague is great because it lets you say pretty much anything and always leaves a way out ;)
What’s even funnier is that, if you know a little about how gifted individuals function, you know they have a unique relationship with procrastination.
A lot of people face it, whether gifted or not.
But let’s think about three examples. We all know the "head-down, no-strategy" effect. Performance-wise, it’s not always optimal.
We can also think of all those concepts like “less is more,” the "80/20 rule," etc., where performance isn’t about productivity. That’s not exactly new, is it?
Yet, procrastination, concretely, is a matter of productivity.
But without a connection to quality or goals, none of it makes sense.
Delaying a task can serve various roles or have different effects, and they’re not necessarily harmful depending on the task. For example, it allows us to reflect on our strategy or let ideas mature.
And honestly, if it’s just about ironing, I think we couldn’t care less about performance.
Isn’t there also a process of cognitive incubation?
You know, when the brain works on its own in the background on a problem and eventually surfaces the solution once it’s figured it out.
Saving time on a project thanks to mature reflection and good strategy, or by applying the right solution, is also being efficient.
So, let’s procrastinate joyfully and give ourselves a break ;)
That’s my thought process; I’ll leave you to reflect on it.
And by the way... The antidote is certainly not "precrastination," if we think about how, when you rush to jam a key into a lock, you often end up spending more time than if you’d done it calmly.
My example is dumb, and confusing to boot—I love it.