How do I distinguish a project unknown from a task that is simply unfinished?
Quick answer
Ask whether you could start the item now using information already available. If yes, it is an unfinished task: give it an action, an owner, and a next step. If progress depends on an answer or evidence you do not yet have, it is a project unknown. Write down what would resolve it, who or what can provide that evidence, and when you will check. Revisit unknowns and turn them into tasks once the answer is known.
The question, the details, the next step.
I have a project list full of things like “confirm the launch date,” “write the announcement,” and “decide which audience to prioritize.” Some feel like tasks and some feel like unanswered questions. How can I tell them apart?
Use this test: can someone take a concrete step on the item now, without first getting new information or a decision? If yes, it is an unfinished task. If the next move depends on something not yet known—such as a decision, fact, response, or piece of evidence—record it as an unknown.
For example, “write the announcement” is a task if the audience and date are settled. “Confirm the launch date” is usually an unknown if another person or event must establish the date. “Decide which audience to prioritize” may be a decision task if the relevant information is available; it is an unknown if a missing answer, such as audience needs, must come first. The label depends on what is currently blocking progress, not on the wording.
What if an unknown is stopping several tasks? I do not want it to disappear into a notes list while the project waits.
Keep the unknown visible, but give it an action of its own: identify how you will resolve it. An unknown is not the same as doing nothing. It can have an owner, a question to answer, a source of evidence, and a check-in date. If you cannot name a way to get the answer yet, make finding that route the next task.
A paired list can look like this:
Open questions / unknowns
- Question: What is the confirmed launch date?
- What would resolve it: A date confirmed by the project decision-maker.
- How to get the evidence: Ask the decision-maker to confirm the date.
- Owner / check-in: [name] / [date].
Actionable tasks
- Action: Draft the announcement using the approved message points.
- Owner / next step: [name] / Create a first draft.
- Dependency: Use the confirmed date when it is available.
That last line makes the relationship visible without pretending the date is already known.
How do I decide what counts as enough evidence to close an unknown? I can imagine some questions getting debated forever.
Before investigating, write a closure condition: the specific answer or evidence that would let the project make its next decision. Keep it proportional to the decision. For a scheduling question, a confirmed date may be enough; for a choice between options, you might need agreed criteria and information that addresses them. These are planning examples, not universal standards—set the threshold with the people responsible for the decision.
Try this format: “This unknown is resolved when [person or source] provides [specific answer or evidence], and [decision-maker or team] accepts it as enough to [next decision].” If the evidence is inconclusive, record what is still unknown and choose the next investigation step rather than marking the question complete.
Once I get the answer, how do I keep the list useful instead of maintaining two lists forever?
At each review, check whether the unknown is still open, resolved, or blocked. When resolved, record the answer and its basis briefly, then convert any resulting work into a task with an owner and next step. Close the unknown rather than leaving it among active questions. If the answer changes, reopen it with the new question and a fresh closure condition.
For example, if the date is confirmed as [date], close “What is the launch date?” and add “Update announcement with [date]” if that edit remains undone. The first item was a question about missing information; the second is executable work. Keeping that distinction lets the list show both what the project still needs to learn and what people can do now.
A practical checklist
For each item, ask whether it can be acted on with information already available.
Phrase unknowns as questions, and name the missing answer or evidence.
Set a closure condition before investigating: what answer is enough for the next decision?
Give each unknown a resolution step, an owner, and a check-in date.
When resolved, record the answer and create any remaining executable tasks.
A few more useful answers
Can one item be both an unknown and a task?
The item may involve both, but separate the question from the action that investigates it. For example, keep “Which audience is the priority?” as the unknown and “Review the available audience feedback” as the task.
What if nobody knows how to get the answer?
Record that as an open unknown, then create a task to identify possible evidence sources or ask who can help determine them. Set a review point so the question does not silently stall.
Should I keep resolved unknowns on my active list?
Move them out of the active list, retaining a brief answer if it helps explain a decision. Add any follow-up work as separate tasks.