Look Into, Figure Out, and Follow Up

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

• distinguish starting an investigation from reaching an explanation and committing to a later action;

• choose look into, figure out, or follow up without claiming more certainty than the evidence supports;

• write an investigation handoff with a current signal, an owner, an open question, and a concrete follow-up.

Idea in one sentence: These phrasal verbs mark progress through an investigation, so the verb should match what the team knows now and what it promises to do next.

Core Insight

The previous lesson tracked physical resources through setup, startup, teardown, and cleanup. An incident investigation has a similar lifecycle, but its states are about knowledge and ownership:

signal ── look into ──> evidence gathering
evidence ── figure out ──> explanation or solution
decision ── follow up ──> later check or action

Consider this short update:

I will look into the timeout and follow up today.

It promises investigation and a later communication, but it does not claim that the cause is known. Compare it with:

We figured out that the connection pool was exhausted. We will follow up with a capacity change tomorrow.

The second update makes a stronger knowledge claim and adds a specific action. Choosing figure out too early would make the first update sound resolved when it is only being investigated.

The Small Situation

At 14:05, the API team receives an alert:

checkout requests: p95 2.8 s
normal p95: 450 ms
error rate: 0.7%
recent change: parser release at 13:50

The on-call engineer must write a handoff while the investigation is still open. The team tracks these states:

The naive note is:

Maya figured out the timeout, so she will look into it and follow up sometime.

The sentence reverses the investigation stages and makes the follow-up vague. A useful handoff says what has been investigated, what is still uncertain, and who owns the next check.

The Naive Idea: “Investigate” Is One Finished Action

A reader may use one verb for all three moments:

We investigated the alert.

That can mean a first inspection, a complete root-cause analysis, or a long project. In a fast technical update, the distinction matters because the team needs to know whether it should wait for evidence, act on an explanation, or expect a later commitment.

Use a small state model:

look into = start or conduct an investigation
figure out = reach an understanding or solution
follow up = return later to check, communicate, or complete an action

The model is not a promise about the size of the incident. It is a way to keep knowledge and ownership aligned with the sentence.

The Mechanism: Investigation State and Commitment

Plain meaning:

Ask three questions:

1. Are we gathering evidence or checking a question? Use look into.
2. Do we have a supported explanation or solution? Use figure out.
3. Is there a later action or check that someone owns? Use follow up.

Technical name:

These are operational phrasal verbs for investigation and follow-through. They encode epistemic progress and ownership rather than a physical system transition.

Use Look Into When the Question Is Open

Look into means investigate, inspect, or gather evidence about a problem. It does not say that the investigator has reached a conclusion:

Maya will look into the checkout timeout.
We are looking into the connection waits now.

The object follows into:

look into the timeout
look into the traces
look into it

Do not split it as if it were look plus a separable particle:

We will look it into.

That form is not natural for this meaning. Use look into it.

Add the evidence or scope when a handoff needs to be actionable:

Maya will look into the timeout by comparing connection-pool metrics with the parser rollout.

The sentence gives a question and a method without pretending that the answer is known.

Use Figure Out When an Explanation or Solution Is Supported

Figure out means reach an understanding, discover a cause, or determine a solution:

The team figured out why checkout latency rose.
We figured out the immediate cause: the connection pool was exhausted.

With a full noun, both positions can work:

We figured out the cause.
We figured the cause out.

With a pronoun, put it in the middle:

We figured it out.

Not:

We figured out it.

Be careful with the strength of the claim. Figure out suggests that the team has an explanation or solution, but it does not prove that the fix is deployed or that every contributing cause is known:

We figured out the immediate cause, but we have not verified the fix under peak traffic.

This boundary keeps a useful discovery from becoming an unsupported “incident solved” statement.

Use Follow Up for a Later Check, Message, or Action

Follow up means return to an issue later to check progress, communicate, verify a result, or complete an agreed action:

I will follow up tomorrow after the load test.
We will follow up with the database team about the connection limit.
We will follow up on the alert after the next canary.

The verb can stand alone when the context is clear:

I will follow up by 16:00 UTC.

Use follow up with for a person or team and follow up on for an issue, request, or item:

Maya will follow up with the database owner on the connection-limit change.

Do not use follow up as proof that the current problem is fixed. It is a commitment about a later step:

We figured out the immediate cause and will follow up after the mitigation.

The investigation can be understood while the follow-up remains necessary.

A Worked Investigation Handoff

Start with the alert and the current evidence:

14:05: p95 rises to 2.8 s
14:08: parser release is the most recent change
14:12: traces show waits for database connections
14:20: pool exhaustion is reproduced at canary concurrency
14:30: pool limit increased on the canary
16:00: full-load verification scheduled

Input: the open question

Maya is looking into the checkout timeout and comparing traces with the parser rollout.

The sentence states current work. It does not call the cause solved.

Transition: evidence narrows the explanation

The traces show connection waits, so the team is looking into pool exhaustion as the leading hypothesis.

The causal connector so links evidence to the next investigative focus. “Leading hypothesis” preserves uncertainty.

Intermediate state: a cause is reproduced

Maya figured out the immediate cause: the pool was exhausted at canary concurrency.

The explanation is now supported by reproduction. The word “immediate” leaves room for deeper contributing causes.

Decision and later commitment

We increased the pool limit on the canary. Maya will follow up with the database owner after the full-load verification at 16:00 UTC.

The follow-up names a person, a collaborator, a trigger, and a time. It is an operational commitment, not a vague promise to remember the issue.

The complete handoff is:

Maya is looking into the checkout timeout and comparing traces with the parser rollout. The traces show connection waits, so the team is looking into pool exhaustion as the leading hypothesis. Maya figured out the immediate cause: the pool was exhausted at canary concurrency. We increased the pool limit on the canary. Maya will follow up with the database owner after the full-load verification at 16:00 UTC.

