Rethinking Poverty: From Charity to Real Change
- Celeste Carlson
- Feb 16
- 4 min read

Our Poverty Playbook Is Keeping People Poor
In the United States, we don’t just fight poverty—we often help people stay there. We make sure families can survive this month with food, blankets, and sometimes shelter, but we rarely design for what it would take for them to stop living in poverty altogether.
I see this tension every day in my own neighborhood, where most homes are rented, not owned. Landlords build equity; families build receipts. The one asset that has historically helped American families build wealth—homeownership—sits out of reach for many of my neighbors, even as nonprofits and churches work hard to “serve” them.
When We Count the Wrong Things
Kansas City is full of well‑intentioned people and churches running food pantries and other services. At the same time, we have a massive affordable housing gap and an education and workforce system that too often fails people with justice‑involved backgrounds.
In that context, it’s easy for nonprofits to default to counting what’s simple instead of what matters. I routinely see organizations of all sizes celebrating:
Number of meal boxes distributed
Number of classes offered
Number of people who “completed” a program
Those numbers are not meaningless—but they can become misleading when they’re treated as proof that we’re reducing poverty. We almost never ask the harder, truer questions:
Did anyone obtain a job—and keep it?
Did anyone move into decent, stable housing?
Did anyone pay off a car, secure legal documents, or build even a small emergency fund?
Are families less dependent on public assistance over time?
When we don’t track those kinds of outcomes, we leave ourselves with a dangerous illusion of progress.
Treating People in Poverty as Customers, Not Cases
One of the most important shifts I’ve seen is the idea of treating people in poverty as customers—primary users of a “product” whose insights should drive design—rather than cases to be managed or outputs to be counted.
To me, that means:
Their circumstances and voices are not side notes; they are the starting point.
We co‑design solutions with them, instead of asking them to fit into what we’ve always done.
We assume they are the experts on their own lives.
I see this in action at organizations like Youth Core Ministries, where the mission explicitly focuses on “wrapping around families to solve poverty,” not just running youth programs in isolation. That kind of language—and the practices behind it—signals a fundamentally different posture: people in poverty are contributors and decision‑makers, not passive recipients.
From Survival Stories to Design Thinking
Another powerful tool is design thinking. Instead of defending a program model because “this is how we’ve always done it,” design thinking invites us to:
Start with empathy, listening deeply to people living in poverty
Define the real problem from their perspective
Co‑create solutions, test them small, and iterate based on what actually works
Experiences like Essdack’s Poverty simulation make this painfully real for middle‑ and upper‑income participants. For one simulated month, they feel the stress, trade‑offs, and constant crisis management that families in poverty navigate every day. That kind of embodied understanding often opens people up to new ways of partnering, funding, and designing.
But simulations are just the start. The real test is whether boards and leadership teams are willing to run small, real‑world experiments that might challenge their current metrics, routines, or even funding strategies.
Dreaming Bigger About Outcomes
When I talk with nonprofit teams about outcomes, I hear two things:
Vanity metrics are easy to measure.
Dreaming big feels risky when funding is on the line.
Yet if we’re serious about helping people move out of poverty—not just survive it—we have to name and measure outcomes like:
Obtaining and keeping a job over time
Securing safe, decent housing
Building a savings cushion and reducing debt
Increasing income and reducing reliance on public assistance
Strengthening community and support networks
These are not “nice to have” add‑ons; they are the real indicators that poverty is loosening its grip. Boards and funders need to see these on dashboards—not just in occasional success stories.
Where Change Starts
The current system is understandably obsessed with funding. Leaders feel pressure to show quick numbers, protect relationships with funders, and avoid anything that might look like failure.
That’s why I believe innovation has to start close to the ground—with the people and organizations who live this reality every day—and then move outward into community conversations, public policy, and funder behavior. It’s fair to challenge all three.
Change looks like:
Frontline nonprofits inviting people in poverty to co‑design programs and define success
Boards asking for outcome data that shows real life change, not just activity
Funders making room for learning, iteration, and longer time horizons
An Invitation to Nonprofit Leaders
If any part of this resonates—if you suspect your metrics are more about comfort than change—I’d love to talk.
I help nonprofit leaders and boards:
Rethink what they measure and why
Facilitate “dream sessions” about the impact they really want to have
Design governance and learning practices that support customer‑centered, outcome‑driven work
If this sparked something for you, tell me: what’s one metric you’d like to track but aren’t yet? Share in the comments so we can learn from each other. If you’re ready for a conversation about moving from counting outputs to changing lives, send me a message—or, if you want help rethinking your outcomes or engaging your board differently, you’re welcome to book a complementary consult with me here.
Let’s build the kind of metrics—and the kind of community partnerships—that actually help people get out of poverty, not just survive it.
#NonprofitLeadership, #PovertySolutions, #OutcomesNotOutputs, #DesignThinking, #CustomerFirst, #SocialImpact, #KCNonprofits, #BoardGovernance, #ImpactMeasurement, #SystemsChange



Comments