Bottom-Up Execution: Staying Effective in Everyday Life

One thing to decide before publishing: the image. I left Stepping-Stone.jpg as the template placeholder. If each article gets its own image, that’s the only front-matter field I’d consider unfinished.

Last week, we explored Top-Down Execution, beginning with the direction established by our Mission Statement and Vision Statement and carrying that direction through Projects, Defined Goals, Tasks, and ultimately action. This allows the work we do today to create meaningful progress toward who we want to become and what we want to accomplish. But Top-Down Execution accounts for only one direction from which work enters our lives.

Not all necessary work comes from our priorities. Responsibilities need attention, commitments need to be fulfilled, things need to be maintained, and circumstances create demands that may have little or nothing to do with our Mission Statement or Vision Statement. Some of this work is predictable, while other work appears unexpectedly. Either way, it can legitimately require our attention.

This work enters Execution from the Bottom-Up. What makes something Bottom-Up is not whether it is mundane, unplanned, urgent, or less important. It is Bottom-Up because it does not originate from the direction established by our Mission Statement and Vision Statement. Where that boundary falls will be different for each of us because the Mission and Vision that establish our Top-Down direction are themselves personal.

Bottom-Up Execution gives us a way to recognize and handle work that comes from outside that direction without pretending that everything we do must advance our Mission or Vision. Like Top-Down Execution, however, it must operate within the limits of our available time, attention, energy, and resources. To understand this second direction, we first need to recognize why necessary work does not always come from the priorities we have deliberately established.

Not All Necessary Work Comes From Our Priorities

Our Mission Statement and Vision Statement establish direction. They help us decide what we are working toward and provide a basis for creating the Projects, Defined Goals, and Tasks that move us in that direction. Top-Down Execution carries those priorities toward action, but our priorities are not the only source of work that legitimately requires our attention.

Everyday life continually presents responsibilities, commitments, maintenance, and changing circumstances that need to be handled. Some are recurring and predictable enough to plan for well in advance. Others emerge as circumstances change. Their importance does not depend upon whether they can be traced back through our Planning System to something we deliberately chose to pursue.

Work Also Comes From Present Reality

Plans begin with decisions about what we intend to do, but Execution takes place within the reality that already surrounds us. Existing responsibilities continue to make demands upon our time. Commitments made to other people still need to be fulfilled. Things we depend upon require maintenance. New information and changing circumstances can create work that did not exist when our plans were made.

This work can be just as real as the work generated by our Mission Statement and Vision Statement. The difference is its origin. Rather than beginning with the direction we have established and moving downward toward action, it begins with something in our present reality that requires a response and enters the Planning System from the Bottom-Up.

Bottom-Up work begins with present reality rather than the direction established by Mission and Vision.

Necessary Does Not Mean Top-Down

It can be tempting to connect every worthwhile action back to our Mission Statement or Vision Statement. Doing so makes the Planning Hierarchy appear neatly aligned, but it also creates connections that may not actually exist. Some things need to be done simply because they are part of the life we are currently responsible for managing.

Recognizing this does not make Bottom-Up work less important than Top-Down work. It allows each kind of work to be understood according to where it actually comes from. Mission and Vision provide direction for the life we are trying to build, while Bottom-Up Execution recognizes that we must also remain effective within the life we already have.

Mission and Vision Help Define the Boundary

Bottom-Up Execution becomes easier to understand once we are clear about what makes work Top-Down. Our Personal Compass helps us develop our Mission Statement and Vision Statement by identifying the Values, Roles, and Relationships that matter to us. Mission and Vision then establish the direction we use to determine what we are working toward.

That direction gives us a reference point. When work originates from our Mission Statement and Vision Statement, it enters Execution from the Top-Down. When necessary work does not originate from that direction, it enters from the Bottom-Up. We do not need a separate list of activities that qualify as Bottom-Up because the distinction comes from where the work originates.

Start by Identifying What Is Top-Down

The simplest way to recognize Bottom-Up work is to first ask whether the work originates from our Mission Statement and Vision Statement. If it does, it is Top-Down. Projects, Defined Goals, and Tasks can then translate that direction into action at whatever level of the Planning Hierarchy is appropriate.

If necessary work does not originate there, it is Bottom-Up. It may still be important. It may even require more immediate attention than something that originated Top-Down. None of that changes its origin.

If necessary work does not originate Top-Down, it enters Execution from the Bottom-Up.

This distinction also keeps us from creating artificial connections simply to make everything appear aligned. Mission and Vision do not need to justify every action we take. They establish our Top-Down direction, which in turn allows us to recognize the work coming from somewhere else.

The Boundary Is Personal

Because our Mission Statement and Vision Statement are personal, the boundary between Top-Down and Bottom-Up is personal as well. We cannot create a universal list declaring particular kinds of work Top-Down or Bottom-Up. What originates from one person’s Mission and Vision may not originate from another person’s.

The important question is not what kind of work we are considering, but where that work originates for us. Returning to our Mission Statement and Vision Statement gives us the lens needed to make that distinction without assigning greater or lesser value to either direction.

Do not try to make an activity Top-Down or Bottom-Up based on the kind of work it is. Look at where it originates within your own Mission and Vision.

Bottom-Up Work Enters the Same Planning System

Top-Down and Bottom-Up describe where work originates, not separate systems for managing it. Once we determine that something needs to be done, it enters the same Planning System we already use to organize our commitments and move them toward action. We do not need one system for the direction established by Mission and Vision and another for the responsibilities and realities that enter from the Bottom-Up.

Bottom-Up work can vary just as much in size and complexity as Top-Down work. Some things require a single clear Task. Others require an outcome that needs several Tasks to complete. Larger or more complex work may need to be organized as a Project containing one or more Defined Goals. The Planning Hierarchy gives us the structure needed to manage the work regardless of where it originated.

Enter at the Level the Work Requires

Not every piece of work needs to begin as a Project. If something can be handled with a single Task, creating a Project and Defined Goal above it only adds unnecessary structure. If several Tasks are required to reach a clear outcome, a Defined Goal may be appropriate. When the work contains multiple outcomes or enough complexity to require additional organization, it may belong within a Project.

The work therefore enters the Planning Hierarchy at the level it actually requires:

• Project
• Defined Goal
• Task

A Project is a defined group of related outcomes. A Defined Goal describes a desired outcome that requires more than one Task to complete. A Task is a single concrete action that can be completed in one sitting.

Bottom-Up work does not need to pass through every level of the Planning Hierarchy. It only needs enough structure to organize the work and move it toward action.

Enter the work at the level it requires. Do not create a Project or Defined Goal when a Task is enough.

Origin Does Not Change the Planning System

Once work enters the Planning System, its origin does not change how the Components themselves work. A Project remains a Project, a Defined Goal remains a Defined Goal, and a Task remains a Task. Each should still be clear enough to serve its purpose within the Planning Hierarchy and help move the work toward action.

Top-Down and Bottom-Up work can exist within the same system without becoming the same kind of work. We can retain an understanding of where a commitment came from while using the same Components to organize and execute it.

The important distinction remains at the point of origin. Top-Down work begins with the direction established by Mission and Vision. Bottom-Up work begins elsewhere in the realities and responsibilities of everyday life. Once either becomes work we intend to do, both move toward action through the same Planning System.

Bottom-Up Execution Keeps Everyday Life Working

Top-Down Execution creates progress toward the direction established by our Mission Statement and Vision Statement. Bottom-Up Execution serves a different purpose. Much of the work entering from the Bottom-Up exists because something in our present reality needs attention. Completing that work may not move us closer to a Defined Goal or produce an obvious change in direction, but it can still be necessary for remaining effective.

Responsibilities continue whether or not they contribute directly to our Mission and Vision. Commitments still need to be fulfilled, and the things we rely upon need to be maintained. Handling this work allows us to meet the demands of the life we already have while continuing to pursue the direction we have chosen.

Maintenance Is Legitimate Execution

