Tag Archives: project management

Nonprofit technology and drive-by volunteering: Not a good combination!

scream

This is not a popular point of view, but hackathons and other short term tech volunteering opportunities bring on my anxiety rather than my enthusiasm.  I think of these situations as drive-by volunteerism, and potential disasters for nonprofit organizations.

Let’s switch to a less violent metaphor than a drive-by shooting – we can talk in terms of the perinatal year.  (I’ve worked with programs for teen mothers and their babies, which gave me the idea for the comparison.)

The birth of a child and the completion of a nonprofit technology project have a lot in common:

  • Planning (This does not always happen, but it’s advisable.)
  • Conception (I admit that this generally more fun in cases of human reproduction than in cases of nonprofit technology projects.)
  • Gravidity (This often includes nausea and stretch marks.)
  • Labor (This is usually painful.)
  • Delivery (This can involve emergency surgery.)
  • After care for mother and child (This often includes a hand-over from one specialist to another.)

Perhaps it’s not a perfect analogy; however, it illustrates my point that it’s realistic to think in terms of a twelve-month cycle for the successful implementation of a nonprofit technology project.  A technology implementation does not begin at the labor stage, and delivery certainly does not mark the end.

Skills-based volunteering, especially skills-based tech volunteering, is simply different from spending the afternoon stuffing envelopes on behalf of your favorite cause.

Moreover, volunteer management is a professional skill set in its own right; it requires experience and knowledge of best practices. It’s not something than just anyone can do spontaneously.

Unfortunately, the sort of nonprofit that is most in need of volunteer assistance with its technology – a small, under-funded organization – is the least likely to have a professional volunteer manager on staff, or an IT professional who can take long term responsibility for the tech implementation.

This is why the thought of a short term tech volunteer project for a small, under-funded and highly worthy nonprofit fills me with horror.  The likelihood seems so strong that the long term implications haven’t been considered, and that it might actually be a disservice to the organization.

This is also why I’m deeply grateful that Common Impact, a wonderful nonprofit based here in Boston, has developed a model for skills-based volunteering that is highly effective for tech implementations.  Fortunately for all of us, they are willing to share what they’ve learned.  Tomorrow, Patricia Vaccaro-Coburn of Common Impact will be our featured guest at a TNB Roundtable session on best practices in managing tech volunteers, and I am confident that this will be an enlightening experience for nonprofit professionals who see short-term volunteer tech projects as the solution to their problems, rather than the beginning of new set of challenges.

The Massachusetts Institute of Nonprofit Technology: Let’s Do This!

Massachusetts Institute of Nonprofit Technology

 

We need a Massachusetts Institute of Nonprofit Technology, and I can tell you what degree program we need to establish first:  Bachelor of Nonprofit Data.

The inspiration for this comes from many conversations with many people, but I’d especially like to credit Susan Labandibar, Julia Gittleman, and Laura Beals for pointing out, in their different ways, that one of the most pressing real-life challenges in nonprofit technology today is finding people who can bridge between the outcomes / impact assessment / evaluation / research team (on one hand) and the information systems team (on the other hand) at a nonprofit organization.

Not that I’m a professional full-time data analyst myself, but if I were, I’d find the numbers, and start doing the math:

  • How many brilliant computer scientists are graduating right here in Massachusetts every year from our best high schools, colleges, and universities?
  • Of those graduates, what percentage have strong skills in database design, database development, database management, or data analysis?
  • Of those who have strong data skills, what percentage would be eager to use their geek skills for good, if they were offered an attractive career ladder?

That’s our applicant pool for the Massachusetts Institute of Nonprofit Technology.  (Or MINT, if you prefer.)

Now, let’s figure out the absolute minimum of additional knowledge that these computer science graduates would need in order to be the kind of data analysts who could bridge between the outcomes / impact assessment / evaluation / research team and the information systems team  at a nonprofit:

  • Outcomes measurement
  • Outcomes management
  • Impact assessment
  • Evaluation
  • Social research methods
  • Knowledge management
  • Organizational cultures of nonprofits
  • Nonprofit operations
  • Organizational cultures of philanthropic foundations

That’s our basic curriculum.

If we want to expand the curriculum beyond the basics, we can add these elective subjects:

  • Nonprofit budgeting
  • Group dynamics
  • Ethics
  • Etiquette
  • Negotiation
  • Project management
  • Appreciative inquiry
  • Meeting facilitation

All of these electives would pave the way for other degree programs, in which they would also be extremely useful:

  • Bachelor of Nonprofit Systems Engineering
  • Bachelor of Nonprofit Web Development
  • Bachelor of Nonprofit Help Desk Support
  • Bachelor of Nonprofit Hands On Tech Support
  • Bachelor of Nonprofit Social Media

I already have my eye on some great local colleagues who could be the faculty for the Bachelor of Nonprofit Data program.  In addition to Susan, Julia, and Laura, I’d want to recruit these folks:

Please note that three members of the TNB team top the list of potential faculty members.  Why?  Because I work there, and because TNB has set a Big Hairy Audacious Goal of developing the careers of 1,000 technology professionals. This undertaking would be very congruent with its vision!

However, setting up the Massachusetts Institute of Nonprofit Technology must be a collaborative effort.  It will take a strong network of colleagues and friends to make this happen.

Do you think that this is needed?  Do you think my plan needs a lot of work?  Do you have any ideas or resources that you’d like to suggest?  Please feel free to use the comments section here to share your thoughts.

%d bloggers like this: