This document provides guidance for non-technical managers on budgeting for and managing technology. It addresses allocating 96% of annual budgets to core IT needs and 4% to other technology, the basics of asset management including tracking purchases and disposals, and risks of inadequate documentation for technology systems. The document offers tips and answers questions on budgeting, asset management, and documentation best practices to help non-technical managers oversee their organization's technology successfully.
Zac MutruxCEO, Sarai13 years where the rubber meets the road in nonprofit technologyTech problems are primarily caused by poor management.Solid management makes for solid infrastructureSolid infrastructure makes for solid operationsSolid operations = Mission Impact
:5 MinutesHow many people have dedicated IT staff?How many people in the audience have operational responsibility for technology in their organization?Any “Accidental Techies” in the audience?What are you hoping to get out of this session? (I make no promises)
Multi-million dollar environmental organization in San FranciscoExchange ServerFile ServerWireless NetworkSocial services organization in San FranciscoComputers strained to the breaking pointCan’t upgrade software due to hardware ageVery limited access to tech support
In both nonprofit and for-profit organizations4% - 6% of gross revenue/annual budget3% as absolute floorOrganizations spending less than this are almost always in trouble with their technology
:15 MinutesDoes anyone in the audience know how much they budget for technology?What challenges do you have around budgeting for IT?
What are technology Assets? Ask audience for their inputHardwareWarranty/service contractSoftware licenseSoftware installation mediaSoftware installation key codeInternet domain nameSSL Certificate
Everything has a beginning and an endRisks include:Unscheduled down timeDollars down the drainLoss of dataCash flow impactCompatibility
:15 MinutesHow are you managing assets in your organization?What do you see as obstacles to managing your technology assets?How many people have a single centralized location for software installation files?
Poll audience: does anyone have written documentation of their information systems?Documentation might include:PasswordsLocations/Acknowledgement of ReceiptConfigurationsVendor AccountsService Contracts/WarrantiesProceduresEnd-user documentationTechnical support contacts
What happens when you don’t have documentation?Network Cabling MysteryNonprofit housing developer wanted to add a computer to the networkCould not determine where the cabling ledElectrical schematics lostRisks of Online DocumentationWhat happens when the power goes out?Public Health Organization in OaklandKept passwords in a binderEmployee looked up others’ passwords and was reading email
:15 MinutesWhere do you keep your documentation? Anyone?