ISSUE 002

Lending Forward

Benjamin Reynolds - @benreynoldsmtg

---

The Question I Couldn't Answer

---

I got back from Bangor on Saturday Afternoon (had a flight get canceled, stayed 10 extra hours in a hotel, it was a whole thing...). I've been sitting with one question ever since.

From June 2–4, I was at the Oweesta Capital Access Convening presenting the Design-Build Framework to a room of Native CDFI practitioners and lending professionals. It was the first time I've taken this work outside Cook Inlet Lending Center.

The framework held up well! But teaching something is different from doing it. When you build a methodology inside your own organization, you bake in assumptions you don't know are there. The room finds them for you.

The question that stopped me came from a lending manager at a small Native CDFI. She was listening to the DESIGN phase — the friction-mapping process — and she asked:

At CILC, I was the manager. I had the authority to say "this process isn't working." For someone in a mid-level role at a smaller organization, or one with a less receptive leadership structure, the permission question isn't solved by having a framework. It's the first problem you have to solve before the framework can work at all.

I didn't have a clean answer. I've been building one since.

---

WHAT I'M WATCHING

The capacity gap is real — and it shows up in the room.

Every CDFI leader I spoke with is doing more with less — demand up, teams flat, infrastructure stretched. The Design-Build Framework starts with a phase that requires slowing down before you speed up. That's easy to say. For a team of three managing sharply higher loan volume than a year ago, slowing down isn't a methodology problem. It's a resource problem. The framework needs better on-ramps for organizations that don't have the bandwidth to pause before they redesign.

Take: A framework that can't account for resource constraints isn't a framework — it's an aspirational document. That's the version I'm not building.

The practitioners at Oweesta are past the "why modernize" conversation.

This room didn't need convincing. They are living the demand. What they need are transferable systems — ones that can be adapted for a small team, a specific charter, a specific community. The appetite was there. The hunger for practical, portable curriculum was visible.

Take: That's the direction this work is going.

---

FROM THE FIELD In audio production, the mastering pass isn't where you fix problems. It's where you find out if you built something coherent — whether everything holds together when it plays back from the beginning. Bangor was the mastering pass for the Design-Build Framework. What I found: the BUILD phase travels. Phased rollouts, train the team, measure and iterate — that logic landed across organizations of different sizes and configurations. The DESIGN phase is where I have more work to do. Specifically, building tools that help practitioners without positional authority make the internal case for change before the redesign begins. The permission problem she named is real, and it's mine to solve.

The next edition is going to go deeper on exactly that — how to map friction in an organization when you don't have the title to say what's broken. If you were in Bangor and want to continue the conversation, reply. If you weren't but you're working through something similar at your CDFI, I want to hear what you're running into.

The framework got better last week because a room of practitioners told me where it wasn't enough. That's the only way this works.