Monday, July 30, 2007

Corporate IT vs Nonprofit IT part 1

OK, so my title says part 1, not sure how many parts this will be but I know it is more than one. So here we go.

Why does there have to appear to be such a HUGE gap in corporate technology and nonprofit technology understanding. Over the next few blogs, I will ponder why there appears to be such a large gap in the articles I read on nonprofit tech sites vs the corp tech sites.

First a caveat, I do understand that there are enormous differences in the focus and resources of corps vs nonprofits. We may not need the same level of spending and high tech gadgets, but why do many nonprofits appear narrow in their technology thinking?

OK, so my first example. Right now almost all of the corp tech sites are pushing for business process management or aligning your technology with your business:

Business alignment remains a top priority for IT executives. James Champy offers CIOs advice for turning IT into an integral part of their business operations, and no longer just a service center.

While the nonprofit tech sites are still just offering advice on how to convince your Exec Director why technology is important.

10 Things Every Nonprofit Executive Needs to Know about IT

I am not knocking the content of the above article, I think it is beyond great and should be a must read for every Exec or manager in my organization.

But what I am saying is that maybe a large part of my struggle is that the leadership in nonprofits are so fired up about mission that they lose any understanding about running the business of the nonprofit. Now I have seen the opposite, nonprofit has great mission, hires new exec from for-profit to focus on business and nonprofit looses mission focus. But that is not what I mean. I think that nonprofit leaders often only think of technology as another mission or communications tool, so they never acknowledge the importance of their business technology.

So as an example the org that I work for did not include technology in our new strategic plan and mission focus because it was CEOs and execs that were creating the vision. So now as they go through the next phases of planning, technology is an after thought.

But if you look at the corporate side of the house, the execs get it. They see that solid business practices supported by the best technology creates a foundation that delivers EFFECTIVENESS and well as efficiency.

So I vote that nonprofits continue to be less effective and only use tech as a gadget and not bother to focus on their core business practices supported by solid technology. It gives people like me something to do.

Anyway, cool random things:

Blog from Isoph on online learning, thought they would have done this sooner though. But great content already!

Beth Kanter continues her blog quest for world domination and awesome information. Now she shares a gem about creating demonstrations!

Monday, July 23, 2007

Measuring impact without data

For the last few years my organization has launched a major initiative that has been paraded as a mission imperative. This initiative has the right intentions and a solid foundation that feeds right into the new strategic plan and vision. It is wonderful when it all comes together. But (of course there is a but in this story) it pushes for all of us to start measuring impact, not just outcomes and numbers. Dont just tell us how many people you served and what the objectives were, tell us how those people changed and what else was impacted.

When I hear them talk like that it makes me chuckle a little, not because I disagree, because I do agree. But rather I chuckle because we already have a hard enough time with filling complete and timely 990s, getting simple counts and gathering solid data. So now we expect them to measure real impact? But wait it gets better...

Not only does this new initiative ask for impact measurements, it provides no insight on how to do that, what data to gather, what to track, data standards or any tactical operation changes needed. To their credit after years of this, they finally see this weakness and they are working on it, but (wow there are a lot of buts in this story) the key word is "they" in that sentence. We, meaning the tech and operations staff, helped point out the needed clarity. But it is "they" who are working alone to try to fix this and develop a strategy, "they" have yet to include us in the conversation.

Anyway, I guess the lesson here is that it is not enough for leadership and others to just set a vision and hope people will figure out how to follow it.

Random things I have bumped into lately:

www.capaciteria.org, this seems like a cool site, but it does not appear to get used or to be very active, hmmm. In their words,
Capaciteria is a comprehensive, searchable database directory of administrative resources that help nonprofits leverage their own capacity. It promotes peer review because MEMBERS can comment on and rate individual resource links as well as add useful new links. Like Google, search requests return link results weighted to rise based on ratings and popularity given to them by nonprofit users.

The Anecdote blog offered up an article,
Why people don't use collaboration tools, that I found to be true and interesting. Often we throw a website or technology at a problem to fix it, which will always work, NOT!

Monday, June 25, 2007

LOLnptech, nice humor release, http://lolnptech.blogspot.com/

Congrats to those who created and inspired this humorous blog and what a great name, http://lolnptech.blogspot.com/. Even mentioned by the Chronicle of Philanthropy.

I think the web is a great place for people to escape from the real world and have some fun. The lolnptech is a good example of that.

Dont have anything to say this week though, but there is always next week.

Monday, June 18, 2007

2 steps forward, 1 back or 1 steps forward, 2 back?

In order to make real progress with the use of technology it often seems you have to take some backward steps before moving forward. But when we take those backward steps, do we ever really recover?

Here is an example, an org is about 4 years old, they come up with a great idea to revamp their website and include an awesome platform that transforms their audience into a worldwide collaboration and opens new doors. But in the 2 years it took for all parts to complete the site:
  • their infrastructure and desktops which were donated equipment to begin with, are now 8 years old and are barely operating
  • fiscal management software and data is non-existent
  • operating system on the server hosting the site hasnt been patched
  • credit card #s of donors are not secured
So now this org, with a trail blazing site, is faced with taking large steps backward. But with no funds, expertise or maybe even awareness at what danger they have exposed themselves, all their donors and others to. All this work could go up in a second when the server crashes with no tested backup to restore from or an unnoticed embezzlement.

Or a larger org that decides to move to a new software to meet changing business needs only to find out staff have no computer skills, infrastructure wont support it, desktops cant handle it, etc. So they go ahead with it anyway and begin to fix all the areas they neglected for years, because they just didnt think it was important enough. So the software quickly gets the blame for all the bad things that begin happening like staff quiting, computers crashing, poor IT support, network outages, etc. But in all reality, it was just poor management and funding of the core technology. For the next unforeseeable future though IT has a black eye or two.

Does IT ever really recover from these situations? How do we have direct conversations with the leadership to impress upon them that we have to go back and fix the basics before taking the continual steps forward. Or do we just like taking one step forward and then two back?

Tuesday, June 12, 2007

Is technology the step child in older orgs?

Look at orgs that are over 100 years old, and technology is 10-15 years old. So for 90+ years the org is doing great, growing and so on, then suddenly these silly computer things come along, everyone (even computer companies) say their is a limited market. Then networks, internet, email and more starts coming, please make it stop.

So these large orgs, where they have only ever needed a CFO and COO, are now looking at CIOs. But will that CIO ever be a part of the family as much as the others anytime in the near future?

You can argue this point all you want, but step-children are different than birth children, hence the name difference. I am not saying either is better or worse, just different. Many step families are healthier and more functional than nuclear families, but by definition are different.

So to continue the analogy, if technology has been forced into an older org by the tech staff or even worse by outside parties, then it may by similar definition, is that a step child, that will always be a little different? Does it make a difference if the technology was brought in by the CFO\COO team and gradually built, accepted and created?

I often feel like people in the older orgs may discount technology as just the latest fad that will wear off. They see the importance and will say that, but still treat it differently than the ideas, tools and strategies that were used when the organization was founded. You hear something like, we were founded and have been very successful because of the way we work and we didnt need computers then.

Anyway, not sure I even came close to making sense in my incoherent rambling and you may be dumber for having read this. But I hope someone is able to translate this into a rational thought, if not, there is always next week.

NOTE: please dont argue about how old technology is, many orgs have only been using it heavily for 10 years. Yes many have been using it for over 10 years. And when I say technology, I mean the technology (networks, internet, etc) that is readily available today. Just play along and dont fight the semantics.

DISCLAIMERS: Please dont take my analogy of step families as negative toward them, that was not my intention.