Checklist
Check what the solution does to neighboring systems
A solved local contradiction can export its cost next door.
When it fits
- A local invention appears to solve the target problem and enthusiasm is narrowing attention to the immediate component.
When to avoid it
- Do not expand the review indefinitely; focus on neighboring systems materially affected by the new design.
Checklist
- Upstream and downstream systems are identified.
- New dependencies and interfaces are listed.
- Operational and maintenance burden is considered.
- A new failure mode or shifted bottleneck is explicitly sought.
- Useful reuse of the mechanism is considered separately from harmful side effects.
Why it matters
Before calling the concept done, inspect adjacent components, users, interfaces, operations and future maintenance. Ask what new load, dependency, failure mode or opportunity the solution creates outside the original boundary. Keep the solution only after those effects are either acceptable or redesigned.
An example
Smaller batches may reduce data-loss blast radius but increase queue overhead and operational coordination; both effects belong in the solution review.
Check your result
The solution record includes at least one adjacent-system consequence rather than only local benefits.
Keep this limit in mind
- Do not expand the review indefinitely; focus on neighboring systems materially affected by the new design.
Evidence and sources
ARIZ includes checking how a proposed solution affects adjacent systems and searching for additional applications of the solution.
Adjacent-system analysis should include harms and new constraints, not only opportunities to reuse the idea.
ARIZ · Step 8: utilization of found solution