How to explain a technical mechanism without distorting it

What to take away

• State the output the mechanism produces and the conditions under which it operates.
• Name only the parts needed to trace that output.
• Distinguish physical parts, signals, states, and causal interactions.
• Use a numbered sequence without implying that all mechanisms are linear.
• Check the model against failure, feedback, and edge cases.

A mechanism explanation answers more than "what happens next?" It shows how organized components interact to produce a result. The challenge is to simplify the system without changing what causes what.

Use the following method for a mechanical device, biological pathway, algorithmic system, or control process.

Step 1: Define the output and boundary

Write:

This explanation shows how [input] becomes or changes [output] within [system boundary] under [conditions].

For a bicycle's rear derailleur, the input may be cable movement and the output may be lateral guide-pulley position. The full bicycle, rider, and road need not all be inside the boundary, but their relevant effects may enter as conditions.

NASA's systems engineering handbook, in the chapter on the fundamentals of systems engineering, defines a system as a combination of elements that function together to produce the capability required to meet a need. The value added beyond the parts alone comes mainly from their interconnections.

Drawing a boundary is therefore a claim about which relationships matter.

List what the explanation excludes. Exclusion is not evasion when it is visible.

Step 2: Inventory functional parts

Name a part by what it does before adding detail about material or history.

Part	Function	State that can change
Spring	Applies return force	Extension
Cable	Transfers pull	Tension and position
Parallelogram linkage	Constrains motion	Lateral position
Guide pulley	Aligns chain	Position under sprocket
Shifter index	Selects increments	Chosen detent

Seton Hill University's guide to mechanism description defines the form as an account of an object's function, appearance, and operation and recommends giving readers a concise overview before treating parts in separate sections. The overview supplies a map; the causal sequence gives it motion.

Step 3: Draw the interaction chain

Use arrows before prose:

Lever motion -> cable tension change -> linkage position change -> guide pulley alignment -> chain moves during pedaling.

Label the kind of relation over each arrow: pulls, rotates, opens, heats, detects, transmits, inhibits, or updates. "Affects" is too vague when the mechanism is known.

Step 4: Add order and concurrency

Some processes are sequential. Others have feedback, parallel paths, thresholds, or continuous adjustment.

Use a table:

Stage	Change	Why it occurs	What else is active?
Input	Cable shortens	Lever takes up cable	Spring resists
Transfer	Linkage moves	Tension exceeds return force	Pulley rotates with chain
Output	Chain reaches larger sprocket	Guide position changes chain angle	Pedaling supplies motion

Do not imply that the shifter directly pushes the chain if the pulley position and chain motion mediate the change.

Step 5: Explain energy, information, or material flow

Readers often confuse a control signal with the power that performs the work. A thermostat supplies information to a heating system; it does not supply the heat. A software command selects an operation; electrical energy runs the hardware.

Name the carrier and direction of each flow.

Step 6: Add feedback and control

If an output changes the next input, draw the loop. Explain the target state, sensor, comparison, corrective action, delay, and possible overshoot.

Avoid saying a system "wants" equilibrium unless the personifying shorthand is immediately unpacked.

Step 7: Use failure as a test

Ask what happens when each part fails, saturates, sticks, delays, disconnects, or receives an out-of-range input. A mechanism model that cannot predict a basic failure may omit a necessary relation.

For the derailleur:

• low cable tension may prevent movement toward larger sprockets;
• a bent hanger changes alignment even when indexing is correct;
• movement without pedaling may reposition the guide but not transfer the chain.

These cases expose which component performs each function.

Step 8: Declare simplifications

State what has been idealized: friction ignored, constant temperature assumed, latency omitted, individual variation excluded, or one software implementation chosen.

Do not hide exceptions in "basically." Explain the central model first, then give the condition under which it stops working.

Step 9: Run the teach-back test

Ask a reader to draw the parts and arrows from memory. Then ask:

• What produces the output?
• Where does the energy or information enter?
• Which part controls the change?
• What happens if one part fails?
• Which condition limits the model?

Revise any relationship the reader reverses or invents.

Common questions

Is a mechanism explanation the same as instructions?

No. A mechanism explains how a system operates; instructions tell a reader what actions to perform.

Must every component be named?

No. Include components needed to explain the selected output and state the boundary.

Can I use personifying language?

Only as temporary shorthand. Replace intention with sensing, control, response, or physical interaction.

How do I know whether simplification became distortion?

If the model reverses causation, fails basic cases, or creates a false prediction, it is too simple.