How to Choose the Next Step When a Task Is Stuck for Missing Information
If a task keeps stalling because you don’t have all the details, write down the specific information you need, who or what can provide it, and the smallest action you can take now. If someone else must respond, record a follow-up point; if part of the task can continue without the answer, name that part separately. This turns “waiting for more information” into a clear, resumable plan—useful whether you’re arranging a meal, choosing a day trip, or working on a personal project.
First, name what is missing
“Need more information” describes a feeling of uncertainty, not a next step. Identify the missing piece in terms that could be answered or checked. Is it a date, a preference, a price, a measurement, an approval, or a detail about what someone can do?
Try completing this sentence: **“I can’t decide or do ___ until I know ___.”** For example: “I can’t book the table until I know whether Sam can join on Saturday.” That is more useful than “Plan dinner—unfinished,” because it identifies the decision that is paused.
Keep the request narrow. If you are choosing a place to eat with a friend, you might need to know whether they are free on Saturday and whether they have a food preference. You probably do not need to ask them to decide the whole evening for you. Ask only for information that could change your next decision.
Use this decision process to label the next step
Once you have named the missing information, work through these questions in order.
1. **Can you find it yourself?** If the answer is in a document, schedule, message, or reliable public source, label the action specifically: “Check the venue’s Saturday hours” or “Find the train timetable for the return trip.” Include the source or location if it may be hard to remember later.
2. **Does someone else need to provide it?** Record a concrete request: “Message Sam to ask whether Saturday works and whether they have a cuisine preference.” If you have already asked, move the item to a waiting list and record who owes the reply and when you will check again.
3. **Can any part continue without it?** If so, give that independent part its own next action: “Make a shortlist of two places near the station.” Keep the unresolved decision visible, so the task does not appear fully ready to finish.
4. **Is the missing detail actually a choice you can make?** If no outside fact is required, write the decision itself: “Choose between the two places based on travel time and price.” You can set a reasonable limit for comparing options, then decide with what you know.
5. **Is the task still worth doing?** Sometimes new information changes the plan or the activity no longer matters. Close it, revise it, or leave it paused deliberately rather than repeatedly carrying an obsolete task forward.
Write a next step that can be started
A useful next step begins with an observable verb and points to a clear result. “Sort out the weekend” is broad; “Check the museum’s opening hours for Saturday” can be done. “Think about the trip” is hard to restart; “List two nearby places to visit if it rains” tells you what to produce.
The [Getting Things Done guide to next-action lists](https://gettingthingsdone.com/insights/next-action-list/) emphasizes the specificity of next actions. Applied to a task stalled by missing details, specificity means capturing the question or action that would move it forward—not simply copying the overall goal into a task list.
A compact note can hold the pieces you need:
For example: **Task:** Choose a place for dinner with Sam. **Missing:** Whether Saturday works for Sam. **Next action:** Message Sam to ask about Saturday and any food preference. **If no reply:** Check in Thursday afternoon. **Can do meanwhile:** Shortlist two places near the station.
This is an illustrative example, not a rule that every task needs five fields. Use the smallest note that will help you resume without reconstructing the situation from memory. For a quick lookup, a single action may be enough. For a task with several dependencies, a little more context can prevent another round of “What was I waiting for?”
If you are waiting on a person or response
Make the waiting item identifiable: **what you need, from whom, and what you will do if it does not arrive.** “Waiting for details” omits the person and the detail; “Waiting for Jo to confirm the headcount for Saturday’s picnic; check in Wednesday” gives you a way to recognize and review it.
Choose the check-in point based on the decision it affects. If you need the answer to reserve something by Friday, checking again after Friday is too late. If the plan is flexible, a later check may be fine. A follow-up date is a reminder for you to reassess or contact the person; it does not guarantee a response, so avoid writing it as though the answer is certain to arrive.
The GTD approach to [linking next actions and projects](https://gettingthingsdone.com/2020/06/the-gtd-approach-to-linking-next-actions-and-projects/) describes keeping actions easy to find while retaining project support for dependent or future work. For a blocked task, the practical lesson is to keep the current follow-up visible and preserve the relevant background with the larger task. That way, you can act on the request without losing sight of why you need the answer.
When missing information blocks everything
Some tasks truly cannot proceed until a required detail, permission, or decision arrives. Mark the task as blocked and state the dependency in plain language: “Cannot confirm the booking until the group chooses a date.” Do not disguise it as an action you can already complete.
Then decide whether there is a useful action you control: ask for the decision, clarify who will make it, or set a time to revisit the plan. If there is no action now, record the condition that will restart the task: “Resume when the group confirms a date.” The task is paused, but its restart point is clear.
[Atlassian’s overview of project blockers](https://www.atlassian.com/blog/teamwork/most-common-project-blockers) distinguishes work that cannot move forward until a blocker is removed from impediments that slow progress. It also recommends naming and tracking blockers. For an individual task, that distinction helps: if a missing detail prevents the next meaningful action, record the dependency; if it only makes the task slower, identify what can still move ahead.
A quick review before you leave the task
Read the note as if you will return to it next week. Can you answer these questions without reopening old messages or guessing?
What exact information is missing?
Who or what can provide it?
What is the next action, if any?
What can continue independently?
When or under what condition should you review the task again?
If one answer is missing, add only what is needed. The aim is not to document every thought; it is to leave yourself a clear handhold.
For a task built around an enjoyable everyday activity, such as planning a relaxed picnic or choosing a new walking route with a friend, the method should make the activity easier to return to. Ask for the detail that affects the plan, take one small step that remains open, and let the rest wait with a visible reminder. When the information arrives, update the next action rather than rereading the whole task from scratch.