Inspiration can come at any time. One evening, Jessica Jackley went to hear Mohammed Yunus, founder of the Grameen Bank and modern microfinance, who was giving a talk at her business school. He spoke about the power of microcredit to change lives and help people with little money but big hopes become entrepreneurs. Excited by what she heard and inspired by his stories, she stayed around to ask him questions. Yunus’s respectful framing of the poor as capable entrepreneurs compelled her to act. “It really changed the way I saw so many things… So, a few weeks later I quit my job and was in East Africa to learn about this microfinance thing myself.”
She took an internship with Village Enterprise, a non-profit microlending organization. They supported people starting their own small businesses in Kenya, Uganda, and Tanzania. She interviewed these micro-entrepreneurs and witnessed firsthand how simple resources, even a $100 grant, could change lives. Their small businesses enable people to sleep on real mattresses, eat better, and send their children to school. Her three-month internship forged her conviction that entrepreneurship is often a way out of poverty. This perspective shaped the mission of the microfinance organization she co-founded on her return. Kiva lent money to people with ideas and ambition. When these entrepreneurs repaid their loans, Kiva would recycle the funds to new entrepreneurs. Talking shop with entrepreneurs over coffee or at their business sites, Jessica tested and improved her idea.
Define the Problem Clearly
A social enterprise begins with a clear problem statement. Without one, it’s easy to drift toward building “solutions in search of a problem.” A simple way to sharpen your focus is with a Needs Statement template like this:
When [condition], [client] needs a way to [goal].
For example: When small-scale organic farmers face a pest infestation, they need a way to protect their crops without chemical pesticides so they can grow certifiable organic food safely.
This brief statement puts boundaries around your idea. It forces you to specify who you’re helping, under what circumstances, and what outcome they need. It doesn’t describe your solution. That comes later. Right now, the goal is clarity.
Linking Design Thinking for Social Impact (DT4SI)
This problem-statement step connects directly to the Define phase of the Design Thinking for Social Impact model I outlined in Design Thinking: A Guide to Innovation. The process is not linear. You’ll move back and forth between Empathy (listening, observing, interviewing) and Notice & Reflect (your own motives, the community’s response) as you refine the problem.
This cycle helps you avoid two common traps: (1) seeing yourself as a rescuer instead of a partner, and (2) jumping too quickly to solutions before you’ve truly understood the challenge. Staying in the Empathy ↔ Define loop ensures your idea grows from the community’s actual needs and your authentic commitment.
Tools for Early Testing
So how do you “test drive” your ideas in practice? Start small and simple.
- Interviews: Talk to potential clients, partners, or beneficiaries. Ask open-ended questions: What’s hard about this situation? What’s already working for others? What would make life easier?
- Observation: Watch how people currently solve the problem. Where do you see workarounds or frustration?
- Focus Group: Bring a small group together and ask them to react to your problem statement. Do they agree? What are you missing? Facilitate a good discussion and encourage interaction among the participants.
- Design Journal: Keep a written record of what you’re hearing and noticing, such as conversations, quotes, surprising details. Your journal becomes both a memory aid and a source of insights later.
Each of these tools costs little more than time, but the payoff is huge. You’ll soon learn whether your idea resonates with the community or if it needs reshaping.
Closing: Your Turn
Every strong social enterprise begins with listening. You don’t need a polished plan or big budget to get started. You just need curiosity and the courage to test-drive your idea, along with respect for your community partners.
Here’s a simple next action step: Write one problem statement using the Needs Statement template above. Put it in your design journal. Then share it with a few people in your community and ask, Does this sound right? What’s missing?
You’ll be amazed at what you learn when you get community input.
I’d love to hear what you discover. Send me your problem statement or a reflection on your test drive at Fred3Estes@gmail.com. With your permission, we may share some of them in future posts.