Universal Data Model?
Is the Universal Data Model truly a myth in the nonprofit sector? After all, if such a thing were possible, why hasn’t it already happened in the NPO sector? I think we need to start by deconstructing the definition of the nonprofit sector. Often “nonprofit” is treated as a vertical; however, the reality is that “nonprofit” is a broader categorization comprised of many verticals (Health, Education, Human Services, Environment, etc.). We could probably even dissect those macro level vertical into sub-verticals. When we look at the NPO sector from the sub-vertical perspective, there is clear evidence that a universal data model is possible. All you have to do is look at the thriving ecosystem of software companies that are out there servicing these sub-verticals. Some of these software companies have even been able to more broadly define the data model and extract out to a sector level or macro-level vertical (fundraising software is a prime example). So, there is clear evidence that there is the possibility of a data model that could resonate across organizations.
What would it take for the NPO sector to define a universal data model? I think the most important element may be an understanding that the goal of 100% definition is not possible. If the goal is defining the 80% that is common and providing 20% flexibility/customization, then there is a chance to succeed. This is the model that the more successful NPO software vendors have already adopted.
We can take these same lessons and apply them to the CRM space and more specifically to the thriving Salesforce Ecosystem. Salesforce has afforded the NPO community a stable and secure platform to build upon. The next step is for us to agree on some operating standards for nonprofits. To date, this has been the work of the NPSF community and the non-profit template. The ideal scenario would be if we could agree on a general set of operating standards (i.e. Use of Person Accounts, How Financial transactions are handled, How we use the standard objects, etc.) and encode these standards into V2 of the Nonprofit Template. Doing so, would give us a strong base to operate off of and would allow for the development of Modules that can plug into and extend the V2 template. The Modules themselves would represent the data model of the sub-verticals (i.e. Soup Kitchen, Volunteer Program, Large Event Fundraising, etc.). When we combine the platform with a V2 template and a vibrant ecosystem of Modules, we should be able to achieve 80% or more of the needs of many organizations. There will still be the 20% of customization organizations will need to do in order to fine tune the application to their unique business model and operating procedures.
If we can strive for this goal, it would be a huge leap forward for the entire NPO community and especially the subset of the NPO market that is looking at or currently using Salesforce. If we can get to the point where we put the platform and NPO standards behind us, then we can begin the real acceleration of Module development which may be the beginning of the “Universal Data Model”.
Excellent summary of the knowledge convergence paradigm we are witnessing in the NPO/NGO world. Knowledge tools need to keep up with this trend, and the notion of “good enough for now” modular software will be key to providing good support to NGOs as they scale up and provide ever broader services globally, and donors seek to track these services in ever smaller slices. Software, and even IT, is only useful if it is delivered quickly, not perfectly! Thanks Anand. -SG