Need-to-Solution Adaptation Loop
Turn a community's urgent need into a focused solution quickly
- Difficulty
- Moderate
- Time to result
- ~weeks to results
- Steps
- 5
- Confidence
- 94%
The Need-to-Solution Adaptation Loop treats the organization as a responsive vehicle rather than a fixed bundle of programs. Listen for a concrete barrier raised by someone in the community, clarify what prevents progress, and decide whether the organization should build a solution itself or press industry partners to act. Once the need is selected, hyperfocus the team and ship the smallest useful response quickly. Rogelio illustrates the loop with a request for Spanish NMLS preparation: his team accepted the idea and developed a course in about 30 days. He also describes using persistent advocacy and an economic article to push lenders toward ITIN products and Spanish-language access. The output changes as needs change, but people development remains the mission anchor.
Origin
Rogelio Goertzen II explained that HOME stays fluid and adapts to industry needs. He illustrated the approach with Spanish NMLS training, ITIN lending advocacy, and language-access work.
Core principles
- 01The organization's form should follow the community's current need
- 02Frontline requests are signals for what to build next
- 03Focused execution beats preserving a fixed program menu
- 04Advocacy can mobilize partners when one organization cannot solve the need alone
How to run it
- 1
Capture the need
Listen for a concrete request from the people closest to the barrier. State the need in terms of what they cannot currently do.
Pro tip Prioritize needs that repeatedly block participation or development.
- 2
Choose the response path
Decide whether your team can build the answer directly or whether partners must change products, documents, or access. Keep the response tied to the identified barrier.
Watch out Do not force every need into an existing program.
- 3
Hyperfocus execution
Direct the team toward the selected need and build the smallest useful response. Move quickly enough that the community can use it while the need is current.
Pro tip Use a short delivery window when the requirement is clear.
- 4
Mobilize the ecosystem
When direct delivery is insufficient, make the case publicly and repeatedly to relevant partners. Use evidence to show why action matters.
Pro tip Quantify the wider economic or community benefit when possible.
- 5
Adapt to the next need
Keep the organization fluid and reassess what the industry needs next. Preserve the mission while changing the intervention.
Watch out Fluidity without a stable mission can become reactive drift.
In the wild
A Hispanic loan officer asked for Spanish training to help candidates understand how the English-language NMLS exam frames its questions. Rogelio called it a great idea, and his team developed a course in about 30 days.
→ The organization converted a frontline request into a targeted training resource.
After lenders resisted requests for ITIN products and Spanish documents, Rogelio published an article arguing that the ITIN market could stimulate the economy by $300 billion. He reports that eight lenders now lend in the ITIN space.
→ Persistent advocacy helped draw more lender attention to an underserved product area.
Common mistakes
Protecting a fixed program menu
Defining the organization by existing activities can prevent it from responding to the barrier the community faces now.
Building without a concrete request
The loop starts with an observed need, not a speculative program idea. Without that signal, rapid execution can still solve the wrong problem.
Is it for you?
Best for
It is best for nonprofits, associations, and ecosystem builders serving a fast-changing industry.
Not ideal for
It is not ideal when a request is vague, unsupported, or outside the organization's ability to execute responsibly.
From the transcript
“Yeah, it's interesting because there is no one thing that home is because home is very fluid in a sense where if the industry needs…”
From the episode
He Gave Them the Plan… Nobody Executed ft. Rogelio Goertzen II
Rogelio Goertzen II