The input is the alert. The transitions are evidence gathering, a supported explanation, mitigation, and a scheduled verification. The naive failure contrast is the original sentence that claimed resolution before evidence and left follow-up ownership vague.

Where the Investigation Language Breaks

Suppose the traces are incomplete:

We are looking into the timeout, but we have not figured out the cause yet.

This sentence is strong because it states both the current action and the missing conclusion. Do not write:

We figured out the timeout, but we are still looking into what caused it.

That may be grammatical if “figured out the timeout” means something narrow, but it is ambiguous in an incident handoff. Name the scope:

We figured out how to reproduce the timeout, but we are still looking into its root cause.

Now the two knowledge states are compatible.

Common Confusions

Confusion: look into means the issue is solved

Why it is tempting:

An owner and an action sound reassuring.

Better model:

Look into marks investigation in progress. Add a conclusion only when evidence supports it:

We are looking into the alert; the cause is still unknown.

Confusion: figure out means every cause is known

Why it is tempting:

The phrase sounds like a complete answer.

Better model:

Name the scope of the discovery:

We figured out the immediate cause, but the long-term capacity issue remains open.

Confusion: follow up is a polite ending with no owner

Why it is tempting:

Status updates often end with “we will follow up.”

Better model:

Name who will follow up, with whom or on what, and when:

Maya will follow up with the database owner after the load test.

Confusion: follow up and look into are interchangeable

Why it is tempting:

Both can involve checking information later.

Better model:

Look into starts or continues the investigation. Follow up returns to an item after a prior action, conversation, or deadline:

I will look into the alert now and follow up after the next canary.

Check Your Understanding

Check: The cause is still unknown, but an engineer has started collecting traces. Which sentence fits?

1. Maya will look into the timeout.
2. Maya figured out the timeout completely.

Think first, then reveal.

Answer: Sentence 1. Look into reports investigation without claiming a conclusion.

Check: The team reproduced pool exhaustion and can explain the immediate latency spike. Which sentence fits?

1. We are looking into the cause as a vague possibility.
2. We figured out the immediate cause, but the fix still needs verification.

Think first, then reveal.

Answer: Sentence 2. The explanation is supported, but the verification boundary remains visible.

Check: Which follow-up is actionable?

1. We will follow up sometime.
2. Maya will follow up with the database owner after the full-load test at 16:00 UTC.

Think first, then reveal.

Answer: Sentence 2. It names the owner, collaborator, trigger, and time.

Transfer Challenge: Repair the Investigation Handoff

A teammate writes:

We figured out the timeout, so there is no more work. Someone will look into the database later and we will follow up.

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

• traces show connection waits, but the root cause is not fully verified;
• the team can reproduce pool exhaustion at canary concurrency;
• Maya owns the next investigation step;
• the database owner will check the limit after the mitigation;
• a full-load test is scheduled for 16:00 UTC.

Your answer should:

• use look into for the open investigation;
• use figure out only for the supported immediate explanation;
• use follow up with or follow up on for the later commitment;
• avoid claiming that the whole issue is solved.

One possible answer:

The traces show connection waits, and Maya is looking into pool exhaustion as the leading cause. We figured out that the pool is exhausted at canary concurrency, but the fix still needs verification. Maya will follow up with the database owner after the mitigation. The full-load test is scheduled for 16:00 UTC.

The answer gives the current evidence, the bounded discovery, the owner, and the next checkpoint.

Daily Practice Lines

• Maya is looking into the checkout timeout; the cause is still open.
• We figured out the immediate cause, but the fix still needs verification.
• Maya will follow up with the database owner after the load test.

The first line reuses the investigation vocabulary while preserving uncertainty. Replace timeout with queue lag or certificate error, but keep the progression from open question to bounded explanation to later commitment.

What This Changes

The phrasal-verb cluster now covers the lifecycle of an operational question. A team can name the current investigation, the explanation it has earned, and the work it promises to revisit. This supports the track’s central goal: a reader should reconstruct not only what the system did, but what the team knows and who acts next.

The next lesson reviews the phrasal verbs from rollout, availability, environment lifecycle, and investigation. It will ask the learner to choose an action from a state table and repair object placement without losing agency or evidence.

Trade-offs and Limits

The trade-off is between a concise progress update and a calibrated knowledge claim. Figure out is efficient when the cause is reproduced, but it can overstate certainty if the team has only a plausible correlation. Look into is safer early, but by itself it does not tell the reader what evidence has been gathered or when a decision will be made.

Follow-up commitments add accountability and coordination cost. Naming an owner, collaborator, trigger, and time makes the handoff actionable, but the owner must actually have access and authority to perform the check. A follow-up is not a fix, and an explanation is not proof that the mitigation works. The boundary signal is the verification result after the next test or observation.

Object placement also reflects the construction of each verb: look into it, figure it out, and follow up with the owner. If the sentence hides the object or uses a vague “someone,” the reader cannot tell what knowledge or action is still open.

Resources

• [ARTICLE] Cambridge Dictionary Grammar - Review separable and non-separable phrasal verbs, object placement, and prepositions after follow up.
• [ARTICLE] Microsoft Writing Style Guide - Review investigation handoffs, calibrated claims, named owners, and concrete follow-up commitments.

Key Takeaways

• Use look into for an investigation that is open or in progress.
• Use figure out when evidence supports an explanation or solution; state its scope.
• Use follow up for a later check, message, or action, and name the owner and trigger.
• Write look into it, figure it out, and follow up with the owner naturally.
• A good handoff distinguishes current evidence, supported knowledge, remaining uncertainty, and the next accountable action.