Is Your "How-To" Guide Actually a Stealthy Argument? A Critical Look at Technical Instruction
Ever followed a set of instructions to the letter, only to wonder why you were doing it that particular way? Or perhaps you've written a "how-to" guide, assuming you were just imparting neutral facts. What if I told you that every piece of technical instruction, from assembling flat-pack furniture to writing a complex piece of code, is actually a carefully constructed argument?
Let's dive into this intriguing idea through the lens of critical thinking.
The Myth of Neutral Instructions
When we think about technical instruction, we often picture a straightforward, objective transfer of knowledge: "Do A, then B, then C." It feels purely descriptive, like a map showing the only path. But dig a little deeper, and you'll find there's always a hidden layer of persuasion at play.
The Core Question: Is Instruction Just Another Argument?
The fundamental question we're exploring is this: To what extent does the efficacy of technical instruction depend upon the implicit logical structures of argumentation (claim, evidence, and warrant), and what are the implications of treating "instruction" as "persuasion"?
This isn't just an academic exercise. Understanding this can radically change how we teach, learn, and even critique the tools and processes we use every day.
Unpacking the "How-To" with Critical Thinking
Let's dissect a typical piece of technical instruction using an analytical framework:
1. The Hidden Purpose:
Explicit: To show you how to achieve a specific outcome (e.g., "how to update your software").
Implicit: To assert that this particular method is the most efficient, safest, or "correct" way. It often implicitly rejects other approaches as inferior.
2. The Unasked Questions:
You're told what to do. But are you ever told why this specific sequence is optimal? What alternative approaches were considered and discarded?
3. The 'Evidence' Behind the Steps:
Technical instructions rely on evidence like empirical results ("it works"), industry standards, or even physical laws.
But what's missing? Rarely do we see the data on alternative workflows, or the cognitive load analysis showing this is the easiest way for all learners.
4. The Core Concepts:
Instructional design often uses concepts like "scaffolding" (building knowledge step-by-step) or "cognitive load theory" (managing how much information a learner processes).
Yet, these methods are essentially arguments about the best way to facilitate learning.
5. Sneaky Assumptions:
Instructions often assume the instructor's method is the most efficient (without proving it).
They assume the learner shares the same definition of "success" or "efficiency."
Crucially, they assume technical "facts" are neutral and don't need justification – when often, they do.
6. Drawing Conclusions:
If a learner follows an instruction and fails, the common conclusion is that the learner is at fault. Rarely do we question if the instruction itself (the "argument") was flawed.
This leads to instruction being a "monologue of truth" rather than a critical "dialogue of justification."
7. The Ripple Effect (Implications):
If instructions are arguments, then every user manual is a persuasive essay!
In the short term, this can lead to learners blindly following steps without true understanding.
Long-term, it can create a workforce that can execute tasks but struggles to innovate or critique the very systems they operate.
8. Whose Viewpoint Dominates?
Most instruction comes from an efficiency-driven, top-down perspective, focused on a single "correct" way.
It often ignores or marginalises alternative perspectives or creative problem-solving methods.
The Brutal Truth: Evaluating Our Instructions
When we examine instructions through this critical lens, we find that while they are often clear, precise, and logical in their steps, they often lack depth (by not explaining the 'why') and breadth (by ignoring alternatives). This means many instructions are only moderately fair, as they present one way as the only way, without acknowledging other valid approaches.
So, How Intellectually Robust Are Our Instructions?
Overall, the idea that technical instruction is fundamentally a form of argument is quite strong. It highlights that simply telling someone how to do something is an assertion of authority and a claim of optimal methodology. The main weakness is that over-analysing every simple instruction could be overkill; not every recipe needs a philosophical debate on flour composition!
The "Pure Proceduralist" Counter-Argument
Of course, some would argue that instruction is purely descriptive. They'd say: "The user just wants to get the job done quickly. Our purpose is to minimise friction, not to get into a debate." This viewpoint prioritises speed and directness. It's highly significant for practical purposes and very precise for execution, but it critically lacks depth and breadth because it doesn't prepare the learner for when the prescribed steps don't work or when innovation is needed.
Beyond Blind Following: Towards Intellectual Virtue
To truly master this interplay between instruction and argument, we need to cultivate certain intellectual virtues:
Intellectual Humility: Recognizing that even our "best practices" are temporary and open to improvement.
Intellectual Courage: Daring to question established procedures and seek better ways.
Intellectual Empathy: Understanding why a learner might struggle, and asking if our instruction (our "argument") is truly clear and convincing.
Intellectual Fairness: Acknowledging that there might be multiple valid ways to achieve a goal, even if we're teaching just one.
The Future: Argumentative Instruction
Imagine a world where technical instructions aren't just a list of steps, but a clear argument:
The Claim: "This method is the most efficient way to achieve X."
The Evidence: "Because data shows it reduces processing time by 20% in standard environments."
The Warrant: "We chose this method because in this context, performance is our highest priority, outweighing factors like code brevity."
The Instruction: "Now, follow these steps..."
This approach would empower learners, fostering a deeper understanding and encouraging critical thinking, rather than just rote memorisation. It's about moving from simply knowing how to understanding why.
