Jump to: content, navigation, search

Navigation menu

Strategic Plan 2023 Cycle: Difference between revisions

Strategic Plan 2023 Cycle (view source)

Revision as of 13:29, 20 January 2023

28,295 bytes removed ,  2 years ago
m
Replaced content with "__NOTOC__ Home page for Strategic Planning ==OSMF Strategic Plan Outline - 2023 Cycle of Revisions== ====Key Inputs and Process==== A strategic plan is a big undertaking. Our approach is to set high-level directions across all the efforts and structures of the Foundation, and then to take a phased approached to develop more specific ideas and determine details of plans. The highest levels of direction are set by the Vision and Mission s..."
m (Replaced content with "__NOTOC__ Home page for Strategic Planning ==OSMF Strategic Plan Outline - 2023 Cycle of Revisions== ====Key Inputs and Process==== A strategic plan is a big undertaking. Our approach is to set high-level directions across all the efforts and structures of the Foundation, and then to take a phased approached to develop more specific ideas and determine details of plans. The highest levels of direction are set by the Vision and Mission s...")
Tag: Replaced
* [[Cluster D|Cluster D: Financial Management and Fundraising]]
Under each of the major Clusters are Strategies and a level below that are Tasks. Tasks are designed to be implementable projects and each task is supported by a lot of detail related to timing, resources and managerial oversight.
 
==Strategy Cluster A: Technical Development and Resilience==
 
===Strategy A01: Platform Services Demand Growth Forecast 2023–2028===
 
====Task A101: Growth Projections to 5 year horizon====
 
* '''Description''':
* '''Action''': Develop a range (low/medium/high) of OpenStreetMap platform services growth projections in 1-, 3-, and 5-year timelines.
* '''Responsible''': X, working with SSRE and OWG
* '''Oversight responsibility''': Unknown
* '''Priority''': Unknown
* '''Start date''': Unknown
* '''End Date''': Unknown
* '''Project status''': Not started
* '''Project progress''': 0%
* '''Budget estimate''': No cost. All voluntary work.
* '''Deliverable''': Document specifying projected growth in 1,3,5 years, and reflecting 3 scenarios
 
====Task A102: Engineering Design of 5 Year projected platform changes====
 
* '''Action''': Use platform services growth scenarios to determine implications for hardware, hosting, software and operations workload.
* '''Responsible''': X, working with SSRE and OWG
* '''Deliverable''': Document identifying hosting, hardware, software and ops resources required over the next 5 years.
 
====Task A103: Financial Planning for 5 year horizon====
 
* '''Action''': Prepare a financial plan to accommodate changing demand for platform services.
* '''Responsible''': X, working with SSRE and OWG
* '''Deliverable''': Document showing 5 year financial forecast for platform services
 
===Strategy A2: Technical strategy for Hardware===
====Task A201: Provision of a suite of Developer tools====
 
* '''Note:''': ''This is probably better written as a strategy to support developers and under that a bundle of tasks.''
* '''Description''': Providing tools mappers need to collect, enter, check quality of, and use data
* '''Action''': providing tools
 
====Task A202: Implement a Development Version of Vector tiles====
 
* '''Description''': Set up a development platform for experimental and trial deployment of vector tile mapping
* '''Action''': development platform for vector tiles by volunteers
 
===Strategy A3: Technical strategy for Software===
 
====Task A301: Revitalise the Engineering Working Group====
* '''Description''': Need more detail on what this is about. Some history.
* '''Action''': revitalise EWG
 
====Task A302: Evolve the OSM Data Model and API====
 
* '''Description''': Need more detail on what this is about. Maybe Jochen's paper?
* '''Action''': evolve data model + API
 
====Task A303: Encourage and Collaborate on Standardisation in the mapping ecosystem====
 
* '''Description''': Need more detail on what this is about
* '''Action''': Expand the OSM role in encouraging standardisation and collaboration in the mapping ecosystem
 
====Task A304: Foster ecosystem of open source tooling and libraries====
 
* '''Description''': Need more detail on what fostering an ecosystem requires.
*'''Action''': Foster ecosystem of open source tooling and libraries
 
====Task A305: Review of Hosting Policy====
 
