Pointers for Designing Context-Aware e-Government Strategy in Zambia: Context, Issues, and Opportunities

Research output: Chapter in Book/Report/Conference proceedingChapterpeer-review

Abstract

Successful implementation of any e-government interventions or programs is hinged on having a carefully thought strategy which is informed by the local context. It cannot be overemphasized that every contextual setting has unique inherent contextual characteristics, which demand that any e-government interventions be designed bearing those characteristics in mind. In order to understand the contextual characteristics in Zambia, a quantitative research approach is utilized, where methodological triangulation is employed at all stages of the research cycle. The endpoint of this empirical research is that inherent factors that influence adoption of e-government mostly at individual (citizen’s and bussinesses’) levels are understood. The only major limitation of this research is that the sample (408 participants) may not be representative of the 14 million people in Zambia and therefore may not guarantee statistical generalizations. The chapter posits that there is chance that affluent e-Government development can be achieved in Zambia once a context-aware e-Government strategy/roadmap is put in place and followed.

Original languageEnglish
Title of host publicationPublic Administration and Information Technology
PublisherSpringer
Pages345-361
Number of pages17
DOIs
Publication statusPublished - 2014

Publication series

NamePublic Administration and Information Technology
Volume3
ISSN (Print)2512-1812
ISSN (Electronic)2512-1839

Keywords

  • Context-aware
  • Design
  • Strategy
  • e-Government

ASJC Scopus subject areas

  • Management Information Systems
  • Information Systems
  • Public Administration
  • Information Systems and Management

Fingerprint

Dive into the research topics of 'Pointers for Designing Context-Aware e-Government Strategy in Zambia: Context, Issues, and Opportunities'. Together they form a unique fingerprint.

Cite this