Count the useful result—and the work required to get it

Compare useful results with the resources needed to produce them, including checking and correction. Faster output counts only to the extent that its value survives those demands.

A quick draft may be valuable. If it takes someone else longer to repair, the apparent saving can disappear.

When comparing workflows, ask:

• Are we comparing similar work against a clear baseline?
• Does the output meet the required quality standard?
• What time, cost, checking and correction does the whole relevant workflow require?
• Where is the gain demonstrated: a person's work, a team, or the entire service?

The framework separates efficiency, capacity, capability and creation. Those describe what changed. Amplification describes a material and disproportionate gain relative to resources. [§8.3] [Theory companion §12.1] [Measurement companion §22]

A simple numerical illustration

That is a threefold increase in quality-adjusted productivity in this simplified example. The estimates do not need to be a new kind of product for the gain to matter. A real claim would still need evidence that the comparison is credible and the gain persists.

Where to go next

Source passages

Related

Examples

• Suggested first
  Preparing funding applications: A nonprofit increases its capacity to prepare sound applications
  Illustrative scenario — assumed threefold preparation capacity
• Repairing equipment: A repair technician investigates an unfamiliar fault
  Illustrative scenario — outcome not yet established
• Building websites: A web developer changes where their effort goes
  Based on a real-world practitioner account
• Running a cabinet shop: A cabinetmaker builds a tool around the business
  Illustrative scenario · assumed outcomes

A limit worth testing

“This sounds like ordinary process improvement with an expensive evaluation layer.”