* '''Description''': OSMF hosts applications on our servers that are not linked directly to ehe core functions of the organisation. Examples are (No data) There are costs to doing so, both capital and operating costs. It is proposed to review the cost/benefit of these applications and take action.
* '''Action''': define what we host ourselves, and what we leave to third parties
* '''Responsible''': Unknown
 
===Strategy A4: Technical Strategy for Staffing===
 
====Task A401: Appointment of a Website maintainer====
 
* '''Description''': There is a need for someone to maintain the websites operated by OSMF. The task description is currently not available. After the job is well-defined, a voluntary worker or employed contractor is needed to do the work.
* '''Action''': Prepare JD. Review available resources for voluntary workers. If suitable voluntary workers are not available, apply to the Board for a contractor position. If granted, appoint contractor.
* '''Responsible''':
 
====Task A402: Key updates: make site easier to develop====
 
* '''Description''': (No data. Please describe this task and steps needed to implement it.)
* '''Action''':
* '''Responsible''':
 
====Task A403: European General Data Protection Regulation (GDPR)====
* '''Note''': Simon Poole Jn 2023 Podcast says that The European General Data Protection Regulation (GDPR) has not been implemented, despite most of the work having been completed in 2018. Possible Action: Prepare Board resolution on proceeding. Assign the task to a new volunteer team or if that fails assign the work to a professional consultant. Podcast here: Scrub forward to 23:13 = https://thegeomob.com/podcast/episode-164
'''Description''': The General Data Protection Regulation is a Regulation in EU law on data protection and privacy in the EU and the European Economic Area. The GDPR is an important component of EU privacy law and of human rights law, in particular Article 8 of the Charter of Fundamental Rights of the European Union. The OSMF wishes to modify much of the software in use to reduce personal information contained in OSMF websites. The changes required are documented but now need to be coded. There have been problems recruiting a Ruby developer from the volunteer world to undertake this work. See https://gitlab.com/osmfoundation/board/-/issues/131
 
* '''Action''': (Please describe this task and steps needed to implement it.)
* '''Deliverable''': No data
 
====Task A404: Support contributors to OSM====
 
* '''Description''': Many people provide mapping and non-mapping contributions to OSM and OSMF. To encourage and increase such support OSMF plans to (No data)
* '''Action''': (Please describe this task and steps needed to implement it.)
 
====Task A405: Additional sysadmin====
 
* '''Description''': SysAdmins are the volnteers who manage OSMF's servers. (Please add to this)
 
* '''Action''':
 
====Task A406: Successor(s) for iD development====
 
* '''Description''': (Please describe this task)
 
* '''Action''':
 
====Task A407: Supporting other editors in agreement with maintainers====
 
* '''Description''': The OSM maps can be edited with many different applications. (Please describe this task)
 
* '''Action''':
 
===Strategy A5: IT security review and plan===
Introduction:
 
The goals of OSMF with regard to offering a mapping platform is that the platform should be resilient and stable. Resilience is the ability to continue running after small or large errors in hardware and software. One example is the ability to survive failure of a disk drive. The term "bounce back" describes resilience. Stability is the ability to offer an unchanged and uninterrupted set of services to users for long periods of time. Highly stable systems will run for hundreds of days without interruption of service.
 
====Task A501: Backups====
 
* '''Description''': (Please expand on this task)
* '''Action''':
* '''Deliverable''':
 
====Task A502: Disaster recovery====
 
* '''Description''': (Please expand on this task)
* '''Action''':
* '''Deliverable''':
 
====Task A503: Separation of privilege====
* '''Description''': (Please expand on this task)
* '''Action''':
* '''Deliverable''':
 
====Task A504: Redundancy====
* '''Description''': (Please expand on this task)
* '''Action''':
* '''Deliverable''':
 
====Task A505: Vulnerability assessment====
 
* '''Description''': (Please expand on this task)
* '''Action''':
* '''Deliverable''':
 
====Task A506: Project hosting====
* '''Description''': (Please expand on this task)
* '''Action''':
* '''Deliverable''':
 
==Strategy Cluster B: Community Development for OSM==
 
