September 2011

AskIdealware: Facebook Scatterplot, Redux

Recently, we posted a Facebook scatterplot called How Many Facebook Fans Should your Organization Expect? that compared the size of organizations' lists against their number of Facebook friends. In this quick Ask Idealware video, Laura Quinn explains how to read that graphic to make the most of it.

Got a question for Idealware? Send us an email and we'll try to answer it in a video.

 

 

Nonprofit Cues from the Retail Sector

Our executive director’s husband, Henry Quinn, is a creative thinker and occasional blogger whose thoughts sometimes stray into topics of interest to the nonprofit sector.

 
I just got back, in my professional capacity, from this year's Shop.org annual summit in Boston, and a couple of things seemed worth sharing here. Obviously, we were talking retail, but the tone of the technology discussion had some relevant features. (I apologize in advance for using marketing rather than nonprofit lingo; hopefully the outside perspective is worth having to do some translation.)
 
  • People were surprisingly negative on social media. I'm a skeptic, and always have been, of its revenue-generating value, but even I was taken aback by how matter-of-fact many of the dismissals of social media were. The recurring theme -- not quite a consensus, but not far from one either -- was, “Look, you have to do social because that's the current state of our target's expectations, but we're not sure why, none of the usual metrics work on it, and you absolutely shouldn't expect any money from it directly.”
 
  • The leitmotif regarding the value of engagement wasn't much better: “Until you can tell me the exchange rate between ‘Like's’ and U.S. Dollars, I have no idea why I want to spend money to acquire ‘Like's.’” It's 2011, we're three years into a massive downturn, and it felt to me that antiquities like “income minus costs equals net revenue” were back in fashion.
 
  • The phone vs. tablet conversations were quite nuanced. If you're trying to incent a relatively simple behavior, there was agreement that phones should be part of the conversation. Selling movie tickets, finding the time of a train, or soliciting a donation for a very specific cause—these were the kinds of things people were talking about on phones. Anything larger, about engaging via the device (rather than executing on existing inclination to spend), the entire discussion was about tablets. I do see this point – until someone invents an app that makes your phone's screen bigger, it's a pretty limited experience. Also, I think that app would make it a tablet.
 
  • Ray Kurzweil, who spoke at the summit, is a very interesting guy and gives a good talk. His likes include exponential curves, and his dislikes include giving any indication that any prediction he's ever made has turned out to be wrong.
 
  • Attribution got its own session, and it totally deserved it. It's a pet obsession of mine -- if I contact a person 30 times, and they donate, how do I allocate that donation to the 30 touches? And what's leftover, the residual portion of donations that came completely independent of (or even in spite of) my efforts? (That is, what's incremental, and what's not?)
 
If you're not thinking about attribution, or if you're assuming that the envelope the donation came in or the email that was clicked through is the whole story, you're shooting in the dark with your promotional spend. It is vital, regardless of the size of your organization, to work on determining what share of each conversion comes from each of your marketing programs. You cannot NOT do this and then go to your board and make the claim that you're doing things that are (or are not) working, because you don't know.
 
  • Those Kiva robot inventory systems are CRAAAAAAAZY! I watched a bunch of them for like 20 minutes and my only disappointment was that none of them responded to my attempts to communicate. (This is a less relevant point unless your organization helps jobless robots, and I guess it's sort of a bummer if your organization helps jobless humans. All I'm saying is, it was really cool.)
 
  • A handful of people were vocally down on QR codes. They generally didn't acknowledge what I think is the most important point: the codes are incrementally free to implement on top of some other effort, which makes the “I” in “ROI” close to zero. There was agreement that they're only effective if you use them to land someone somewhere compelling in service of a conversion. If you land people somewhere dull, it doesn't matter whether they got there with a QR code or not.
 

Things like this summit are really useful for taking the pulse of how people are thinking about technology and ecommerce. Like I said, not all of this is applicable to the nonprofit space, but this was a large group of smart, experienced people, and I thought it might be a helpful
perspective.

How Many Facebook Fans Should your Organization Expect?

In April 2011, Idealware asked a diverse set of nonprofits using Facebook how many people were on their email list, and how many Facebook fans they had. To find out how the two numbers related, we took the results from each of the 477 organizations that answered and plotted them visually.

Wondering how your organization stacks up? Check out the graphic here, and tell us what you think.

 

 

AskIdealware: Cloud Security

Cloud computing seems to be the wave of the future, but how secure is it? Jay Leslie explains the risks and benefits of keeping your data in the cloud in this AskIdealware video.

 

 

 

Is It Time To Worry About Cybercrime?

For the past decade, the bulk of unlawful web-based activities have been profit-motivated: phishing, spam, "Nigerian" money scams, and hacking to get credit cards. This year has seen a rise in politically motivated crimes, most widely exemplified by the loosely-knit group of hackers known as "Anonymous".  Anonymous hackers attack the websites of organizations, be they government, corporate or otherwise that they deem to be repressive or unethical.  In addition to defacing the sites, they've also routinely exposed confidential user information, such as login names, passwords and addresses.  If we are now entering the age where political cybercrime is commonplace, what does that mean for nonprofits?  How can we defend oursleves when we already struggle with basic security on tight budgets and limited resources? 

Two high profile victims were Sony, the gigantic electronics and entertainment conglomerate, and BART, the Bay Area Rapid Transit commuter service.

  • Sony was initially a target for Anonymous after they took legal action against a computer geek named George Holtz, who figured out how to reprogram a Playstation game device in order to play blocked third-party games on it.  This violated the Sony license, but the hacking and gaming communities felt that the license restriction wasn't very fair in the first place. They considered the action against Holtz unwarranted and severe.  Sony also, famously, installed a hacker's rootkit, themselves, on a number of music CDs with interactive computer features, and were sued for that crime.,  Could it be that the hackers were particularly annoyed that this mega-corporation will stoop to their tactics, but sue them for similar actions?
  • BART was targeted for more visceral actions.  Their internal police force shot Oscar Grant, an unarmed youth, in the back a few years ago, and then, again, recently, fired on a homeless man holding a knife, killing him. These actions drew the attention of the community and resulted in protests, some violent.  But BART only drew the attention of Anonymous when they took the step of blocking cell phone service at their four downtown San Francisco stations in order to quell communication about a planned protest.  This action is under investigation by the FCC and has been decried by the ACLU; it was quite likely illegal. Then it was revealed that, at a press conference to discuss the protests, they seeded the audience with BART proponents coached in what to ask and say.  
  •  

Anonymous hacked a dozen or more Sony Websites and three BART websites in protest/retaliation for what they consider to be corporate crime. Here's how easy it was for them: one of the Sony servers containing hundreds of thousands of user account records was running on an old, unpatched version of Apache with no encryption. The initial attack was simply accomplished using a hack (SQL Injection) that is ridiculously easy to block (by updating to a current software version, in most cases). The Administrator password to get into the BART police site was "admin123".  The "hacker" who broke into that site reported that she'd never hacked a web site in her life, she just did a bit of googling and got right in.

These were corporate web sites, run by companies that take in vast amounts of consumer dollars every day, and they couldn't be bothered to do even the minimum amount of safeguarding of their customer's data.  They might not be the criminals, but is it wild to suggest that they were criminally negligent? This isn't a matter of them not having the money, resources or available expertise to protect our data.  It was a matter of them not taking the responsibility to protect it.  

What can nonprofit organizations, that aren't obsessed with bottom lines, do to avoid the problems that BART and Sony have faced?

  • First and foremost, we need to protect constituent data.  If your NPO doesn't have the weherewithal to do that internally, than your online data should be hosted with companies that have strong commitments to security and privacy of customer data. 
  • Second, should breaches occur (and they do), your primary goal should be timely, open communication with the victims of the data breach.  We're getting past the point where our constituents are naive about all of this (Sony has done a great job of prepping them for us).  So your first response to exposed constituent data should be to tell the constituents exacty what was exposed.
  • One uncomfortable situation like this won't kill your credibility, but a history of bad or callous relationships will amplify it.  This is one of the reasons why good social media policies are critical -- the people who can support or sink you when something like a data breach occurs are on Twitter and Facebook, and they'll feed the media stream with support or slander, depending on how well you relate to them.
  • We promote causes online, but we admit faults there, too.  We don't engage customers by lying to them, hiding things that impact them, or dictating the terms of our relationships with them.
  • Our supporters are people, and they have their motivations for supporting us (or not) and their ideas about how they should be doing it.  Their motivations and reasoning might be quite different from what we assume. Accordingly, we should be basing our assumptions -- and campaigns -- on the best feedback that we can coax out of them.  Long-held industry assumptions are suspect simply because they're long-held, in a world where technology, and how we interact with it, is constantly changing.

 

