Tag Archives: budgeting

The telephone analogy (Redux)

This is another article salvaged from my now-defunct first blog.  (Many thanks are due to the Wayback Machine, which enabled me to retrieve a copy.) It was first published in 2005, well before smart phones were prevalent among non-geeks. 

An inherent flaw in the analogy at the time was that telephones, once installed, caused much less trouble to nonprofit executives than the typical IT infrastructure. 

As we flash forward to 2013, with a culture in which smart phones are not only prevalent but offer functions previously associated with information systems, it’s interesting to reflect on how well the telephone analogy has stood the test of time. 

So many of us, inside and outside of the nonprofit sector, devote an inordinate amount of time looking forward to upgrading our phones, and that’s a shocking change. 

One thing that hasn’t changed enough is the failure of many nonprofit organizations to think through the budgetary and operational implications of acquiring new technologies.

The telephone analogy

Fri 11 Feb 2005 10:52 AM EST

Are you a nonprofit/philanthropic professional who is having trouble making the case that your organization needs to bring its technology infrastructure into the 21st century – or at least into the 1990s?

Please allow me to acquaint you with the telephone analogy.*

First of all, can you think of a functioning nonprofit/philanthropic organization whose board, chief executive officer, or chief financial officer would ever say…

  • “… we don’t need to find or raise the money to install telephones or pay our monthly phone bill.”
  • “…we don’t need to dedicate staff time to answering the phone or returning phone calls.”
  • “…we don’t need to orient staff and volunteers about personal use of the phones, about what statements they can make on our behalf to members of the media and the public who call our organization, or about how queries that come into the main switchboard are routed to various departments, or about how swiftly high-priority phone calls are returned.”
  • “…we don’t need to make sure that when donors, stakeholders, constituents, and clients call our main number they can navigate the automated menu of choices.”
  • “…we don’t need to show staff members how to put callers on hold, transfer calls, or check voice-mail now that we have an entirely new phone system.”

Apparently, most mission-based organizations have resigned themselves to the fact that telephone systems are an operational necessity.  Somehow, the leadership finds the money, time, and motivation to meet the organization’s telephony needs.

If only we could get the same kind of tacit assumption in place for every mission-based organization’s technology infrastructure!

I propose two possible strategies, either of which would of course need to be tailored your organization’s culture:

  • Encourage your board, CEO, and CFO to see your technology infrastructure as analogous to your telephone system.
  • Persuade them that your telephone system is an information and communication technology system – and then encourage them to regard other components of the system (such as computers, networks, and web sites) with the same kind of tacit support and acceptance.

I look forward to hearing from anyone who has tried this strategy – or developed one that is even more persuasive.



* N.B.:  I need to warn you in advance that all analogies eventually break down, but this is a pretty useful one, especially since a telephone these days really is the front end of an information and communications technology system.

Why are you always talking about “saving the whales?” (Redux)

This is an article that appeared in my first blog in January 2005.  Many thanks are due to the Wayback Machine, which enabled me to salvage it. 

undefined
11:46AM (EST) on January 20, 2005

Whenever I am speaking or writing on the topic of mission-based technology planning, I seem to end up talking about  “saving the whales.”  Several people have asked me (or teased me) about this, so here are some reasons:

  • I like whales. It’s quite possible that they have forms of language, cognition, and social structure that are as rich as – but completely different from – what humans have developed. For someone with my moderate-progressive values, saving them from extinction seems like an obviously good idea.
  • It sounds like a very straightforward mission, but is actually fraught with complexity and nuance.  I have a sort of fantasy scenario about the disconnect between serious techies and nonprofit professionals.  The techies might be brought in to help a nonprofit organization that exists to save the whales; they get very excited telling the nonprofit team about how they are going to equip all the staff and volunteers of the nonprofit with personal digital assistants (with global positioning systems, naturally) and program them so that the PDAs will start beeping whenever a whale is washed ashore within ten miles of the person with the PDA.  Everyone on staff delves deep into considering whether there’s room in the budget for this exciting but possibly complicated and expensive technology.  Then the Cyber-Yenta does her best to call time-out and remind both the techies and the nonprofit workers that their organization does not actually “save the whales” by going down to the beach with big nets to drag them back into the water.  In fact, what they do is “save the whales” by working for laws and policies that protect the whales.  Can they think of a way that PDAs with GPS would help them do that?  Usually, the answer is no, because legislators and policy-makers won’t consent to being tagged and tracked like wildlife by lobbyists.  In this fantasy scenario, the optimum outcome is that everyone goes back to thinking about technology that actually supports their mission, strategy, and tactics.
  • It’s a great way to introduce the concept of realistic outcomes measurement to a nonprofit organization that is struggling with it.  The introductory question can be:  how many whales do you save a year?  This is actually very difficult to calculate, but is absolutely crucial before moving on to advanced questions such as: how many MORE whales will you save a year with that new technology implementation?

 

%d bloggers like this: