Instead, Otherwise, and In Case

By the end of this lesson, you will be able to...

• distinguish a replacement action from a consequence when a condition fails and from a precaution for a possible problem;

• write a rollout note with a preferred path, a visible fallback, and an observable trigger for switching paths;

• avoid treating in case as a prediction or otherwise as a vague synonym for “also.”

Idea in one sentence: Fallback language tells the reader whether the team is choosing a different path, reacting to failure, or preparing for a risk.

Core Insight

Lesson 007 made the preferred rollout path easy to scan: pause traffic, drain workers, deploy the fix, verify the canary, and restore traffic gradually. A safe plan also answers a second question:

What do we do if the preferred path is blocked or the system behaves badly?

Consider this note:

Keep the old path in case the rollout fails. Otherwise, pause traffic. Use the old path instead.

The words are familiar, but the plan is not clear. What is being replaced? What condition triggers the pause? Is the old path active now, or only prepared as protection?

Repair the relationships:

We will serve reads from the new index. If the canary exceeds the latency budget, we will pause the rollout; otherwise, we will increase traffic by 10%. We will keep the old index available in case we need to switch back.

The main path, failure consequence, and precaution are separate. That separation lets another engineer operate the plan without guessing which action happens first.

The Small Situation

The team is moving search reads from an old index to a new index. The new index has passed count checks and receives 10% of reads. The release policy is:

preferred path: continue increasing traffic if error rate and p95 stay within budget
failure response: pause and return reads to the old index if the canary crosses a limit
precaution: keep the old index and rollback configuration ready while traffic grows

The decision table is:

The naive update collapses all of this into one sentence:

We can use the new index, otherwise use the old one in case something happens.

This does not tell the reader whether “otherwise” refers to high latency, stale data, or any unknown problem. It also treats a precaution as if it were an immediate alternative. The three connectors solve different jobs.

The Naive Idea: Every Backup Sentence Is the Same

A writer may translate three different ideas with one vague phrase such as “if not”:

1. Replacement: choose B rather than A.
2. Consequence: if the required condition is not true, do B.
3. Precaution: prepare B because a problem might happen.

In the rollout:

We serve reads from the old index instead of the new index.

Keep the old index available; otherwise, a failed canary would leave us without a safe read path.

Keep the old index available in case the canary fails.

The first sentence states a current choice. The second states a consequence when the preparation is missing. The third states a precaution. They are not interchangeable.

The Mechanism: Three Fallback Relations

Plain meaning:

These connectors answer three different questions:

Technical name:

Instead is an alternative marker. Otherwise is a conditional consequence marker. In case introduces a precaution clause. The technical names matter less than the direction of the relation: choice, failure consequence, or preparation.

Use Instead for a Deliberate Replacement

Instead says that one action or object replaces another. It often appears at the beginning of a sentence:

Instead, we will keep reads on the old index.

It can also follow the action it corrects:

We will pause the rollout instead of increasing traffic.

Or it can replace a noun or phrase:

Use the old index instead of the new index while we investigate.

The replacement should be explicit. This sentence is too vague:

We will use another path instead.

Which path? For what operation? Name the actor and object:

We will serve reads from the old index instead.

Instead does not itself explain why the replacement happened. Add a reason or condition when needed:

The canary returned stale results, so we will serve reads from the old index instead.

Use Otherwise for the Consequence of a Missing Condition

Otherwise means “if that does not happen” or “if that condition is not met.” It usually refers to a condition in the preceding clause or sentence:

Keep p95 below 300 ms; otherwise, pause the rollout.

The implied condition is p95 stays below 300 ms. Make the condition concrete when the note could be read by someone outside the release call:

If p95 rises above 300 ms, pause the rollout; otherwise, increase traffic by 10%.

Otherwise can also warn about a consequence of skipping a preparation:

Keep the rollback configuration loaded; otherwise, recovery will take longer.

It does not mean “in another way” in every context. If the writer wants to describe a replacement, instead is clearer:

Serve reads from the old index instead.

Use In Case for a Precaution, Not a Prediction

In case says that the team prepares for a possible event. The event may never happen:

Keep the old index available in case the canary fails.

The team is not saying that the canary will fail. It is saying that the cost of keeping the old path available is worth the protection while uncertainty remains.

Compare in case with if:

Keep the old index available in case the canary fails.
If the canary fails, switch reads to the old index.

The first sentence is preparation before the event. The second is the response after the condition is observed. A complete fallback plan may need both.

Do not use in case when the event is a known condition that determines the next action:

If p95 exceeds 300 ms, pause the rollout.

This is a decision rule, not a precaution. In case p95 exceeds 300 ms, pause the rollout sounds as if the pause is taken in advance, before the signal exists.

A Worked Fallback Trace

Start with the canary at 10%:

error rate: 0.4%
p95: 220 ms
old index: available
rollback configuration: loaded

The preferred path is allowed:

If error rate and p95 stay within budget, we will increase traffic by 10%.

The precaution remains active:

We will keep the old index available in case the next stage exposes stale reads.

At the next stage, p95 reaches 340 ms. The fallback rule becomes active:

P95 is above 300 ms, so we will pause the rollout. Instead, we will serve reads from the old index while we investigate. We will not increase traffic; otherwise, the latency risk would spread to more users.

Each sentence has a different relation. So links evidence to consequence. Instead names the replacement action. Otherwise warns about the consequence of ignoring the pause.

After investigation, the team finds that the new cache is cold. They warm it and run the canary again:

We will keep the old index available in case the warmup does not resolve the latency. If p95 returns below 300 ms, we can resume the canary; otherwise, we will keep reads on the old path.

The trace is now executable:

preferred path ── metrics pass ──> increase by 10%
                         │
                         └─ metrics fail ──> pause
                                             │
                                             ├─ instead ──> old index serves reads
                                             ├─ otherwise ──> do not widen
                                             └─ in case ──> old path stays ready

The naive failure contrast is the original “use another path in case something happens.” That phrase hides the trigger, the replacement, and the preparation. The repaired trace gives each one a visible edge.

Common Confusions

Confusion: instead and otherwise are synonyms

Why it is tempting:

Both can introduce a path that differs from the preferred one.

Better model:

Instead names the replacement. Otherwise points to the consequence when a condition is not met:

Pause the rollout instead of increasing traffic.
Keep p95 below 300 ms; otherwise, pause the rollout.

Confusion: in case means that failure is expected

Why it is tempting:

The clause names a possible bad event, so it may sound like a forecast.

Better model:

In case describes preparation under uncertainty. The event may never occur:

Keep rollback ready in case the canary fails.

Confusion: otherwise can stand without a condition

Why it is tempting:

The reader may know the missing condition from a conversation.

Better model:

State the condition in the note or make the reference unambiguous:

If the compatibility check is incomplete, hold traffic at 25%; otherwise, continue the canary.

Confusion: a fallback is always safer than the main path

Why it is tempting:

The word “fallback” sounds like a guaranteed rescue.

Better model:

A fallback is another path with its own limits. The old index may be stale, overloaded, or missing a new field. State what it protects and what it does not:

The old index protects read availability, but it may not include the newest ranking field.

Check Your Understanding

Check: The team stops increasing traffic and returns reads to the old index. Which sentence names the replacement?

1. We will serve reads from the old index instead of increasing traffic.
2. We will serve reads from the old index in case increasing traffic happens.

Think first, then reveal.

Answer: Sentence 1. Instead of names the action that replaces the planned increase. Sentence 2 describes an unclear precaution.

Check: Which sentence makes a failed condition lead to a consequence?

1. Keep rollback ready in case the canary fails.
2. If p95 exceeds 300 ms, pause the rollout; otherwise, increase traffic by 10%.

Think first, then reveal.

Answer: Sentence 2. Otherwise refers to the case in which the stated condition is not the failure case; it completes the two-branch decision.

Check: Which sentence describes preparation for an event that may never happen?

1. Keep the old index available in case the canary fails.
2. Keep the old index available, otherwise the canary will fail.

Think first, then reveal.

Answer: Sentence 1. In case introduces a precaution. Sentence 2 makes a much stronger claim that the missing preparation will cause failure.

Transfer Challenge: Repair the Fallback Plan

A teammate writes:

If p95 is high, otherwise we increase traffic. Keep the old path instead in case the rollout is successful. We can use the new index instead, otherwise.

Rewrite the note in four or five sentences. Keep these facts:

• increase traffic only while error rate and p95 remain within budget;
• pause and serve reads from the old index when p95 exceeds 300 ms;
• keep rollback configuration ready before the next stage;
• the old path is a precaution and may become the active replacement after a failure.

Use:

• otherwise for the consequence of an unmet condition;
• instead for the replacement action;
• in case for preparation before a possible failure.

One possible answer:

If error rate and p95 stay within budget, we will increase traffic by 10%; otherwise, we will pause the rollout. If p95 exceeds 300 ms, we will serve reads from the old index instead. We will load the rollback configuration in case the next canary stage fails. We will not widen traffic until the metrics return to the budget.

The answer separates the preferred branch, the observed failure response, and the precaution. It does not promise that the old path will solve every problem.

Daily Practice Lines

• If p95 exceeds 300 ms, we will serve reads from the old index instead.
• Increase traffic by 10%; otherwise, pause the rollout.
• Keep the rollback configuration ready in case the canary fails.

The first line reuses the condition and canary vocabulary from lessons 004–007. Say the lines with index, then replace it with worker pool or queue consumer while keeping the fallback relation intact.

What This Changes

The track now has a complete local model for a controlled path: conditions permit an action, time and sequence markers order it, and alternatives preserve a safe response when the preferred path is blocked. This lesson does not add more deployment mechanics. It gives the reader the language to state what happens on the other branch.

The next lesson begins the phrasal-verb cluster with roll out, roll back, and phase in. Those verbs will name the operational actions that these connectors currently govern. The fallback plan will become more natural when the action itself has a precise object and direction.

Trade-offs and Limits

The trade-off is between preparedness and active complexity. Keeping an old path, rollback configuration, or duplicate read route ready costs storage, monitoring, and operator attention. It reduces the blast radius of a bad canary, but it does not make the fallback correct or current automatically.

Fallback language also has a precision cost. Otherwise is compact, but it can be ambiguous when several conditions appear in the previous paragraph. Repeat the condition or split the sentence when the consequence matters. In case is useful before uncertainty becomes an incident, but preparation without an owner or test can become a false sense of safety.

You can see the boundary when a reader cannot answer three questions: What triggers the switch? Which action replaces the preferred one? Who verifies that the fallback still works? Add the signal, object, and owner instead of adding more connectors.

Resources

• [ARTICLE] Cambridge Dictionary Grammar - Review instead, otherwise, conditional clauses, and in case as a precaution expression.
• [ARTICLE] Microsoft Writing Style Guide - Review explicit alternatives, failure paths, named actors, and concise operational instructions.

Key Takeaways

• Use instead to name a replacement action or object.
• Use otherwise to state what happens when a condition is not met; make that condition visible.
• Use in case for preparation before a possible problem, not as a prediction or immediate response.
• A fallback plan needs a trigger, a replacement path, and an owner or verification signal.
• Keeping an alternative ready reduces blast radius, but it does not guarantee that the alternative will work.