===Strategy B1: Volunteer working groups===
* '''Note''': Simon Poole podcast Jan 2023 suggested that Board did not have Licensing Working group's back. Possible Action: Check with all WG if there are problems with Board attitude/support.
* '''Introduction''':Working Groups are the OpenStreetMap Foundation’s operative organs. Community participation in the Working Groups is critical to OpenStreetMap’s health. Therefore, the Board seeks to:
 
====Task B101: Membership recruitment and retention====
* '''Description''': increase retention and recruitment.
* '''Action''':
* '''Deliverable''':
====Task B102: Communication about Working Groups====
* '''Description''': increase the visibility of Working Groups and their activity, so that the community recognises and understands them.
* '''Action''':
* '''Deliverable''':
====Task B103: Best Practices and Onboarding====
* '''Description''': offer help to Working Groups to exchange best practices and in particular to enhance onboarding.
* '''Action''':
* '''Deliverable''':
====Task B104: Working Group Membership drive====
* '''Description''': organise a Working Group Membership drive, using its access to promotional channels.
* '''Action''':
* '''Deliverable''':
 
===Strategy B2: Community strategy===
'''Introduction''':
This task is poorly developed. Please add content to these tasks.
 
====Task B201: Focus on local knowledge and distributed intelligence====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B202: Expand local chapters and communities====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B203: Provide opportunities for more structured input to project direction and topics====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B204: Promote local groups and events====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B205: Give better visibility to community content====
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
===Strategy B4: Cross-border and cross-cultural collaboration===
This Strategy is poorly developed. Please add detail to all actions.
====Task B401: Support SOTM and support local SOTMs====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B402: Address language barriers====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B403: Address cultural barriers====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B404: Address trust and safety in communication, define role of local chapters in moderation====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B405: Provide a modern, open communication platforms====
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
===Strategy B5: Gender diversity===
 
====Task B501: Develop a policy to promote gender diversity within the OSM movement====
* '''Note''': ''This is probably more than 1 Task. Can it be broken up into smaller work packages and smaller deliverables. Work packages can be done in serial sequence to level resource demands.''
* '''Description''': With confirmation from the recent survey, the Board recognises the lack of non-male participation in the project and considers it a problem since our ambition for the project is to benefit the whole of society and to take advantage of as many contributions as possible. The Board will develop a strategy to promote gender diversity. To give it sound foundations, it will start with the Board Members personally reaching out to non-male persons around OpenStreetMap, including former participants and non-participants. From analysing that round of interviews, the Board will start pursuing specific initiatives.
* '''Action''': Conduct initial research among board-adjacent OpenStreetMap community, prepare an analysis and develop specific initiatives
* '''Deliverable''':
 
===Strategy B6: Community relations===
Introduction:
As we have defined OSM’s core as the mapping process, we have to remain engaged with each of its stakeholders – individuals and corporations, contributors and users.
====Task B601: Maintain Volunteer relations====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B602: Maintain Corporate relations====
* '''Note''': Simon Pool podcast Jan 2023 suggested Overture Foundation will result in less financial and development resources flowing to OSMF. Possible action: Improve relations with Overture members. Spread corporate support wider to non-overture companies. Diversify fundraising.
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
====Task B603: Maintain Data user relations====
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
===Strategy B7: Empowering volunteers===
 
====Task B701: Provide education and training====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B702: Provide wiki.openstreetmap.org====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B703: Provide curated tags proposal====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B704: Provide dialogue moderation====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B705: Provide infrastructure for testing/development====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B706: Provide access to test databases====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B707: Provide project hosting====
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
===Strategy B8: Undertake OSMF strategic planning process===
 
Introduction:
This document is a conversation. We will seek commentary on the document, perform structured surveys for input, and directly reach out with questions to stakeholders.
 
