From TRIZ, developed by Genrich Altshuller (Creativity as an Exact Science, 1979).
Pushes a design's size, time, or cost to zero and then to infinity in imagination, exposing hidden assumptions and resources that point to a way through a contradiction.
Five absurd extremes for a delivery drone, and what each one exposes
The drone reaches twelve kilometers, and a bigger battery adds as much weight as range. The facilitator pushes one dimension to an extreme at a time; at each of the team's turns, pick a reading: dismiss the absurd case, or name what it exposes. Illustrative.
Facilitator
Team
Facilitator
Team
Assumptions and resources found: 0 of 5Assumptions and resources found: 1 of 5Assumptions and resources found: 2 of 5Assumptions and resources found: 3 of 5Assumptions and resources found: 4 of 5Assumptions and resources found: 5 of 5
- Size to zero (Facilitator). Picture the drone shrunk to the size of a bee. It still has to deliver prescriptions. What would that take?
- Reading the tiny drone (Team). A drone the size of a bee still has to deliver prescriptions. Pick the team's reading.
- A drone that small carries nothing, so it tells us nothing. The facilitator writes nothing on the board and moves on. Dismissed: the absurd case was where the assumption sat.
- Then the order must be tiny. What do our orders actually weigh? Most refills weigh under 150 grams. The drone was specified for the rare two-kilogram order. An assumption found: the drone was sized for the exception.
- Size to infinity (Facilitator). Now picture it as large as you like. What could a drone that big do?
- Reading the giant (Team). A drone as big as a cargo plane could fly any distance. Pick the team's reading.
- It would need a runway, so it is impossible. The board stays blank under size. Dismissed again: the extreme never got asked what it is for.
- A big carrier could take small drones with it: launch from the delivery vans. The vans already pass within five kilometers of most farm towns every week. A resource found: range now counts from the van.
- Time to zero (Facilitator). Picture the prescription arriving the moment the doctor sends it. What would have to be true?
- Reading instant delivery (Team). The prescription arrives the moment the doctor sends it. Pick the team's reading.
- Nothing travels instantly. Skip it. Time stays at the current promise of same day. Dismissed: the impossibility pointed somewhere.
- Only if the medicine is already in town: stock common refills in village lockers. Twelve village shops already host parcel lockers and would rent space. An assumption found: not every order has to start at the store.
- Time to infinity (Facilitator). Picture a customer who does not mind waiting a week. What changes?
- Reading the long wait (Team). The customer does not mind waiting a week. Pick the team's reading.
- Customers would never accept a week, so it does not apply. The pilot keeps flying every order. Dismissed: the question of which orders are urgent never came up.
- Most refills are known weeks ahead. Only the urgent orders need to fly. Seven orders in ten are repeat refills on a fixed schedule. An assumption found: the drone was serving orders that could ride the van.
- Cost to zero (Facilitator). Picture flights that cost nothing at all. How would the chain use them?
- Reading free flights (Team). Every flight costs nothing. Pick the team's reading.
- Free flights just mean more flights of the same drone. Range stays the limit. A shrug: the extreme was read at today's design.
- Free flights would mean short hops, swapping batteries at the locker shops. The locker shops have power and staff who could swap a battery in a minute. A resource found: the shops are relay stations already in place.
- Back to real values (Facilitator). The redesign: a drone for 600 grams, launched from the vans, routine refills in lockers, and battery swaps at the shops. Reach rises from two customers in five to nine in ten.
An example
A regional pharmacy chain was piloting drone delivery of prescriptions to farm towns, and the pilot had stalled on range. The drones reached twelve kilometers from a store, which covered two customers in five. A larger battery added range and weight in equal measure.
The operations lead ran a session that pushed the drone's size, the delivery time, and the cost of a flight to nothing and to no limit. A bee-sized drone raised a question nobody had asked: what does an order weigh? Most refills came in under 150 grams, and the drone had been specified for the rare two-kilogram order. A drone as big as a cargo plane suggested a carrier for small ones: the delivery vans. Instant delivery meant the medicine had to be in town already, in lockers at village shops. A week's wait showed that most refills were known weeks ahead, and free flights pointed to short hops with battery swaps at the shops.
The redesign used a lighter drone launched from the vans, and refills in lockers. Reach rose to nine customers in ten.
Why it works
A stuck design problem usually rests on dimensions everyone takes as given: this payload, this delivery promise, this budget per trip. People cannot question an assumption they do not see, and ordinary brainstorming stays close to the current values, so it keeps rediscovering the same compromises.
Pushing a dimension to an absurd extreme breaks the current design so completely that the reason it was built that way becomes visible. A bee-sized drone fails at once, and the way it fails asks what it was supposed to carry. An instant delivery is impossible from a store, and the impossibility asks where the stock has to be. Nobody builds the extremes. Their value lies in the question each one forces, and in the resource or the assumption that question turns up, which the team then carries back to realistic values.
The thinking behind it
Genrich Altshuller Genrich Altshuller, an engineer and inventor, built TRIZ, the theory of inventive problem solving, from the study of thousands of patents, and set it out in Creativity as an Exact Science (1979). TRIZ holds that technical systems evolve by knowable patterns and that inventive problems turn on contradictions, resolved by a small set of principles, the separation of conflicting requirements, and ARIZ, his step-by-step algorithm. The size-time-cost operator comes from that body of methods: a deliberate thought experiment that loosens a team's fixed picture of the system before the harder analysis begins.
How to run it
- State the stuck point. Write the problem and the trade-off it is caught in: more range costs as much weight as it buys.
- List the dimensions. Name the size, time, and cost figures the current design assumes, with their values.
- Shrink each one to nothing. Picture the dimension at zero and describe what the system would have to be.
- Grow each one without limit. Picture the dimension as large as you like and describe that system too.
- Ask what each extreme exposes. Write the assumption it breaks or the resource it brings into view, one line each.
- Check each finding against data. Look up the real figures, such as order weights or how far ahead refills are known.
- Carry the findings back. Redesign at realistic values using the assumptions dropped and the resources found.
Where it goes wrong
The team laughs at the extremes and moves on. A drone the size of a bee is absurd, so it is dismissed, and the question it raised goes unasked. Insist that each extreme ends in a written line: the assumption it broke or the resource it showed.
Only one dimension gets pushed, usually cost, because budgets are the familiar constraint. The finding that matters often comes from the dimension nobody thought was movable. Run all three, both ways.
The session produces findings that are never checked. A team that believes most orders are light, without looking, may build the wrong drone with confidence. Turn each finding into a question for the data before it shapes a design.
When to use something else
- Separation Principles. When the problem is one property that must take two opposite values, and the task is finding where they come apart.
- Thought Experiments. When the question is what a theory or plan implies, worked through one imagined case with care.
- First Principles Thinking. When the costs and constraints themselves need rebuilding from what physics, law, or measured need actually require.
Where it sits in SOLVE eX
Go to the source
- Creativity as an Exact Science, Tvorchestvo kak tochnaya nauka, Moscow; English translation Gordon and Breach, 1984, 1979