Choose and act
Define “done” before the task grows
You start with a short task, then discover that it could include a better layout, another example and a more complete version. None of those ideas is necessarily bad. The difficulty is deciding which ones belong to this task. A stopping condition is easier to use when you set it before every new possibility feels like an obligation.
Start with who will use the result
“Make a good itinerary” leaves the finish line open. “Give two visiting friends enough information to take a two-hour walk from the station” names a use. The necessary details become easier to identify: starting point, route and places where they need to make a decision.
Avoid criteria that cannot be checked, such as “feels professional” or “covers everything”. Translate them into what a person should be able to find or do. If a requirement is unclear, ask before investing in the wrong interpretation.
An illustrative walking plan
You are making a short route for friends. You agree to include a meeting point, a map link and one indoor fallback if it rains. You also need to confirm the route suits their access needs. A detailed history of every building is interesting, but not required for this version.
In this fictional example, completion means the friends can follow the route with the agreed information. It does not mean the route is suitable for everyone or that every condition has been checked forever. If a closure or access issue appears, that is new information requiring a change.
Write a small completion agreement
Three meaningful checks are often enough for a modest task, but the number is not a rule. Include every essential requirement, especially where omission would cause a real problem.
- For: the person who will use this.
- Purpose: what they need to be able to do.
- Finished when: the observable checks that show it works for that purpose.
- Outside this version: useful extras that are not part of the commitment.
- Reopen if: an error, changed condition or relevant feedback appears.
Agree before working when someone else decides
If a colleague, friend or client owns the result, check the criteria with them. “I will send a one-page route with these three items. Is that enough for your visit?” can prevent two people working toward different definitions of complete.
New requests can be reasonable. Treat them as a scope discussion rather than silently moving the finish line. Ask what they replace or whether the deadline changes. Defining done is not a way to refuse every improvement; it makes the effect of an improvement visible before you absorb its cost.
Where Nelby fits
Nelby may help you reflect on why stopping feels uncomfortable, through selected messages you can revisit. For this task, the most useful external reference is the completion agreement itself. This page’s worksheet is not an in-app project feature; use your notes or the shared document to keep everyone aligned.
Nelby is the upcoming version of Éclo. The version currently available on the App Store is still called Éclo and offers subscriptions.
Understand the app and upcoming offer →