To Do as a Goal or Next Step

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

• Explain when to do points to a goal, next step, plan, need, or decision.

• Compare discussed splitting with agreed to split in a technical comment.

• Rewrite short implementation notes so the reader can see whether an action is only a topic or an actual commitment.

Idea in one sentence: Use to do when the second action is the goal, next step, need, plan, or decision created by the first verb.

Core Insight

The previous lesson made one pattern visible:

We discussed splitting the table.

In that sentence, splitting the table is the topic. The team talked about the action. The sentence does not say the team chose to do it.

Now compare this:

We agreed to split the table.

The meaning changes. The split is no longer only a topic. It is now a goal or decision.

That is the second core shape in this track:

to do = the action as a goal, next step, need, plan, or decision

This pattern is everywhere in engineering work:

We agreed to split the table.
We need to update the migration.
We plan to deploy the worker after the backfill.
We decided to keep the rollback simple.

The to does not make the sentence more formal. It gives the second action a job. It points forward.

The Small Situation

Use the same backend team from lesson 001.

They have a large events table. Queries are slow. Yesterday, they only discussed the option:

We discussed splitting the table.

Today, after checking query logs and migration risk, the team makes a decision.

The pull request comment says:

We agreed to split the table after the backfill finishes.

This sentence carries more commitment than yesterday's sentence.

Yesterday:

The split was a topic.

Today:

The split is a planned action.

That difference matters. A teammate reading the thread needs to know whether to prepare a migration, write tests, warn support, or do nothing yet.

Grammar is not decoration here. It changes the operational meaning of the comment.

The Naive Idea

The naive idea after lesson 001 is:

If a second action appears after a verb, maybe I should use doing.

That works for verbs like discuss, delay, consider, avoid, and finish.

But it breaks with verbs that point forward:

Awkward:
We agreed splitting the table.

Natural:
We agreed to split the table.

The verb agreed does not only need a topic here. It creates a commitment.

The same thing happens with common engineering verbs:

We need to update the migration.
We plan to deploy the worker tomorrow.
We decided to keep the old index for one week.
We want to reduce the number of manual steps.

These verbs do not treat the second action as an object. They point the reader toward a target.

The better question is:

Does the first verb point to an action we intend, need, plan, or decide?

If yes, to do is often the natural shape.

The Pattern

Plain meaning:

To do points toward an action.

In this scenario:

to split the table is the action the team agreed to do.

Technical name:

This is an infinitive phrase.

infinitive phrase = to + base verb

Again, the label is not the main lesson. The job is the lesson.

Ask:

What is the first verb?
What future action does it point to?

For the sentence:

We agreed to split the table.

the answer is:

That last piece matters. A to do sentence often becomes safer when you name the condition.

Compare:

We agreed to split the table.

Clear, but broad.

We agreed to split the table after the backfill finishes.

Clearer, because the next step has a guardrail.

Action Object vs Goal

Lesson 001 and lesson 002 are a pair.

Use them together:

The word before the second action carries the relation.

Discussed, considered, and delayed usually look backward or sideways. They say how the team treated an action.

Agreed, decided, planned, needed, and wanted usually look forward. They say what action the team is moving toward.

This is a small grammar point with a large practical use. It tells a reader whether to interpret a sentence as exploration or execution.

A Worked Rewrite

Let us repair a status update.

Original:

We discussed splitting the table yesterday. Today we agreed splitting the table after the backfill. We need updating the migration first.

The first sentence is good:

We discussed splitting the table yesterday.

The second sentence has the wrong shape because agreed creates a goal:

Today we agreed to split the table after the backfill.

The third sentence also has the wrong shape because need points to a required action:

We need to update the migration first.

Now the update reads:

We discussed splitting the table yesterday.
Today we agreed to split the table after the backfill.
We need to update the migration first.

This is not only more natural. It gives the reader a timeline:

Input:

mixed `doing` and `to do` patterns

Transition:

classify each main verb: discussed, agreed, need

Intermediate state:

topic verbs use `doing`; goal verbs use `to do`

Output:

discussed splitting, agreed to split, need to update

Naive failure contrast:

`agreed splitting` sounds incomplete because the reader expects the agreed action as a goal.
`need updating` sounds like a noun phrase or a different structure, not a direct requirement.

Need, Plan, Want, Decide, Agree

Many useful to do sentences in engineering come from a small set of verbs.

Each verb changes the strength of the statement.

Want is weaker than need.

We want to reduce manual steps.

This says the outcome is desirable.

We need to reduce manual steps before the release.

This says the outcome is required.

Plan is more concrete than want, but it may still change:

We plan to deploy after the backfill.

Decide and agree usually sound stronger:

We decided to deploy after the backfill.
We agreed to deploy after the backfill.

The trade-off is precision versus commitment. A to do sentence can make a next step clear. It can also make an idea sound more decided than it really is.

If the team is only exploring the action, use the lesson 001 pattern:

We are considering deploying after the backfill.

If the team has chosen the action, use the current pattern:

We decided to deploy after the backfill.

Writing Plans Without Overpromising

Technical English often fails in a small social place: the sentence sounds more committed than the team really is.

Imagine these three comments in a design review:

We want to move the cache closer to users.
We plan to move the cache closer to users after the latency test.
We agreed to move the cache closer to users after the latency test.

