From E-Government to M-Government: Emerging Practices in the Use of Mobile Technology by State Governments
by Jae Moon
IBM Center for the Business of Government (November 2004)
(link to PDF of article)
————-
This article builds on the concept of electronic government by considering the increased usage of mobile information technology. Moon defines “m-government” as “government’s efforts to provide information and services to public employees, citizens, businesses, and nonprofit organizations through wireless communication networks and mobile devices such as pagers, PDAs, cellular phones, and their supporting systems.” I thought that this was an interesting angle to consider, since most of the technologies that we’d played with in class required a desktop computer with an Internet connection. As cellphone technology continues to evolve at breakneck speed, people seem to become increasingly reliant on them to access and exchange information (perhaps tapping on keys more than actually talking on the phone). It seemed logical to consider how to link a public’s fascination with convenient mobile technology and a need to request and receive information and services from their local governments. The article presents a series of m-government best practices and surveys to convey its potential for improving the delivery of public services.
For the most part, Moon’s best m-government practices revolve around fieldwork, such as fire and natural disaster management, public safety, and security concerns. Mobile technology such as Geographic Information Systems, Global Positioning Systems, and basic e-mail exchange all play a part in helping services successfully coordinate effective and efficient responses during time-critical situations. It seems that the investment in m-government is driven by the notion of immediacy as necessity, and not luxury.
The use of m-government is not without its concerns. Moon’s surveys explain that while mobile technology is recognized by governments as providing numerous advantages (portability, convenience, etc.), it also creates issues with standardization and interoperability. Different agencies (or even different departments within the same agency) employ different business practices, including technology applications. It becomes challenging to ensure that systems are able to easily connect with minimal disruption. Establishing a robust technology infrastructure (cellular towers, transmitters, receivers, wireless networks, and the costs involved) is perceived by the surveyed agencies as a major barrier to a full transition to m-government. There are also concerns with the security of data transmitted across mobile networks. How to ensure that data isn’t delayed or intercepted? These are significant concerns for government agencies, and an inherent barrier to expanding m-government offerings that ask the general public to submit private data via a portable device.
That said, government agencies recognize the benefits of m-technology and are moving toward improving its use. Moon’s survey lists the reported affects of mobile technology usage, both positive (e.g., improved efficiency, reduced time and stress demands, and reduced costs) and negative (e.g., increased time and stress, and increased costs). To me, it didn’t seem like that much of a stretch from technology as applied to traditional e-government. Success in technology implementation requires a careful study of the business processes involved, and the open-minded willingness to adapt that process in order to improve it. Unfortunately, this is far easier said than done.
Moon’s conclusions were helpful to articulate, but (at the risk of sounding arrogant) struck me as blindingly obvious:
1) State governments should develop strategic m-government plans, which include enterprise architecture.
2) The strategic m-government plans should include a strong business case.
3) Adequate financial resources will be required to implement m-government in the states.
4) Strong, sustained political leadership will also be required to implement m-government in the states.
5) Implementation of m-government in the states will require intergovernmental, interagency, and intersectoral collaboration.
Okay, but it seemed like that these were general guidelines for implementing any new wide-scale process approach. You could swap out the term “m-government” and replace it with just about anything.
I think that the idea of m-government has an inherent appeal to tech geeks in this age of instant and portable access to information, but a long way to go before it’s of remote interest or practical usage to the general public.