Review: Purpose and Responsibility

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

• Choose between doing and to do when an engineering note describes an activity, goal, or plan.

• Connect responsibility, interest, skill, and purpose without turning one meaning into another.

• Repair a short implementation note and explain what each action pattern contributes.

Idea in one sentence: Good technical English makes the role of each action visible: what someone owns, what they can do, what they want to explore, and what a change is meant to achieve.

Core Insight

At the beginning of the track, a second verb could look like a translation problem. Should the sentence say doing, to do, or something else? The review so far gives us a more useful question:

What job does the second action have in this sentence?

Consider this small set of engineering sentences:

We avoid changing the schema during the incident.
We plan to change the schema next week.
Maya is good at tracing migration failures.
Omar is responsible for reviewing the rollback plan.
Priya is interested in testing a safer index.
We added an index to reduce read latency.
The dashboard is for monitoring query latency.

The action forms are different because the meanings are different:

This is retrieval, not a new grammar list. Say the meaning before you choose the form. If the team owns an activity, use responsible for doing. If the team intends to perform an action, use plans to do. If a tool has a function, for + noun or for + -ing may be clearer than a direct purpose phrase.

The Review Situation

A platform team is preparing a small migration for a request service. The service has a slow query, a noisy alert, and a rollback plan that has not been tested yet. Four people contribute to the implementation note:

• Maya has skill at following a request through several services.
• Omar owns routine API maintenance.
• Priya wants to investigate whether a new index will help.
• The team wants to add the index to reduce latency and create a dashboard to observe the result.

A weak note says:

Maya is good to trace the request.
Omar is responsible to maintain the API.
Priya plans improving the index.
We added an index for reduce latency.
We created a dashboard to monitoring the query.

The meaning is recoverable, but the note mixes patterns. A reader may also misunderstand the commitments. Is Priya merely interested, or has she agreed to run an experiment? Is the dashboard a tool for monitoring, or is the team taking an action to monitor something? Is the index intended to reduce latency, or has that result already been measured?

The Concepts Together

Repair the note one sentence at a time.

Skill is not a plan

The first sentence describes Maya's ability:

Maya is good at tracing the request across services.

Good at takes a noun or an -ing activity. It does not announce what Maya will do next. If the team assigns her a task, use a plan:

Maya plans to trace the request after the next staging run.

The two sentences can both be true. The first gives a skill; the second gives an intended action.

Responsibility is not interest

Omar owns a recurring duty:

Omar is responsible for maintaining the API.

Priya is curious about a possible change:

Priya is interested in testing a new index.

Interest is not an assignment. If the team decides that Priya will run the test, state that decision separately:

Priya plans to test the new index in staging.

The pattern changes the expectation. Interested in testing leaves the work open. Plans to test presents a next step. Responsible for maintaining identifies ownership, which can include coordination and review rather than every physical action.

Purpose is not a result

The migration sentence should state intention:

We added an index to reduce read latency.

The to + verb phrase answers “Why did the team add the index?” It does not prove that latency fell. A result needs evidence:

The staging test reduced p95 read latency from 240 ms to 160 ms.

If the team wants to describe the dashboard's function, use for + -ing:

We created a dashboard for monitoring query latency.

If the plan needs an especially explicit goal, use in order to + verb:

We tested the rollback path in order to reduce deployment risk.

A Synthesis Example

Now build the implementation note from the same facts. The input is a slow query and an ownership question. The note should separate ability, duty, interest, decision, purpose, and evidence.

The complete note is:

Maya is good at tracing requests across services, and Omar is responsible for maintaining the API. Priya is interested in testing a new index, so she plans to run the first staging test. The team will add the index to reduce read latency. The dashboard is for monitoring query latency, but the first run did not reduce latency.

This note is compact, but its relationships are visible. It does not say that interest is ownership, that skill is a plan, or that purpose is proof of success.

Common Confusions

Avoid doing versus plan to do

Avoid changing the schema treats changing as the action the team does not want. Plan to change the schema treats changing as a future goal. The same technical verb can appear in both patterns, but the surrounding verb controls the role:

We avoid deploying during the migration.
We plan to deploy after the rollback test.