All three use to move. The grammar shape is the same. The commitment is not.

Want to says the outcome is desirable.

Plan to says there is an intended path.

Agree to says the team has reached a shared decision.

That means a good technical sentence often needs two parts:

commitment word + guardrail

Examples:

We plan to deploy after the backfill passes.
We need to update the migration before the deploy.
We agreed to split the table, but not before the rollback script is ready.

The guardrail protects the reader from hearing the to do action as immediate or unconditional.

This is especially useful in asynchronous work. A teammate may read your comment six hours later. They need to know whether the action is a wish, a plan, a requirement, or a decision with a condition.

So when you write a to do sentence, ask one extra question:

What condition keeps this goal honest?

If there is no condition, the sentence may still be fine:

We need to update the migration.

But if the condition changes the risk, say it:

We need to update the migration before the backfill starts.

Common Confusions

Confusion: To do always means the action will definitely happen

Why it is tempting:

To do points forward, so it can sound like a promise.

Better model:

To do marks the action as a goal, need, plan, or decision. The first verb tells you how strong that commitment is.

Weak desire:
We want to reduce manual steps.

Stronger requirement:
We need to reduce manual steps before the release.

Plan:
We plan to reduce manual steps in the next deploy.

Decision:
We decided to reduce manual steps before launch.

The to shape points forward. It does not, by itself, prove certainty.

Confusion: Doing is always wrong after a planning verb

Why it is tempting:

This lesson shows many planning verbs with to do.

Better model:

Some expressions use a noun or doing structure with a different first verb:

We discussed reducing manual steps.
We considered reducing manual steps.
We are responsible for reducing manual steps.

Those are not the same as:

We plan to reduce manual steps.
We need to reduce manual steps.

The first verb decides the pattern.

Trade-offs and Limits

The trade-off is that to do makes direction visible, but it can also create accidental commitment.

This helps when a reader needs a clear next step:

We need to update the migration first.

It costs care because to do can make a sentence sound more final than the team intended:

Too strong if still exploring:
We decided to split the table.

Better if still exploring:
We discussed splitting the table.

It does not solve every future-looking sentence. Sometimes a modal verb is the right tool:

We should update the migration first.
We might delay the deploy.
We could split the table later.

Those belong more to the modals track. Here, focus on the relation between the first verb and the second action.

You can see the boundary when the sentence changes the team's responsibility:

We considered changing production during the incident.
We decided to change production during the incident.

The first sentence says the team evaluated an option. The second says the team chose a risky action. That is a big difference.

Check Your Understanding

Check: Which sentence says the split became a decision?

A. We discussed splitting the table. B. We agreed to split the table.

Think first, then reveal.

Answer: B. Agreed to split points to a decision or shared commitment. Discussed splitting only says the split was a topic.

Check: In We need to update the migration before deploy, what is the goal action?

Think first, then reveal.

Answer: to update the migration. The main verb is need, and it points to a required action.

Practice

Rewrite each sentence so the relation is clear.

1. We agreed splitting the table after the backfill.
2. We need updating the migration first.
3. We decided keeping the old index for one week.
4. We want reducing manual steps before the release.

Model answers:

We agreed to split the table after the backfill.
We need to update the migration first.
We decided to keep the old index for one week.
We want to reduce manual steps before the release.

Now compare with lesson 001.

For each pair, choose the sentence that matches the meaning.

Exploration:
We discussed splitting the table.

Decision:
We agreed to split the table.

Option under evaluation:
We considered caching the response.

Chosen action:
We decided to cache the response.

Daily Practice Lines

We agreed to split the table.
We need to update the migration first.
We plan to deploy after the backfill.

Spaced review from lesson 001:

We discussed splitting the table.

Small variation:

Change one technical noun or action, but keep the relation honest.

table -> cache -> parser -> worker -> queue

Example:

We agreed to split the cache.
We agreed to replace the parser.
We agreed to restart the worker.

Some variants will sound strange because the system action is strange. That is useful. Natural technical English needs both a correct pattern and a believable system action.

What To Carry Forward

You now have the track's first two shapes.

Use doing when the second action is the object:

We discussed splitting the table.
We considered caching the response.

Use to do when the second action is the goal, next step, need, plan, or decision:

We agreed to split the table.
We decided to cache the response.

The small diagnostic is:

Is the second action being treated as a topic, or is it pointing forward as a goal?

That question will keep helping in the next lesson, where verbs like avoid, finish, keep, and stop make the doing pattern more automatic.

Resources

• [ARTICLE] Cambridge Dictionary Grammar: Verb patterns - Use it as a reference for which verbs commonly take -ing or to.
• [ARTICLE] Cambridge Dictionary Grammar: Infinitives - Notice how to + verb can point to purpose, intention, and future action.
• [ARTICLE] Microsoft Writing Style Guide - Use it for clear, reader-friendly technical sentences, not for grammar drilling.

Key Takeaways

• To do points to an action as a goal, next step, need, plan, or decision.
• We agreed to split the table is stronger than We discussed splitting the table.
• The first verb controls the pattern: discussed splitting, but agreed to split; considered caching, but decided to cache.
• Use to do carefully because it can make an idea sound more committed than it is.