# 17B Thinking Through an Alternative

An alternative plan becomes useful when it changes a relevant constraint, rather than simply move the same uncertainty into a different environment.
Suppose that a workflow depends on a remote service, and that service is sometimes unavailable during the hours when we need it.
We might keep a local copy of suitable public data, reduce the number of requests, or design a clear way to resume later.
Each option has a cost, and the choice depends on whether freshness, availability, privacy, or simplicity matters most for the current task.
If the data were available locally, we could continue reading during an outage, but we would still need a plan for updates.
This hypothetical statement helps us explore a possibility without claiming that the local copy already exists or is automatically the best solution.
We can then ask what would happen if the connection failed halfway through a task and whether a partial result could be recovered.
A practical alternative should explain both the ordinary workflow and the condition under which a different path becomes necessary or useful.
When we compare these possibilities, we are choosing how to handle uncertainty rather than promising that no failure will ever occur.
The final plan should state its assumptions clearly so that the team knows when to keep following it and when to reconsider the approach.