Responsible for doing versus responsible to do

Use responsible for for the activity:

The release owner is responsible for checking the rollback path.

Responsible to can describe accountability to a person or authority, but it is not the normal activity pattern in this lesson. Do not use it as a replacement for responsible for checking.

For monitoring versus to monitor

Both can be natural, but the focus differs:

The dashboard is for monitoring latency.
We created the dashboard to monitor latency.

The first describes the dashboard's use. The second describes the team's purpose when creating it. Choose the sentence that answers the reader's question.

Interested in versus plans to

Interest is a lower-commitment statement:

Priya is interested in testing the index.

A plan is a next step:

Priya plans to test the index tomorrow.

Do not turn a person's curiosity into a delivery promise by accident.

Retrieval Check

Complete each sentence before reading the answer. Say the meaning aloud: skill, duty, interest, plan, purpose, use, avoidance, or result.

Check: The team does not want to change the schema during an incident.

Think first, then reveal.

Answer: The team avoids changing the schema during the incident. The schema change is the activity being avoided, so avoid takes -ing.

Check: The team has decided to change the schema next week.

Think first, then reveal.

Answer: The team plans to change the schema next week. The change is a future goal, so plan takes to + base verb.

Check: The dashboard's function is checking queue depth.

Think first, then reveal.

Answer: The dashboard is for checking queue depth. For introduces the activity that names the tool's use.

Check: The index was intended to reduce latency, but measurements are incomplete.

Think first, then reveal.

Answer: We added the index to reduce latency, but we have not measured the production result yet. The purpose phrase states intention and the second clause keeps the evidence boundary visible.

Transfer Challenge

Write a four-sentence implementation note for a change to a service, worker, queue, cache, or migration. Include:

1. one skill claim with good at doing;
2. one ownership claim with responsible for doing;
3. one explicit purpose with to + verb or in order to + verb;
4. one tool use with for + noun or for + -ing;
5. a result or uncertainty that is clearly separate from the purpose.

Then inspect your note with this rubric:

If the note says The team is interested in fixing the queue, ask whether that is enough. If the work has been assigned, revise it to The team is responsible for fixing the queue or The team plans to fix the queue, depending on the intended meaning.

Trade-offs and Limits

These patterns make short engineering notes more precise, but precision costs a small amount of attention. The trade-off is that the writer must decide whether a sentence describes skill, ownership, interest, a plan, purpose, or evidence. A vague sentence can be faster to write, but it makes the reader reconstruct the commitment.

The grammar cannot prove that a person is skilled, that an owner will succeed, or that a purpose was achieved. It only makes the claim's shape visible. Pair skill with observed work, responsibility with an assignment, purpose with a measurement, and interest with a clear decision if the context requires it.

The boundary signal is the difference between what the sentence intends and what the system shows. That difference is not a grammar failure. It is useful engineering information:

We added the index to reduce latency, but the query plan still uses a full scan.

The purpose remains clear, while the evidence tells the team what to investigate next.

Daily Practice Lines

Repeat these during the day. The third line revisits the familiarity pattern from lesson 008.

• We plan to test the migration in staging.
• The dashboard is for monitoring queue depth.
• We are used to reviewing grouped alerts.

Change one technical noun when the lines feel easy: migration, worker, queue, cache, or alert. Keep the pattern stable while the situation changes.

Resources

• [ARTICLE] Cambridge Dictionary: Verb patterns - Use it to compare verbs followed by -ing, to + verb, and preposition-based activity patterns.
• [ARTICLE] Cambridge Dictionary: In order to - Review direct purpose, explicit purpose, and the base verb after in order to.
• [ARTICLE] Microsoft Writing Style Guide - Keep implementation notes concrete and separate ownership, intention, and evidence for the reader.

Key Takeaways

• Doing can name an action being avoided, owned, practiced, or treated as an activity.
• To do can express a goal, plan, decision, or direct purpose.
• Good at doing, responsible for doing, and interested in doing describe skill, duty, and interest; they are not interchangeable.
• For + noun/-ing often describes a tool's use, while to + verb often explains why an action was performed.
• Purpose is intention, not proof. Keep results and uncertainty visible in the technical note.