Between Two Seats

Most people who know me would assume I spent recent years mostly helping Shluchim set up a CRM or delegate to a virtual assistant. In large part they would be right. What would surprise them is that a good deal of my discussions were spent explaining to a Shliach why a CRM, VA, or a better system was not going to solve the problem he had called about. That conversation kept happening, and slowly over time it stopped being the detour and became the work. These pages are the formalization of it.

I came to this slowly, and against my own instinct, which was always to fix the thing in front of me. Whatever I treated as the cause kept turning out to be a symptom of something deeper. Eventually I made my way to the bottom layer, where the same root cause sat: a gap between the role a Shliach's title gives him and the role he quietly identifies with. He never decides on that second role, and never notices he has settled into it. But it is the thing that decides, long before any system or strategy, what he treats as his to carry.

Take a Shliach I spoke with recently. He had come about fundraising, like many others. It hadn't worked in a long time, and he had the explanation ready before I asked.

He presented two reasons. The town: people here aren't traditional, they don't know what carrying a moisad costs or why it should matter to them. And himself: he isn't organized, and he isn't good at time management. One reason outward, one inward.

So we looked at what he had actually done. Every so often he would decide to get serious about fundraising, run his friends' approach exactly as they do, and watch it underperform, then let it go until the next time. What he never did, across all those rounds, was change anything: not the ask, not who he asked, not what he asked for. He had run the same borrowed motion again and again and read each failure as a verdict, never as information.

So I stopped asking about fundraising and asked what he was actually good at. He didn't hesitate: the programming. The turnout, the families who come back, the room when it's full. He's good at it, and he knows he is.

That was all I needed to see. Both reasons he'd walked in with fell apart against it. He'd blamed his organization and his time management, but he runs a packed program calendar and runs it well, which takes both. He'd blamed the town, but those same people fill his programs and come back for more; they connect with him fine. The abilities he faulted for the fundraising are ones he clearly has. He just wasn't pointing them at it.

Everything he lit up about, and everything he skipped, pointed to the same thing: his role. To him, the real work was the programs, connecting with neshamos and gathering the community. He operated from the program director's seat, and from there fundraising was a support function, distant from the mission, the kind of administrative task you get to when the quarter is quiet or the books need tidying. It had never occurred to him to ask who was responsible for building the moisad that would design, develop and support the programs.

The only thing that ever drove him to fundraise was pressure: the bills, the shortfall, the month coming. And pressure is a terrible engine for anything you have to build, because it only runs while it's on. A big gift comes in, buys three months, and the fundraising goes quiet, no longer urgent, so no longer done. The work is never outright rejected. It just never happens except under threat, so it never compounds, so it never builds into anything.

Fundraising was failing because it wasn't really part of his job description.

Pull back from this one Shliach and you have the shape of so many of my conversations with Shluchim over the past years. The request is for a tool (a system, a platform, a hire), and the tool would be an excellent solve for a real efficiency or capacity challenge. But in those calls, it was not the problem on the line. The real problem was the gap between two seats. His title put him in one of them: Executive Director, the person answerable for whether the institution exists in five years, its funding, its direction, its whole future. In his own mind he sat in the other: program director, the man who runs the activities.

A title only seats you on paper.

But a title only seats you on paper. Actually occupying the executive director's seat (being the author of the institution, not merely the runner of its programs) is a different thing, and far rarer. So the programs succeeded, the room was full, he felt like a Shliach doing his job, and that seat sat empty behind all of it. He had the title. He had never fully sat down in it, nor did he ever really notice that he had to.

For most, the question never comes up, because fundraising from the program seat should work. Plenty of Shluchim raise real money where this Shliach sat. The approaches that have circulated for twenty years do produce. In the right community, with the right person, run with enough energy, the funds come in. Under the right conditions, the method works; it just has a ceiling.

You can see the ceiling in how the success itself gets talked about. Ask a Shliach about a large gift he received and it tends to come out as a kind of miracle: a big check from out of the blue, a wonder that landed. Sometimes it genuinely is. But the reaction gives the seat away. To someone fundraising from the program seat, where the money was always the afterthought, a large result can only be a fluke; there is no real container for it to belong to. From the executive director's seat the same gift lands differently, worth celebrating, but not something that fell on him from outside. It is a function of what the work is about.

I believe the donor feels this as well. A Shliach who carries fundraising as the overhead on his programs is, without meaning to, telling his donors exactly that: help me cover what it costs to run this. So that is what they give toward: the running of it, maybe a little past it. Anything beyond would be, to them as much as to him, a windfall. It is likely why so many Shluchim contend with their donors' assumption that some head office in New York is funding them, when they are entirely self-funded. The assumption is not random; it fits the posture he fundraises from.

None of this is an argument that every Shliach must make fundraising the center of his work. The point is to see the seat, and to know whether you are sitting in it.

A pattern this widespread is not random. It is an inheritance from the operator era. That inheritance was, first, a gift: shared playbooks, proven programs, a network that had already solved a version of the problem each new couple was about to meet. It is what let Shlichus scale at all. But it came at a cost no one noticed: when something arrives already built, you never have to learn to build it.

When something arrives already built, you never have to learn to build it.

A Shliach can run an inherited model for fifteen years and never once face the question of what his own situation requires him to create from scratch. And so the building got delegated upward: to the network, to a coach, to the head moidos, to a more seasoned Shliach, to the knowledgeable congregant, or the rich one who might one day swoop in.

Each piece before this has been circling some version of this, and here it is at its root: the gap between the seat a Shliach's title gives him and the seat he actually sits in. It sits under the fundraising, under the systems, under every borrowed playbook. And it is not a gap that another playbook can close.

A gap like this has first to be seen, taken in, and understood, and my hope is that these pages have brought it into view. The distance between the name on the seat and the person in it is, almost exactly, the size of everything the operator era has left him struggling with. Closing that distance is where the transition into the leadership era actually begins, and it is what these pages turn to next.

Keep integrating,
Yosef