There is something reassuring about being able to point to a result.
A problem has been identified, an action has been taken, and a visible improvement can be presented to others. In the early days of a new role, a major initiative, or a change in leadership, this reassurance can be especially valuable. People want to see movement. Stakeholders want evidence that their confidence was justified. The person responsible wants to establish credibility. None of this is unreasonable. The difficulty begins when the need to demonstrate progress starts determining what progress is worth pursuing.
I have often wondered why organizations become so attracted to low-hanging fruit, even when the stakes are high and the problems they face are considerably more complex. The phrase itself sounds sensible. Why would we make things harder than they need to be? Why not begin with what is readily achievable, build momentum, and use early success to create the conditions for more ambitious work? There is sound logic in this approach. Yet somewhere between identifying an opportunity and deciding that it deserves our attention, a useful principle can become a rather convenient excuse for avoiding the harder questions.
What makes an initiative low-hanging fruit? Is it genuinely valuable and relatively easy to accomplish, or is it simply easy to accomplish? The distinction appears small, but it can determine the direction of an entire organization. When we assess an opportunity primarily through the lens of immediate feasibility, we are already narrowing our field of vision. We begin to favour what can be done quickly over what needs to be understood deeply, and what can be demonstrated easily over what might make a meaningful difference over time.
I think this is where the psychology of early wins becomes particularly interesting. A visible result provides reassurance not only to stakeholders but also to the people delivering it. It creates a sense of control in situations where uncertainty may otherwise be uncomfortable. A new leader can show that things are happening. A team can point to completed tasks. A board can see evidence of activity. In a relatively short period, everyone has something tangible to discuss. The result may be perfectly legitimate, but the satisfaction it produces can sometimes be disproportionate to the value it creates.
There is also a human incentive at work. We live and work in environments where people are frequently judged on what they can demonstrate. It is easier to explain a completed initiative than to describe the careful investigation that revealed an initiative was unnecessary. It is easier to present a new system than to explain why existing processes, incentives, or responsibilities need to change. It is easier to show a list of accomplishments than to make the case for work that may take months to produce a discernible outcome. The visible is rewarded more readily than the consequential, even when the latter is what the organization most needs.
This is not necessarily a failure of character. Often, it is a consequence of the environment in which people operate. Leaders face expectations, timelines, scrutiny, and pressure to establish credibility. Teams want to demonstrate competence. Stakeholders want confidence that their resources are being used well. When these expectations are not balanced by a serious commitment to understanding the problem, people can gravitate towards the work that is easiest to explain and defend. The organization may appear to be making progress while quietly becoming less attentive to the things that matter most.
What concerns me even more is how little analysis can sometimes go into deciding what qualifies as low-hanging fruit in the first place. We may identify an obvious inefficiency without asking why it exists. We may hear from the people who own a process without speaking to the people who depend on it. We may select a technology because its capabilities are immediately apparent, before examining whether the underlying process should exist in its current form. We may reach a conclusion after one meeting when the people closest to the problem have spent years living with its consequences.
In these situations, the apparent simplicity of the solution can be a reflection of the limited depth of our inquiry. We have not necessarily discovered that the problem is simple. We may simply have stopped looking before its complexity became apparent.
My experience in technology, entrepreneurship, and social-purpose organizations has taught me to be cautious about this distinction. A problem that appears to be about a tool may actually be about an unclear decision, a poorly designed process, or an absence of ownership. What looks like a performance issue may have more to do with competing priorities or a system that makes good performance unnecessarily difficult. And what appears to be an opportunity to save time may turn out to be an opportunity to reconsider why the work is being done at all.
The temptation is to begin with the solution because solutions create momentum. Questions, by comparison, can make progress look slow. Yet a little patience at the beginning can prevent a great deal of unnecessary effort later. Before deciding what to improve, we need to understand what is happening, why it is happening, whom it affects, and what a meaningful improvement would look like. This requires more than consulting a few stakeholders or reviewing a process document. It requires enough curiosity to challenge our first interpretation and enough humility to accept that the most obvious answer may not be the right one.
I believe this is one of the quiet responsibilities of leadership: to protect the quality of the inquiry, especially when there is pressure to produce an answer.
That responsibility becomes more important when organizations begin introducing artificial intelligence, automation, and other technologies in the hope of becoming more efficient. A process that is poorly understood can be automated with remarkable speed. A redundant activity can be completed more efficiently without anyone asking whether it should continue. A flawed decision can be made faster and at greater scale. The technology may work exactly as intended, while the organization remains no better off.
The same principle applies well beyond technology. A new reporting structure can make accountability appear clearer without resolving conflicting responsibilities. A revised policy can address a visible symptom while leaving the underlying incentive untouched. A new program can attract attention and participation without addressing the need it was intended to meet. In each case, the organization has produced something that can be shown to others. Whether it has improved the situation is a separate question.
This is why I would contend that the quality of an early win depends less on how quickly it is delivered than on how intelligently it has been chosen. A quick improvement can be immensely valuable when it emerges from a sound understanding of the problem, addresses a genuine need, and helps create the conditions for further progress. It can build trust, free up resources, and demonstrate that thoughtful action produces results. There is no virtue in making work unnecessarily difficult or delaying useful improvements in pursuit of perfect information.
But an early win should earn its place within a larger intention. It should be connected to an outcome that matters, rather than serving primarily as evidence of activity. Its value should survive the presentation in which it is announced and the meeting in which it is celebrated. If the improvement were never mentioned publicly, would it still be worth doing? That is a question worth asking, particularly when the principal beneficiaries of an initiative are the people who get to report its success.
I also think we need to reconsider what we mean by momentum. We tend to associate momentum with the visible accumulation of completed work. Yet there is another kind of momentum that develops when an organization becomes more capable of understanding itself. A team learns to identify root causes rather than treating symptoms. People become more willing to question assumptions before committing resources. Decisions improve because those affected by them are involved early enough to shape them. Over time, less effort is wasted on work that should never have been undertaken.
This kind of progress is harder to display on a slide. It may not provide the immediate satisfaction of announcing a completed initiative. Nevertheless, it can change the quality of everything an organization does thereafter. The ability to ask better questions, make clearer decisions, and direct effort towards consequential work is itself an organizational asset. It compounds quietly, often becoming most visible in the problems the organization no longer has to solve.
There is a further cost to choosing easy wins too casually: the opportunity cost of the work left unattended. Every initiative consumes some combination of people’s attention, time, trust, and organizational capacity. Even a relatively inexpensive project can impose a significant burden if it requires repeated meetings, changes in behaviour, additional reporting, or ongoing maintenance. When we fill an organization’s limited capacity with convenient improvements, we may leave too little room for the more difficult work that would have produced a greater return. The cost is not always what we spend on the initiative. It is what we can no longer give our attention to because the initiative is there.
This is particularly relevant in organizations whose purpose extends beyond their own performance. In social-purpose work, for example, it is possible to become very good at administering programs, improving internal processes, and reporting activities while losing sight of the people those activities are meant to serve. Operational discipline matters enormously. Good intentions do not excuse waste, and efficient systems can release resources for the mission. But efficiency has to remain in service of purpose. Otherwise, we risk perfecting the machinery while becoming less attentive to what the machinery exists to accomplish.
Perhaps this is where a more useful distinction emerges. We should not divide opportunities into those that are easy and those that are difficult. We should distinguish between opportunities that are easy because we understand them well and opportunities that appear easy because we have not yet understood them sufficiently. The former deserve attention. The latter deserve investigation.
The distinction also asks something of stakeholders. If we expect leaders to make sound decisions, we must give them room to do the work that precedes visible results. We should be willing to hear that an apparent opportunity is less important than it first seemed, that a familiar process needs to be reconsidered, or that the most responsible first step is to spend time understanding the problem. Patience should not become an excuse for inaction, but urgency should not become an excuse for shallow thinking either. Both have their place, and good judgment lies in knowing which the situation requires.
I have come to appreciate that meaningful progress often begins with a moment that does not look particularly impressive. Someone asks a question that unsettles an accepted assumption. A team pauses long enough to hear from the people who have been working around a broken process. A leader resists the pressure to announce a solution before the problem is understood. Resources are redirected from an attractive initiative towards a less visible need. Nothing dramatic may happen in that moment, but the quality of what follows can be fundamentally different.
There is a kind of discipline in being willing to look beyond what is immediately available. It requires us to separate our desire to be seen making progress from our responsibility to make progress that matters. It also requires us to accept that the best contribution a leader can make in the early stages of an initiative may be to improve the question, rather than accelerate the answer.
Low-hanging fruit will always have its place. The danger lies in allowing convenience to become a measure of importance and visibility to become a substitute for value. When that happens, we can spend an extraordinary amount of energy demonstrating that we are moving forward without ever becoming certain that we are moving in the right direction.
The real test of leadership is not how quickly we can find something to do. It is whether we have taken the time to understand what is worth doing, and whether we have the resolve to pursue it even when the result takes longer to show.
Sometimes the most valuable early win is not an accomplishment at all. It is the decision to stop looking for one long enough to discover what would actually make a difference.