====Task B801: Seek community commentary on the strategic planning document====
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
====Task B802: Perform structured community surveys for input====
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
====Task B803: Directly reach out with questions to stakeholders====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B804: Prepare and revise OSMF Strategic Plan====
* '''Description''':
* '''Action''': Gather information from the community and use it to prepare a plan for performing the Mission of OSMF, as a step towards the future state of OSMF as stated in the Vision. All to be done in full accord with the OSMF statement of ethics.
* '''Deliverable''': An annually updated strategic plan, with enough detail on implementation to manage the projects and operations of the institution.
* '''Assigned to''': Allan, Sarah, Craig
* '''Management oversight''': OSMF Board
* '''Budget allocation''': Zero. Voluntary work
* '''Priority''': Very High
* '''Start date''': January, annually
* '''End date''': October, annually
* '''Project status''': In progress
* '''Project progress''': 5% @ 17 Jan 2023
====Task B805: Project manage the implementation of the strategic plan====
* '''Description''': Follow up on all actionable items in the strategic plan and ensure that the managerial oversight team and assigned implementer are progressing with their tasks. Problem solve if necessary to ensure progress.
* '''Action''':
* '''Deliverable''':Progress reports on the progress of implementing the entire Strategic Plan
 
===Strategy B9: Regular OSM Community Surveys===
'''Introduction''':
====Task B901: Directly reach out to Mappers====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B902: Directly reach out to Developers====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B903: Directly reach out to Data users====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task B904: Directly reach out to Funders====
(Note: this can clash or synergise with Fundraising strategies. See D7)
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
====Task B905: Directly reach out to Companies====
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
===Strategy B10: Humanitarian Mapping===
====Task B1001: Humanitarian mapping====
* '''Note''': ''Can we have more detail about the problem and the proposed soution. What is the desired outcome of this work?''
* '''Description''': Through dialog, explore ways for the OSMF to support the expanding and changing ecosystem of diverse actors in humanitarian mapping.
* '''Action''':
* '''Deliverable''':
 
==Strategy Cluster C: Institutional Development of OSMF==
 
 
* '''Note''': Simon Pool January 2023 podcast said that the OSMF is in stagnation. It is impossible to change things. There is no leadership. No push to get things done. Possible action: Develop strategic plan with clearly actionable tasks assigned to people. Establish Project Manager portfolio in the Board to manage task implementation across the entire plan. Develop documented Working Group responsibilities, delegate operational matters to working groups, and enhance WG project management skills.
 
 
===Strategy C1: Institutional strategy===
'''Introduction''':
The Foundation is established for the two purposes below:
 
#encouraging the growth, development, and distribution of free geospatial data; and
#providing geospatial data for anybody to use and share.
 
Questions arising are:
*What definitely falls within the OpenStreetMap Foundation’s mission?
*What definitely doesn’t fall within the OpenStreetMap Foundation’s mission?
*What are we unsure about falling within the OpenStreetMap Foundation’s mission?
*What is the procedure to amend the purpose of establishment if required?
*Should we make some of that explicit, in response to questions about the OpenStreetMap Foundation’s legitimate scope of action?
====Task C101: Define OSMF's legitimate scope of action====
* '''Action''': Research and report on OSMF's legitimate scope of action
* '''Deliverable''': A report on the legitimate scope of action of the OSMF.
 
===Strategy C2: Responding to Brexit===
'''Introduction''':
 
Brexit is important to OSM because the OSMF is incorporated in the UK. Brexit threatens enforcement of our database rights in the European Union. To OSM, Brexit isn’t an incoming wall – the erosion will be gradual. Nevertheless, it is now time to start studying whether to move to a more favourable jurisdiction and how that could happen.
 
====Task C201: Moving OSMF Banking to EU====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task C202: Moving OSMF Data to EU====
* '''Description''':
* '''Action''':
* '''Deliverable''':
====Task C203: Moving OSMF Offices to EU====
* '''Note''': This was touched on in Simon Poole's Jan 2023 Podcast here: https://thegeomob.com/podcast/episode-164
 
* '''Description''':
* '''Action''':
* '''Deliverable''':
 
===Strategy C3: OSMF Fortification===
====Task C301: Protect OSMF from Hostile Takeover====
* '''Note''': ''This appears to be a bundle of tasks. It may be better to break them apart for separate implementation.''
* '''Description''': Public trust in the Foundation’s commitment to OpenStreetMap is paramount to the Foundation’s mission. The Board will therefore seek to enhance institutional mitigation of the risks of third parties leading it astray, through thorough assessment and identification of major and subtle risks. From there, the design of mitigation at the organisation, process, and financial levels will be implemented.
====Task C302: Protect OSMF Intellectual Property against Piracy====
* '''Note''': Simon Poole in his Jan 2023 podcast touched on the need to urgently protect OSMF trademarks.
* '''Description''': No data
* '''Action''': No data
 
