In the world of workforce development, we are often defined by our metrics. We focus on placement rates, retention statistics, and credential attainment. These numbers are vital; they are the language we use to communicate our efficacy to funders and stakeholders. However, after years of operating a youth workforce program in Delaware, I learned that while data measures success, it rarely creates it. Success is created in the messy, beautiful, and often slow-building space between people.
Years ago, we created and operated a youth workforce program called HYPE (Helping Youth Pursue Excellence). We served a specific population: 100 percent of our youth lived in poverty, and 100 percent faced significant barriers to academic and career success. These were young people who had been written off, failed by systems, and had every reason to be skeptical of yet another program promising to change their lives. Programs like HYPE reflect many of the same principles that drive successful earn-and-learn models, where relationships, mentorship, and real-world experience shape outcomes just as much as technical training.
Before we even won the RFP to operate in Delaware, we made a strategic decision. We committed to operating under two core philosophies that would guide every interaction, every policy, and every crisis:
1. “Kids are not committed to programs; kids are committed to people.”
2. “A student with a dream is a student with a future; however, that dream is fueled by a caring adult who believes in it.”
These were not just nice sentiments to hang on a poster. They became the guardrails for our entire operation. And they were put to the test immediately by a young man named Korey.
Korey came into our program failing academically. He was making poor choices, and he carried a palpable distrust of any adult who tried to get close to him. He was the kind of case that makes skeptics shake their heads. Most people in the community thought we were wasting our time, that some kids were simply beyond help.
But we had our blueprint. We knew that if we led with programming—forcing him into workshops or job placements before addressing the relational gap—we would lose him. So, we created a relationship-focused plan of action. It took months. For months, we showed up. We built trust slowly, brick by brick, without demanding immediate results in return. We introduced him to community stakeholders who treated him with respect, not pity. We brought in partners who saw his potential, not his file.
