• Save
Lessons Learned from Implementing Single Supporter Systems for Charities
Upcoming SlideShare
Loading in...5
×
 

Lessons Learned from Implementing Single Supporter Systems for Charities

on

  • 641 views

As a project manager and consultant, I have implemented several Single Supporter Databases. I discuss what I have learned: what works and what doesn't and why the people and processes are more ...

As a project manager and consultant, I have implemented several Single Supporter Databases. I discuss what I have learned: what works and what doesn't and why the people and processes are more difficult to manage thant the technology. I also give away a tub of ice cream.

Statistics

Views

Total Views
641
Views on SlideShare
630
Embed Views
11

Actions

Likes
0
Downloads
0
Comments
0

3 Embeds 11

http://www.linkedin.com 7
https://www.linkedin.com 3
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

Lessons Learned from Implementing Single Supporter Systems for Charities Lessons Learned from Implementing Single Supporter Systems for Charities Presentation Transcript

  • Lessons Learned from Implementing Single Supporter Systems Ivan Wainewright [email_address] http://blog.itforcharities.co.uk @itforcharities
  • Agenda
    • What is a Single Supporter System
    • Lessons Learned
    • Q&A throughout the session
    My 5 second summary of the whole seminar: “ It is the People and Processes which are the harder part; the technology is the simpler bit” (NB: Simp ler – not simple…) [email_address]
  • What is a Single Supporter System?
    • Single
    • Central
    • Holistic
    • 360 degree
    • Supporter
    • Customer
    • Donor
    • Fundraising
    • CRM
    • Contact
    • System
    • Database
    • View
    • Solution
    For the purposes of this presentation: Something which enables you to see everything about a defined set of constituents in one place. Of course, the actual system (the 'something') could be a single database or it might be a ‘marketing view’ of several source databases. OR… [email_address]
  • Create a (Strong) Business Case
    • Define scope of contacts
    • Define scope of functionality
    • Objectives and Benefits
    • (Measurable)
    • Top level management support
    [email_address]
  • Manage User Engagement http://blog.itforcharities.co.uk/2010/07/16-ways-to-improve-user-buy-in.html
    • Stop the “But it’s my data… I don’t want anyone else to be able to contact them…” syndrome
    • Address the “I don’t know what I want because I don’t know what a database can do…” issue
    [email_address]
  • We need to define our Business Processes
    • Fit Your Business Processes Around the Software
      • Software design
      • Cheaper & quicker (usually…)
      • May have to compromise with so many views
    • It isn’t easy defining processes
      • And it is hard for users to sign-off documents written in ‘tech speak’ and/or ‘system-specific language’
    • Why do we do something ‘as is’ anyway?
    [email_address]
  • Technology: 4 Lessons
    • Keep it Vanilla Data Migration is tough
            • (but it’s just technology)
    • Integration Implement reporting in is tough initial implementation
    So start early in the project; Get supplier/expert involved; See it as a specific work item [email_address]
  • Just because you have a joined-up CRM system doesn’t mean you can now do joined-up CRM It’s all about the Change Management [email_address]
  • Thank You
    • Ivan Wainewright
    • [email_address]
    • http://blog.itforcharities.co.uk @itforcharities