I had a delightful time at last week’s meeting of the Boston 501 Tech Club. The theme was technology planning (a topic close to my heart), and Gavin Murphy of Annkissam (a colleague, esteemed client, and friend) gave an outstanding overview that I recommend to any nonprofit professional who has mastered his/her own field and is ready to think about the big picture in technology for his/her organization. Naturally, during the Q&A time after Gavin’s presentation, I did some nitpicking on the topic of metrics, but never mind. What you see below is the complete set of Gavin’s notes for this presentation, with no editorial changes from yours truly. Many thanks are due to Gavin for permission to post his notes!
Presented at the Boston 501 Tech Club
Chief Operating Officer
1. What is Tech Planning?
- “Technology” can means lots of things, from office wiring and networks to social networking and RFID chips.
- Today we will focus on concepts of technology planning that should be universally applicable to whatever planning you need to do.
- One key concept is recognizing that most decisions involve trade-offs; there is rarely a “right” option, rather different options will present different trade-offs (upfront cost, ongoing cost, quality, time, other resources or risks, etc.).
- At the end we’ll talk about some resources that are available for people that are interested in exploring more specific topics, and we’ll also have a short Q&A session.
2. Strategic Alignment
“Plans are worthless. Planning is essential.” – Dwight D. Eisenhower, general and president (1890-1961)
- Technology strategy (and planning) should support organization strategy.
- Show of hands: how many people are part of an organization that has a strategy (and you know what it is, on some level)?
- How many people’s organizations have a technology strategy (and you know what it is, on some level)?
- If you don’t have an organizational strategy, that’s a bigger issue! And, frankly, one that should be addressed first.
3. Why Plan?
“It is not the strongest of the species that survive, not the most intelligent, but the one most responsive to change.” – Charles Darwin, scientist
- Planning will help you be more adaptable to change.
- The act of planning will force you to think through the resources you have to commit to the process (both time and money) and tradeoffs that different options represent.
- The executive leadership needs to be involved in the planning process to some degree, although other staff or by someone from outside the organization can manage the process.
- Even if your plans change, the act of planning will get people engaged in the options and will help to avoid “shiny object syndrome”. Ultimately, planning will help you respond to both expected and unexpected changes to your organization or environment.
4. Planning is a Process!
- It’s not an event, or even a single project (although there could be a project to kick it off or reevaluate things).
- Similarly, planning can produce documents that are quite helpful, but only to the extent those documents are used to guide the decisions of the organization.
- It’s important to budget time and resources to technology planning and implementation, just as you would dedicate ongoing resources to other critical aspects of your organization.
- One potential trap is committing to an ongoing technology obligation without anticipating the resources it will take to maintain; for example, maintaining your own servers or establishing a social media presence.
- It’s possible that technology is not a critical part of your organization, and that’s fine too as long as you are engaging in the process of evaluating tradeoffs to come to that conclusion.
5. Importance of metrics and measurements
- Once you have decided on a strategy, the next thing is to think about is how to measure your progress.
- Metrics are one way to make sure your technology strategy is closely aligned to your organizational strategy.
- For example, if data security is a concern, you might track the percentage of your computers that have AV or disk encryption installed; if outreach is an organizational imperative then perhaps Twitter followers or Facebook friends might be a better metric.
- Metrics should be as quantitative as possible, to minimize the risk that people will make subjective judgments and obscure the true picture of how things are going.
6. Need to set goals and track success (or failure)
- Once you have chosen your metrics, you should set goals for those metrics and track your progress over a preset time period which should be long enough to judge results but short enough to preserve momentum.
- If you succeed in achieving your goals–great! Adjust your goals for the next time period to be a little more challenging and keep trying to meet them. It’s important to avoid “autopilot” goals that are too easy to meet and never adjust up.
- If you don’t meet your goals, that’s ok too. Now you have valuable information and you can either adjust your plan, your metrics, your goals, or the resources you are applying to technology. After a few cycles you should be able to find the right balance and establish a pattern of success.
7. Things went wrong?!
“Everyone has a plan – until they get punched in the face.” – Mike Tyson, Boxer
- If things go wrong, that’s ok! That’s all part of the process.
- The benefit of having a plan is that at least you will know when things are going wrong, which is always preferable (even if nothing can be done about it in the short run) to finding out everything has already gone wrong in the past and now things are in crisis.
“Those who plan do better than those who do not plan even though they rarely stick to their plan.” – Winston Churchill, British Prime Minister
- Volunteer groups: 501 Tech Club, NetSquared, Meetup, etc.
- Orgs: Common Impact, NTEN, etc.
- Mailing lists: Mission-Based Massachusetts, Information Systems Forum, etc.
- Consultants: NCN, lots!
- In house vs external resources; incentives but long term commitment with in house folks, external resources tend to me more expensive but should have particular skills or expertise that might be hard to have in house (too expensive, only need them periodically, etc.)
Tagged: 501 tech club, adaptable, annkissam, anticipation, av, balance, basic concepts, big picture, boston, boston 501 tech club, budget, change, charles darwin, client, commitment, common impact, computers, crisis, cycle, data security, decision, disk encryption, documentation, documents, dwight eisenhower, esteemed client, evaluation, event, executive leadership, external resources, facebook, failure, gavin murphy, goals, high level, in-house resources, information systems forum, introduction, it's not an exact science, maintenance, managing the process, massachusetts, measurement, meetup, metrics, mike tyson, mission-based massachusetts, mission-critical, momentum, ncn, net2, netsquared, network, nonprofit, nonprofit executive, nonprofit technology, nonprofit technology network, notes, nptech, nten, obligation, office wiring, ongoing commitment, ongoing cost, option, organizational imperative, organizational strategy, outcomes, outputs, outreach, performance measurement, plan, planning, planning is a process, presentation, priorities, process, progress, project, q & a, quality, quantitative, resource, resources, results, rfid, risks, shiny object syndrome, social media, social network, strategic alignment, strategic planning, strategic technology planning, strategy, subjective, success, tech planning, technology, technology planning, time, tracking, trade off, trap, twitter, upfront cost, winston churchill