Progress usually leaves something visibly different than it was before. A Project advances, a Defined Goal is completed, or something we have deliberately chosen to pursue moves closer to completion. Maintenance often produces a less visible result because its purpose is to preserve something that is already working.

That does not make maintenance a failure to progress. Some things need regular attention precisely so they can continue serving their purpose. Completing that work may leave us in much the same place we started, but maintaining a necessary condition can be the intended result.

Some responsibilities and commitments need to be handled simply because they are legitimate parts of our present reality. Their value does not depend upon finding a way to connect them to Mission and Vision. Bottom-Up Execution allows us to recognize that work for what it is and handle it accordingly.

Maintaining something that needs to keep working can be a successful result even when nothing appears to move forward.

Effectiveness Includes Handling the Life We Already Have

Mission and Vision help us determine where we are going, but we do not begin that journey with an empty schedule, unlimited resources, or freedom from existing responsibilities. Execution takes place within a life that is already in motion. Moving toward the future we want therefore occurs alongside the work required by the present.

Remaining effective means handling both. We need to make progress toward the direction we have established, while also handling work that legitimately requires our attention for other reasons. Neither kind of work becomes more legitimate simply because of where it originates.

Bottom-Up Execution gives that second source of work a place within the methodology. It recognizes that some Execution moves us toward something new, while other Execution allows us to continue functioning effectively where we are.

Bottom-Up Execution Has Limits

Recognizing Bottom-Up work does not mean that everything entering from the Bottom-Up can or should immediately become action. New information, requests, responsibilities, and changing circumstances may all require consideration, but allowing each new demand to determine what we do next would replace deliberate Execution with reaction.

Both Top-Down and Bottom-Up Execution operate within limits on our:

• Time
• Attention
• Energy
• Resources

These limits apply regardless of where work originates. Something can legitimately need to be done without needing to be done immediately, and recognizing a demand does not automatically create the capacity to act upon it.

Something requiring attention does not necessarily mean it requires action right now.

Mission and Vision can create opportunities for meaningful progress, while present reality can create legitimate responsibilities and demands. Understanding both directions gives us the foundation we need to consider how they can work together without allowing either one to dominate.

Bottom-Up Is the Other Direction of Execution

Top-Down and Bottom-Up Execution begin from different places, but both ultimately lead toward action. Top-Down Execution begins with the direction established by our Mission Statement and Vision Statement. Bottom-Up Execution begins with the work that does not originate from that direction. Together, they account for the two directions from which work enters our Planning System.

Neither direction makes the other unnecessary. Focusing only on Top-Down Execution can leave legitimate responsibilities and present realities unattended. Focusing only on Bottom-Up Execution can leave us responding to what needs attention without making deliberate progress toward the direction we have established. Effective Execution needs to account for both.

Understanding Bottom-Up Execution gives us the second half of the problem. We now have meaningful progress entering from the Top-Down and work entering from the Bottom-Up, both drawing upon the same limited capacity for Execution. The next step is finding the Middle Way between them.

Summary

Bottom-Up Execution handles work that does not originate from the direction established by our Mission Statement and Vision Statement. Responsibilities, commitments, maintenance, and changing circumstances can all require our attention without needing to be connected artificially to the priorities we have established. This work is not less legitimate because it enters Execution from a different direction.

Mission and Vision help us recognize that distinction. Work that originates from the direction they establish enters from the Top-Down. Necessary work that does not originate there enters from the Bottom-Up. Because our Mission and Vision are personal, where that boundary falls will be personal as well.

Once we determine that Bottom-Up work needs to be done, it enters the same Planning System as Top-Down work. Depending on what the work requires, it may become a Project, Defined Goal, or Task and move toward action from there. Bottom-Up Execution does not require a separate system; it gives work from present reality a place within the system we already use.

Execution therefore has to account for work entering from both directions while operating within the same limited time, attention, energy, and resources. Top-Down Execution moves us toward the direction we have established, while Bottom-Up Execution helps us remain effective within the life we already have. Understanding both directions prepares us to consider how to find the appropriate balance between them.

Bottom-Up Execution keeps life working well enough for meaningful progress to remain possible.