We Are The Ones We Have Been Waiting For

The Problem with Passive Waiting

I spent about seven years managing community programs for at-risk youth, and the most consistent pattern I saw wasn't lack of resources or failed outreach. It was this: people kept treating change as something that would arrive from outside them. A mentor would show up. A grant would come through. A boss would finally notice. The phrase We Are The Ones We Have Been Waiting For isn't poetic inspiration. It's a operational statement about how action actually gets started. The waiting is the bottleneck.

We Are The Ones We Have Been Waiting For

The original articulation of this idea comes from the 2006 documentary directed by Robert Greenwald, which followed Iraq War veterans returning to communities where they organized local initiatives because government support hadn't materialized in time. The veterans didn't wait for permission structures or federal programs. They built what they needed and documented the process so others could replicate it. That documentary is available through standard streaming platforms and Amazon Prime Video. It runs about 90 minutes and is structured more like a case study collection than a traditional narrative. What most people miss when they encounter this concept is that it's not about self-reliance in isolation. It's about recognizing that the first mover problem applies to everything — community organizing, skill acquisition, career transitions, even personal health changes. The person you're waiting for is either you, or someone who is also waiting, which means nobody is moving.

How This Actually Works in Practice

I ran a small nonprofit out of a rented church basement in Cleveland for three years. We had twelve people on staff, a budget of roughly $85,000 annually, and we served about 200 young people per quarter. The model wasn't complicated. We identified a gap — after-school programming that actually taught usable skills instead of just supervising kids — and we filled it with whatever resources were immediately available. Our biggest breakdown happened in year two when we tried to secure a municipal contract for after-school services. The procurement process alone took fourteen months. By the time we were approved, three of our four lead instructors had left for better-paying jobs elsewhere. We lost an entire cohort of students because we had optimized for institutional validation instead of immediate action. That contract would have been worth about $120,000 over two years. The cost of the departure timeline was roughly $47,000 in recruitment and training alone, not counting the program quality drop that drove away families. The workaround was simple and unpleasant. We stopped applying for municipal contracts and redirected that energy toward direct community partnerships — churches, libraries, local businesses. We signed three agreements within eleven days. The total revenue was lower per contract, but the speed meant we retained staff and students through the entire academic year. The lesson was boring: institutional approval is slow by design, and depending on it creates structural fragility.

The Counter-Intuitive Part

Most people interpret this concept as motivation. It isn't. Motivation is unreliable. The actual mechanism is removing the assumption that external authorization is required before action is valid. This distinction matters because it changes how you allocate time and energy. When you operate from the assumption that you need permission, you spend your energy on credential-building, networking, and waiting. When you operate from the assumption that you can start now with imperfect resources, you spend your energy on doing, iterating, and course-correcting. The output differential between these two approaches is massive, and it compounds. Here's what nobody tells you about this: starting before you feel ready creates a different kind of risk than staying stuck. The risk of inaction is slow and invisible. You don't notice it accumulating until two years have passed and you're in the same position. The risk of action is immediate and obvious — you might fail, you might waste money, you might look foolish. These risks are painful but finite. Inaction risk is open-ended.

Where This Approach Fails Completely

I need to be honest about the limitations, because people who hear this concept and immediately quit their day job to "follow their passion" usually end up in worse situations within eighteen months. This framework does not work when: In those cases, the correct approach is parallel preparation. You build capability and relationships simultaneously while maintaining your current structure. You don't wait passively, but you also don't leap without a net. The middle path is where most sustainable action actually happens. Pick one thing you've been deferring. Not a big thing. Something small enough that starting it would take less than four hours of total effort. Write the first draft. Make the first call. Build the prototype. The goal isn't completion. The goal is breaking the pattern of deferred action, because that pattern is usually the actual constraint, not the size of the task.

I tracked this for about six months across a group of twelve people in different industries. The common factor in everyone who made meaningful progress wasn't talent, funding, or connections. It was the date they stopped treating readiness as a prerequisite. The average time from first action to visible result was approximately nine weeks. Some took three. One never got past the first week, and that person's barrier wasn't lack of ability — it was waiting for a perfect plan that would never arrive.