If we ever needed reverse primers in how to manage constituent relationships, the Sony and BART fiascos are prime ones.  They are victims of illegal and unethical behaviour.  But by viewing their customers and constituents as threats, with callous regard for the people who keep them in business in the first place, they've created a public relationship that did nothing to stem the attacks. Sony has put far more money and effort into attacking and dehumanizing their customers with lawsuits and invasive, annoying copyright protection schemes than they have in listening, or trying to understand the needs and desires of their constituents.  BART has tried to block their ears so tightly to shut out public criticism of their violent, shoot first police force that they've crossed constitutional lines of conduct. We -- nonprofits -- know better. It's a two way relationship, not a dictatorial relationship with our supporters, that will serve as our most effective firewall.

AskIdealware: Processing Credit Cards by Smartphone

Collecting credit card payments in the field used to be a lot more challenging than it is now. Amazingly, most of us already have the technology we need right in our pockets. In this AskIdealware video, Kyle Andrei tells you how to process payments by smartphone.  

To learn how to use other tools to accomplish this, or to learn more about this one, read our free article, A Few Good Methods for Processing Credit Cards.

Have a question about technology you'd like us to answer? Drop us an email

Let Nonprofits Know You Provide Social Media Consulting!

Idealware has social media on the brain lately. Over the past year, we've done a lot of work around social media, and based on the eager response from our audience, have no plans to stop anytime soon. Not only are we updating our Nonprofit Social Media Decision Guide for October 2011, but we're also planning a new Social Media Policy Workbook to be released in the first quarter of 2012.

And both of these publications will include a directory of the consultants who can help organizations define and execute social media strategies. The nonprofits using our resources ask us over and over again for recommendations of consultants - purchase an affordable listing in the directory to make sure you're on their radar!

Our Nonprofit Social Media Decision Guide earned us a lot of praise when we published it last July, and we're updating it for an October release this year. But we also received feedback from organizations seeking more guidance and instruction as they began to take social media more seriously. To answer those concerns, we're working with a partner organization to create a second publication that addresses the next stage of social media activity. The Social Media Policy Workbook, to be released in the first quarter of 2012, will walk nonprofits of all sizes through the step-by-step process of creating an internal social media policy and formal documentation to meet the specific needs of their organizations.

Used in conjunction with one another, these publications will map the way for nonprofits to develop comprehensive strategies for external social media practice and internal policy. And both will include the Social Media Consultant Directory to allow them to find consultants who can help in the process.

The benefits to constituents are obvious. The benefits to consultants include getting your name out twice to those specifically thinking about social media strategy - once in October and again in early 2012, in both publications. And the directory is priced to make listings accessible to all--a basic listing starts at just $45.

Make sure nonprofits can find you when they're looking for a social media consultant by buying a listing in our Social Media Directory. Read more or purchase a listing at http://www.idealware.org/social-media-consultant-directory-2011

Have questions? Call or email Andrea at andrea@idealware.org, or call 207-699-4236 x102.

AskIdealware: Augmented Reality

Q: What do Star Trek, the NFL, advertising and trash cans have in common?

A: Idealware's senior researcher, Jay Leslie, who manages to namedrop all of them in his short video explaining "augmented reality."

  

 

Want to know what a technology is, what some terminology refers to, or how to do something with software you're currently doing the hard way? Email us with your question and we'll try to answer it in our AskIdealware video series. 

Biting off more than you can chew?

 Dog eating a watermelonI saw this Harvard Business Review stat that claims one in six IT projects are money pits, going on average 200 percent overbudget and taking 70 percent longer than planned.  I wonder what would happen if we could see only nonprofit IT project performance--what would that look like?  I suspect not much better, and possibly even worse on the scheduling side, as that's certainly been my experience. It makes me think that nonprofit organizations have a tendency to want to bite off more than they can chew when starting a new technology project, and this adversely affects the project.  This may be because the organization doesn't really know what's involved in--for example, setting up a new fundraising database or redesigning their website--or it may be that organizations simply don't allocate staff time for people who aren't "directly involved" on the project.  

Regardless of whether an internal IT person or consultant is assigned one of these projects, it's their responsiblity to make it very clear assistance is required from the rest of the organization, both in terms of staff time required and skills required.  I really enjoyed this post by David Geilhufe on the NTEN Discuss List (of course, you're an NTEN member, right? Right?!) which talks about a few of these issues.

