
Idea #9: It’s time for a systems upgrade
This installment of the 28days28ideas comes from Jewcy.com, but is appearing today on the Fundermentalist because of technical difficulties. When Jewcy is back up and running, we'll put the post back where it belongs.
As I read through the collection of ideas -- big and small, new and not-so-new -- that make up this project, I’m struck by how many of them are attempted game changers.
Even the ideas that aren’t big, huge, transformative are still presented with the scent of hope that somehow they will revolutionize Jewish life. We’ve proposed models to reinvent Jewish media, Jewish outreach, Jewish education, and pretty much any thing else Jewish. We’ve proposed -- as Patrick Aleph did with idea #2 -- to tear down the old and start anew. We’ve proposed -- as Ami Eden did with idea #1 -- to pool our collective resources in a broad new initiative, and we’ve proposed -- as Ari Wallach did with idea #6 -- to update old behaviors in tech-assisted new ways.
Most of these ideas are sexy. They’re bold and visible, impacting mostly on the front-end of Jewish life. They’re just the kinds of ideas that can seduce philanthropists, score seed money, and yield yet another Jewish venture. Few of them address the underlying weaknesses of or seek to reinforce the existing Jewish structures, because most of them are offered up on the premise that existing Jewish structures are inherently flawed.
Yet from everything I’ve seen, in the new Jewish ventures and the established Jewish institutions, there is more that can be done within the system than outside of it. Day after day, as I read Daniel Sieradski’s precursor to this project, I kept having the same thought, “This would be a wonderful project for the synagogue I work for to undertake.” The irony is that so many of his ideas are born from the Jewish DIY movement and so many of them are geared to building a Jewish life outside the synagogue.
Why this false dichotomy?
To be fair, I’m painting with a broad brush. I know Daniel, know that he’d be thrilled to see a synagogue commit sufficient resources over a sustained period to see these ideas to fruition. Almost all of the contributors to this project are trying to work within the existing system, even if only out of practical necessity.
Yet there remains this implacable notion that institutional Judaism is a staid place where only the biggest checkbooks get any real say, where the inertia of the old ways and sociopolitical orthodoxies overwhelms any real innovation. It is true that big funders can have an outsized influence, and that organizations sometimes outgrow their mission. Old methods are sometimes too slow to evolve.
But that’s hardly the entire picture. Institutional Judaism is also a place where resources are available, funders are willing to bankroll merited ideas, and practically everyone is ready to jump on any idea that works.
And it should be said, there are lots of ideas that work, including many listed here. I have my job as director of communications at The Temple in Atlanta because of a commitment to exploring those ideas, and I’m lucky to see young families and young leaders pour into the community every day.
I’m less interested in changing the game than I am in playing it at the highest level of competence. The question, for me, is what are the weaknesses? What are the structural points that need reinforcing? How can I build a sustainable game plan for the institutions that will outlive me and my involvement?
So here’s my big idea: Stop having big ideas. Instead let’s all get together and do what Ami Eden and Ari Wallach suggested. Let’s pool our resources and build the strongest technical back-end we can for the organized Jewish world.
Time and again I’m struck by how under-resourced the back-end is, even at large Jewish institutions. Our user databases are static and full of holes in the data, making it near impossible to target our outreach and communications. So we rely on an outdated broadcast model and wonder why we have a hard time reaching people. That’s just one example.
In Idea #8, Rebecca Guber proposed a residency program for Jewish artists. What if Jewish philanthropists came together to endow a communications and technology residency program, placing Jewish communications and technology professionals at synagogues across the country? (I keep focusing on synagogues, because I firmly believe they’re the one place where all Jews can come together regardless of their background, politics, or bank account.)
I guarantee you there are sexier ideas out there. This isn’t always fun work. In fact, it’s often a dreary slog. Funders will likely get more immediate bang for their buck elsewhere, but in the long run they’ll get more bullets for their guns by investing in the back-end.
(Bradford R. Pilcher is the director of communications at The Temple in Atlanta. The synagogue, founded in 1867, was listed by Newsweek magazine as one of America’s 25 most vibrant congregations. Pilcher’s work has included stints at Jewsweek.com, American Jewish Life magazine, and Jewish Funds for Justice. Visit The Fundermentalist to read "Idea #8: jewish Artists Residency" and stay tuned to ejewishphilanthropy for Idea #10. You can also visit 28days28ideas.com for the full list of ideas as they progress.
1 Comment
28days28ideas,
Jewcy,
The Temple
Comments RSS Feed Reader Comments
Leave a Comment
To leave a comment, you must first be logged in to JTA. If you are not registered, please click here.
Already a JTA member?
Need to know? Get JTA's free e-newsletters!
Share



Harlan Cohen
02/09/10 09:29 PM
“Time and again I’m struck by how under-resourced the back-end is, even at large Jewish institutions. Our user databases are static and full of holes in the data, making it near impossible to target our outreach and communications. So we rely on an outdated broadcast model and wonder why we have a hard time reaching people. That’s just one example.”
I think you are completely aware why back end systems languish, but allow me to elaborate for you.
In my limited exposures to fundraising and synagogue administration (two separate experiences), I perceive progress is not made any faster than a key leader wills it.
When my synagogue first went to personal computing for the administrative system, it was soon settled that Apple Macintosh’s would not be in the mix and monitors would be gray-scale and not color. This is about the time DOS was still prevalent and Windows was becoming interesting. These were cost savings but completely arbitrary and disregarding of trends and science (the human capacity to get more information out of color displays) in the latter case. But a complete fit to the chairman’s (a very competant executive of a tech company) view of the world.
When my university employer was discussing a full blown alumni web site, we saw the bells and whistles in demos and could not determine how to proceed because we really didn’t know what was most important to our prospective audience nor what would justify the expense. Leadership was rightly focussed on the close of a capital campaign but the alumni board wanted some attention to this languishing issue.
So are you certain of your audience (who they are, what they need and what they want and the difference between the two) and the priorities on the organization’s part (generally saving money or increasing revenue and hopefully both)?
At another university the change over to client-server from mainframe alumni and development system was as much a product of the desire of the university to rid itself of the mainframe operating and maintenance costs as much as anyone thinking the new software was.in some way a salvation.
I understand third-hand that one Jewish Federation group had a fine administrative system that also allowed other federations to outsource access and work. The demise of the hardware vendor seems to have broken those relationships and the consulting firm that implemented the system was not involved further with that federation or any other. At least I never heard more about it.
So do relationships continue to thrive if the infrastructure is ignored or did the infrastructure fail to evolve because the relationships were not thriving?
Since volunteerism is encouraged in both universities and synagogue venues, the resources obtained aren’t necessarily the resources you need. Nor will minimally salaried positions draw people with cutting edge skills. If we could build systems that acted the same only better after ten years, this wouldn’t be so much of a problem. But developers want to keep trying new paradigms and forgetting old ones until they resurrected in the next full generation of methodologies and tools.
So I hope you appreciate what I wrote and I hope I didn’t take up too much of your time in the reading.