From the Leningrad TRIZ school's function analysis and trimming, credited chiefly to Simon S. Litvin, and set out by Darrell Mann (Hands-On Systematic Innovation, 2002).
Removes a component from a product, process, or organization by handing its function to something already present, cutting cost and complexity while keeping the function.
Six steps in approving a supplier invoice: trim a step only when something already there can do its job
Each step exists to perform one function. Trim a step, and a line below says which part already there takes the function over and what that saves, or that the function is lost. Scanning starts trimmed as a worked example. Today the process costs $14 an invoice. Illustrative.
Mailroom scans paper invoices
Clerk keys in the fields
Clerk matches PO and receipt
Manager signs every invoice
Finance assigns the account code
Treasurer approves the payment run
- Nothing trimmed: six steps, $14 an invoice.Scanning trimmed: suppliers submit through the portal the company already licenses. Saves $2.Keying trimmed: the portal hands over the fields the supplier typed. Saves $4.Function lost: scanned pictures arrive with no fields, and no later step can read them.Matching trimmed: the purchasing system's three-way match flags only exceptions. Saves $3.Sign-off trimmed: the manager approved the spend when the purchase order was raised. Saves $2.Coding trimmed: the purchase order already carries the account code. Saves $1.Function lost: nothing else guards the cash or catches a fraudster's changed bank details.
- Nothing trimmed: six steps, $14 an invoice.Scanning trimmed: suppliers submit through the portal the company already licenses. Saves $2.Keying trimmed: the portal hands over the fields the supplier typed. Saves $4.Function lost: scanned pictures arrive with no fields, and no later step can read them.Matching trimmed: the purchasing system's three-way match flags only exceptions. Saves $3.Sign-off trimmed: the manager approved the spend when the purchase order was raised. Saves $2.Coding trimmed: the purchase order already carries the account code. Saves $1.Function lost: nothing else guards the cash or catches a fraudster's changed bank details.
- Nothing trimmed: six steps, $14 an invoice.Scanning trimmed: suppliers submit through the portal the company already licenses. Saves $2.Keying trimmed: the portal hands over the fields the supplier typed. Saves $4.Function lost: scanned pictures arrive with no fields, and no later step can read them.Matching trimmed: the purchasing system's three-way match flags only exceptions. Saves $3.Sign-off trimmed: the manager approved the spend when the purchase order was raised. Saves $2.Coding trimmed: the purchase order already carries the account code. Saves $1.Function lost: nothing else guards the cash or catches a fraudster's changed bank details.
- Nothing trimmed: six steps, $14 an invoice.Scanning trimmed: suppliers submit through the portal the company already licenses. Saves $2.Keying trimmed: the portal hands over the fields the supplier typed. Saves $4.Function lost: scanned pictures arrive with no fields, and no later step can read them.Matching trimmed: the purchasing system's three-way match flags only exceptions. Saves $3.Sign-off trimmed: the manager approved the spend when the purchase order was raised. Saves $2.Coding trimmed: the purchase order already carries the account code. Saves $1.Function lost: nothing else guards the cash or catches a fraudster's changed bank details.
- Nothing trimmed: six steps, $14 an invoice.Scanning trimmed: suppliers submit through the portal the company already licenses. Saves $2.Keying trimmed: the portal hands over the fields the supplier typed. Saves $4.Function lost: scanned pictures arrive with no fields, and no later step can read them.Matching trimmed: the purchasing system's three-way match flags only exceptions. Saves $3.Sign-off trimmed: the manager approved the spend when the purchase order was raised. Saves $2.Coding trimmed: the purchase order already carries the account code. Saves $1.Function lost: nothing else guards the cash or catches a fraudster's changed bank details.
- Nothing trimmed: six steps, $14 an invoice.Scanning trimmed: suppliers submit through the portal the company already licenses. Saves $2.Keying trimmed: the portal hands over the fields the supplier typed. Saves $4.Function lost: scanned pictures arrive with no fields, and no later step can read them.Matching trimmed: the purchasing system's three-way match flags only exceptions. Saves $3.Sign-off trimmed: the manager approved the spend when the purchase order was raised. Saves $2.Coding trimmed: the purchase order already carries the account code. Saves $1.Function lost: nothing else guards the cash or catches a fraudster's changed bank details.
- Scanning trimmed: suppliers submit through the portal the company already licenses. Saves $2. (scan: Trim)
- Keying trimmed: the portal hands over the fields the supplier typed. Saves $4. (scan: Trim, key: Trim)
- Function lost: scanned pictures arrive with no fields, and no later step can read them. (scan: Keep, key: Trim)
- Matching trimmed: the purchasing system's three-way match flags only exceptions. Saves $3. (match: Trim)
- Sign-off trimmed: the manager approved the spend when the purchase order was raised. Saves $2. (sign: Trim)
- Coding trimmed: the purchase order already carries the account code. Saves $1. (code: Trim)
- Function lost: nothing else guards the cash or catches a fraudster's changed bank details. (pay: Trim)
- Every function still carried?
- Pick every rowYesNo, a function is lost
An example
The accounts payable team at a building supplies distributor handled 9,000 supplier invoices a month, at about $14 each, through six steps. A request to cut the cost by a third had produced only a list of steps each owner called essential, and nothing moved.
The controller mapped the function of each step instead, and asked of each one whether something already in place could do its job. The supplier portal the company licensed but barely used could take in invoices and hand over typed fields, which made both scanning and keying redundant. The purchasing system's three-way match could compare order, receipt, and invoice and flag only the exceptions. For invoices against a purchase order, the manager's signature repeated an approval given when the order was raised, and the account code came with the order. Only the treasurer's approval of the payment run guarded against a supplier's bank details being changed by a fraudster, and nothing else could. Five steps were trimmed for purchase-order invoices, and their cost fell to about $2 each.
Why it works
Cost cutting usually asks which step matters least, and every step has a defender, because every step does something. Trimming asks a narrower question: is something already in the system able to do this step's job? That moves the argument from importance to function. A step can matter a great deal and still be removable when its function is carried elsewhere, here by a purchase order that already holds the approval and the account code.
Mapping functions first is what makes trimming safe. Each trim names the new carrier of the function, so the team can check that the function still happens. When no carrier exists, as with the payment check against fraud, the map says so plainly, and the step stays however costly it looks.
The thinking behind it
Darrell Mann Darrell Mann set out trimming in Hands-On Systematic Innovation (CREAX Press, 2002), his practitioner's handbook of TRIZ. The method comes from the Leningrad TRIZ school, which joined TRIZ with function-cost analysis in the 1980s, and it is credited chiefly to Simon S. Litvin. Once every component's function is mapped, a component is removed when another component, or something already in the system's surroundings, can carry its useful function, so the system keeps what it does and loses a part.
Genrich Altshuller Genrich Altshuller created TRIZ, the theory of inventive problem solving, from the study of thousands of patents, and set out its methods in works including Algorithm of Invention (1969) and Creativity as an Exact Science (1979). TRIZ holds that technical systems evolve by knowable patterns and that inventive problems turn on contradictions, which a small set of principles can resolve. Trimming came later, from the school that carried his work forward, as one of the tools added to his theory.
How to run it
- Map each component and its function. Write what each step, part, or role does, as a verb and an object.
- Note what the function protects. Say what would go wrong if it stopped, so a trim never removes a real need.
- Look for a carrier already present. Ask whether another component, a system already paid for, or the customer could perform it.
- Hand the function over. Move it explicitly, with an owner, and change any rule that assumed the old step.
- Remove the redundant component. Retire the step, part, or role only after its function runs elsewhere.
- Confirm the function still happens. Test with real cases, including the exceptions the old step used to catch.
- Look for the next trim. Each removal can open another, as trimming scanning made keying redundant.
Where it goes wrong
The first failure is trimming the component and forgetting the function. A step disappears, nobody takes over what it did, and the gap shows up months later as an error or a fraud. Spot it when a trim proposal names what is removed but not what now performs its job.
The second is trimming in the wrong order. Removing the keying clerk before invoices arrive as fields leaves pictures nobody can read, so check which trims depend on earlier ones. The third is treating every function as movable. Some, such as an independent check on payments, exist because one party must not do two jobs, and handing them to a step that already does the other job defeats their purpose.
When to use something else
- Function Analysis. When the functions have not been mapped yet, or the trouble is harmful and weak functions more than surplus parts.
- Value Stream Mapping. When the cost lies in waiting and handoffs between steps, more than in the steps themselves.
- Ideal Final Result. When the team wants to start from the result with no system at all and work back to the fewest parts.
Where it sits in SOLVE eX
Go to the source
- Hands-On Systematic Innovation, 2002