===Strategy C4: The Foundation at OpenStreetMap’s core===
 
====Task C401: Ensure the availability of a FOSS path to complete the OSM mapping process====
 
* '''Note''': ''This Task is overly complex. It may be better stated as Strategy with several tasks.''
* '''Description''': Discussions of the OpenStreetMap Foundation’s role have often turned to discussing what is core. To build its strategy on firm ground, the Board has sought to improve that definition. The conclusion is that the functional core of the OSM movement is the mapping process. This is complemented by the technical core, which at root is the database and the supporting API.
* '''Action''': Ensure that there is at least one fully Free and Open Source Software path to complete the OpenStreetMap mapping process. Decisions about what software to support will follow directly from this.
 
===Strategy C5: Foundation Management===
====Task C501: Manage the foundation====
* '''Description''': (please add detail here)
* '''Action''':
* '''Priority''':
* '''Deliverable''':
 
===Strategy C6: Public Relations Programme===
* '''Note''': Raised by Simon Poole in his Jan 2023 podcast: The OSM Project is an important global initiative and has not been marketed sufficiently. Possible Action: Create PR protfolio on Board. Work with Communications WG to develop PR policy for OSMF. Cooms WG asked to create a best-practice PR campaign for OSMF and OSM movement. Hire consultants if necessary.
 
====Task C601: Public Relations====
* '''Description''': (There should be more than one task. See note above. Please add detail here)
* '''Action''':
* '''Priority''':
* '''Deliverable''':
 
==Strategy Cluster D: Financial Management and Fundraising==
===Strategy D1: Financial Expenditure Matters===
====Task D101: Policy for Funding Projects====
* '''Description''': Financial scalability. Establish a framework to match funds to projects. It should be possible to earmark donations to fund specific projects. Project developers should match their operational duration to the duration of funding allocated
* '''Action''':
* '''Priority''':
* '''Deliverable''':
 
====Task D102: Policy for Funding Operational Expenses====
* '''Description''': Avoid funding running expenses with exceptional income
 
===Strategy D2: Maintain and Improve the Financial Viability of OSMF===
 
===Strategy D3: Maintain and Develop Corporate Sponsorships===
* '''Note''': This is duplication with Community actions in building relationshps with corporates. Repeating is bad. Provide a link here to an existing task elsewhere in the plan. See Section B602 Maintain_Corporate_relations Suggest that this is not directly financial and should be deleted.
 
====Task D301: Maintain Corporate Sponsors====
* '''Description''': Engage with existing Corporate Sponsors to continue their support of the OpenStreetMap movement
* '''Actions''':
* '''Priority''': No data
* '''Assigned to''': No data
* '''Start date''': No data
* '''End date''': No data
* '''Deliverable''':
 
====Task D302: Recruit Additional Corporate Sponsors====
* '''Description''': Engage with the Mapping Industry to encourage their support of the OpenStreetMap movement
* '''Actions''':
* '''Priority''': No data
* '''Assigned to''': No data
* '''Start date''': No data
* '''End date''': No data
* '''Deliverable''':
 
===Strategy D5: Prepare Contingency Plans for Financial Emergencies===
 
====Task D501: Prepare a Financial Reserve Policy for OSMF====
 
* '''Description''':
A financial reserve ensures OpenStreetMaps sustainability. The reserve fund will serve a buffer role to cover temporary gaps in funding. By establishing a reserve fund OSMF will protects the ongoing operations of the technical core, avoids opportunity costs and avoids contract termination costs. The policy should identify pre-emptive financial steps to be taken in a pending emergency, to avoid reaching a point where reserve use is considered. The size of the reserve should be scaled to be proportional to the size of the budget.
 
A more granular approach to using reserve funds, where parts of the reserve are earmarked for specific purposes should be considered. ''(More details please)''
 
The reserve fund will become part of the financial Doomsday contingency plan to sustain OpenStreetMaps through a disaster scenario.
 
