Is Technique a Technology?
An inquiry into Method, Knowledge, and Tools
There are a million ways to pursue systems thinking. One of my favorites is the kind that requires you to throw out a definition you thought was settled and rebuild it from scratch. This is one of those times. We’ve been using Technology too narrowly and in ways in ways that have real consequences for how we think about innovation and improvement. In fact, some of the most powerful interventions available to any system are the ones that never appear in a capital budget.
What is Technology?
Ask someone what technology is and they will gesture at objects. As I look around my desk I see a smart phone, computer monitors, and a kindle. These are the usual objects that the mind conjures up when the topic turns to technology. I could press further, there is also a pen on my desk, a coffee mug, a lamp. These are not technologies on the cutting edge, but they were at one point in time and still remain invaluable technological tools.
Outside of my office, industries are full of these sorts of objects. Industrial lathes, MRI machines, cranes and excavators. They needn’t be hardware either. Indeed, we are living through an information revolution at the hands of AI.
This, idea of technology, however, is impoverished. It is too narrow in its view and in its focus. The problem is the idea that technology is only a thing. When in fact the realm of technology extends into process and method.
To see what I mean, I want to start with the US Army. Though not known for their philosophical nuance, The US Army is perhaps the greatest learning organization in the world. The military culture is steeped in after action reviews, adjustments, and of course, the use of advanced and complicated technology. How they approach technology is noteworthy, and it serves as a foundation for everything that follows. The US Army defines technology as the scientific knowledge, techniques, and tools applied to design, develop, produce, or maintain equipment that provides a decisive competitive edge and operational capability.
Isn’t it interesting that technology is not limited to just the tools but also expands into the realm of knowledge and techniques? Not merely equipment, techniques and knowledge are in the definition and are not merely a supplement to the tools or a prerequisite for their use. So if technique is technology, then the way you do something is as much a technological asset as the machine you use to do it. This entails that any new method is a new technology. The organizations that treat methods as merely administrative overhead, as policies to be updated when convenient rather than capabilities to be engineered and protected, are making a category error with significant operational consequences.
This is actually what is going on with most technological improvements. In terms of innovation, it is rarely the case that the innovation is the product itself. Instead, innovation usually happens up the value stream where it is unseen and relatively unnoticed.
For instance, a tire manufacturer may find that by changing the temperature and pressure and amount of carbon black in their rubber they are able to cure tires faster. This sort of discovery will save the company millions of dollars in economies of scale, but it requires no new equipment or apparatus. It is akin to finding a recipe that takes less time to prepare and cook. It is technological innovation, nevertheless.
Artificial Intelligence is essentially a methodological technology all the same. Yes they require huge data centers to process the large swaths of data, but the real technology behind the AI is a methodological change in how the computer organizes, computes, and associates data. We are still using semiconductors and electrons to do the work, but how the work is done inside the computer has changed.
A History of Method as Invention
The received history of innovation is overwhelmingly a history of objects. From Watt’s steam engine to the telegraph to the transistor to the polio vaccine. Don’t forget Edison’s lightbulb! These are the canonical moments in technological history, and they deserve their canonical status. But they crowd out a parallel history of methodological innovation that is, in aggregate, at least as consequential and, in many individual cases, more so. Indeed, is the scientific method less profound than all of these put together?
Consider double-entry bookkeeping. Developed in medieval Italy and systematized by Luca Pacioli in 1494, double-entry bookkeeping transformed commerce not by inventing any new physical technology but by inventing a new method for tracking obligations and assets. Every transaction recorded twice, once as a debit and once as a credit, with the requirement that the ledger always balance. This created, for the first time, a reliable system for detecting error and fraud, a method for understanding the financial state of a business at any moment, and a common language for commercial relationships across organizations and geographies. Anybody vaguely familiar with accounting will recognize this as the same system we still use today, over 500 years later.
Double-entry bookkeeping did not require any new apparatus. Paper and ink existed. The quill existed. The method, when it arrived, made the rise of modern capitalism possible. Modern finance, insurance, multinational trade, corporate accounting, and eventually the audited financial statements required by public securities markets all descend from Pacioli’s technique. This is a technology as revolutionary as anything. It changed what was possible for every organization that adopted it.
As another example of method as technology consider the surgical checklist. Atul Gawande’s work and the subsequent WHO Surgical Safety Checklist implementation study showed that a simple, structured pre-operative checklist, reduced major complications in surgery by more than a third. Deaths by nearly half. The checklist introduced no new surgical instruments, no new drugs, no new procedures. It was a method for ensuring that existing knowledge was applied consistently, that the right questions were asked before every operation, and that communication between team members was explicitly structured rather than assumed.
The checklist is merely a method for preparation. It is a technology. It is technique applied which has an outsized effect on surgical performance and adverse consequences. It lives entirely in the domain of method and its adoption has been, by any reasonable measure, one of the most cost-effective safety interventions in the history of medicine.
And then famously, we have Toyota Production System. Know as “The Machine that changed the world” it is perhaps one of the best testaments of method as technology. In the postwar period Toyota did was not inventing new machines. The lathes, welding equipment, and assembly fixtures that Toyota used in the 1950s were available to every automobile manufacturer in the world. What Toyota did invent was a method, a set of principles and practices governing how production was organized, how defects were detected and addressed, how inventory was managed, and how workers related to the improvement of their own processes. Just-in-time production, andon cords, kaizen, poka-yoke, standardized work, visual management. All of these are techniques and their use and application had a compounding effect on the entire global automobile industry. General Motors had better equipment than Toyota for much of the postwar period. Toyota built better cars. The difference was not in the hardware. It was in the method.
Standards as Technology
One of the clearest examples of method as technology is the standard, and it is one we have almost completely naturalized, which makes it invisible.
A standard is a codified agreement about how something shall be done, measured, or described. Consider what became possible when standard screw thread specifications were established by Joseph Whitworth in 1841. Before standardization, a bolt made in one factory was incompatible with a nut made in another. Repair required the original manufacturer or custom fabrication. The mechanical interoperability of industrial civilization, everything from railways to ships to rifles to automobiles and aircraft, depended on the establishment and adoption of thread standards. No new machining technique was invented. The standard created the capability.
The interchangeable parts revolution, often attributed to Eli Whitney and the American system of manufacturing, was a methodological innovation at its core. The technological progress was codified and remembered as things like the Steam engine, the railroad, and the cotton gin, but that’s only half of the story. The method, too was a new in the age of industrial change. The method of working to tolerances tight enough that components from different production runs could be assembled interchangeably was no less a part of the Industrial Revolution than the textile factory.
In the modern era, standards continue to constitute technology in ways we routinely undervalue. TCP/IP is a standard. It is not a piece of hardware. It is a method for addressing, routing, and transmitting packets of data across networks. The internet runs on TCP/IP not because anyone invented a new kind of wire but because an agreed-upon method for communication was established and adopted. Every connected device on earth is enabled by this methodological technology. If you’re reading this and are old enough to remember what it sounded like to log onto the internet in the age of dial up you’ll appreciate that those blips and beeps and static were actually a standardized “handshake” protocol which allowed your computer get access the world wide web.
Accounting standards, clinical practice guidelines, building codes, electrical safety standards, food handling protocols, software API specifications. These are all methodological technologies. They encode tested knowledge about how to do things well, create the preconditions for interoperability and cooperation across organizations, and reduce variance in ways that prevent failures. They are not hardware. They are technique. Under the Army’s definition, they are technology.
Measurement as Technology
Measurement deserves its own attention, because it is one of the oldest and most powerful forms of methodological technology, and it is consistently underestimated.
The development of reliable measurement was not a discovery of nature. It was a technological achievement. The establishment of standard units of length, weight, time, and temperature required not just agreement on definitions but the development of methods for creating and maintaining physical standards, calibrating instruments against those standards, and propagating accuracy from the standard down through instruments used in daily practice. This is the science of metrology, and it is among the most consequential technical achievements of the modern world.
Without reliable measurement, industrialization is impossible. You cannot hold tolerances without measurement. You cannot control a process without measurement. You cannot know whether a drug dose is correct without measurement. You cannot design a building, navigate a ship, or schedule a railway without measurement. Measurement is not the passive observation of an objective reality. It is an active methodological technology that makes entire categories of work possible.
Goldratt was famously insistent on this point: what you measure determines what you can manage, and what you measure shapes the behavior of the system whether you intend it to or not. The introduction of new measurement into a system is a technological intervention, akin to purchasing new equipment and may be just as disruptive.
It shouldn’t surprise us to find that in the era of the industrial revolution the sciences of measurement and numbers were never too far behind the mechanical inventions. In fact, we might even see our technological triumphs as a result of advances in measurement (such as optics, and kinematics). Late in the 19th century and early 20th century advances in economics began to emerge thanks in large part to parallel developments in statistical methods.
Visualization as Technology
Closely related to measurement, and equally underappreciated as technology, is the method of visual organization. Not visualization in the sense of how data is charted or presented, but something more fundamental: the deliberate structuring of physical and perceptual environments so that the right information is available to the right person at the right moment, without any additional cognitive work required to find it. This is a technology of the environment itself. And like all the best methodological technologies, it is almost free, almost universally applicable, and almost universally underestimated.
The clearest industrial expression of this principle is 5S, developed within the Toyota Production System and now practiced, with varying degrees of fidelity, in manufacturing and service operations around the world. The five S’s, Sort, Set in Order, Shine, Standardize, and Sustain, are a method for organizing a physical workspace such that the normal state of the environment communicates directly to the people working in it. Tools have defined locations marked on the floor or bench. The shadow board behind the workstation shows exactly which tools belong there and makes instantly visible, without counting or searching, whether any are missing. Materials are stored at defined quantities at defined locations, so that a visual scan is sufficient to detect shortage. Abnormal conditions, a tool out of place, a bin running low, a machine in an unexpected state, are detectable at a glance because the normal state has been defined and made legible in the environment itself.
What 5S is actually doing, beneath its surface of tidiness and organization, is encoding “knowledge into the world,” to borrow Don Norman’s phrase. The knowledge of what normal looks like, of where things belong and what quantities are correct. Before 5S, that knowledge lived in people’s heads, which means it was unevenly distributed, inconsistently applied, and entirely invisible to anyone who did not already possess it. After 5S, it lives in the environment, which means it is available to everyone, requires no memory to access, and makes deviations detectable by people who have never been explicitly trained to look for them. This is a profound shift in where a system’s knowledge resides. And it is accomplished entirely through method.
The underlying perceptual science here is not new, and the fact that it has a name and a history outside of manufacturing is itself instructive. The Gestalt psychologists of the early twentieth century, working in Germany in the 1910s and 1920s, developed a systematic account of how human perception organizes visual fields. Their principles, proximity, similarity, continuity, closure, figure-ground, are not merely observations about how people see. They are a technology of design. They describe, with enough precision to be applied deliberately, how the human perceptual system will interpret any given visual arrangement.
The principle of figure-ground, for instance, describes the automatic perceptual process by which humans separate a visual field into an object of attention and a background. A well-designed workspace uses this principle deliberately. The tool that should be grabbed is made visually distinct from the surface it rests on. The abnormal condition is made to stand out from the normal background, not by adding a warning sign, but by designing the normal state so that anything deviating from it is automatically prominent. The andon light above a Toyota production station is not just a signal. It is an application of figure-ground. The normal state is no light. Any light is figure against that ground. The perceptual technology makes the abnormality detectable without vigilance, without attention, without the operator needing to actively look for it.
The principle of proximity describes the tendency of the perceptual system to group nearby elements together. This principle, applied as a workplace design method, means that tools used together should be stored together, that related information should be co-located, and that spatial arrangement communicates functional relationship whether the designer intends it to or not. An environment designed without awareness of proximity is still applying it; it is simply applying it accidentally, and the results are a workspace that teaches the wrong lessons about what belongs with what and what sequence of operations is normal.
The consequences of ignoring these principles are not minor. Human factors research (of which I’m a huge fanboy of) consistently shows that error rates in complex tasks are strongly influenced by the quality of environmental design. The wrong tool in the wrong place is not merely inconvenient. In surgical suites, aircraft cockpits, pharmaceutical compounding rooms, and nuclear control stations, it is a documented cause of catastrophic error. The research tradition that produced this knowledge, the same tradition that established the value of cockpit standardization across aircraft types, that studied medication error rates in hospital dispensing, and that analyzed accident sequences in industrial operations, is a research tradition about the technology of environment. It takes seriously the idea that where things are, what they look like, how they relate visually to their surroundings, constitutes a technological choice with performance consequences.
This is why the methodology of visual management, of which 5S is one expression, belongs in the same category as the surgical checklist and the thread standard. It is technique applied to produce reliable performance from human operators working under real conditions of cognitive load, time pressure, and divided attention. It does not ask operators to be more careful, more attentive, or more experienced. It restructures the environment so that the right action is also the visually obvious action, and the wrong action, or the abnormal condition, is visually prominent rather than hidden in undifferentiated background. The technology is the method. The method is the environment.
From Method to Organization
I have been arguing that method is technology, and that this is not merely a semantic broadening but a consequential reframing with practical implications for how systems are understood and improved. But I want to end with a forward look, because this reframing has an implication that extends beyond method itself.
If technique is technology, then the question naturally follows: what else that we have been treating as merely administrative, organizational, or cultural is actually technological? What other categories of capability have we been systematically undervaluing because they do not look like equipment?
The answer is organization. The way people are grouped, the way authority and accountability are distributed, the way communication is structured, the way decisions are made. We see this alluded to already in the Toyota Production System. These are not merely the backdrop against which technology operates. They are, under the definition we have been building toward, technologies in their own right.
But that is an argument for the next piece. For now, the claim to take forward is this: every time you describe a methodological improvement as merely a process change, every time you categorize a standard as administrative overhead, every time you dismiss measurement, visualization, or technique as soft rather than technical, you are working with a definition of technology that blinds you to some of your most powerful available interventions.
The US Army got this right, even if it did not develop the point as far as it might. Technique is in the definition because technique is what changes what is possible. It always was. The greatest bottleneck in most organizations is not a piece of equipment on an operations floor somewhere. It is a method that has not yet been invented, adopted, or taken seriously. That method, when it arrives and takes hold, will be technological. It will look like a checklist, or a standard. And it will change everything.
You finished reading the article!
It was free!
Please:



