Technology Questions (Goldratt’s Six Questions) §

Pattern: A named solution to a recurring problem.

Goldratt’s six-question sequence for assessing whether a new technology creates real value, by tracing it from raw capability to the limitation it removes to the old rules that must change before the value appears.

Also known as: Goldratt’s Six Questions; the Six Questions of Technology; the New Technology Questions.

A new technology isn’t valuable because it is powerful. It is valuable because it removes a limitation someone is paying to live with, and because the people who live with that limitation are willing to change the rules they built around it. The Technology Questions are six questions, in order, that separate the technology’s raw capability from the value a customer will actually realize. Goldratt developed them to keep technology developers, and the organizations buying their products, from confusing the first with the second.

Understand This First §

Context §

A technology that overcomes a real limitation looks, to its developers, like a new wagon taking everyone to a new world. The flood of such wagons is the problem. Big Data, blockchain, AI, IoT, RFID, and whatever arrives next each carry a slogan and a promise, and the organization evaluating them has to decide quickly whether a given one is worth money. Enthusiasm is a poor filter. The developer is sure of the technology’s power; the buyer is unsure what changes in their own operation, and that gap is where most technology investment is wasted.

TOC frames the question the same way it frames any system question: the value of a new capability is not in the capability, it is in the limitation removed and the new behavior that becomes possible. Goldratt posed the assessment as a fixed sequence so the analysis cannot skip the steps that developers most want to skip. The questions move from the technology, to the user’s limitation, to the rules that exist because of that limitation, to the rules that must change, to the application that lets people change without resisting, to the business logic that turns all of it into a sustainable advantage. The order matters. Each question only makes sense once the previous one is answered honestly.

Problem §

Technology evaluation usually starts and stops at the first question. The developer can describe what the technology does, the demo is impressive, and the decision is made on the strength of the capability alone. Then the value doesn’t appear, or appears far more slowly than the business case assumed, because no one traced the path from capability to changed behavior.

The failure has a recognizable shape. A capability that genuinely removes a limitation still delivers nothing if the customer keeps operating by the rules the old limitation forced on them. A long-life battery that lasts two hundred times longer is worth little to a buyer who still keeps a drawer of spares and a recharging habit, because the value was never in the battery’s chemistry; it was in giving up the buying, storing, and carrying that the short battery life required. Until those rules change, the new capability sits unused. Worse, the change itself can carry costs and resistance the developer never looked for, so a technology that should win is rejected for reasons that had nothing to do with its power.

The deeper trap is that the most important question is usually invisible to the people who built the technology. They are fluent in question 1, the power, and nearly blind to question 4, the rules that must change, and question 5, the resistance the change provokes. Those are the answers that decide whether the value is realized.

Forces §

Solution §

Answer the six questions in order, and refuse to move forward until each is honestly answered.

1. What is the power of the new technology? Describe plainly what the technology can do, and just as plainly what it cannot do. The power statement includes the boundaries and the costs. A battery that lasts far longer but costs twenty-five times as much is a different proposition than one that is merely better, and the analysis has to carry both facts from the start.

2. What limitation or barrier does it reduce or eliminate? This is where value is defined, because the user is the one who suffers the limitation. Name the specific limitation, and recognize that a single technology can remove more than one, with different value for different segments. The device that stops without warning when it is needed most, the document that cannot be read because it is in a foreign language: these are the limitations, not the chemistry or the algorithm.

3. What usage rules, patterns, and behaviors exist today because of that limitation? People bypass limitations as best they can, and the workarounds are the measure of the damage. Carrying spare batteries, recharging on a schedule, hiring professional editors, discarding foreign-language documents whose value is unclear: each habit exists because of a limitation, and each names value that becomes available when the limitation is gone.

4. What rules, patterns, and behaviors must change to get the benefit? This is the question developers most often skip, and the one that decides whether the value is realized. The user rarely sees on their own what they must stop doing and start doing to draw the full value. The long-life battery is worthless until the buyer gives up the drawer of spares; the writing tool delivers nothing until the organization changes how it produces and reviews documents. Name the changes explicitly.

