Meta Fund Raising

From FreekiWiki
Revision as of 08:23, 7 May 2009 by Matteo (talk | contribs) (donations)
Jump to navigation Jump to search

Meta Fund Raising (and Resource Wrangling?)

INTRODUCTION TO FREEGEEK FUNDING META PROCESS (FMP)

In the beginning there was fund raising, and it was good. Now we have a fund raising working group, and the group is giving birth to itself as an integrated part of the larger Free Geek operation. When there is birth, there are questions like “Why am I here?” “What is my purpose?” “How should I be day to day?” “How will I affect others around me, and those who come after me?”

On this page, the fund raising working group is addressing the questions:

Q: What should-be the big picture around funding and at Free Geek?
Q: What does a fund raising process need to achieve?
Q: What are funds? Is this more "resource wrangling" than grant writing?


Fund Raising Process

This is a graph with borders and nodes. Maybe there is an Imagemap used so the nodes may be linking to some Pages.

What should the fund raising process look like?

The fund raising process should include a formally recognized process for establishing formal agreement that pursuing a particular resource is a Free Geek priority.
(from random referrals to council approval)
A formally recognized process for fund-raising should include a strong coordination function, that is, it must keep others in the loop, other FG people, working groups, and other organizations.
Example 1: coordinating with budget writers; Bean Counters so their documents are available and make fund raising easy.
Example 2: coordinate with council and then the board, by advocating for clarity on long range programmatic planning.
A formally recognized process for fund-raising should be a working part of strategic planning.
FMP needs to show where long term planning fits in.
For example: Which planning documents best represent the current consensus of long range thinking?
+Long Range Planning category on the wiki
+Vision Statement for 2010
FMP must also show how it uses those documents.
A formally recognized process for fund-raising should prevent losing accomplished work when a volunteer or staff person leaves a project
(Question: How to do this simply? RT, open wikis, secure wikis and more?)
The formally recognized process for fund-raising should be easy, so good projects don't get unnecessarily bogged down.
The formally recognized process for fund-raising should provide guidance for plugging people into tasks that fit both their interests, and the needs of FreeGeek as a whole.
The formally recognized process for fund-raising should provide guidance for sorting through “great opportunities” to separate the “wheat from the chaff.”
(see Grant Writing Triage)
The formally recognized process for fund-raising should provide guidance on prioritizing staff and volunteer time in real time.
Remember that almost every step in a fund raising process is reiterative. That is, each circle of activity loops around over and over. Establishing priorities <---> finding resource opportunities, like requests for grant proposals, or new recycling income streams among others <---> researching new relationships, arranging collaborations, and finally writing formal proposals <---> tracking proposal processes <---> keeping funders informed with newsletters and informal meetings, or at least filling out reports <---> generating new resource options, and like that...
The formally recognized process for fund-raising should provide records about contacts with funders and other organizations related to specific grants.
(For example, we need to know when we first heard about or made contact with a funder, then when recommendations are followed and promises are made.)
The formally recognized process for fund-raising should provide actual time-lines for particular efforts.
(This might be a mixture of RT and wiki documentation).
Time-lines are needed for both the formally recognized process for fund-raising, and for individual resource requests.
When developing timelines, contrasting colors can be used to show contact information, RFP (request for proposals) deadlines, milestones in FreeGeek's strategic plans and refinements on FreeGeek's visions of the future.
proposal1: each resource development project gets a ticket?
proposal2: RT tickets are projects with owners, for example, creating a triage format is a project. It has a “wrangler” or owner. Another task-project is keeping the grant opportunities list up to date.

ADD MORE PAGES SUPPORTING FUNDRAISING FOR FREEGEEK!

You probably know of more wiki pages that are crucial for understanding fund raising at FreeGeek. Add them in! Or maybe some of these shouldn't be there. Edit them out! Here's what we found in a random search: