Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Technology management for non-technical Leaders

Technology management for non-technical Leaders

Slides from the NZ Connecting Up conference 2014 in Auckland.

Dale Jennings Associates

June 18, 2014
Tweet

More Decks by Dale Jennings Associates

Other Decks in Business

Transcript

  1. Role of Technology Cost E-mail, documents and online presence AND

    essential for critical operational processes AND essential for organisation and service decisions AND is part of the product or service AND is the product or service HOW DO YOU USE TECHNOLOGY? Fundview, Disaster Response Quitline, NZ Navigator Contract for Services Providing Public Services Every Organisation Management effort
  2.  Never consider technology in isolation  Know what technology

    you use – keep a complete list!  Understand your processes – map significant journeys  Manage your technology for performance and contribution – measure both.  Someone should be responsibility for technology development  Try software before you buy  Agree technology guidelines and review annually WHERE TO START?
  3. YOU ALWAYS RETAIN RESPONSIBILITY FOR o Legal compliance o Performance

    management o Defining operational requirements o Managing your data in your systems o Ensuring systems are fit for purpose o Training staff in context o Business continuity planning and provision
  4. SUPPLIERS CANNOT  Be more expert in your work than

    you are  Suggest a technology they don’t sell  Be experts in a new technology the first time they supply it  Manage your staff & volunteers Suppliers rarely suggest something that reduces their income
  5.  Ensure core roles and responsibilities covered  Data quality,

    maintenance and development  Operationally independent project and change management  Separate technology management from operations  Develop a technology “foundation” to guide planning and development  Develop a “vision” for how technology will contribute to your mission  Design intentions e.g. Integrate applications around our finance system  What roles are in-house? Which are outsourced? TECHNOLOGY MANAGEMENT BASICS
  6.  Risk management  Back-ups kept in two places (the

    cloud is only one place)  Controlled access to organisational files/data  Continuity and crisis plans – at least in outline  Security for confidential information  Use databases not spreadsheets wherever possible  Cloud offers far superior security than the “server in the cupboard”  Make technology part of practice  Professional development is needed for everyone  Three skill levels: individual, management and governance TECHNOLOGY MANAGEMENT BASICS (CONTINUED)
  7. USEFUL LINKS  My website www.dalejennings.co.nz has an ever developing,

    free DIY toolbox.  Ask if you want something added!  Connect on LinkedIn to see my postings on charity capability development including (but not limited to) ICT.  The NZ Privacy Commissioner has an excellent plain English guide to cloud computing covering many risk areas as well as compliance. The IITP Cloud Computing Code has more technical details and questions to ask suppliers.  Follow some relevant technical websites  TechSoup NZ for software donations and technical training  Naked Security – for up to date commentary on security and privacy issues  NTEN and Idealware for (American) NFP software comparisons, advice and training If in doubt - Google your question and watch the videos!