One of the main responsiblities of the IT staff (or consultant) will be to divide the project into easily digestible chunks.  This work entails dividing the project into phases, defining clear business goals, assigning people to the project, and other steps.  Often this simply isn't done, or is hurriedly rushed through because "we need that website live next week!"  This is not a strategy for success, and then the organization gets into a downward spiral of "we need A, but it's taking too long to get, so we'll just assume B, and move on to the next item: C," which ends with no one being satisfied because what was created was not what was expected.

The attitude that "the technology will save us" seems to somehow prevent many organizations from doing much of this up-front work (planning, defining clear goals, process mapping, assigning people to the project, breaking projects down into pieces) required to have these technology projects be succesful.  You wouldn't roll out a new Homeless Prevention Initiative without doing up-front planning, so why would you think IT is any different?

Thoughts from the field?  How are projects handled at your org?  Are you biting off more than you can chew?

Five Tips for A Successful Open Source CMS Project on a Budget

Sometimes it seems like open source CMSs should "just work." Anyone who's built a site in an open-source CMS knows that that's far from true. They often need quite a bit of tweaking to get the job done. And when your org doesn't have a bottomless budget, how can you can you build the perfect site? In my experience, sometimes budget limitations can make a website better. When you have to be disciplined in your approach, it can help to clarify a project in ways that can make it more stable and more sustainable. Here are five tips for making an open-source web project manageable, affordable and successful.

1. Articulate a mission for your project. What are you trying to accomplish with this new site? If you need to reach those goals with the absolute minimum number of bells and whistles, what does that finished product look like? Start there. Write it down, and use it as a touchstone every time you make a decision. On my most recent project, our mantra was “upgrade and simplify." The goal was better information architecture in the latest version of Drupal with a clean design, pared down so that it can be enhanced in the future. Every time our team felt the allure of a big, fancy module that might solve some problems but would increase the chance of bugs, we went back to this mission statement and asked ourselves if there was a simpler way to do it. As a result, we got a more stable site. Which leads me to...

2. Build closely in alignment with your CMS’ development community. After your site’s built on a budget, chances are it will need to be maintained on a budget, too. The point of a CMS is that you should be able to maintain your site relatively easily long after the people who helped you build it are gone. To help ensure that the maintenance of your new site will be sustainable, stick close to core functionality whenever possible. When you want to add a feature, choose a module or plugin that’s heavily used. Check its bug list, and make sure it’s being actively maintained. If you really need something that’s not in heavy use, have a backup plan. Above all, try not to install anything you really don’t need. Check all desired features against your mission. Keep a wishlist of things you want if and only if there’s extra time and money in the budget. In other words...

3. Simplify. Complexity costs money. Some complexity in a mid- to large-sized site is inevitable, and when it truly serves your site’s mission, it can be a good thing. You can put the budget money toward complexity that’s needed by eliminating places where it’s not. In my most recent project, the org had many different content types in their Drupal 6 site including features, press releases and blog posts. If they ever had a good argument for why there should be so many, they didn’t any more, and the press is now used to the blog format. So they merged those three content types into a big new blog area in their new site, and they created thoughtful, flexible categories and tags to organize the posts. This single river of their most frequently updated content is, in theory, easier for them to maintain and promote via social media. Instead of dividing design and development energy across three different content areas, we poured all our time into building the blog really, really well.

4. Make sure the designer understands what CMS design on a budget means. It’s okay if your designer and builder are not the same person, or are not part of the same firm. They should have some familiarity with the CMS you’ve chosen. Most importantly, things go best when the designer is a good communicator and there’s not a wall between design and development. In my last project, my client org ran each design by me (the front-end developer) before they signed off on it. When I saw too much variance in the designs, I let the designer know he needed to make things more template-like, and he responded beautifully. Advomatic has a great post about designing for a CMS.

5. Expect things to go wrong. Especially when you’re working with the cutting edge (or, in some cases, bleeding edge) of open source, things will go wrong. If you can prepare to be flexible, make compromises where needed, and keep your sense of humor, you’ll end up with a better site, and you’ll probably learn a lot in the process. 

For more in-depth minutiae about the project I mention here, check out A Drupal 7 Rebuild for Action Against Hunger.

Photo Credit: Images of Money on Flickr.