Beneath the Hire
Planning was one of the questions facing every growing moisad. Hiring is another. A Shliach who builds something serious eventually meets the ceiling of what he and his wife can carry alone. Systemizing and optimizing can raise that ceiling, but only by so much; past a certain point, what binds the moisad is no longer the workflow but the couple. Hiring becomes the only path forward. Building a team is how Shlichus scales beyond what one couple can do.
Hiring is also hard. Most Shluchim describe the trouble in terms of finding the right candidate or having the budget. But neither is where the hire actually succeeds or fails. What determines that is the frame the Shliach brings to the act of hiring.
Take a Shliach I was on a call with recently, one preparing to bring on a new couple he had been targeting for a while. When I asked what he was hiring them for, his initial answer was a lot to parse, the kind of input that would need real conversation to sort into anything resembling an actual job description.
He and his wife had been running the whole operation themselves for ten or fifteen years, a capacity ceiling they had been bumping against for a long time. The call was to cross the T's and dot the I's for the couple he had already chosen. He wanted a quick meeting: get the job description out, move on with the Shlichus. As I pressed on what these roles actually were (what the moisad needed them to be, what his priorities were), he grew visibly reluctant. The deeper questions felt foreign, like unnecessary fluff.
Behind the decision was years of carrying with no time, no money, no one obvious to bring in to help. Now things were different: there was some money, a couple he believed in had surfaced, and he wanted to close the loop.
That is not how hiring succeeds.
The moisad had been built by moving forward and figuring things out along the way: programs launched on that model, crises handled on that model. When it came time to hire, he reached for the same one.
Within that approach, a detailed job description reads as useless overhead. We'll figure it out as we go is how things are necessarily done. Or the way I usually hear it: the contract is only as good as those signing it; if you're a mentch, you don't really need it.
The Pioneer Hires Sub-Pioneers
The Shliach is looking for a specific kind of hire, the kind most pioneers default to. Someone who will step in and operate the way he and his wife have operated. Someone who will look at what isn't getting done and find a way to get it done. Someone who will absorb-and-stretch the way they have been absorbing-and-stretching for fifteen years.
He is hiring a sub-pioneer.
It doesn't work, and for a specific structural reason. The pioneer's level of carrying is not professional. It is closer to existential. The moisad is his: his family lives in it, his calling runs through it, his mesiras nefesh built it from nothing. No employee comes in with that math. The pioneer method works for the pioneer because his commitment is, by definition, unreasonable.
Without onboarding, without defined responsibility, without a clear edge to what's being asked, the work will flood toward the new hire: the shul, CTeens, young professionals, Shabbos meals on rotation, more beyond that. He is left to figure it out on his own. Whatever he produces will land somewhere off the Shliach's silent expectations, either falling short of them or stepping past them. If he falls short, the Shliach grows frustrated. The hire isn't carrying his weight. At some point he has to reassert his expectations, calling the employee out for underperforming. If he does well (really well, taking things further than the Shliach himself had), the Shliach grows uncomfortable for a different reason. The moisad has been his alone for fifteen years. Someone new acting on it with genuine authority, making real decisions about the direction, is something he has never had to make room for. At some point he reels it back in. However it evolves, the correction launches a cycle that erodes motivation, goodwill, and eventually trust.
You simply cannot pay someone to be a sub-pioneer.
The Rebbe touches on the limitations of this approach in the sicha on parshas Lech Lecha 5742. Mesiras nefesh can take a person from a roof to the ground. It cannot take him from the ground to the roof.
Mesiras nefesh created the Shlichus. The Shliach leapt from a roof to a ground and brought a world into being where there was nothing. He is now standing on that ground and trying to climb, reaching for the same instrument that worked before. He is asking the hire to leap with him.
But a climb isn't a leap. A climb needs stairs.
The Operator Builds Stairs
He has more experience now. He has seen what happens when hiring is improvised, and he has done the work of preparing. There is a proper job description, a signed contract, perhaps a consultant or mediator who helped think it through. Both sides know what they agreed to; there is goodwill on both sides, and process where the pioneer had instinct. He has upgraded the mechanism of hiring, and that is not nothing. Stairs are real infrastructure.
And it still doesn't work.
The reason is structural: the contract is a lateral instrument that ignores the vertical force it will have to withstand. An agreement between two people about what one will do for the other cannot hold against the moisad's distributed weight, pressing on the hire from every staff member, every congregant, every unfinished program at once. The operator designed mechanism into the role; he did not build mechanism into the moisad.
The most common form of vertical force that unexpectedly lands on a new hire is operational debt.
The pioneer has spent fifteen years protecting one kind of resource above all others: money. Financial debt is the debt he has been trained to recognize as a liability. And in order to keep that line clean, he has paid for it in another currency: overextending his operations, neglecting relationships, shortchanging administration. A volunteer base that was never built. Staff check-ins that never quite happen. Donor follow-ups depending on him remembering to make them. Bookkeeping attended to sporadically and superficially at best. Software no one knows how to maintain. Programs whose entire continuity sits in his head. Relationships stretched thin from being asked, year after year, to forgive what should have been resolved cleanly.
The pioneer has never called this operational debt, because his frame doesn't see it. From his vantage he has been careful. The moisad is solvent. But underneath the financial line is an unaccounted-for ledger, and it is exactly the ledger the new hire walks into.
Operational debt doesn't stay dormant; it presses. Every week brings the next thing the moisad never built right surfacing as the next thing that needs handling now. And this is on top of him getting pulled in to help with upcoming events, new initiatives the Shliach wants to launch: weight a job description couldn't have anticipated.
Initially, the employee believes in the job description. The Shliach does too. But belief succumbs to reality. The young Shliach hired to develop the camp and increase community engagement ends up only maintaining the camp and participating in community engagement, while also taking care of tech issues, managing the fundraising campaign, and designing the flyer for the upcoming Lag B'Omer party.
Eventually,The employee gravitates toward whatever feels productive to him, or, if he is the kind of person who cares about pleasing his employer, toward whatever he senses will please the operator in the moment. Eventually he gets it: the job isn't the job he signed on for. The job is being defined by the stress of the hour, and he steps up to meet that calling.
The original ambition that prompted the hire never materializes.
It's a common operator pattern. The mechanism assumes a clean handoff. The employer assumes a competent employee. The employee assumes a leader waiting to guide him. None of those hold up in practice.
Step back from both eras and the pattern is clear. The pioneer seeks to grow by hiring a sub-pioneer. The operator seeks to grow with a clean handoff. In both cases, it doesn't work. A person cannot deliver growth the moisad is not yet prepared to receive.
The leader operates from the other side of it. The shape of the growth is worked out before the role is named, so that the hire steps into something the moisad is already prepared to receive. How that work gets done, what the leader is actually thinking about when he is doing it, what makes a direction "shaped" enough to hire into, is its own subject. We have only located the seam here. The territory on the other side is what these pages will be spending time in.
Keep integrating,
Yosef