there is a horrifying amount of undeclared methodological knowledge everywhere once you start looking. secretaries who know the bureaucracy inside and out. engineers with procedural knowledge that will be lost once they retire. artisans with techniques so specialized no one can replicate them. people with deep knowledge of social networks, who can assemble teams of people to solve almost any problem, etc. etc.
thank you for writing. i love your posts!
You promoted me with this, because now I can argue that my work, namely reshaping organizations through methods, is actually technology. Brilliant! I am going to put this on my website right away! :-)
I am also a big fan of Lean thinking and have applied many of its principles to how teams, leadership teams, and ways of working are shaped. The workplace example can also be transferred very well to virtual workplaces in offices. There are companies that have three different apps with dozens of channels for sending messages and the communication paths are a mess, there is no visual order.
But also the way leadership is practiced could also easily be standardized and everyone could be assessed against it annually.
Industries with high risk are good examples. A few days ago I had a long conversation with a flight attendant. All procedures are trained regularly. In an escalation scenario, everyone knows what to do. That is why it works. The methods there are strictly monitored.
All organizations can take a page from that book. Naming methods as technologies is exactly the right approach. Now with AI this is becoming highly relevant again.
I think what has been a bit exhausting in recent years was the overflow of methods in offices and soon people could not stand hearing about them anymore. Everyone came along with something new. Then it was just managed half heartedly.
But I have also accompanied organizations through transformations that very deliberately chose which methods to adopt and introduced them very strictly and with discipline, and that was successful.
What I find important is that the people who want to introduce methods understand their craft.
Through your articles you can see how much knowledge and experience one needs to bring.
With many technologies the barrier is much higher, you have to be an expert. With methods you only need to be a good talker. But in practice it does not work. The barrier should be higher. If you call it a technology, you would need to describe which expertise is required for defining and introducing the method. I see more of a cross functional team that jointly develops, defines, and introduces the method.
What would be your advice to organizations when they want to introduce methods or change their organization? Who should they bring into the team and who should they not?