What’s New in ePhilanthropy

Usability testing is a great way to find out how well your web site is really meeting the needs of your audience.  Take a look at Userfly and how Beaconfire is helping Nten to redesign its web site.

Often projects fail because of a breakdown in communication.  No Surprises: The Key to Good Communication offers suggestions on how to keep all stakeholders on the same page.

Need a general list of online services?  Try 100 Online Tools for Non-Profits.

Beth’s Blog consistently offers wonderful material, even when she’s not the author – 4 Keys to Building a Successful Nonprofit Web Site.

Blackbaud is offering a good review of online strategies in a webinar series later this month.  Registration and details.

Some great Nten offerings coming up in September, offering an online version of events usually held live:

Personally, my wife and I are finally moving into our new home Monday, Aug. 17 after living in temporary quarters for the last month.  We’re looking forward to entering the next stage of our lives together.

Tips on Working with an Online Vendor

At my current organization, we’ve just rolled out our first week of going live with Convio for our national walks program, which raised over $6 million in the past year.  Having worked with many online services products, below I offer some tips in maintaining a successful relationship with your vendor:

  1. Take advantage of any training that is available to learn the product.  This enables you to deal with issues more quickly and avoids the situation where support staff impatiently tell you to ‘read the manual’
  2. Develop a rapport with your account manager or whoever has been assigned to handle your relationship.  This includes asking not only what the vendor can do for you, but what your responsibilities are in using the product and dealing with the vendor’s staff.
  3. Document problems over the web;  Convio provides a Salesforce enabled support system which allows me to review calls I’ve placed, and add updates.  If your vendor doesn’t provide this, use your own tracking system, as I did in the past with a product like Elementool.
  4. Be respectful about prioritizing issues.  If a problem is affecting a major application and / or many of your co-workers, make sure the vendor knows this and use escalation procedures.  (Make sure you specifically ask about how to escalate issues.)  If you make every problem into an ‘emergency,’ then nothing will be treated as a high priority.
  5. If you’re dealing with a vendor like Convio that has many modules, learn which products are most actively supported (preferably before you’ve decided on a vendor);  you can find this out by asking which modules are used by the most large clients.
  6. When rolling out a new application, be sure to test exhaustively.  We’re dealing with a problem this week that we might have avoided had we tested a bit more extensively.
  7. Develop a relationship with other nonprofits that are already using the product and take advantage of any online forums (either promoted by the vendor or not) to learn from others and share your own experiences.
  8. Be careful of criticizing your vendor to internal staff.  Even if you’re feeling frustrated on a particular day, don’t vent to your co-workers;  you want them to feel positively about the product you’ve selected despite any occasional glitches that come up. 

Do We Really Need a Custom Application?

Recently I was asked by my organization to do an analysis of technology platforms so that we could plan strategies for next year’s national events.  Over the past year we’ve rebranded our program and are doing a lot more national promotion than in the past, so we wanted to be sure we are on a solid path.

To gather information, I sought out development and technology staff at ten large nonprofit organizations which do comparable events.  Not surprisingly for the nonprofit community, I was gratified by the helpfulness I received from the people I spoke to.  I asked what products they were using, what worked vs. what didn’t, and whether they would make the same choices today that they made in the past.

I wasn’t really interested in which CRM product was best, since what’s best for one organization may be not a good choice for another.  However, I was curious about those organizations that chose to develop customized solutions rather than select prepackaged or hosted applications.  At my current organization, we’ve struggled with multiple vendors in getting screens, processes etc. to work the way we would like them to.  We’ve also heard from some constituents about user interfaces that are confusing or which otherwise make it difficult for them to participate in our programs.

As expected, many of my peers at other nonprofits have struggled to integrate online and offline data;  some are doing only a partial integration; others have tried but fallen short; others have chosen to do data entry into two separate systems.  I am encouraged by the new popularity of ‘open’ alternatives, but it’s too early to report on organization successes resulting from these initiatives.

Generally, organizations that have developed custom solutions reported as much satisfaction as those who have chosen the large eCRM vendors.  Yet, these nonprofits also admitted that system development had been a long, expensive process.  Those who stuck with hosted products explained how they’ve had to closely project manage their vendor to make sure their needs were met as much as possible (as has been my experience).

My summary recommendation to my organization was to attempt a hybrid solution: consider staying with the vendors we have now if they can adapt to our requirements or connect to customized screens / systems developed elsewhere.  I won’t tell my national staff event managers they can’t have what they want but we must be able to clearly document our requirements to give to the vendor or developer.  In addition, we need to be able to differentiate between items that are deal breakers vs. others that would be ‘nice to have.’

I’d like to especially thank these organizations whose staff generously gave of their time to help with my analysis: Alzheimer’s Association, American Diabetes Association, Cystic Fibrosis Foundation, Juvenile Diabetes Research Foundation, Multiple Sclerosis Society and Y-ME National Breast Cancer Organization.

A New Day at Kintera

Since my current organization has used Kintera since January 2005, I eagerly signed up for yesterday’s Nten conference call with Scott Crowder, who joined the firm as Chief Technology Officer earlier this year.  Although I’ve raised nearly $7 million in online fundraising revenues, working with Kintera has been a challenge, especially when trying to integrate with Raiser’s Edge, our offline fundraising software.

In addition to Scott’s arrival, Kintera also hired a new Chief Executive earlier this year, Richard LaBarbera, replacing the firm’s founder who had long held the position.  Recently, Kintera announced a new initiative - Kintera Connectwhich promised a new approach to integrating with other systems, a complete reversal from Kintera’s past strategy.  However, when few details of this program were available, I feared this was mostly talk with little substance.

By agreeing to do yesterday’s call, Scott made himself available for questions by the entire Nten community.  Although Kintera Connect was a main topic, he also addressed many other issues including one that Kintera has always sought to bury – the company’s financial viability.  After detailing many new technical initiatives currently in process, Scott described the firm’s goal of reaching profitability later this year and that they are “almost there now.”

Scott also described how Kintera no longer wants to do “everything for everybody,’ which has led to it having a product which tries to do too many things, not all which it does well.  By opening up to tie in with other systems, Kintera seems to now realize that it must focus on its strengths: e.g. CRM, CMS, advocacy, and leave the rest to others.

Other announcements included:

  1. implementation of Akamai technology to enhance performance
  2. data center migration
  3. sharp increase in capacity to send mass emails
  4. enhanced CMS, replacing current system

Although I’ve often been a critic of Kintera in the past, this conference call shows that the new management at Kintera is determined to set things right.  I’ll wait and see if the results equal the promise, but Scott’s willingness to talk openly is a promising sign.  A recording of the conference call is available at Nten’s site.