Heuristic
Move the problem boundary outward when the local frame is stuck
Sometimes the component cannot solve the problem because the useful resource lives one level above it.
When it fits
- Every local solution worsens another requirement and the component itself offers no remaining degrees of freedom.
When to avoid it
- Supersystem changes can be politically or technically expensive; compare implementation authority and side effects before preferring them.
Why it matters
Reformulate the required function at the supersystem level: what larger workflow, environment, user interaction or neighboring component could absorb, remove or bypass the conflict? Generate solutions there, then check whether the local component can become simpler as a result.
An example
Instead of making an import program handle every malformed source value, change the upstream data contract so invalid combinations cannot enter the pipeline.
Check your result
At least one solution changes the surrounding system rather than adding another workaround inside the stuck component.
Keep this limit in mind
- Supersystem changes can be politically or technically expensive; compare implementation authority and side effects before preferring them.
Evidence and sources
ARIZ recommends reformulating a resistant problem with respect to the supersystem when the current formulation does not yield a solution.
Moving the boundary outward can increase complexity; do it to reveal a different solution space, not to avoid a well-defined local fix.
ARIZ · Step 6: change or reformulate the problem