The Problem with Rushing to the Right Solution
- Feb 27
- 6 min read
In the social impact space, we care deeply about solutions.
Programmes. Frameworks. Toolkits. Pilots. Scaling plans.
They give us direction. They give us legitimacy. They give us something tangible to build around, something teams can rally behind, partners can support, and reports can confidently describe.
And yet, many of us have also experienced moments like this:
A project that looks strong on paper but feels different in practice. An intervention that technically “works,” but doesn’t quite shift the deeper reality it hoped to influence.
This is not about poor design or lack of commitment. Most practitioners are working with immense dedication, navigating pressure, timelines, funding cycles, and expectations that rarely leave much room for uncertainty.
Perhaps what feels uncomfortable in these moments is not failure itself.
Perhaps it is the invitation to slow down, just long enough to more fully understand what we are intervening in.
Many of us are here because we care enough to reflect, to learn, and to try again. Not to assign blame, but to sharpen our judgment and deepen our understanding.
This piece is simply an invitation to spend some time in that space.
What Are We Really Solving For?
Before asking how to intervene, or why something didn’t unfold as expected, it may help to pause here:
What are we actually solving for? And how do we know when it is truly being addressed?
Do we care about: Seeing our solution succeed?
Or about seeing the underlying problem meaningfully reduced, even if that requires reshaping, adapting, or even letting go of our initial idea?
Most of us enter this work because we care about people and outcomes. At the same time, we operate within structures that naturally encourage:
Programmes to continue
Organisations to grow
Credibility to remain intact
There is no criticism in naming this. It is simply a tension that many of us quietly navigate.
When Gayatri Vasudevan founded LabourNet in 2006, the intention was clear: to enable livelihoods in the informal sector through vocational training and job placements.
With years of experience in policy and labour issues, the model appeared strong, replicable, fundable, and persuasive on paper. Within the first two years, however, the organisation encountered a serious financial strain. It became evident that what seemed like a viable concept required deeper understanding in practice. Reflecting on that period, Gayatri has spoken about how experience and confidence can sometimes create the impression of clarity, even as realities on the ground unfold in unexpected ways.
Over time, this led to thoughtful course corrections: shifting focus from model to mission, from individual expertise to diverse teams, and from short-term success to longer, more patient pathways, including recognising that certain livelihood pathways may take years to stabilise.
The question that kept resurfacing was not whether the idea was good, but whether it remained aligned with the problem LabourNet was trying to address.
Source: Gayatri Vasudevan, “LabourNet: Course Corrections on the Journey to Scale,” Fail Loud! (SELCO Foundation, Impact Failure Platform, 2018).
Letting go of an approach we have invested in can feel deeply personal.
It can challenge our sense of identity and effort. That feeling is real. And yet, sometimes staying loyal to the problem means allowing our role within it to evolve.
Perhaps integrity in impact work is less about defending our ideas and more about remaining attentive to the problem itself.
When Solutions Move Faster Than Understanding
Most practitioners act because they care. Urgency is often a reflection of responsibility.
And yet, urgency can also move us forward before we have fully understood the terrain. A pattern many of us may recognise:
A solution is designed. A programme is rolled out. Momentum builds. Later, we realise that some important dimension of the problem was not fully explored.
In one instance, a solar-powered irrigation solution was introduced to address farmers’ unreliable access to energy.
The technology worked. It provided consistent power and reduced dependence on diesel or erratic grid supply.
Over time, however, it became clear that energy access was only one part of a much larger system. Water use patterns, crop cycles, maintenance responsibilities, market dynamics, and local incentives all shaped whether and how the solution was sustained. While the technology functioned, its place within the broader agricultural system was more complex than initially assumed.
This prompted a deeper reflection: was the goal to scale a solar irrigation solution or to reduce farmers’ vulnerability within a shifting and interconnected system?
Source: “When the Sun Doesn’t Shine: The Ups and Downs of Solar-Powered Irrigation,” Fail Loud! (SELCO Foundation, Impact Failure Platform).
Focusing on solutions can feel productive and energising. Turning our attention back to the problem can feel slower.
Often, what we uncover is not an implementation gap, but an understanding gap.
If we recognise ourselves here, it does not mean we have erred. It simply means we acted with the information available at the time.
Revisiting the problem is not a pause from the work. It is part of the work.
Why is Depth Difficult?
This is where gentle honesty helps.
Sometimes depth is difficult because:
Problems unfold slowly and don’t always offer visible progress for the communities involved or for those working alongside them.
Funding structures often require clarity and deliverables, leaving limited space to explore what is still uncertain.
As practitioners, we are often valued for decisiveness and expertise, and complexity can stretch those expectations.
Deep, systemic challenges are rarely owned by a single programme or organisation; they cut across mandates and identities.
None of these realities are flaws. They are features of the systems we operate within.
If we have leaned toward action over inquiry, it is understandable. Many of us have been shaped by environments that reward clarity, speed, and confidence.
The quieter question may simply be: is there space to hold both action and deeper inquiry?
In 2018, SELCO Foundation extended its solar energy–based livelihood solutions into agriculture, introducing solar-powered agri-processing units for turmeric farmers.
The intention was thoughtful: better machines and reliable energy could enable value addition and higher incomes.
In practice, the outcomes varied. While farmers were familiar with selling fresh turmeric, processed turmeric powder required new market linkages, networks, and demand patterns. Some units were underutilised, and there was limited clarity around break-even timelines.
The learning here was not about misalignment of intent. It was about recognising that a solution that worked in one livelihood context required a deeper understanding of the ecosystem when applied to another.
What initially appeared as underperformance turned out to be a reminder: each context carries its own market dynamics, incentives, and rhythms.
What may look like “failure” can sometimes be early certainty before the system has fully revealed itself.
Turning Towards the Problem
What if a shift does not mean stepping away from action, but stepping closer to understanding?
What might it look like to run alongside the problem, not just ahead with a solution?
It could mean:
Spending time where the problem is experienced, not only where plans are drafted.
Listening without immediately translating insights into interventions.
Asking, “What keeps this problem in place?” before asking, “How do we fix it?”
Progress here may be measured in clarity rather than output.
Stronger solutions often emerge not from sharper answers, but from more patient questions.
Depth might look
like
Understanding histories, incentives, power dynamics, and trade-offs.
Noticing who benefits from the status quo.
Recognising whose voices are absent.
A deeply understood problem may feel more complex, but it is often more grounded.
Instead of asking
What intervention works?
We might also ask:
What assumptions are we carrying into this work?
Who defines this as a problem, and who might see it differently?
Could this behaviour be rational within its context?
A Closing Reflection
As we continue our work, perhaps these reflections can accompany us:
What might change if understanding the problem were treated as an ongoing commitment, not just an initial step?
Where can we create space, individually or organisationally, to listen without immediately responding?
How might we recognise and value depth, learning, and honesty, even when they slow visible momentum?
What kind of practitioners do we want to be when clarity is still emerging?
Staying with the problem does not make us less effective. It can make us more grounded. And in a sector shaped by complexity, that grounding may be one of the most powerful contributions we can offer.
Comments