Congratulation to Ethan West of Carriage House, the first weekly winner of our blog contest!  Ethan has won a 1.0 GB USB drive.  (To enter in this random drawing, simply post a comment to any article on our blog now through May 31.)

I attended the Bagels & Bytes of Westmoreland County group’s monthly meeting earlier today.  (Bagels & Bytes meetings are peer support groups for professional and “accidental” nonprofit techies or anyone who has an interest in nonprofit IT.)

At one point, we had a conversation that had us all laughing to the point of tears because it “hit home” for all of us.  In a discussion on dealing with computer users, one of our members said he keeps them from “doing stupid things” by giving them a “rueful look” when they ask him about computer issues.  I think all nonprofit techies (and probably quite a few non-techies) have had that look more than once in their careers.  It’s a pretty typical face that is made when a nonprofit worker, especially one who has a full-time position worth of work other than IT, gets pulled away from their regular duties to deal with IT problems they aren’t technically being paid to sort out.

It was a comical conversation at the time, but I got to thinking afterwards.  Is “rueful” the way we want to be perceived as nonprofit techies, professional or otherwise?  Does that reaction lessen our credibility or personal power in any way?  Does it really help us to keep users from doing things they shouldn’t? 

Perhaps a different approach might be more effective and to our own advantage.  If we are feeling rueful, perhaps we are submitting too much to the beck and call of our users, instead of allowing them to make mistakes and not automatically answering their cries every time they yell for us.  They say that you shouldn’t pick up an infant every time it cries because it will associate crying with getting what it wants and keep on using it to manipulate its environment.  Perhaps our end-users have learned to get what they want in the same manner because we have been too responsive.   Perhaps its better to let users mull it over for a while and try self-support first so they learn on their own and become a bit less co-dependent. 

At any rate, I’m thinking out loud here and I’m interested in hearing anyone else’s musings on this subject – please leave a comment if you agree or have a different take on things.

Oh, and as a special treat for my friend Radly Brichards, here’s a little something from the LOLnptech blog:


I subscribe to a Yahoo Group called the Information Systems Forum, the members of which are generally comprised of nonprofit technology professionals and a handful of tech vendors and providers.

A hot and interesting conversation got started via the group’s listserv this morning in which a member asked for advice on selecting software for his organization.  Another member responded that he might check into a popular software review website for advice and ideas.  Then (and this is where all heck broke loose), a vendor responded, criticizing the software review site as “exclusionary” and riddled with conflicts of interest.  The comments flew back and forth afterwards, containing a variety of praises and condemnations of the site in question. (I’m not naming names here because I personally like the site enough, cannot verify the criticisms being thrown in either direction, and don’t want to cause additional harm to its reputation.)

I stayed out of this debate, but it got me thinking.  Fact: Vendors are a necessary part of the nonprofit technology equation.  Fact: Many of them form partnerships with each other as part of their business models in order to keep themselves afloat financially.  What does this mean to the typical nonprofit working with vendors to procure technology services? 

It means that you should be aware of this fact when working with any vendor.  For example, if you request a network upgrade from a vendor and they recommend a Cisco brand router (generally expensive), is it because a Cisco router would best serve your needs, or is it because they are a Cisco partner?  Be wary of vendors selling you technology because of who their partners are, rather than selling you the best choice of technology for your organization and its budget.

This may make you wonder – well, what about the Bayer Center?  All those vendors exhibiting at our TechNow Conference and listed in the Southwestern PA Technology Resource Directory?  I am happy to report that the Bayer Center is vendor neutral and deliberately so.  I sit through software demos on a regular basis, and almost without fail, the subject of partnership comes up – that we could earn revenue by recommending their product to the nonprofits with whom we work.  And every time, I gracefully decline the opportunity and explain why. 

We take pride in the fact that we are a neutral party when it comes to advising our clients on vendor and software selection.  When we work with nonprofits, we assess needs and locate the hardware, software or vendor that fits them.  No conflicts of interest, no kickbacks for doing so.  It is the nonprofit community whom we serve…period.  Despite the economic condition of our nation and the fact that we have to watch our budget and earned revenues as much as any other organization; we are still committed serving our clients honestly, fairly and transparently.  This may sound haughty, but it’s not intended as such.  It’s simply the model we believe to be the best for the nonprofits we serve.

So…my final advice or thoughts on the matter?  I still believe in forming good relationships with your vendors.  Strong vendor relationships are critical to your nonprofit’s success.  As in any other relationship, however, keep your eyes open and your head clear.  Don’t be afraid to question and don’t blindly accept recommendations.  Do your homework, be aware, and stay informed.  Make thoughtful, intelligent tech decisions of your own accord.

vendorsatthedoorSource: LOLnptech Blog (