We respect the work our partner organizations do. We know that no tech tool or app can take the place of solid on-the-ground organizing. No tech team ninja-wizard-unicorn squad can understand the needs of communities like those who have been working in and with their communities for years or even decades.
We empower our partner organizations to harness amplifying power of technology to build their movements and achieve their goals. We teach and train our partners so that they can build capacity for tech in their own organizations. We know that the long-term sustainability of activist organizations requires at least a basic understanding of the tech tools available for organizing, and how to make the most of them.
We include our partners as active participants in discussions about what their needs are, and how we might help. We actively work to be inclusive in the products we build, by building for accessibility as well as approachability. Our goal is to make sure that lack of tech knowledge, skill, or confidence is never the barrier to active participation in civic or political life.
How does Ragtag decide on what projects to work on?
Ragtag values transparency, and we want our volunteers and community to feel good about the way we choose projects to work on. The Ragtag leadership team evaluates all potential projects and partnerships to determine if they fit our mission and goals as an organization. The list of questions below is not exhaustive, but it’s the foundation that we work from when deciding to move forward with a project or collaboration.
Is this partner a good fit for Ragtag?
Does this partner’s work follow our core principles of “Respect, Empower, and Include”?
Are we confident the partner will abide by Ragtag’s Code of Conduct in their interactions with the Ragtag community?
Does the partner’s work promote the progressive values of the Ragtag community?
Do they have genuine relationships with the communities they are trying to serve?
Do they have grounding in the particular problem that makes it likely that they would know how to solve it?
Will this project benefit the communities we want to serve?
Is technology proposed the right way to solve the problem?
Are we confident that the project is not redundant?
Is the project designed to meet the real needs of a real set of users?
Is it likely to solve the problem it is designed to address?
Has the impact of the project on adjacent communities been broadly considered?
Does the impact of the project justify the effort?
Is this a project that the Ragtag community is well-suited for?
Is the project a good fit for volunteer work? We take into consideration the Intellectual Property ownership, the timeframe of the project, and if the project is more appropriate for full-time or paid workers.
Does the Ragtag community have the necessary skills to complete this project?
Can we mobilize our volunteers within the necessary timeframe?
Does the commitment of time and effort for this project fit in with other current projects?
Are Ragtag’s volunteers interested in working on this type of project or this kind of issue?
Is this a project or partnership that benefits Ragtag’s community?
Does the project support Ragtag’s participation in the civic and progressive tech community?
Does it broaden future opportunities for Ragtag and our community?
Will it help sustain Ragtag in the long-term?
Will it help us build and grow Ragtag’s volunteer community?
Will we learn new and valuable lessons by doing this project?