The Systems Minute: Is Technique a Technology?
A short overview of this week's longform post.
What is Technology?
Ask someone what technology is and they will point to objects. Phones, machines, software. The visible artifacts of progress. This is the default answer, and it feels sufficient until you look a little closer. The object-oriented definition leaves something out. It assumes technology is a thing, when in reality it is just as often a way.
The U.S. Army is a premier learning organization and they’re no stranger to using new and advanced technologies. So I thought it would be helpful to see how they think about technology. Interestingly, they define technology in a threefold way: knowledge, techniques, and tools. The implication is easy to miss and hard to overstate. The way something is done is as much a technology as the machine used to do it. Once you see this, innovation starts to look different. It is rarely the product that changes everything. It is the method upstream.
For instance, A manufacturer improves output not by buying new equipment, but by changing how materials are processed. The gains show up in cost and speed, not in new machinery. Artificial intelligence follows the same pattern. The hardware matters, but the breakthrough is methodological. A new way of organizing and associating data. The same electrons, doing different work.
History is full of these surprising revolutions:
Double entry bookkeeping enabled modern commerce without inventing a single physical tool. It created a reliable method for tracking value and detecting error. A new capability emerged from a new way of recording transactions.
The surgical checklist reduced complications and deaths without introducing new instruments or procedures. It ensured that existing knowledge was applied consistently. A simple method, with disproportionate impact.
The Toyota Production System transformed manufacturing not through superior machines, but through techniques. Just in time production. Standardized work. Visual management. Competitors had access to the same equipment. They did not have the same method.
Standards follow the same logic. They are agreements about how something is done, measured, or described. Thread standards made interchangeable parts possible. TCP IP made the internet possible. These are not objects. They are methods that create compatibility and scale.
Measurement itself is a technology. It does not just describe reality. It makes control possible. Without it there is no precision, no repeatability, no improvement. What you measure determines what you can manage, and how a system behaves.
Even the design of environments functions this way. When a workspace is organized so that the right action is obvious and the wrong one is visible, performance changes without new tools or additional effort. The method is embedded in the environment.
The pattern is consistent. Some of the most powerful technologies do not look like technology at all. They look like process, standards, or routine. And this is where organizations make a mistake. Methods are treated as administrative detail. Standards as overhead. Measurement as secondary. But under a broader and more accurate definition, these are core technologies. The constraint is usually not a missing machine. It is a missing method.
You finished the article!
It was free!
Please: