Most tasks are judged not by the effort invested, but by the outcome they produce. Yet, when we perform a task ourselves, our own effort is highly visible. We remember the time spent, the decisions made, and the obstacles overcome. Because we experience this effort directly, it is easy to mistake effort for completion. This tendency to evaluate our work by how much we did, rather than whether the intended outcome was achieved, is a common trap.
There are trees near my house, and their leaves constantly fall onto the terrace. My daily task is to sweep the terrace and place the leaves in a bin to keep the area clean. There are many ways to approach this, but consider two scenarios where this simple task can go wrong.
The Leaf Pile (Under-Delivery)
My action: I sweep the terrace cleanly but leave the leaves in a neat pile in the corner, intending to bin them later.
My perspective: I feel as though I have done a great job; after all, sweeping is 99% of the heavy lifting, and binning them is barely a task.
The outcome: Before I return, the wind and my pets scatter the leaves across the terrace again. The task is incomplete because the objective was not merely “to sweep”, but to clear the terrace.
The Costly Trim (Hidden Repercussions)
My action: I put the leaves in the bin and then take the initiative to trim the overhanging branches to prevent future leaves from falling.
My perspective: I see myself as a proactive problem-solver, thinking several steps ahead.
The outcome: Cleaning up the heavy, trimmed branches takes hours. In the process, a branch accidentally cracks a window. Later, I discover a neighbour agreement that prohibits anyone from cutting those trees—a constraint I was never told. The task remains incomplete because additional work is now required to rectify the damage.
While there are times when unexpected actions yield positive results, these scenarios usually create fresh problems because the actual outcomes tell a different story. From a requirements perspective, both scenarios represent incomplete tasks because both left behind more work to be done.
The point is not merely whether a task is finished; it is about awareness. Do I truly know what is required, and am I intentionally handling it differently? Conflict often arises because I fail to recognise the gap between my intent and the impact.
If I believe the task is complete after sweeping but before binning, I must recognise that a fundamental part remains unfinished.
If I believe the task is complete only after trimming the branches, I must realise that I have begun solving an entirely different problem from the one I was asked to solve.
Identifying the need for trimming may demonstrate initiative—a valuable quality—but initiative still requires alignment, discussion, and proper execution. When I focus primarily on the effort I believe I have invested rather than the outcome I have delivered, I fall victim to the Effort Illusion and risk habitually delivering incomplete work.
When someone critiques the scattered leaves or the broken window, they are looking at the impact of the work. Because I know how hard I worked, I feel as though my intent or character is being judged. Without awareness of this distinction, feedback feels like a personal attack. The discussion quickly becomes emotional: “I spent hours on this, and it is being dismissed,” versus, “The outcome is unfinished and has caused problems.” These moments of friction are draining and can easily damage morale.
True alignment is a two-way street. If a requirement is vaguely stated, it has failed to provide the necessary context. The real art of completing a task lies in first securing the agreed baseline requirement—ensuring the core need is met perfectly. Only once that foundation is solid should extra value be added, and even then, it must be done with a deliberate awareness of the consequences. A simple, proactive message bridges the gap entirely: “The terrace is swept, but I also noticed the branches are low. Should I look into trimming them?”
If you consider yourself as someone who often leaves tasks subtly incomplete, how do you build this awareness? The answer lies in paying attention to the exact moment you feel a task is “done”. Pause and ask yourself:
What additional effort—whether from me or someone else, now or in the future—is still required before the intended outcome is truly achieved?
Shifting your focus from how tired you are to the value you actually delivered is not just about doing a better job; it is about protecting your own peace of mind. When you align early and see the full picture, feedback stops feeling like an attack and becomes a collaborative tool for your growth.
Comments