thegoodbadandugly

© 2008 TANO and Center for Community-Based and Nonprofit Organizations at Austin Community College

2007-2008 Certificate in Nonprofit Leadership & Management

The good, bad, and the uglyThe good, bad, and the ugly

Technology implementationsTechnology implementationsSilona BonewaldFounder of [email protected]

2


What makes Tech go bad?What makes Tech go bad? No support Not understanding the

purpose Too much Too little Too complex No backups Not having a policy in place to

deal with errors No restorable backups Multiple databases No change management Data isn’t portable Thinking Free means no cost Partial implementations Not enough budgeted

No training or materials Tech doesn’t match abilities

of staff or volunteers Risks not managed Insufficient governance Underestimating complexity No stress tests Not enough infrastructure No planning for process

changes Wrong language Bad User Interface Volunteers leaving you

stranded Not maintainable Software no longer supported

3


Really boils down to…Really boils down to… Poor design Bad management

4


BudgetBudgetAnalysisDesign (see if something has already

been written)ImplementationTesting

repeat

5


For example…For example…Business process and equipment inventory to

determine starting ptDetermine exactly what you want the new

system to do and create an RFP of featuresResearch current implementations Bid this outCommunicate what this means to all levels in

your org, employees, board, supporters, volunteers

Training for all during and before deploymentCheck in with all volunteers and staff Determine if current deployment is effective

6


Unexpected gotcha’sUnexpected gotcha’s Keeps your information from you No data integration

Get an expert to help with design

7


That said…That said…What are some problems you have had?What are some mistakes in implementation you

have seen or experienced?

thegoodbadandugly

Economy & Finance