Define what success looks like for a goal before you begin

Start with the intended use

Ask yourself what the result will be used for. “Make an album” is still broad. “Be able to give my sister a readable, 20-page album for her birthday” specifies a use, a recipient, and a deadline. Then you can decide whether the page count is essential or just an initial idea.

For learning, describe a situation. “Get better at cooking” can become “prepare this meal on my own by following clear instructions.” The criterion focuses on a specific action. It doesn’t claim to measure every cooking skill or guarantee the same result under any conditions.

If the goal mainly expresses a direction, keep it flexible. The guide intention or goal helps you distinguish a way of acting from a specific outcome. You can set an intention to be curious and choose a limited goal to explore it, such as attending a workshop and then writing down what you took away from it. To track a marker you can actually observe, distinguish between outcome goals and process goals. For an artistic project, clarifying the name’s purpose also helps you choose a title without trying to explain everything. If you want to write about what really matters, you can explore values affirmation.

Distinguish three levels of criteria

The first level contains essential conditions. Without them, the result won’t serve its intended purpose: the file opens, the object fits in the space provided, the text answers the question. Keep this list to what’s truly necessary. An aesthetic preference can matter without becoming an absolute requirement.

The second level brings together desirable improvements. They add comfort, detail, or polish, but their absence doesn’t prevent the main use. The third level contains future possibilities. Keeping these levels separate prevents every good idea that comes up along the way from becoming an immediate requirement.

You can write these levels in three columns. For each item, ask what would happen if it were missing. If the result would still be usable, the item may not be essential. This question isn’t meant to simplify everything as much as possible; it helps you consciously choose where to draw the line.

Set a criterion you can verify

Avoid entirely vague descriptions: beautiful, professional, perfect, convincing. Look for what they mean in the project. For a document, “readable” might mean that the recipient can find the three main pieces of information without extra explanation. For an object, it might refer to its stability or how easy it is to store.

A number is useful only if it answers a question. Counting the number of sessions shows consistency, but doesn’t automatically prove learning. You can pair an activity measure with evidence of an outcome: four sessions completed and one benchmark exercise done under defined conditions.

Specify how the result will be checked. Who will review it? In what context? With what help permitted? A text understood by its author and one understood by someone new to the topic aren’t subject to the same check. Choose a review that’s proportional to the project’s stakes.

Separate your actions from outcomes that depend on other people

Some outcomes aren’t entirely within your control: getting a response, being selected, selling a creation, or persuading an audience. You can hope for them, but distinguish them from the actions you can prepare for and verify. Submitting a complete application on time isn’t the same as being selected.

Write down both levels if needed: the hoped-for outcome and your personal commitment. This lets you assess the work you’ve done without claiming that effort guarantees the outcome. If the goal depends on someone else’s agreement, note that dependency and when you’ll look for a response.

Don’t reduce the goal to a tiny action that doesn’t serve the result, either. “Open the file” can help you get started, but it doesn’t mean the project is finished. Starting, making progress, and finishing can each have different criteria and serve a different purpose.

Plan for a sufficient version and room to improve

Describe a first version that meets the main need. For an amateur exhibition, that could mean a cohesive selection, works ready to hang, and readable information. A more elaborate presentation may still be desirable. The choice depends on the venue, the time, and the resources actually available.

Also note what imperfections you’d accept. A slight difference in shade, simple wording, or an understated finish may still be compatible with the result. This doesn’t mean overlooking an important flaw; it means distinguishing what prevents something from being used from what could be improved later.

The guide to recognize an achievement without waiting for perfection can extend this reflection. Preparing the criteria makes that recognition more concrete: you can name what you’ve accomplished instead of judging it only by how you feel that day.

Review the criteria when information changes

The criteria aren’t set in stone. A new constraint, useful feedback, or an initial mistake may justify a revision. Note what changes and why. This will help you distinguish a necessary adjustment from a new requirement added simply because the finish line is near.

If several people are involved, share the change with them. A criterion changed in your journal doesn’t automatically become a shared expectation. Confirm the scope, deadline, and how you’ll check it. This clarification prevents you from working for a long time with different definitions of the expected result.

For a personal project, keep the previous version in a few words. You’ll be able to understand the path you took and the reasons for the adjustments. The goal review can then compare the result with the criteria you actually chose, rather than with an ambition reconstructed after the fact. As delivery approaches, sort through the final details to finish a defined version.

Do a simple final check

At the end, revisit each essential criterion and pair it with concrete evidence: a file opened, a test completed, information included, feedback received. If something is missing, decide whether to fix it, reduce the scope, or acknowledge that this version isn’t finished. You can draw a precise conclusion without turning it into a judgment about yourself.

Put desirable improvements on a separate list and choose which ones truly deserve a new version. Some may no longer be useful once the project is in use. You can bring a project to a close while keeping ideas for what comes next, without letting every possibility keep you from recognizing the result you’ve already achieved.