Process only when you can name what you are hearing that needs to change

Trying processors without a clear diagnostic reason — experimenting to see what happens — leads to chain bloat, time waste, and a higher risk of damaging qualities that were already good. The goal-driven approach requires the engineer to articulate the problem before selecting a tool: ‘I want more density → try compression’; ‘I want more loudness → try a second limiter’; ‘the mix feels packed in and needs space → try a stereo imager’. This frames tool selection as problem-solving rather than exploration, and makes it easier to evaluate whether the tool succeeded. When no problem can be articulated, the correct action is to apply no further processing.

Examples

Before reaching for a compressor, state out loud: ‘I want the mid-range to feel more glued and dense.’ Then apply parallel RMS compression targeting the mids. If the result does not deliver that quality, remove the process rather than adjusting randomly.

Assessment

You feel a master is ‘not quite there’ but cannot name what is missing. What does the goal-driven approach prescribe in this situation, and why is continued experimentation risky?