A thoughtful formal approach to the reserve fund will reassure stakeholders, among which are OSMF members, donors and community volunteers that the OSMF is taking serious measures to ensure sustainability. In times of crisis, a formal, approved policy document has a stabilising effect.
* '''Action''': The Board shall commission a formal financial reserve policy.
* '''Priority''': No data
* '''Assigned to''': No data
* '''Start Date''': No data
* '''End Date''': No data
* '''Deliverable''': Approved Financial Reserve Policy
 
====Task D502: Prepare a Financial Doomsday Plan====
 
* '''Description""": Given the donor funded nature of OSMF and the possibility of financial collapse of OSMF in an unpredictable disaster, it is necessary to prepare for the continuation of the broader OpenStreetMap movement under circumstances that may bankrupt OSMF.
This would involve a fallback to core OpenStreetMap which defines the barest minimal OpenStreetMap that remains OpenStreetMap.
In preparation OSMF should define and calculate a minimal core gross burn rate for OpenStreetMap and provide for a disaster-proof insulated operational reserve to fund a transition to a state of financial thrift.
* '''Action''': Prepare a contingency plan to guide the OpenStreetMap Foundation through a financial crisis requiring a sudden down-scaling of expenditure.
* '''Priority''': No data
* '''Assigned to''': No data
* '''Start Date''': No data
* '''End Date''': No data
* '''Deliverable''': Approved Financial Disaster Management Plan
 
===Strategy D6: Set up functional financial infrastructure===
====Task D601: Eliminate International Banking Problems====
* '''Description''': Banking in multiple currencies remains challenging and time-consuming – it is unusual for a small organisation like the OSMF to have such a broad international financial context.
* '''Actions''': Take steps to make banking in USD and EUR easier. Conduct or commission research. Contact financial institutions that may have appropriate inter-currency experience.
* '''Priority''': No data
* '''Assigned to''': No data
* '''Start date''': No data
* '''End date''': No data
* '''Deliverable''': Stable Simple International Banking Arrangements
 
===Strategy D7: Fundraising for OSMF===
 
Unplaced text:
*fundraising and budgeting
*strategic diversification and leverage of OSMF’s unique position
*limits on expenditures and growth of overhead
*Administrative support for the Board
 
====Task D701: Fundraising Pitch Document====
* '''Description''': A document that records the selling points and sales media to be used by OSMF volunteers approaching potential donors. The Pitch document, and amendments to the document, must be approved by the OSMF Board
* '''Action''':
* '''Deliverable''':
====Task D702: Fundraising Policy Document====
* '''Description''': A document that defines the range of acceptable and unacceptable fundraising practices as approved by the OSMF Board
* '''Action''':
* '''Deliverable''':
====Task D703: Fundraising Guidelines Manual====
* '''Description''': A manual for people engaged in fundraising. It sets out best practice for fundraising as well as practical advice on how to maximise fundraising opportunity, sustain committed funders and avoid alienating funders.
* '''Action''':
* '''Deliverable''':
====Task D704: Donor Relations Management====
* '''Description''': Software, similar to CRM software, that allows recording of contacts made with potential and existing funders and a log of the outcomes of such contacts. Serves as institutional memory to ensure volunteers working on successive fundraising rounds done over many years are aware of previous donations (or refusals) by any one potential or confirmed donor.
* '''Action''':
* '''Deliverable''':
====Task D705: Learning to Work with Donors====
* '''Description''': Donor funding from outside the mapping industry has long supported OSMF. It is common that Donors like to know their funds are in good hands. Corporate reputation is very important when making funding applications. OSMF has to be consciously aware of the information needs of most corporate donors and must provide to them the basic financial and project information that they require to support any application for funding. Donor preferences are quite varied. Some prefer funding discrete projects. Others may be open to funding operational expenses or might be interested in funding an endowment to enhance the financial resilience of OSMF.
* '''Actions''': Determine the operational and financial data, organisational profile and reputational information that will be required by the majority of OSMF relevant donors.
* '''Priority''': No data
* '''Assigned to''': No data
* '''Start date''': No data
* '''End date''': No data
* '''Deliverable''':
Craig Allan
797

edits

Retrieved from "https://osmfoundation.org/wiki/Special:MobileDiff/10106"