The Future Of Technology
…is the name of the track that I am co-facilitating at NTEN’s Leading Change Summit. I’m a late addition, there to support Tracy Kronzak and Tanya Tarr. Unlike the popular Nonprofit Technology Conference, LCS (not to be confused with LSC, as the company I work for is commonly called, or LSC, my wife’s initials) is a smaller, more focused affair with three tracks: Impact Leadership, Digital Strategy, and The Future of Technology. The expectation is that attendees will pick a track and stick with it. Nine hours of interactive sessions on each topic will be followed by a day spent at the Idea Accelerator, a workshop designed to jump-start each attendee’s work in their areas. I’m flattered that they asked me to help out, and excited about what we can do to help resource and energize emerging nptech leaders at this event.
The future of technology is also something that I think about often (hey, I’m paid to!) Both in terms of what’s coming, and how we (LSC and the nonprofit sector) are going to adapt to it. Here are some of the ideas that I’m bringing to LCS this fall:
- At a tactical level, no surprise, the future is in the cloud; it’s mobile; it’s software as a service and apps, not server rooms and applications.
- The current gap between enterprise and personal software is going to go away, and “bring your own app” is going to be the computing norm.
- Software evaluation will look more at interoperability, mobile, and user interface than advanced functionality. In a world where staff are more independent in their software use, with less standardization, usability will trump sophistication. We’ll expect less of our software, but we’ll expect to use it without any training.
- We’ll expect the same access to information and ability to work with it from every location and every device. There will still be desktop computers, and they’ll have more sophisticated software, but there will be less people using them.
- A big step will be coming within a year or two, when mobile manufacturers solve the input problem. Today, it’s difficult to do serious content creation on mobile devices, due primarily to the clumsiness of the keyboards and, also, the small screens. They will come up with something creative to address this.
- IT staffing requirements will change. And they’ll change dramatically. But here’s what won’t happen: the percentage of technology labor won’t be reduced. The type of work will change, and the distribution of tech responsibility will be spread out, but there will still be a high demand for technology expertise.
- The lines between individual networks will fade. We’ll do business on shared platforms like Salesforce, Box, and {insert your favorite social media platform here}. Sharing content with external partners and constituents will be far simpler. One network, pervasive computing, no more firewalls (well, not literally — security is still a huge thing that needs to be managed).
This all sounds good! Less IT controlling what you can and can’t do. Consumerization demystifying technology and making it more usable. No more need to toss around acronyms like “VPN.”
Of course, long after this future arrives, many nonprofits will still be doing things the old-fashioned ways. Adapting to and adopting these new technologies will require some changes in our organizational cultures. If technology is going to become less of a specialty and more of a commodity, then technical competency and comfort using new tools need to be common attributes of every employee. Here are the stereotypes that must go away today:
- The technophobic executive. It is no longer allowable to say you are qualified to lead an organization or a department if you aren’t comfortable thinking about how technology supports your work. It disqualifies you.
- The control freak techie. They will fight the adoption of consumer technology with tooth and claw, and use the potential security risks to justify their approach. Well, yes, security is a real concern. But the risk of data breaches has to be balanced against the lost business opportunities we face when we restrict all technology innovation. I blogged about that here.
- The paper-pushing staffer. All staff should have basic data management skills; enough to use a spreadsheet to analyze information and understand when the spreadsheet won’t work as well as a database would.
- Silos, big and small. The key benefit of our tech future is the ability to collaborate, both inside our company walls and out. So data needs to be public by default; secured only when necessary. Policy and planning has to cross department lines.
- The “technology as savior” trope. Technology can’t solve your problems. You can solve your problems, and technology can facilitate your solution. It needs to be understood that big technology implementations have to be preceded by business process analysis. Otherwise, you’re simply automating bad or outdated processes.
I’m looking forward to the future, and I can’t wait to dive into these ideas and more about how we use tech to enhance our operations, collaborate with our community and constituents, and change the world for the better. Does this all sound right to you? What have I got wrong, and what have I missed?
This blog post is just one of the many, many reasons we at NTEN are stoked you’ll be joining us in SF, Peter! Hope both LSC’s (and EC) know how happy we are that they approved your participation. 😉
Awesome post, Peter. Underscores why we are so lucky to have you!
“We’ll expect less of our software, but we’ll expect to use it without any training.”
I would actually argue this is a different trend. The consumerization of technology drives this simplicity trend. At the low end of the market, the executive director will give up functionality for usability.
But the winning technology at the low end will not actually give up functionality… they will hard code it… “here are the donor metrics, take them or leave them.” All that promise of analytics & big data will still be there, just not adjustable at the low end of the market.
At the higher end of the market, the drive for end user simplicity belies a massive need for complexity… big data, reporting, analytics, custom business process, workflows, etc.
So this is the interplay of a decision support trend — which means were expecting far more from our software. And the consumerization trend — which means the end user will not really be exposed to everything we’re expecting from our software.