Whether to continue an existing task depends mainly on whether the new request still supports the original goal.
When should you continue the current task?
Continue when the new request supplements, revises, or extends the existing work, such as:
- Adding new material or data.
- Revising part of the content, tone, or structure.
- Changing the language, length, or delivery format.
- Improving the result after feedback.
- Creating a later version for the same project.
- Completing the next step toward the same goal.
Continuing preserves the existing context, files, and revision history.
When should you start a new task?
Create a new task when the request has become a separate piece of work, such as when:
- The final objective changes completely.
- The audience or use case is entirely different.
- A separate set of source materials is required.
- The original task is finished and the new work is unrelated to its result.
- The two pieces of work need separate tracking.
- Combining them would confuse requirements or versions.
For example, turning a competitive analysis into an executive summary can stay in the same task. Creating a launch plan for another product should be a new task.
A quick decision method
Ask:
- Does the new request serve the same final objective?
- Are the existing materials and context still applicable?
If both answers are mostly yes, continue. If they are mostly no, start a new task.
How should you continue an existing task?
State its relationship to the previous result.
Continue from the previous report and condense it into a 10-slide presentation. Keep the existing data and conclusions.
What should you do in a new task?
Restate the current objective and essential information. If you need a specific result from an older task, upload it or identify it clearly so it can be referenced accurately.