The good, bad, and the ugly Technology implementations Silona Bonewald Founder of Leagueoftechvoters.org [email_address]
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
Really boils down to… Poor design  Bad management
Budget Analysis Design (see if something has already been written) Implementation Testing repeat
For example… Business process and equipment inventory to determine starting pt Determine exactly what you want the new system to do and create an RFP of features Research current implementations  Bid this out Communicate what this means to all levels in your org, employees, board, supporters, volunteers Training for all during and before deployment Check in with all volunteers and staff  Determine if current deployment is effective
Unexpected gotcha’s Keeps your information from you No data integration Get an expert to help with design
That said… What are some problems you have had? What are some mistakes in implementation you have seen or experienced?

Thegoodbadandugly

  • 1.
    The good, bad,and the ugly Technology implementations Silona Bonewald Founder of Leagueoftechvoters.org [email_address]
  • 2.
    What makes Techgo 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 downto… Poor design Bad management
  • 4.
    Budget Analysis Design(see if something has already been written) Implementation Testing repeat
  • 5.
    For example… Businessprocess and equipment inventory to determine starting pt Determine exactly what you want the new system to do and create an RFP of features Research current implementations Bid this out Communicate what this means to all levels in your org, employees, board, supporters, volunteers Training for all during and before deployment Check in with all volunteers and staff Determine if current deployment is effective
  • 6.
    Unexpected gotcha’s Keepsyour information from you No data integration Get an expert to help with design
  • 7.
    That said… Whatare some problems you have had? What are some mistakes in implementation you have seen or experienced?