layout: post title: “From Purpose to Action: Projects, Goals, and Tasks” series_title: “The Middle-Way Method: An Overview” series: middle-way-method-an-overview date: 2026-11-01 11:00 -0700 categories: [planning, productivity, self-improvement, middle-way] tags: [middle-way-method, planning-hierarchy, projects, defined-goals, tasks, goal-setting, task-management, personal-compass, mission-alignment, top-down-planning, bottom-up-planning, project-filter, goal-filter, task-filter, reviews] image: /assets/article_images/2026/11/Mount-Blanca.jpg description: “Learn how Projects, Defined Goals, and Tasks connect purpose with action, organize commitments, and support a flexible Planning Hierarchy in the Middle-Way Method.” robots: yes responsive_image: true —
The Personal Compass, Mission Statement, and Vision Statement help us establish the direction we want our lives to take. In Finding Your Direction: Values, Mission, and Vision, we examined how these elements bring our Values, Roles, Relationships, enduring purpose, and long-term intentions into our planning. They provide a foundation for deciding what matters and where we want to direct our efforts.
Knowing where we want to go does not automatically tell us how to get there. We may have a clear Vision of something we want to accomplish, but still need to determine what work is involved. Meanwhile, everyday responsibilities continue to demand our attention. We need a way to organize both the commitments we deliberately choose and those that arise through the ordinary course of life.
The second pillar of the Middle-Way Method addresses this through Projects, Defined Goals, and Tasks. Together, they form the Planning Hierarchy, which connects larger undertakings with the outcomes we intend to achieve and the individual actions necessary to accomplish them. Each level serves a different purpose, helping us understand our commitments and the work required to move them forward.
The Planning Hierarchy does not require every commitment to follow the same structure. Some undertakings involve several Goals and many Tasks, while others require only a few actions. Understanding the differences between Projects, Goals, and Tasks allows us to organize work according to its actual requirements, giving us enough structure to plan effectively without making the Planning System unnecessarily complicated.
When we begin planning something we want to accomplish, we often start with a general idea of the result. We may want to establish a garden, improve a skill, or complete a household improvement. We know what we want, but may not yet understand everything required to accomplish it.
As we examine the undertaking, we begin identifying the different outcomes involved and the actions necessary to achieve them. The Planning Hierarchy gives us a way to organize those relationships, connecting the larger undertaking with its individual parts.
The Planning Hierarchy consists of three primary levels. Each answers a different question about the work we intend to accomplish:
The usual arrangement moves from Projects to Goals to Tasks. A Project may contain several Goals, with each Goal supported by the Tasks necessary to complete it.
Consider establishing a vegetable garden. The overall undertaking might be organized as a Project. Preparing the garden site, constructing planting beds, installing irrigation, and planting vegetables could each become Goals within that Project. Purchasing lumber, assembling the beds, and connecting irrigation tubing would be Tasks supporting those Goals.
This arrangement allows us to examine the work at different levels. Looking at the Project tells us what the larger undertaking involves. Its Goals show which outcomes have been accomplished and which remain unfinished. The Tasks identify the individual actions we can take to make progress.
Although Projects, Goals, and Tasks normally follow this progression, not every commitment requires all three levels. Some outcomes stand independently, and many everyday responsibilities consist of individual actions that do not need a larger organizational structure.
The Planning Hierarchy accommodates several arrangements:
These differences matter because a Planning System must accommodate the work we actually need to perform. Replacing a light bulb does not require us to establish a household maintenance Goal. Likewise, reading twelve books during the year may be a meaningful Goal without requiring a separate Project to contain it.
The amount of work involved does not determine its classification. A Goal may require many Tasks, and an individual Task may take considerable effort. What matters is whether we are organizing a larger undertaking, describing an intended outcome, or identifying an action we can perform.
When additional structure helps us organize meaningful work, we can use it. When a simpler arrangement is sufficient, there is no reason to create unnecessary levels.
Some undertakings involve several related outcomes that need to be considered together. We may be able to accomplish each outcome separately, but treating them as unrelated commitments can make it difficult to understand the larger work.
Projects provide a common structure for organizing those outcomes. They help us see how the individual parts contribute to the undertaking and allow us to evaluate progress beyond the completion of any one Goal.
A Project represents a meaningful undertaking that brings related Goals and Tasks together around a larger intended result. Its purpose is to organize work that benefits from being considered as a whole.
Establishing a vegetable garden provides an example. Preparing the ground, constructing planting beds, installing irrigation, and planting vegetables each produce a different result. Together, they contribute to creating a usable garden.
Organizing these outcomes within a Project allows us to understand their relationship. We can recognize which parts have been completed, identify what remains unfinished, and consider whether the overall undertaking is progressing as intended.
A Project is not defined simply by how much time or effort it requires. A relatively modest undertaking may benefit from being organized as a Project when it contains several related outcomes. Something that requires considerable work may still be a Goal if it represents a single intended result.
The distinction becomes clearer when we consider what completion means. Completing a Goal produces a particular outcome. Completing a Project means that its related work has collectively accomplished the larger undertaking.
Goals divide a Project into meaningful outcomes that can be pursued and completed individually. They allow us to recognize progress without requiring the entire Project to be finished before anything can be considered accomplished.
For the vegetable garden, we might establish the following Goals:
Each Goal contributes to the Project, but each also represents a distinct result. Once the planting beds are constructed, that Goal can be completed even though the irrigation system has not yet been installed.
Instead of viewing the Project as one large commitment that remains unfinished until the garden is established, we can recognize the individual outcomes already achieved and concentrate on those that still require attention.
Not every action associated with a Project belongs naturally to a particular Goal. Some Tasks support the undertaking as a whole without contributing to one distinct outcome.
For example, arranging a consultation, obtaining a permit, or contacting someone involved in the undertaking may be necessary for the Project. These actions may not justify establishing separate Goals, particularly when each can be accomplished through a single Task.
Allowing Tasks to belong directly to Projects gives us a way to manage these responsibilities without creating artificial Goals. This flexibility keeps the Planning Hierarchy useful without requiring every action to pass through an intermediate level.
Projects organize larger undertakings, but we also need to identify the specific results we intend to accomplish. These outcomes give our efforts direction and help us recognize when something has been achieved.
Defined Goals serve this purpose. They describe what we intend to accomplish, whether that outcome contributes to a larger Project or stands independently.
A Goal describes a result rather than the individual actions required to produce it. We should be able to recognize what successful completion means, even if we have not yet identified every Task involved.
For example, installing a functioning irrigation system is a Goal. Purchasing tubing, connecting the water supply, and testing the installation are actions that contribute to accomplishing it.
We may understand the desired outcome before we know everything required to achieve it. As work progresses, we may discover that some of our original assumptions were incorrect or that a different approach would be more effective.
Suppose the irrigation design needs to change after we begin working. We may need different materials or a revised layout, but the Goal remains the same: establish a functioning irrigation system.
Separating the outcome from the actions necessary to accomplish it allows us to revise our approach without necessarily changing what we intend to achieve.
Within a Project, Goals identify the distinct outcomes that contribute to completing the larger undertaking.
Constructing planting beds and installing irrigation are separate Goals within our vegetable garden Project. Both contribute to establishing the garden, but each involves different requirements and produces a recognizable result.
Completing the irrigation system advances the Project even though preparing the soil or planting vegetables may remain unfinished. We can recognize that progress without treating the entire undertaking as complete.
A Goal should belong to a Project because it contributes to that undertaking. Two Goals may concern similar subjects without necessarily belonging together. Their relationship should help us understand the larger work rather than merely provide another place to organize them.
Not every Goal requires a Project. Some outcomes are meaningful commitments on their own, and adding a larger structure would provide little benefit.
Someone who wants to read twelve books during the year may establish that as a Goal. The intended result is clear, and the necessary Tasks can be organized directly beneath it. Unless the reading contributes to a larger undertaking, there may be no reason to create a Project.
The same principle applies to much simpler outcomes. Suppose our Goal is to drink freshly squeezed orange juice. We might need to perform several Tasks:
Although several actions are involved, they all contribute to one intended outcome. Creating a Project would not make the work easier to understand or accomplish.
A Goal may be simple or complex, short-term or long-term. Its classification depends upon the outcome we intend to achieve and its relationship to our other commitments, not merely the number of Tasks required.
Projects and Goals establish what we intend to accomplish, but neither completes the work. Eventually, we need to identify actions that can be performed.
Tasks provide that connection between planning and Execution. They describe the individual actions necessary to make progress, allowing us to move from considering an outcome to doing the work required to achieve it.
A Task should identify a specific action that can be performed through direct effort. Within the Middle-Way Method, we want Tasks to be doable, clear, appropriately small, and ready to perform.
Consider the difference between “prepare the garden” and “remove weeds from the planting bed.” The first describes a broader result that may involve several activities. The second identifies an action we can undertake directly.
The Task Filter helps us examine whether an action is sufficiently defined:
These qualities do not require every Task to take only a few minutes. Some actions naturally take longer than others. What matters is whether we can approach the work as a defined action without needing another round of planning.
For example, “install irrigation” may be too broad to function as a Task if we have not determined the materials, layout, or installation process. Measuring the garden, purchasing tubing, and connecting the water supply are more specific actions that can be considered individually.
A Task may also be clear without being ready to perform. We may understand exactly how to connect the irrigation tubing, but we cannot complete that action until the necessary materials are available.
Recognizing these differences helps us prepare work that can actually be performed rather than filling our Task lists with commitments that still require decisions or preparation.
Many Tasks contribute to a larger commitment. Within a Goal, they identify the actions necessary to produce the intended outcome.
Installing irrigation might require measuring the garden, selecting materials, purchasing tubing, assembling the system, and testing its operation. Each Task advances the Goal, while the Goal provides the context for understanding why those actions are necessary.
Tasks can also support a Project directly. An action that benefits the larger undertaking may not belong naturally to any one Goal, and creating another Goal solely to contain it would add unnecessary organization.
Knowing where a Task belongs helps us understand its purpose. It also allows us to examine whether the action remains necessary when a Goal or Project changes.
Many of the actions we need to perform have no direct connection to a larger Goal or Project. Bills need to be paid, light bulbs need replacing, and telephone calls need to be returned.
These responsibilities still belong in our Planning System. They require time and attention, even when they do not contribute to something we have deliberately chosen to pursue.
We do not need to invent Goals or Projects to justify their presence. An independent Task is a legitimate commitment when it represents something that needs to be done.
Bottom-Up Planning recognizes responsibilities that arise through everyday life. Our Planning System must accommodate both the actions that advance our long-term direction and the work necessary to manage our present circumstances.
Understanding the definitions of Projects, Goals, and Tasks is one part of using the Planning Hierarchy. Applying those definitions to our own commitments requires us to examine what we intend to accomplish and how the work relates to everything else we are managing.
Some commitments are easy to classify. Others may initially appear to belong at one level, only to reveal a different structure when we examine them more closely.
When organizing a commitment, we can begin by asking what it actually represents. Are we describing a larger undertaking, a particular outcome, or an action we can perform?
Three questions help us make that distinction:
These questions are guides rather than absolute rules. They help us examine the work before deciding how it should be organized.
Suppose we begin with the intention to install garden irrigation. We might initially classify it as a Project because it involves purchasing materials, preparing the layout, connecting tubing, and testing the installation.
However, these actions all contribute to one recognizable outcome: a functioning irrigation system. The undertaking may be better represented as a Goal supported by several Tasks.
If we are also constructing planting beds, preparing soil, and planting vegetables, we have several related outcomes that contribute to establishing a garden. In that situation, the larger undertaking may become a Project, with irrigation as one of its Goals.
The work required to install irrigation has not necessarily changed. What has changed is our understanding of how it should be organized.
A proposed Project containing only Tasks deserves examination. Such an arrangement is permitted, but it may indicate that we have classified a single outcome as a larger undertaking. Reconsidering the classification may provide a simpler and more accurate representation of the work.
The Planning Hierarchy organizes commitments according to how they contribute to one another. A Goal belongs within a Project because accomplishing it advances the larger undertaking. A Task belongs within a Goal because performing it contributes to achieving that outcome.
These organizational relationships are different from dependencies. A dependency exists when one action or outcome must be completed before another can proceed.
For example, constructing planting beds and installing irrigation may both be Goals within the vegetable garden Project. Their place in the hierarchy reflects their contribution to establishing the garden. Whether one must be completed before the other depends upon the garden’s design and the sequence of work involved.
The same distinction applies to Tasks. Purchasing irrigation tubing and connecting it to the water supply may both support the irrigation Goal, but the materials must be available before the connection can be completed.
The hierarchy tells us how commitments belong together. Dependencies tell us what conditions must be satisfied before particular work can proceed. Both relationships matter, but they answer different planning questions.
Organizational relationships may also become clearer over time. A Goal that initially stands alone may become part of a larger Project when additional related outcomes emerge. Conversely, something originally classified as a Project may prove better suited to being a Goal.
These changes do not necessarily alter what we intend to accomplish. They allow the Planning System to reflect our understanding of the work more accurately.
It can be tempting to organize every commitment through the complete Project, Goal, and Task hierarchy. The resulting arrangement may appear orderly, but additional levels do not automatically make planning more effective.
A Goal does not need a Project merely because Goals commonly belong within Projects. An individual Task does not require a Goal simply to provide a place for it.
Every additional organizational layer becomes something we must maintain and review. When those layers represent meaningful relationships, they help us understand the work. When they exist only to satisfy a preferred arrangement, they can make the Planning System more complicated than necessary.
The objective is to use the structure that serves the work. Some commitments benefit from several levels of organization, while others are easier to manage independently.
Organizing work correctly does not necessarily mean we should undertake it. We may identify a well-defined Project or an achievable Goal that does not fit our current responsibilities, available resources, or long-term direction.
The Planning Hierarchy tells us how commitments can be organized. The Personal Compass, Mission Statement, and Vision Statement help us consider whether those commitments deserve our attention.
The Personal Compass brings our Values, Roles, and Relationships into the decisions we make. Our Mission Statement expresses the enduring purpose we intend to serve, while our Vision Statement describes the future we hope to create.
Together, these elements provide a reference for evaluating Projects and Goals before we commit substantial time and resources to them.
Establishing a vegetable garden, for example, might support an interest in self-reliance, household responsibilities, or personal enjoyment. It may be a worthwhile undertaking, but that does not automatically make it appropriate for our present circumstances.
We may have other responsibilities that require more attention, or the time and resources necessary to maintain the garden may not be available. Considering those circumstances helps us determine whether to begin the Project, change its scope, or leave it for another time.
Alignment does not mean every activity must advance a major life ambition. It means considering our commitments in relation to what matters to us rather than accepting every worthwhile opportunity as something we must pursue.
The Middle-Way Method uses Alignment Checks and Filters to help us evaluate commitments. These mechanisms provide different considerations depending upon the kind of work involved.
The Project Filter helps us examine whether a larger undertaking fits our direction, offers sufficient value, and can be supported by our available resources. The Goal Filter considers whether an intended outcome is meaningful, clear, and appropriate within its circumstances. The Task Filter examines whether an action is necessary, sufficiently defined, and suitable for Execution.
These decisions occur at different levels. Determining whether we should establish a vegetable garden is not the same as deciding whether we can purchase irrigation tubing today.
The Filters do not make those decisions for us. They help us consider the relevant questions before accepting or acting upon a commitment.
Not every commitment begins with a long-term ambition. Some work develops from the direction we have deliberately established, while other responsibilities arise through everyday circumstances.
Top-Down Planning begins with purpose and direction. We consider what we intend to accomplish, identify meaningful Projects and Goals, and determine the Tasks necessary to pursue them.
Bottom-Up Planning begins with the responsibilities, information, and opportunities we encounter in everyday life. A household repair may produce an immediate Task. A new responsibility may require a Goal, while a more involved situation may develop into a Project.
Both approaches belong within the Middle-Way Method. The Planning Hierarchy gives us a common structure for organizing commitments regardless of where they originate.
Maintaining alignment does not require every Task to contribute directly to our Vision Statement. Paying bills, maintaining our homes, and fulfilling existing responsibilities are legitimate uses of our time. We need to understand those commitments and make deliberate decisions about how they fit alongside the larger outcomes we want to pursue.
Plans are developed using the information available when we make them. Once work begins, circumstances may change, new information may become available, and our understanding of an undertaking may improve.
The Planning Hierarchy needs to accommodate these developments. Because Projects, Goals, and Tasks serve different purposes, we can make adjustments at the level where they are needed without necessarily reconsidering everything else.
Sometimes the intended outcome remains appropriate, but the actions necessary to achieve it need to change.
Suppose we discover that the original irrigation design will not work with the garden’s layout. We may need different materials, a revised arrangement of tubing, or another connection to the water supply.
These changes affect the Tasks required to complete the work, but they do not necessarily change the Goal. We still intend to establish a functioning irrigation system.
Separating the outcome from its supporting actions allows us to reconsider how we accomplish something without automatically abandoning what we intended to achieve.
Other circumstances may require us to reconsider the intended outcome itself. A Goal may become impractical, unnecessary, or inconsistent with our available resources. Sometimes the larger Project must also be reconsidered.
Suppose the vegetable garden proves too large for the available space or the time we can reasonably devote to maintaining it. We may decide to construct fewer planting beds, reduce the planting area, or change the irrigation requirements.
These decisions may affect individual Goals while leaving the larger Project intact. If circumstances make the garden itself inappropriate, we may need to reconsider whether the Project should continue.
A problem with one Task does not necessarily invalidate its Goal, and a change to one Goal does not automatically mean the entire Project should be abandoned. Understanding the differences allows us to adjust the work at the appropriate level.
Regular Reviews give us opportunities to examine our commitments using the information we have now rather than relying entirely upon the assumptions made when we first established them.
The Daily Review helps us prepare immediate work for Execution. The Weekly Review examines the broader Planning System, allowing us to recognize completed work, identify stalled commitments, and determine which actions deserve attention in the coming week. Longer-term Reviews provide opportunities to reconsider our larger direction and the commitments supporting it.
When work becomes stalled or uncertain, the Middle-Way Method provides additional mechanisms for examining the situation. The Stalled Decision Framework helps us address decisions that prevent progress, while Keep, Cut, Change allows us to consider whether a commitment should continue, be removed, or be revised.
These practices help keep the Planning Hierarchy connected to our actual circumstances. We can recognize when Tasks need to change, when Goals no longer serve their intended purpose, or when Projects should be reconsidered.
Maintaining the hierarchy involves more than checking off completed Tasks. It means keeping our understanding of the work current, preserving useful relationships between commitments, and ensuring that the actions we intend to perform still support outcomes worth pursuing.
The Planning Hierarchy connects the direction established through the Personal Compass, Mission Statement, and Vision Statement with the work required to accomplish our intentions. Projects organize larger undertakings, Defined Goals identify meaningful outcomes, and Tasks describe the individual actions we can perform to achieve them.
Although these levels normally follow a progression from Projects through Goals to Tasks, not every commitment requires the complete structure. Goals may stand independently, Tasks may exist without belonging to a larger commitment, and Projects may contain direct Tasks when appropriate. The arrangement should reflect the work involved rather than require us to create organizational levels that serve no useful purpose.
Using the hierarchy effectively also requires judgment. We need to distinguish larger undertakings from individual outcomes, recognize how commitments relate to one another, and reconsider their classification when our understanding changes. Alignment Checks, Filters, and regular Reviews help us evaluate whether those commitments remain appropriate and whether the actions supporting them are still useful.
The Planning Hierarchy connects purpose with action while allowing our plans to develop as circumstances change. With this structure established, we can turn our attention to another part of the Middle-Way Method: Reflection and Journaling. These practices help us examine our experiences, understand what we learn through action, and use that knowledge to make better decisions about the work ahead.