High Value Activity

A task that draws heavily on a person's experience, judgement, and skill to produce outsized impact, as distinct from routine work that almost anyone could pick up. For a quality engineer, identifying which activities are genuinely high value (and reserving their attention for those) is itself a skill, since the same person could spend time on low-impact checks instead. 

The judgement is contextual: a task that is high value on one team or for one change may be low value on another. For example: applying deep exploratory testing to a complex, risky change rather than to a minor copy tweak; leading a story kickoff where requirements are still unclear; or reviewing an architecture for risk before code is written.