Checklist
Inventory resources already present before adding a new one
The cheapest missing component may already be present under a different job title.
When it fits
- The default solution adds another tool, service, role or component to solve a local problem.
When to avoid it
- Reuse can create hidden coupling or overload; an existing resource is useful only if its new role remains safe and maintainable.
Checklist
- Unused capacity or idle time is considered.
- Existing data, signals or logs are listed.
- Current components that could perform another function are considered.
- Waste, side effects or by-products are inspected as possible resources.
- Nearby system or environment resources are included.
- Using a resource is checked for new cost, risk and coupling.
Why it matters
List resources already available in the problem zone and surrounding system: unused capacity, time gaps, data already produced, existing fields or signals, space, waste outputs, permissions, parallel components and environmental effects. Ask whether one can perform the required function before importing a new dependency.
An example
Before adding a new monitoring service, ask whether an existing transaction log already exposes the failure signal needed for the alert.
Check your result
The solution search includes at least one existing resource that was not previously treated as part of the design space.
Keep this limit in mind
- Reuse can create hidden coupling or overload; an existing resource is useful only if its new role remains safe and maintainable.
Evidence and sources
ARIZ includes an assessment of available resources in and around the problem before importing new components or mechanisms.
Using existing resources is not automatically better when those resources create hidden reliability, security or maintenance costs.
ARIZ · Step 2 resources