5. What application of the technology enables those changes without provoking resistance? Goldratt’s later formulation of this question makes it an active search for negative consequences and practical obstacles. Realizing the new rules carry costs is not enough; the costs can be resolved. The analysis of the perfect-writing tool concluded that it shouldn’t be a new word processor at all, because forcing people to abandon Microsoft Word was a needless source of resistance. Delivered instead as a feature called from inside the tools people already use, the same capability won most of the value and provoked little of the objection. Design the application to deliver the value while removing the reason to refuse it.

6. How is the business built, capitalized, and sustained? The first five questions assess the value; the sixth integrates the technology into a strategy. Build acquires the capability to deliver the value. Capitalize makes it clear to customers how to draw the full value. Sustain ensures the organization has the capacity to meet the demand the technology creates without breaking the very promise that created it. The long-life-battery developer choosing between selling to device manufacturers and selling to consumers, the writing-tool developer negotiating access to Microsoft Word rather than competing with it: these are question-6 decisions, and they decide whether a real capability becomes a durable advantage.

How It Plays Out §

The electronic book reader is the canonical worked example, and it shows the sequence end to end. The power (question 1) is the ability to store and display many books on a screen and download more on demand. The limitations removed (question 2) are two: the space many physical books take at home, and the difficulty of carrying a wide choice while traveling. The old rules (question 3) are the workarounds readers built around those limitations: choosing paperbacks to save space and weight, picking books by recommendation because each one is a commitment, feeling compelled to finish a disappointing book because of what it cost to acquire it. The new rules (question 4) are to keep a whole library on the device and carry it everywhere, and to sample a chapter before buying. The application that avoids resistance (question 5) attends to the real obstacle, which is not storage but the discomfort of reading from a screen: make the device light, hard to break, readable in sunlight, and cheap enough that people will try it, since trying it is the barrier. The business logic (question 6) includes pricing books low enough to build a personal library and managing a fast-growing catalog of electronic titles.

Read straight through, the example shows why the order is fixed. Every answer after the second depends on having named the limitation precisely, and every answer after the third depends on having found the rules the limitation created. A team that started at question 5, designing for adoption, without having done question 2 would be optimizing the comfort of a device whose value it had never established.

The pattern also explains a common kind of failure. A capability clears questions 1 through 3, looks unbeatable, and still doesn’t sell, because question 4 was never answered: the customer was never shown what to stop doing, so the old rules quietly absorbed the new capability and nothing changed. Naming the rules that must change is not a formality at the end of the analysis. It is the bridge between a capability and a result.

Consequences §

Benefits. The Technology Questions convert an enthusiastic capability claim into a sober value assessment, and they do it quickly, which matters when new technologies arrive faster than they can be carefully studied. They force the developer to look past the power they understand best toward the changed behavior they understand least, which is exactly where adoption succeeds or fails. Answering question 2 segment by segment focuses both development and marketing on the customers for whom the limitation is real, rather than diffusing both across an undifferentiated market. And the sequence connects cleanly to the rest of the TOC strategy toolkit: the limitation named in question 2 is the seed of a Decisive Competitive Edge, the resistance anticipated in question 5 is the same resistance the Six Layers of Resistance describe, and the build-capitalize-sustain logic of question 6 is the content a Strategy and Tactics Tree carries.

Liabilities. The questions assess value; they do not create it. A technology that removes no real limitation will fail question 2 honestly answered, and no amount of work on the later questions will rescue it. The discipline is in answering each question against the evidence rather than against the team’s hope, and question 4 in particular invites self-deception, because the changes a customer must make are easy to underestimate from the developer’s seat. The framework also stops at the value assessment and the strategic outline. Question 6 names the build, capitalize, and sustain decisions but does not work them out; that is where the Strategy and Tactics Tree and the rest of the strategy tools take over. Treated as a complete strategy method rather than as a value-assessment lens, the six questions promise more than they deliver.

Related Articles §

Sources §