Listen Podcast on How without Why
Transcript
(0:00 – 0:10)
You know, I was thinking about this today, and we are all living right smack in the middle of what you could call the age of tutorials. Oh, absolutely. I mean, think about it for a second.
(0:10 – 2:07)
If there is absolutely anything you need to accomplish today, there is a step-by-step guide just waiting for you on a screen somewhere. Yep, usually a five-minute video. Exactly.
Like, if you want to change a tricky alternator in a really specific model of car, or design a corporate logo from scratch, or even, I don’t know, interpret a dense financial statement for your small business, you don’t actually have to go to school for those things anymore. No, you really don’t. You just type your problem into a search bar, and boom, someone has laid out the exact buttons to press, the exact wrenches to turn.
It feels like the ultimate life hack. I have to say, it totally feels like you’re beating the system. Right.
You get the exact result you wanted without having to put in the years to become a, you know, a genuine expert. But what we are looking at today poses a really uncomfortable question. Is this endless, magnificent supply of step-by-step instructions actually making us smarter, or are we just getting exceptionally good at following directions? It is a question that kind of sneaks up on you, I think.
Yeah. Largely because the immediate reward of a well-made tutorial is just so incredibly satisfying. Oh, for sure.
Like, you follow the steps, you got the expected outcome, and your brain just gives you this little hit of dopamine. You feel capable. Yeah, you feel like a genius for five minutes.
Exactly. But there is this massive hidden cost to our societal obsession with procedural learning. When we prioritize the checklist over actual foundational understanding, we are setting ourselves up for a very specific and honestly very dangerous kind of failure the moment the world stops looking exactly like the tutorial.
And that is exactly our mission for this deep dive. We are looking at a really fascinating article from Support Tips titled, The How Without The Why Is Just Following Directions. It’s a great piece.
It really is. So our goal today is to figure out the hidden costs of our obsession with just knowing the how, and discover the secret to developing genuine, adaptable knowledge. Right.
(2:07 – 2:36)
Okay, so let’s unpack this. Because the article drops this staggering statistic right near the beginning, pulling from a 2019 McKinsey survey. They found that 44% of executives believe their workforce lacks the critical thinking skills needed to adapt to new challenges.
44%. Almost half the workforce. I mean, in an era where we have more access to information than any generation in human history, nearly half the workforce is considered unable to adapt to something new.
(2:36 – 4:00)
That is wild to me. Well, that 44% metric is a direct symptom of corporate and educational training that overwhelmingly prioritizes the how over the why. Okay, say more about that.
So we have built entire systems designed to teach people the procedure, right? The checklist, the daily script, without ever really grounding them in the underlying principles of their industry. Yeah, just checking boxes. Exactly.
We’ve successfully trained a global workforce to execute instructions beautifully. But the fatal flaw is that the modern world is volatile. Right.
The moment the instructions go missing or, you know, the software updates or the economic parameters shift, that perfectly trained workforce is completely paralyzed. Wow. Yeah.
Paralyzed is the right word. And to really grasp the root cause behind that paralysis, we need to take a step back from the workplace, I think, and look at the actual neurological mechanics of learning. Yeah, let’s get into the brain stuff.
Right. Because the source material dives into the work of the renowned developmental psychologist Jean Piaget. He spent his career observing how the human brain processes and catalogs new information.
A total pioneer. Yeah. And he drew a hard line between two distinct cognitive processes, which are assimilation and accommodation.
Right. And Piaget’s work is the absolute bedrock for understanding this problem. So assimilation is basically the brain’s default mode because it is super energy efficient.
It’s lazy. Yeah. The brain likes to be lazy.
(4:00 – 5:23)
When you encounter a new piece of information, assimilation means you just force that new fact into your existing mental framework. Okay. You aren’t changing your world view.
You know, you are just memorizing a new sequence of steps and stuffing it into a pre-existing category in your brain. It is very rigid. Okay.
So to make sure I’m visualizing this correctly, assimilation is essentially like trying to install a brand new, highly advanced software feature onto an operating system from 10 years ago. Oh, that’s a great analogy. Like you are just forcing the new code into the old architecture.
Right. And eventually, because the foundation wasn’t built to handle it, the whole system just crashes. Exactly.
But accommodation, the second process Piaget talks about, that would be like actually taking the time to rewrite your operating system so that the new feature runs smoothly and natively. That is a brilliant way to frame it. Accommodation requires high cognitive load.
It demands that you actually reshape your mental model to fit the reality of the new information. Which takes effort. Tons of effort.
Yeah. You don’t just memorize the new steps. You grasp the underlying reason, the why behind them.
And because you did the hard work of understanding the mechanism, your mental framework expands. It becomes flexible. Exactly.
Flexible. When you grasp why something works, you build a mental model that can accommodate an unpredictable reality. Right.
(5:23 – 6:36)
When you only assimilate the how, you were just building a brittle sequence of steps. And brittle things, no matter how shiny they look, they shatter the moment pressure is applied. Okay.
I have to push back just a little bit here though, on behalf of everyone who relies on a good tutorial. Fair enough. Practically speaking, isn’t the how absolutely necessary just to function in modern society? Sure.
I mean, I don’t need to understand the complex thermodynamics of combustion to know how to drive my car in the grocery store. No, you don’t. And if I don’t know the exact sequence of buttons to turn on a new piece of software at work, all the philosophical why in the world doesn’t help me send an email.
Don’t we have to learn the script first just to survive? Well, what’s fascinating here is that you were completely right about needing the initial mechanics. Oh, okay. The danger highlighted in the research isn’t in learning the how.
The danger is stopping there. Ah. Teaching only the how creates a permanent state of dependency between the learner and the instruction manual.
You learn the exact sequence of buttons to click in your company’s database software, right? Right. And you feel productive. But the moment that software company pushes a mandatory user interface update, all those buttons move.
(6:36 – 6:52)
And suddenly your muscle memory is totally useless. You are back to square one. Exactly.
The script changed, and because you only knew the procedural how, you were left entirely helpless. You have to return to the IT desk or the search bar every single time the digital environment shifts. Which is exhausting.
(6:52 – 7:16)
It is. But teaching the why creates autonomy. If you understand the fundamental architecture of a relational database like why the data is organized the way it is, an interface update is nothing more than a minor annoyance.
Right. Because you know what’s going on under the hood. Exactly.
You know what function you are trying to execute, so you can easily adapt to a new layout. You aren’t looking for a specific button. You are looking for a specific capability.
(7:16 – 7:27)
That makes a lot of sense. And you know, since cognitive theories like Piaget’s accommodation can feel a little theoretical, we should see what this brilliance actually looks like in the wild. Let’s do it.
(7:27 – 7:47)
The article offers some great examples of what happens when the how breaks down in disciplines that demand scale and creativity, and the contrast they draw in the world of graphic design is wild. Oh, design is a perfect crucible for testing this theory. Take graphic design and the standard use of a grid system in digital layouts.
(7:47 – 8:06)
Okay. A novice designer learns how to align objects using their software panels. They watch a tutorial.
They click align left. They set their margins to a uniform half inch, and the result is a perfectly tidy, mathematically straight poster. Which is fine, until a client walks in and says they need promotional material for a chaotic underground jazz festival.
(8:06 – 8:33)
They want the poster to feel improvised, raw, and full of kinetic energy. The designer, who only knows the align tool, is going to freeze. Totally.
They’re rigid how completely fails them because they only know how to make things look organized and polite. Exactly. Now, compare that to a master designer who understands why the grid exists in the first place.
Right. They don’t just know the software. They understand the mathematics of visual hierarchy.
(8:33 – 8:51)
They understand foundational aesthetic concepts, like the golden ratio, and how the human eye naturally scans a page from top left to bottom right. Right. The actual psychology of it.
Yes. To them, the grid is not a cage. Because they know exactly why the rules of alignment exist, they can break them deliberately.
(8:51 – 9:09)
They can place a title completely off center, creating visual chaos, exactly where the human eye will instinctively read it as intentional energy, rather than just sloppy execution. The source includes this fantastic quote from the legendary designer Paul Rand. He says, design is so simple, that’s why it is so complicated.
(9:09 – 9:18)
I love that quote. It makes perfect sense now. If you only have the procedural how, you can never achieve that level of deliberate, complicated simplicity.
(9:18 – 9:25)
You’re just connecting the dots. And the stakes get even higher when you apply this concept to engineering. Oh, yeah.
(9:25 – 9:42)
Because software engineering involves massive exponential scale. The text outlines the scenario with a junior developer who learns how to implement a common sorting algorithm called a bubble sort. It is a really basic piece of code used to organize data.
(9:43 – 10:09)
So the junior developer drops this bubble sort into their company’s app, and it works perfectly. They are sorting 1,000 user records, everything runs smoothly, and they get a pat on the back. But then the company goes viral.
Suddenly, that exact same data set expands from 1,000 records to a billion records, and the entire system grinds to a halt and crashes. The procedural how betrayed them. Why exactly? Because a bubble sort works by comparing every single item to every other item sequentially.
(10:09 – 10:19)
For 1,000 items, a computer does that instantly. For a billion items, the math goes exponential, the processing time skyrockets, and the servers literally cannot handle the load. They melt down.
(10:20 – 10:46)
But a senior developer who understands why data structures matter operates completely differently. They understand foundational concepts like big O notation. Okay.
Let’s make sure we clarify that for anyone who doesn’t code, because it sounds intimidating. Big O notation is essentially just a mathematical way of describing how much longer an algorithm takes to run as the amount of data gets bigger, right? Precisely. It measures the worst-case scenario for performance.
(10:46 – 10:56)
Got it. The senior developer knows that the how must drastically change when the constraints change. They also rely on principles like idempotency and statelessness.
(10:56 – 11:05)
Let’s translate those mechanisms, too. Idempotency is a great concept. It basically means that doing something multiple times has the exact same effect as doing it once.
(11:05 – 11:26)
Right. It’s like impatiently mashing the button at a crosswalk. Pushing it 10 times doesn’t make the light change any faster than pushing it once.
The end state is identical. Perfect example. And in programming, making a payment system idempotent means if a user accidentally double-clicks submit order because the site is lagging, they don’t get charged twice.
(11:26 – 11:39)
Oh, thank goodness for that. Right. The system recognizes the end state has already been achieved, and statelessness means the system doesn’t need to remember previous interactions to process a new one.
(11:39 – 11:54)
How does that work in practice? Think of a massive fast food restaurant where every single cashier can take your order instantly without needing to know what you ordered last week. Okay. It scales infinitely because the servers aren’t bogged down trying to remember the history of every single user.
(11:54 – 12:05)
Here’s where it gets really interesting for me. The beauty of these principles, idempotency, statelessness, big-o notation, is that they aren’t tied to a specific coding language. Not at all.
(12:05 – 12:18)
A deep grasp of those fundamentals allows a senior engineer to walk into a company using an entirely different tech stack and still be effective on day one. They aren’t debating the syntax of the code. They are discussing the structural why.
(12:19 – 12:41)
When you look at both the jazz poster and the scalable server, it really forces you to completely reevaluate what creativity actually is. Oh, 100%. People usually assume creativity is just the absence of rules.
Total freedom. But based on this, creativity is actually the absolute mastery of the rules. You can’t creatively bypass a rule you don’t fully understand.
(12:41 – 12:57)
Mastery requires knowing the boundaries of your discipline so intimately that you know exactly where, when, and how to push past them without breaking the system. But let’s be honest, a crashed software system or a badly designed poster, those are inconveniences. Yeah, nobody’s dying.
(12:57 – 13:11)
Maybe incredibly expensive ones, but still just inconveniences. To truly grasp the absolute stakes of this mindset, we have to look at environments where the system is fragile and unpredictable. Environments where adaptability is literally a matter of life and death.
(13:11 – 13:23)
Which brings us to the operating room. The article references the work of surgeon and author Atul Gawande to make a profound point about medicine. Imagine a medical student who treats surgery like a tutorial.
(13:23 – 13:35)
Okay. They just memorize how to perform an appendectomy. They memorize the exact script, make a three-inch incision at minute two, apply a specific suture pattern at minute 12.
(13:35 – 13:40)
But the human body isn’t an iPhone. It’s not manufactured on an assembly line. Exactly.
(13:40 – 13:55)
That student is inevitably going to open a patient and find an anatomical anomaly, like a blood vessel that simply isn’t where the textbook said it would be, or scar tissue from a previous surgery. Right. If they only know the procedural how, panic sets in immediately because the tutorial is broken.
(13:55 – 14:09)
The expert surgeon, however, understands the why behind every single movement of the scalpel. Right. They understand why that specific incision is normally made in that exact spot, usually to avoid a highly sensitive cluster of nerves beneath the muscle.
(14:09 – 14:20)
Okay. They understand why a particular suture pattern is used to evenly distribute physical tension across the tissue to prevent tearing during the healing process. Which is crucial.
(14:20 – 14:28)
Exactly. Because they understand the foundational why of the human anatomy, they can adapt instantly. They don’t need to recite a manual.
(14:28 – 14:45)
They apply first principles to a physical body they have never seen before, navigating around the anomaly while still achieving the goal. That is the ultimate high-stakes test of accommodation versus assimilation. They’re actively reshaping their mental model in real time while holding a sharp instrument.
(14:45 – 15:02)
It’s incredible. And to bridge the gap from novice to that level of mastery, the article introduces a brilliant methodology originally developed for the Toyota production system by an engineer named Taiichi Ono. Ah, yes.
It is known as the five whys. I love this concept. That’s so good.
(15:02 – 15:15)
The methodology is deceptively simple, but incredibly powerful for forcing the brain out of assimilation mode. When you encounter a problem or a failure in a process, you don’t just ask why once and settle for the first obvious answer. Right.
(15:15 – 15:26)
You ask why five times sequentially, peeling back the layers until you hit the foundational truth of the issue. Let’s walk through what that actually sounds like. Let’s say a critical machine on the factory floor stops working.
(15:27 – 15:32)
The novice asks why. The answer, a fuse blew. Yep.
(15:32 – 15:40)
The procedural fix is just to replace the fuse and walk away. But the master asks the second why. Why did the fuse blow? Because the machine was overloaded.
(15:41 – 15:52)
Why was it overloaded? Because the main bearing wasn’t sufficiently lubricated. Why wasn’t it lubricated? Because the oil pump stopped functioning. Why did the pump fail? Because its intake filter was clogged with metal shavings.
(15:52 – 16:00)
There it is. If you just stopped at the first step and replaced the fuse, the machine would just blow another fuse 10 minutes later. Exactly.
(16:00 – 16:12)
The five whys forces you to move past the superficial symptoms and fix the actual root cause. When I read that, it made me realize how fundamentally flawed our standard educational evaluation systems are. Oh, totally.
(16:12 – 16:28)
Exams that just test rote memorization of the how-like standardized multiple-choice tests are merely measuring compliance. They are just checking if a student can follow orders. They are entirely incapable of measuring actual competence.
(16:28 – 16:36)
Critical thinking isn’t just a buzzword, and it isn’t just being a skeptic who questions everything just to be annoying. Right, just being a contrarian. Yeah, it’s not that at all.
(16:36 – 16:46)
It is a disciplined active ability. You have to actively evaluate your own assumptions weigh the evidence in front of you, and trace the chain of causality. Wow.
(16:46 – 17:09)
You cultivate this skill by repeatedly forcing yourself to ask why. Why does this mathematical formula yield this result? Why did this historical conflict ignite over this specific resource? Why does this user interface succeed where a competitor’s fails? It is an ongoing rigorous interrogation of the world around you. Which means teaching the why isn’t just some nice philosophical educational add-on.
(17:09 – 17:29)
It is the core engine that transforms basic information into actual deployable wisdom. Beautifully said. And if asking why is the mechanism that transforms knowledge into wisdom for individuals like our surgeon or our database engineer, then scaling this concept up reveals some absolutely massive implications for the future of our society.
(17:30 – 17:44)
The economic implications alone are sobering. The article points to a World Economic Forum 2020 report, which projected that by the year 2025, a full 50% of all employees globally will need significant reskilling. Half the workforce.
(17:44 – 17:52)
Half. And the driving force behind that is rapid technological disruption. The tools are simply changing faster than anyone can write tutorials for them.
(17:52 – 18:01)
And here is where the divide between the how and the why becomes an insurmountable economic chasm. Workers who know why their industry functions can pivot. Right.
(18:01 – 18:13)
They can take their foundational knowledge and map it onto the new AI integration, or the new supply chain software. But the workers who only assimilated the steps to operate the old tool. They are essentially starting over from zero.
(18:13 – 18:21)
Exactly. A society that prizes only procedural knowledge is building a workforce that can follow instructions. Yeah.
(18:21 – 18:32)
But cannot innovate when those instructions inevitably become obsolete. If we connect this to the bigger picture, it goes far beyond just maintaining a productive economy. Oh, definitely.
(18:32 – 18:46)
Solving the massive unprecedented challenges we are facing globally. Things like climate adaptation, the ethical and functional governance of artificial intelligence, or building resilient global supply chains. None of these things have pre-written manuals.
(18:46 – 18:58)
No, they don’t. There is no step-by-step YouTube tutorial for governing an artificial general intelligence. If we connect this to the bigger picture, it actually traces all the way back to the foundations of Western philosophy.
(18:58 – 19:15)
Really? How so? Well, the article makes a powerful connection between this concept and the Socratic method referencing Plato’s Apology. Okay, take me back to intro philosophy. Socrates famously annoyed the political establishment of Athens because he refused to accept their procedural conventions.
(19:16 – 19:37)
He constantly peeled back the layers of their societal assumptions, asking why, until he exposed that they didn’t actually understand the foundational truths of justice or virtue. Oh, wow. So what does this all mean for us today, practically speaking, as citizens? It means that civic participation requires so much more than just knowing how to vote.
(19:37 – 19:49)
Right. Knowing where your polling place is and how to fill in a bubble is purely procedural. Grounding a society in the Socratic method, in that disciplined pursuit of the why, makes citizens significantly harder to manipulate.
(19:49 – 19:59)
That is a huge point. People who are mentally trained to ask why are naturally far more resilient to propaganda. They don’t just accept a political claim because it is loudly and frequently repeated.
(19:59 – 20:02)
They apply the five whys. They peel back the layers. Exactly.
(20:03 – 20:19)
They peel back the layers of rhetoric to find out if there is any foundational truth or evidence underneath the noise. They are vastly better equipped to evaluate the long-term consequences of policy, rather than just reacting to the immediate symptom. It is incredible to frame it that way.
(20:19 – 20:33)
Moving from how to why isn’t just about educational reform or making sure a massive database doesn’t crash. No, it’s bigger than that. It is literally the foundational requirement for building and maintaining a durable democracy.
(20:34 – 21:03)
It is the dividing line between a society that blindly follows the loudest, most confident voice and a society that can critically evaluate the complex path forward. And for everyone listening to this right now, the very next time you find yourself pulling up a tutorial to learn a new skill, whether it’s coding, cooking, or managing a spreadsheet, I strongly urge you not to settle for just memorizing the script. Right.
Don’t just assimilate it. Do the harder cognitive work of accommodation. Push yourself to understand the underlying mechanics of what the instructor is showing you.
(21:03 – 21:10)
Because I guarantee you, eventually, the script is going to change. To leave you with one final thought, something to really test this out in your own life as soon
