How to Read This Report
What This Report Is
This report is the official account of Korea’s e-government experience, told through a teaching case set in District A — a recreated district in the Seoul Metropolitan Government at the verge of the full promotion stage (around 2002). It follows Mayor Lee Young Kwon over two intense days of meetings with central ministries, the National Assembly, an IT vendor, a citizens’ representative, and his own employees. Real-world conflicts — between MOGAHA and MOIC over data ownership, between elected mayors and central bureaucracy, between line departments and outsourced IT vendors — are surfaced rather than smoothed.
The case is a sequel to the 2011 KSP module The Introduction of e-Government in Korea (Young B. Lee). It was designed for interactive classroom use — with fourteen discussion questions — to help developing-country officials and graduate students think through what it actually takes to localize e-government, rather than to celebrate UN E-Government Development Index rankings. Korea ranked first in the UN E-Government Survey for three consecutive years and topped the 2014 E-Government Development Index at 0.94623; the case asks how the rankings were built from below, district by district.
Read this report not as a neutral technical description, but as a subject for critical analysis. There are still two strong reasons to read it: first, it is one of the few KSP modules built explicitly as a teaching case, with the dilemmas left intact rather than hidden. Second, how Korea narrates its own e-government experience — which it presents as visionary leadership, which it relegates to the limitations paragraph — is itself a legitimate object of study.
- Diagnose your country’s e-government challenges using five problem types and identify the most relevant Korean institution, law, or operational practice.
- Explain the four stages of Korea’s e-government development (Initiation 1978–1986; Foundation 1987–1996; Full Promotion 1996–2002; Advanced 2003–2012) and the logic, leading agency, and budget arc of each.
- Identify success-bias patterns in the report (e.g., the UN ranking framing, the smoothing of the MOGAHA–MOIC turf war, the partial treatment of employee resistance) and convert what the report does not say into critical questions.
- Draft a policy memo applying Korean e-government experience critically to a specific developing-country context — choosing what to import, what to modify, and what to reject outright.
How This Companion Is Organised
The Companion is organised by reader problem type, not by report section order. Answer three questions in the 🔍 Diagnose tab and you will be routed to one of five problem types in the 📋 Type Guide. The 📚 Read the Report tab gives a structured compression of the report’s case-and-pillars architecture; the 🔬 Critical Reading tab equips you to question both the District A narrative and the broader KSP framing.
Practitioner path: 🔍 Diagnose → 📋 Type Guide (your type) → confirm First Action
Course preparation path: 📚 Read the Report → 🔍 Diagnose → 📋 Type Guide (all types) → 🔬 Critical Reading
Critical reading path: 🔬 Critical Reading → Check Understanding → Scenario Writing → Further Reading
What Problem Am I Trying to Solve?
Diagnostic Tool — Find Your Type in Three Questions
Korean Experience Mapped to Your Problem Type
Type A Legal Block — Central Laws Choke Local Innovation
‘Our mayor wants to pilot one online service. The central ministry says the law applies uniformly to every district. We cannot move one centimetre.’
Korea’s Experience with the Same Problem
The case opens on this exact wall. In the first meeting of Day 1, Mayor Lee Young Kwon asked Director General Cho at the Ministry of Government Administration and Home Affairs (MOGAHA) whether the central government could amend the laws that constrained District A’s e-government pilot. Cho refused — the law applied uniformly to all 25 districts and could not be re-tuned for one. As Lee and his staff left, Cho called after them sarcastically about a district government starting new programmes by spending hundreds of dollars. The Companion records this not as a one-off bureaucratic obstacle but as the structural condition of any sub-national pilot in a unitary state.
What Korea did, over roughly fifteen years, was not negotiate exceptions. It legislated a new general framework that required the kind of local action District A wanted. The 1988 Self-Governance Act broke top-down centralisation in principle, with elections for local legislative councils in 1991 and for mayors and provincial governors in 1995. The 1995 Framework Act on Informatization Promotion made informatization a national policy with annual master plans. The 2001 E-Government Act, drafted under the President’s Special Committee for E-Government, anchored inter-agency duties and created the statutory space inside which a district mayor could pilot legitimately. The legal ladder pre-dated most of the pilots that ran on it.
Mayor Lee did not get an exemption. He got a new general law that made his pilot legal — and made every other district’s subsequent imitation legal too. The right unit of negotiation with the central government is the statute, not the case.
Where to Read in the Report
| Priority | Section | Why read it |
|---|---|---|
| 🔴 Essential | pp. 9–11 | Self-Governance Act 1988, 1991 and 1995 elections, three-level government structure |
| 🔴 Essential | Day 1, Meeting 1 | Mayor Lee versus Director General Cho — the uniform-application argument made concrete |
| 🟡 Recommended | Exhibit 6 | E-government as administrative reform — Framework Act 1995 and E-Government Act 2001 |
| 🟡 Recommended | Five Pillars: Accessibility | The legal preconditions for online tax reporting and integrated registration services |
| ⚪ Optional | Exhibit 9 | Special Committee for E-Government reporting to the President — the coordination architecture |
Statutory anchoring is transferable and indispensable. The Korean three-rung ladder — autonomy law, framework informatization law, e-government law — can be condensed into two laws in most contexts but rarely into one. Do not let the urgency of the pilot push you into negotiating one-off exceptions; redraft the general law and the pilot becomes routine.
Identify the one provision in your existing public-administration law that most directly blocks the online service you want to deliver — a wet-signature requirement, a paper-receipt rule, a single-channel mandate. Draft a one-page amendment note: the existing provision, the proposed replacement, the safeguard that addresses the original concern. The page is the seed of every subsequent statutory move.
Type B Budget Squeeze — Defence, Welfare and Education Crowd Out the Pilot
‘We have one million dollars from the central seed fund. We need another million to finish. The legislature says national defence and social welfare come first. They are not wrong — and the pilot still has to ship.’
Korea’s Experience with the Same Problem
In the second meeting of Day 1, Mayor Lee asked Congressman Kim — a former mayor of District A, now sitting on the National Assembly’s Security and Public Administration Committee — for an additional one million dollars to complete the pilot. Kim refused, and the case spells out exactly what the pilot was competing with. The Ministry of National Defence had filed a supplementary budget request for one hundred eighty million dollars in response to North Korean nuclear threats. The ruling party had committed nine hundred fifty million dollars in the first year alone to expand social-welfare coverage for the aging population. The Ministry of Education estimated fifty million for teacher and principal re-education. Against those, a two-million-dollar local e-government pilot was a luxury — and the case acknowledges that Kim was not wrong.
What Korea did with the budgets it actually had is the more useful lesson. Exhibit 13 shows the entire national e-government budget growing from 5.0 million dollars in 1996 to 16.1 million in 2002. Exhibit 14 breaks down 4.7 million dollars spread across eleven main projects over four years — Civil Petitions (G4C), Home Tax Service, the e-procurement system (G2B), the National Education Information System, the four social-insurance linkage, and the Government Seal and Signature System. None of these was lavishly funded. What they shared was a phased architecture, a clear cost-saving promise to the finance ministry, and an institutional home that could absorb a one-year appropriation without losing momentum when the next year’s budget was cut.
Eleven flagship central projects shared roughly 4.7 million dollars across four years. The lesson is not that Korea had money — it is that Korea built the architecture so each project paid for the next one through measurable administrative cost savings, not through a larger appropriation.
Where to Read in the Report
| Priority | Section | Why read it |
|---|---|---|
| 🔴 Essential | Exhibit 13 | Annual national e-government budget 1996–2002 — the modest scale at each step |
| 🔴 Essential | Exhibit 14 | Budget spending on 11 main projects — G4C, HTS, NEIS, e-procurement, government seal |
| 🔴 Essential | Day 1, Meeting 2 | Mayor Lee versus Congressman Kim — the three competing national priorities, named |
| 🟡 Recommended | Exhibit 11 | District A annual budget 1990–2005 — the gradual 3 to 4 percent annual growth |
| ⚪ Optional | Five Pillars: Capacity Building | How a small permanent IT department absorbs one-year appropriations without losing continuity |
The pattern is highly transferable: do not ask for a large appropriation up front, ask for a small seed plus revenue-retention or administrative-cost-saving redirection rights. The 4.7-million scale of Korea’s central projects across four years is matchable for most middle-income countries; the architecture and the institutional home are what need to be built first.
Build a one-page benefit-cost note for one administrative process in your office — issuing a single certificate, registering a vehicle, paying one fee. Count today’s staff-hours, postage, citizen visits, and error rates. Project the saving under an online version, even with conservative assumptions. The note converts your budget request from a digital aspiration into a fiscal argument the finance ministry can defend without sacrificing national security or welfare priorities.
Type C Data Walls — Central Hoarding Versus Local Need
‘The central data centre holds every citizen record we need. They will not share. The reasons given — privacy, cyber-terror, accuracy — are not unreasonable. The citizen still has to make seven separate trips.’
Korea’s Experience with the Same Problem
The third meeting of Day 1 puts this conflict on the table directly. Mayor Lee asked Director Park of the Special Task Force on the Government Integrated Data Center at the Ministry of Information and Communication (MOIC) to release vehicle-registration and resident-registration data so District A could build a parking-fee payment system and a vehicle-ownership fee system. Park refused. The Special Task Force had invested five million dollars in new servers and storage and another five million in data gathering and security; releasing the data ran against the privacy, cyber-terror and digital-vulnerability concerns the central government held tightly. The case is unusually candid about the institutional cause: MOGAHA and MOIC were running parallel e-government programmes with parallel data centres, and the inter-ministerial coordination needed to settle the question did not yet exist.
The eventual settlement, visible in Exhibit 18, is the most quietly important institutional invention in the entire report. The Administrative Information Sharing Center was built not as a data centraliser but as a relay layer. The info-using entity (e.g. a district government) requests information from the info-owning agency (e.g. the resident-registration authority) through the Sharing Centre, which handles authentication, access-permission checking, log and trail management, and the actual transmission. Privacy is addressed by audit logs and prior consent of the civil applicant; ownership stays with the issuing agency. Shared information expanded from 20 types in 2003 to 92 types by 2010, and from 269 administrative agencies to 422 administrative, public, and financial agencies. Exhibit 19 shows the citizen-side effect: a passport application that once required four separate certificates plus the application itself now requires only the application.
Korea did not resolve the data-sharing fight by deciding who owned the data. It built a relay layer so the question could be left undecided. Privacy and cyber-security objections, the bureaucracy’s veto language, were addressed by audit logs and consent — not by centralisation.
Where to Read in the Report
| Priority | Section | Why read it |
|---|---|---|
| 🔴 Essential | Day 1, Meeting 3 | Mayor Lee versus Director Park — the data-ownership argument and the MOGAHA–MOIC turf war |
| 🔴 Essential | Exhibit 18 | Flow chart of Administrative Information Sharing — info-using entity, relay centre, info-owning agency |
| 🔴 Essential | Exhibit 19 | Before and after — 7 certificates for passport issuance collapsed to one application |
| 🟡 Recommended | Five Pillars: Consolidation | The three levels — management, technology, data — and why none of them works alone |
| ⚪ Optional | Five Pillars: Collaboration | Intergovernmental, interagency and inter-sectoral collaboration in three phases — initiation, development, integration |
The sharing-relay architecture is transferable and addresses the privacy objection without requiring data centralisation. What is not directly transferable is Korea’s background reliance on the Resident Registration Number as a stable join key across agencies. In jurisdictions without a strong national identifier the relay must work on probabilistic matching, which is slower, more contested and produces a different political economy of consent.
Pick one citizen service in your country that today requires more than two certificates — driver licence, business registration, tax-clearance, building permit. Map the agencies that hold each certificate and the legal basis for each holding. That map is the seed of your sharing relay; the one bilateral data exchange with the largest reduction in citizen visits is your first negotiation.
Type D Vendor Lock — Outsourcing the System You Stand Behind
‘The vendor built it. Our staff cannot operate it. The contract is for one year. When the citizen complains, they call us — we forward to the vendor — we wait. Who is actually accountable here?’
Korea’s Experience with the Same Problem
The fourth meeting of Day 2 puts the outsourcing dilemma on the page with unusual honesty. Mayor Lee met President Choi of Cloud-Computing Technologies, Inc. — a global firm with 13.6 billion dollars in revenue, opening a Korean office in 2002. Lee raised three concerns that translate to almost any developing-country e-government context. First, IT staff are technology-centred and lack administrative process knowledge; district staff are administrators who cannot evaluate technical work. Second, one-year contracts will not survive the next budget cycle, and if the pilot does not succeed the vendor loses its investment. Third, when a citizen complains, the district will be blamed regardless of which side caused the defect, but the technical knowledge to fix it sits with the vendor. President Choi was non-committal; Lee left without an agreement.
The report’s five-pillar response — under Capacity Building — is the institutional answer. District A planned a centralised IT department (Exhibit 17): one manager and twenty professionals and staff, split into IT Planning (five general staff and four IT professionals), System Development (six IT professionals), and IT Training (five general professionals). An IT Committee was constituted with the vice-mayor and two Chief Information Officers from different departments, providing general oversight and an advisory role. Cross-learning was made explicit: district staff learned from outsourced vendors, and vendors learned the district’s business processes. A performance-based personnel management system rewarded employees who built e-government training and usage records. None of this is technically impressive; all of it is institutionally hard.
The district contracts the work; the district owns the accountability. A small permanent IT department with the legal authority to receive and audit vendor outputs is what makes outsourcing safe. Without it, every vendor cycle erodes tacit knowledge — and the accountability gap to the citizen widens.
Where to Read in the Report
| Priority | Section | Why read it |
|---|---|---|
| 🔴 Essential | Day 2, Meeting 4 | Mayor Lee versus President Choi — three concerns about outsourcing made concrete |
| 🔴 Essential | Five Pillars: Capacity Building | IT Committee, centralised IT department, training programmes, performance-based personnel |
| 🔴 Essential | Exhibit 17 | District A’s IT department structure — Planning, System Development, Training |
| 🟡 Recommended | Five Pillars: Collaboration | Inter-sectoral collaboration with vendors across initiation, application development, integration phases |
| ⚪ Optional | Day 2, Meeting 6 | Ms. Jung and the employees — the manager’s own concern about supervising outside vendors |
A centralised IT department plus transparent online procurement can be set up within twelve months. The harder transfer is the contractual rule for mandatory knowledge transfer between vendor and district staff — without it, the district loses tacit knowledge with every contract cycle and ends up running a system it cannot itself operate.
Audit one current IT contract in your office. List every place where the vendor holds knowledge that no public servant could reproduce within a week — credentials, source code, configuration scripts, vendor-specific data schemas. Each line is a knowledge-transfer requirement to insert at the next contract renewal, and a personnel decision your IT director should make before that renewal.
Type E Citizen Channel — E-Participation Against Bureaucratic Resistance
‘We launched a citizen petition site. The bureaucracy hates it. Elected officials say it bypasses formal representation. The mayor is afraid the city government will warn him for being too close to citizens. Do we still build it?’
Korea’s Experience with the Same Problem
The fifth meeting of Day 2 raises a tension the report does not flinch from. Mrs. Hwang, Citizen’s Representative of District A, told Mayor Lee that for genuine transparency, district meetings should be broadcast online and a web-board should accept citizen petitions. Currently, only the Citizen’s Representative could attend the quarterly financial and management hearings, and citizens collected paper-signed petitions house by house. Some residents already suspected Mrs. Hwang of filtering the meeting results. Mayor Lee’s discomfort in the scene is unusually honest — his predecessors had received warnings from the Seoul Metropolitan Government for not keeping a certain distance from citizens.
The five-pillar response under Participating Citizenry built four channels: free training at the District’s Academy Hall, with explicit targeting of the elderly and the disadvantaged; a web-board for online petitions replacing paper signatures; online broadcast of senior meetings with publication of official documents; and a programme called We Ask Our Mayor that paired the official portal with social media for direct Q&A. The sixth meeting of Day 2 surfaced the symmetrical bureaucratic worry: Ms. Jung, representative of District A’s employees, reported that staff feared the new system would destroy jobs and reengineer routine workflows out of existence. The case treats the employees’ concern as legitimate and meets it with managerial and IT training programmes, not by walking back the e-participation features. By 2009, Korea’s UN E-Participation Index reached 1.0 — the maximum (Exhibit 1).
E-participation tools are cheap and easy to deploy. What makes them work is the political settlement underneath — elected officials accept that direct citizen channels reduce the buffering value of formal representation, and bureaucrats accept that their evaluations become more visible. Without that settlement the tools become symbolic, and citizens learn that.
Where to Read in the Report
| Priority | Section | Why read it |
|---|---|---|
| 🔴 Essential | Day 2, Meeting 5 | Mrs. Hwang on transparency, web-board petitions, online broadcast of meetings |
| 🔴 Essential | Day 2, Meeting 6 | Ms. Jung and the employees — fear of job loss and the capacity-building response |
| 🔴 Essential | Five Pillars: Participating Citizenry | Training, web-board, online Q&A, and the bureaucratic tensions that remain unresolved |
| 🟡 Recommended | Exhibit 1 | Korea’s E-Participation Index — from 0.48 in 2003 to 1.0 by 2007 |
| ⚪ Optional | Discussion Question 8 and 10 | The gap between citizen expectations and bureaucratic capacity — the question the report leaves open |
The tools are inexpensive and easily transferred; the political settlement is not. In contexts with weaker traditions of public consultation or stronger executive dominance over the legislature, the same web-board can become either a complaint channel that bureaucrats ignore or a mobilisation tool that destabilises ordinary policy work. Decide which settlement you actually have before you launch.
Open one decision your office routinely makes — a parking-fee schedule, a permit-fee adjustment, a service-hours change. Publish the draft and a fourteen-day comment window on a single web page, with a named person responsible for replying. The exercise tests whether your bureaucracy can survive the visibility and shows exactly what to fix before broader rollout.
The Whole Terrain of the Report
1 Introduction — Why the District A Case Matters
1.1 The narrative the report opens with
The report opens on Korea’s rankings. By 2014 Korea topped the UN E-Government Development Index at 0.94623, ahead of Australia (0.91034), Singapore (0.90762), France, the Netherlands, Japan, the United States, the United Kingdom, New Zealand, and Finland (Exhibit 2). Korea had ranked first in the UN E-Government Survey for three consecutive years. In 2011 seven government projects across five ministries received the UN Public Service Award. Exhibit 1 traces the climb: the E-Participation Index moved from 0.48 in 2003 to 1.0 — the maximum — by 2007 and stayed there. The E-Government Development Index moved from 0.74 to 0.94 over the same interval.
The authors then immediately undercut their own opening with a sentence that is essential to read carefully: industrial and technological advancements do not always translate into transparency in governance and Korea was no exception of this phenomenon. The two short paragraphs that follow describe the centralised political culture that confined Korean governance through the 1900s and the 1988 Self-Governance Act that began to break it. This is the case for treating Korea’s top ranking not as the answer but as the question — how was the ranking built, district by district, under what political and institutional conditions?
1.2 Where Korea was when it started
The 1978 Five-Year Plan for Computerization of Government is the doctrinal starting point, but the operational starting point was administrative computerisation inside individual ministries, with no inter-agency network, no online citizen services, and no domestic capacity to plan either. In 1988 the National Assembly passed the Self-Governance Act. In 1991 elections for local legislative councils began. In 1995 elections for city mayors and provincial governors began. Until 1995, mayors and senior local officials had been appointees from the central bureaucracy — and, as the case puts it bluntly, managed their districts according to their own interest rather than residents’ interests. After 1995, elected mayors were free to promote citizen-centred local government culture; Mayor Lee Young Kwon, first elected in 1995, was one of them.
1.3 International comparison the report wants you to make
Exhibit 3 places Korea in three reference groups. The top five — Korea, Australia, Singapore, France, the Netherlands — cluster between 0.89 and 0.95. The middle group (ranks 66–70) — Republic of Moldova, Venezuela, Azerbaijan, Serbia, China — cluster around 0.55. The bottom five — Chad, Guinea, Niger, Eritrea, Somalia — sit between 0.01 and 0.11. The gap is structural rather than technological; the case wants developing-country readers to study the climb from the middle band rather than to imitate the top.
| Country | EGDI 2014 | Group |
|---|---|---|
| Republic of Korea (1) | 0.94623 | Top 5 |
| Australia (2) | 0.91034 | Top 5 |
| Singapore (3) | 0.90762 | Top 5 |
| Republic of Moldova (66) | 0.55708 | Middle |
| Venezuela (67) | 0.55639 | Middle |
| China (70) | 0.54501 | Middle |
| Chad (189) | 0.10761 | Bottom 5 |
| Eritrea (192) | 0.09456 | Bottom 5 |
| Somalia (193) | 0.01387 | Bottom 5 |
Source: UN Public Administration Country Studies Data Center, reproduced from Exhibit 3.
1.4 Development stages — the implicit periodisation
The report partitions Korea’s e-government story into four stages, each with a distinct dominant logic. The same word — infrastructure, service, information sharing — means different things in different stages. Holding the stages in mind while reading later chapters is essential.
| Stage | Years | Dominant logic | Direction |
|---|---|---|---|
| Initiation | 1978–1986 | Administrative computerisation inside individual ministries; no inter-agency network | Internal (G2G) |
| Foundation | 1987–1996 | National Basic Computing Network built between ministries; freely shared information and resources | Internal → external |
| Full Promotion | 1996–2002 | High-speed internet and PCs distributed to public; G2C and G2B services launched; e-government as administrative reform | External (G4C, G4B) |
| Advanced | 2003–2012 | Special Committee for E-Government coordinates inter-agency work; G4C delivered comprehensively; mobile and Hi-speed | Comprehensive service |
Adapted from Young B. Lee (2012), reproduced as Exhibit 4 of the report.
1.5 Why District A — the choice of frame
The case focuses on a single district in the Seoul Metropolitan Government — anonymised as District A — at the verge of the full promotion stage in 2002. Exhibit 10 shows the district’s population around 540,000–560,000 through the early 2000s. Exhibit 11 shows the annual budget growing from around 50 million dollars in 1990 to 450 million in 2005, a 3 to 4 percent annual rate. Exhibit 12 shows public-employee headcount climbing past 1,400 by 2001 with general administrators forming the largest single category. Exhibit 15 records that District A’s largest business sectors in 2002 were computer-related (50,312 businesses, over half a million employees), wholesale and retail, lodging and restaurant, business services, and science and technology services — a profile that made the district one of the most plausible early adopters anywhere in Korea.
The choice of frame is itself an analytical move. The case could have been written as a chronological narrative of the four stages. Instead it slices into one district at one moment and follows Mayor Lee Young Kwon — three-term mayor, former human-rights activist, member of the President’s Special Committee for E-Government — through two days of meetings. Each meeting names one of the structural problems any developing-country official will recognise. The framing is more honest than the index ranking on the cover.
Korea’s top UN ranking is the visible output. The hidden input is twenty-five years of statutory ladder, inter-ministerial conflict, and district-level experimentation under elected mayors. The case is one of the rare KSP modules that lets the reader see the inputs.
The introduction treats the top ranking as evidence of success. Two omissions matter through the rest of the read. First, the report does not interrogate whether the UN E-Government Development Index measures the things citizens actually care about — disclosure of public information, anti-corruption, dispute resolution. Second, the case is set in 2002 but published in 2014, and the twelve-year gap is filled with retrospective tidying. The two days are reconstructed, not transcribed.
2 Policy Design — The Statutory and Planning Ladder
2.1 The political design that pre-dated the technology
The single most important design choice was political rather than technical. The 1988 Self-Governance Act divided Korean government into three levels — Seoul plus six metropolitan governments plus nine provinces at the top; cities, districts (gu) and counties (goon) in the middle; administrative units underneath. It also required municipal legislation to be verified by the central government, which kept top-down channels alive. Without this Act, an elected mayor could not have piloted what District A piloted; without the verification clause, the central ministry could not have refused the pilot. Both halves of the case in Day 1 Meeting 1 — the request and the refusal — are statutory products of 1988.
2.2 The four-stage statutory and planning ladder
The case organises Korea’s e-government plans across four stages. Each stage was launched with a Plan, anchored by a Law, and led by a different organisational vehicle. Exhibit 5 details the Foundation Stage plans; Exhibits 6 and 7 detail Full Promotion; Exhibit 8 lists strategic activities; Exhibit 9 shows the Special Committee structure.
| Stage | Leading body | Anchor law | Major plans |
|---|---|---|---|
| Initiation (1978–1986) | Office of the Prime Minister, line ministries | — | Five-Year Plan for Computerization of Government (1978); Plan to Distribute Multi-functional Office Equipment (1986) |
| Foundation (1987–1996) | Coordinating committees for the National Basic Computing Network | — | 1st and 2nd National Basic Computing Network Projects; Administrative, Education/Research, Financial, Defence, Research network plans (1988–1992); Comprehensive Countermeasures for Information Society (1990) |
| Full Promotion (1996–2000) | MOGAHA and MIC (parallel, often conflicting) | Framework Act on Informatization Promotion (1995) | E-Government Vision and Strategy (1998); Comprehensive E-Government Action Plan (1999); 1st and 2nd NIPMPs |
| Full Promotion → Advanced (2001–2002) | E-Government Special Committee reporting to the President | E-Government Act (2001) | 1st E-Government Plan (2001) — service improvement, administration productivity, infrastructure |
Distilled from Exhibits 5–9 of the report.
2.3 Visions and strategies during Full Promotion (1996–2002)
The Full Promotion stage was organised into three sequential sub-stages (Exhibit 7). The 1st sub-stage (1998–1999) was preparation — e-government demand survey, pilot service operation through an Internet government policy forum, analysis of the feasibility of paperless administration, Y2K resolution, intranet establishment in the central government, electronic-document standardisation, and the legalisation of information sharing. The 2nd sub-stage (2000–2001) established integrated networks — single-window administrative services, exchange of electronic documents between central and local governments, business process reengineering, expansion of the administrative information network down to the local level, and electronic signatures. The 3rd sub-stage (2001–2002) operated the system — digital application and registration, EDI between private and public sectors, non-stop service, an integrated administrative task system, and a supporting system for policy decision making.
2.4 The 1st E-Government Plan (2001–2002) — three strategic areas
Exhibit 8 makes the first formal E-Government Plan unusually concrete. It picked eleven flagship projects across three strategic areas, with explicit budgetary discipline.
| Area | Activity |
|---|---|
| Service for Citizens and Business | Single-window civil-petition portal (G4C); connection of four major social-insurance systems; comprehensive e-Procurement system (G2B); integrated Home Tax Service (HTS) |
| Growing Administrative Productivity (Back Office) | National Finance Information System; informatization of local administration; National Education Information System (NEIS); e-approval and e-document delivery |
| Infrastructure | Electronic seal and signature system; pan-governmental integrated computing environment |
2.5 The coordination architecture — the Special Committee
Exhibit 9 shows the structure of the Special E-Government Committee during Full Promotion. The President sat at the top, the Presidential Committee on Governmental Innovation reported to the President, the E-Government Special Committee reported to that committee, a Working-Level Committee reported to the Special Committee, and a Supporting Team plus four Working Groups (Legal Team, E-Gov Infrastructure Team, Privacy Protection and Security Team, E-Gov Promotion Team) handled the daily work. The architecture is worth pausing over: when MOGAHA and MIC failed to settle their parallel programmes, the resolution came from above — a presidential coordination body, not a memorandum of understanding between equals.
Three laws — Self-Governance Act (1988), Framework Act on Informatization Promotion (1995), E-Government Act (2001) — and a presidential committee to coordinate the ministries that the laws empowered. The hardware and the software ran on this institutional stack; without it, the same investments would have produced disconnected pilots, not a national system.
The chapter treats the statutory ladder as a clean progression. The case body in Day 1 Meeting 1 shows the resistance underneath — MOGAHA officials genuinely did not want to amend uniform legislation for a single district pilot, and the eventual settlement required the Special Committee to lean on them. The Plan-and-Law list is the residue of those fights, not the cause of them.
3 Implementation — Two Days That Show How the System Was Actually Built
3.1 Why the two-day frame
The case authors made an unusual choice. Rather than narrating implementation as a sequence of national plans, they put the reader in Mayor Lee Young Kwon’s office at 7:30 a.m. on the first Monday of August 2002 and walked through six meetings across two days. The decision is honest about what implementation actually consists of: not the issuance of plans, but the negotiated resolution of conflicts between agencies, levels of government, vendors, citizens, and employees. The six meetings map directly onto the six structural problems any localiser will face.
3.2 The six meetings — what each one is for
| Meeting | Counterpart | Structural problem surfaced |
|---|---|---|
| Day 1, 9:00 a.m. | Director General Cho, MOGAHA | Uniform application of central laws — can a single district pilot get legal cover? |
| Day 1, 12:00 p.m. | Mr. Kim, National Assembly Committee | Budget allocation when defence (180M), welfare (950M) and education (50M) compete |
| Day 1, 4:00 p.m. | Director Park, MIC Data Center Task Force | Central data hoarding; MOGAHA–MIC turf war over data ownership and security |
| Day 2, 10:00 a.m. | President Choi, Cloud-Computing Technologies, Inc. | Outsourcing IT applications — culture gap, contract horizon, accountability to citizens |
| Day 2, 2:00 p.m. | Mrs. Hwang, Citizens’ Representative | Transparency, e-petition, online broadcast — political settlement around citizen access |
| Day 2, 4:00 p.m. | Ms. Jung and District A employees | Job security, business-process change, IT capacity gap, vendor supervision |
3.3 Resources at the implementation moment
Several numbers in the case anchor what the district was actually working with. The Ministry of Planning and Budget had allotted one million dollars to District A as a pilot, with discretion to allocate. Mayor Lee’s senior staff calculated that another one million would be needed for application development outsourcing — and Congressman Kim refused the request. The district therefore had to design within the original one million, against a national e-government budget that itself was only 15.0 million dollars in 2001 and 16.1 million in 2002 (Exhibit 13). Eleven main central projects shared 4.7 million dollars across four years (Exhibit 14), with the largest single allocation being Informatization of Local Administration (1.916 million) and the second largest being NEIS (725,000).
| Project (FY1999–2002) | Total spend (USD) | Why named |
|---|---|---|
| Informatization of Local Administration | 1,916,200 | Largest line; the umbrella under which District A’s pilot sat |
| National Education Information System (NEIS) | 725,200 | Politically contested, technically extensive |
| Government Seal and Signature System | 570,000 | Anchor for legal validity of every online transaction |
| Civil petitions (G4C) | 295,900 | The single window — citizen-facing flagship |
| E-Procurement System (G2B) | 287,100 | The business-facing flagship |
| National Financial Information System | 246,500 | The treasury back-office |
| Home Tax Service (HTS) | 192,900 | The first widely-used citizen e-service |
| E-approval and e-document delivery | 172,800 | The inter-agency document plumbing |
| Personnel Policy Supporting System | 150,000 | Central HR plumbing |
| Four social insurance linkage | 95,500 | The first cross-agency data sharing pilot |
| Pan-governmental computing environment | 30,000 | Seed funding for the shared platform |
Reproduced from Exhibit 14 of the report.
3.4 The District A team and its capacity
Exhibit 16 shows the headcount of personal computers in the District A office moving from around 850 in 1995 to roughly 3,500 by 2004–2005 — the visible signature of the Foundation-stage rollout. Exhibit 17 shows the planned IT department that Mayor Lee was building: one manager and twenty professionals and staff, split into IT Planning (five general staff plus four IT professionals), System Development (six IT professionals), and IT Training (five general professionals). The case notes that the IT team had previously sat under the Budget Planning and Computerised Statistics department; centralising the team into a dedicated IT department was itself one of the reforms.
3.5 The settlement at the end of Day 2
The case does not give Mayor Lee a triumphant Friday recommendation. The closing scene has him asking senior staff to devise a new plan on how to implement e-government from each stakeholder’s point of view, looking out the window, and wondering whether he was being reckless and lacking in leadership skill. The honesty is deliberate. The five pillars described in the next section of the report are not what Mayor Lee deduced in two days; they are what the authors reconstructed over the following decade. Implementation in 2002 was a problem still under negotiation — and the reader is invited to sit with that uncertainty.
‘As Mayor Lee returned to his office, he looked out the window and thought he was being reckless for trying what other people would have not done before and worried that he could be lacking in leadership skill.’
Implementation is conflict management on a budget. The six meetings name the six conflicts: legal uniformity, fiscal competition, data ownership, vendor accountability, citizen channels, employee fear. Every developing-country e-government programme has to win all six — usually concurrently, usually with less than two million dollars.
Mayor Lee leaves the case discouraged. The report does not record what happened on Friday — whether the master plan was presented, whether the Prime Minister approved it, whether the pilot succeeded. The closure is deliberate, but it leaves a class question unanswered: by what subsequent decisions did the original pilot become the national pattern? The Companion fills part of this gap in the Outcomes chapter.
4 Outcomes — What the System Delivered and What It Cost
4.1 The headline outcomes
The report names three principal outcomes, each measurable and each carrying a less-visible cost. First, Korea was ranked first in the UN E-Government Survey for three consecutive years through 2014, with the E-Government Development Index at 0.94623 (Exhibit 2) and the E-Participation Index at 1.0 — the maximum — from 2007 onwards (Exhibit 1). Second, in 2011 seven government projects across five ministries received the UN Public Service Award. Third, by the late 2000s the share of administrative services that could be initiated online had risen to roughly 80 percent, and internet penetration reached 57 percent of the population as of the case period.
4.2 The Administrative Information Sharing Center — measurable scale
Exhibit 18 reports the operational scale of the central sharing relay. Shared information expanded from 20 types in 2003 to 92 types by 2010. The number of participating agencies grew from 269 administrative agencies in 2003 to 422 administrative, public and financial agencies by 2010. A single One-Screen Service was developed to show only the relevant fields to officials handling each civil application. Exhibit 19 records the citizen-side effect on a single use case: a passport application that once required four separate certificates (Resident Registration, Certificate of Military Service, Immigration Certificate, Certificate of Family Registration) plus the application itself now required only the application — the four certificates are pulled by the issuing agency through the relay.
| Outcome | 2003 baseline | By 2010 |
|---|---|---|
| Types of information shared between agencies | 20 | 92 |
| Participating agencies in the sharing relay | 269 administrative | 422 administrative, public, financial |
| Documents required for passport application | 4 certificates + application | Application only |
| UN E-Government Development Index | 0.74 | 0.94 (top rank) |
| UN E-Participation Index | 0.48 | 1.0 (since 2007) |
4.3 Stage-by-stage results
The four-stage frame allows the report to claim period-specific outcomes that a single index does not capture. The Initiation stage (1978–1986) produced administrative computerisation inside individual ministries — modest in 1986 but the precondition for everything later. The Foundation stage (1987–1996) built the National Basic Computing Network between ministries through two large project waves (Exhibit 5), establishing the inter-agency network on which Full Promotion could deliver citizen services. The Full Promotion stage (1996–2002) saw the eleven main projects in Exhibit 14 launched: G4C, HTS, NEIS, e-procurement, the National Finance Information System. The Advanced stage (2003–2012) layered the Special Committee for E-Government coordination, comprehensive G4C, mobile access, and the sharing relay scale shown in Exhibit 18.
4.4 District A — the local outcomes
The case credits District A with implementing 71 e-government applications since 1995, under the Smart District — Cyber City Project, ranging from internet civil applications and transactional services to electronic participation applications. The four objectives Mayor Lee originally stated — citizen-centred service, e-government innovation through online services, transparency in local government, increased citizen participation — became the template that other districts in Korea subsequently followed. Korea’s national ranking is therefore not a top-down achievement; it is the aggregation of district-level adoption that began with case studies like District A.
4.5 What the outcomes cost — the parts the report softens
The report acknowledges costs but tends to soften them. Three deserve to be held in mind. First, the parallel MOGAHA and MIC programmes during 1996–2000 produced years of duplicated investment in data infrastructure and competing service portals before the Special Committee architecture (Exhibit 9) imposed coordination from above; the cost of those duplicated years is not totalled. Second, the employees of District A had legitimate fears about job loss and reengineering that the case surfaces in Day 2 Meeting 6 but does not follow into outcomes — what proportion of routine clerical roles disappeared, how were the affected staff redeployed, how did the personnel-management reforms actually treat the transition. Third, the case is set in 2002 but the Sharing Center figures in Exhibit 18 are for 2003 and 2010; the intervening years of negotiation between agencies are compressed out.
The most defensible outcome is the one in Exhibit 19 — citizens stopped needing to collect four certificates for a passport application. Index rankings are political; certificate-reduction is operational. Reporting outcomes in the unit citizens experience is itself a transferable practice.
The chapter is light on negative outcomes. The MOGAHA–MIC duplication is treated as a managerial difficulty rather than a fiscal loss. The displacement of clerical employment is absent. The cyber-security incidents that almost certainly occurred during the rollout are not enumerated. A critical reader should look in Discussion Question 6 for the implicit acknowledgement that the transition costs were real.
5 Lessons — The Five Pillars and Their Boundary Conditions
5.1 The five pillars as analytical frame
The case extracts five pillars from the District A experience and treats them as the lessons portable to other contexts: Accessibility, Capacity Building, Participating Citizenry, Consolidation, Collaboration. Each pillar corresponds, with some looseness, to one of the six meetings: Accessibility connects to Meeting 1 (uniform laws and online registration), Capacity Building to Meetings 4 and 6 (vendor management and employee capacity), Participating Citizenry to Meeting 5 (Mrs. Hwang), Consolidation to Meeting 3 (data sharing), Collaboration cuts across all six. The pillars are not a checklist; they are five lenses through which the same conflicts can be re-read.
5.2 Pillar 1 — Accessibility: from physical to digital
Mayor Lee’s ultimate goal under Accessibility was integrated registrations and payment services online, so that citizens and businesses did not have to go through several administrative procedures before registration. The Satisfaction Survey had identified urgent need for a tax and parking fee payment system and online real-estate registration. With 300,000 businesses registered in District A, the local tax law required businesses to submit reports by regular mail or in-person — a two-to-three-week process per filing. The architectural lesson is the distinction between front end (interoperable IT user interface — software, applications, online portals, easy to use for all ages, free, accessible to elderly and disabled users) and back end (IT infrastructure of database, middleware, and the raw data provided by agencies, supplemented by public records and statistics).
5.3 Pillar 2 — Capacity Building: small, central, accountable
The capacity lesson has three parts. First, technical and managerial competence must coexist in the same IT department; IT experts who cannot manage projects and managers who cannot read a vendor proposal both produce failure. Second, the IT department should be small and centralised (Exhibit 17 — twenty-one people total), with an IT Committee at the vice-mayor level and two CIOs from different departments to handle oversight. Third, performance-based personnel management rewards employees who actually build records of e-government training and usage. Workshops on technical familiarisation, an online procurement system that makes vendor selection transparent, and a strategic plan that gives managers a clear approach to leading the department complete the institutional package.
5.4 Pillar 3 — Participating Citizenry: tools plus political settlement
The participation lesson is the most ambivalent of the five. The four operational components — free training at the District’s Academy Hall with targeting of elderly and disadvantaged users; a web-board for online petitions; online broadcast of senior meetings and publication of official documents; a programme like We Ask Our Mayor combining the official portal with social media — are inexpensive to build. The political conditions under which they actually function are harder to construct. The case names three open issues: conflicts between district legislatures and the mayor over the powers of governance; conflicts between the mayor and the bureaucracy over differing accountability requirements; and the question of how the e-participation system should be standardised across participating governments and platforms. The lesson is that tools without a settled political design become symbolic.
5.5 Pillar 4 — Consolidation: relay, not centralisation
The consolidation lesson has three levels — management, technology, data. Management consolidation runs concurrently with capacity building (Pillar 2): an overseeing IT division reduces personnel, maintenance, and information aggregation costs. Technology consolidation chooses between coordinated contracting versus independent contracting, and between outsourced product development versus joint-venture development. Data consolidation is the operationally consequential one: do not centralise the data, build a sharing relay (Exhibit 18) that enables instantaneous inter-consolidation between district units and intra-consolidation between district, metropolitan and central government, all under strict privacy regulations and data-usage management policies.
5.6 Pillar 5 — Collaboration: three types, three phases
The collaboration framework is the most theoretically developed part of the case. It distinguishes three types of collaboration — intergovernmental (across levels of government), interagency (across agencies and departments within a government), and inter-sectoral (with private vendors and civil society) — and three phases of each: resource allocation/initiation, application development, and application integration. In the initiation phase, visions are set and existing laws are assessed; in the development phase, more complex services such as monetary transactions are built with strengthened security; in the integration phase, applications are connected horizontally (across same-level governments) and vertically (between local and upper-level governments). District A’s Information Systems Plan and Special IT Project Committee are the local-level instruments through which the framework is operationalised.
5.7 Stage-by-stage transferability — what to copy when
| If your country is at this stage | Copy first | Defer |
|---|---|---|
| No real e-government | Self-Governance Act analogue; Framework Act on Informatization analogue; one ministry with clear leadership | G2C portals; sharing relay; e-participation |
| Initiation — back-office only | Inter-agency network; basic computing across ministries; standardised electronic document | One-stop civil-petition portal; PPP for IT |
| Foundation — agency networks built | Special Committee for E-Government (presidential coordination); E-Government Act analogue; CIO appointments | Comprehensive mobile delivery; advanced ITS-style overlay |
| Full promotion — integration launching | Sharing relay (Exhibit 18); business-process reengineering; electronic signature law | — |
| Advanced — comprehensive G4C | Open data; e-participation deepening; cyber-security and AI overlay | — |
5.8 Six key success factors
The case implicitly identifies six factors that made District A’s pilot replicable rather than idiosyncratic. (i) A statutory ladder built before the technology — three laws over thirteen years (1988, 1995, 2001). (ii) A presidential coordination architecture that could settle inter-ministerial conflict. (iii) An elected mayor with a multi-year horizon and a personal stake in the pilot’s success. (iv) A small permanent IT department under district control. (v) Vendor contracts with cross-learning requirements. (vi) Citizen participation channels paired with employee training. Remove any one and the pattern weakens; remove two and the pilot becomes a slide deck.
The five pillars are five lenses, not five activities. The same conflict — central versus local, agency versus agency, government versus citizen, government versus vendor — appears in each pillar at a different angle. A lesson framed pillar-by-pillar transfers; a lesson framed conflict-by-conflict transfers further.
The case is a teaching case and is honest about its limits. Three boundary conditions deserve explicit attention. First, Korea had an authoritarian inheritance that gave it administrative capacity (single Resident Registration Number, professional civil service) most developing countries cannot assume. Second, Korea’s e-government rose with broadband penetration that itself was the result of a separate national policy choice in the 1990s. Third, the District A case is set inside Seoul Metropolitan Government — a wealthy, capital-region district that is the easiest possible localiser. Replication in a poor rural district was, and remains, harder than the case lets on.
6 Conclusion — Overall Assessment and the Unfinished Agenda
6.1 Overall assessment
The District A case is one of the strongest items in the KSP catalogue precisely because it does not flatten its own difficulty. The closing scene of Day 2 — Mayor Lee at his window, wondering whether he is reckless — is the right closing register for a localiser to bring home. The five pillars are honestly extracted from an unfinished story; the report acknowledges that District A’s initiative is presented mid-flight rather than at conclusion. By 2014, Korea topped the UN E-Government Development Index at 0.94623 and held the E-Participation Index at 1.0 — but the case insists that the visible ranking was built on twenty-five years of statutory laddering, inter-ministerial conflict, and district-level experimentation under elected mayors.
6.2 The constraints–solutions table
| Constraint | Korea’s settled solution | The negotiation it required |
|---|---|---|
| Uniform central law blocks local pilots | Self-Governance Act + Framework Act + E-Government Act | Redraft the general law; do not negotiate one-off exceptions |
| Competing budget priorities (defence, welfare, education) | Small phased appropriations; eleven projects sharing 4.7M over four years | Convert each project into a benefit-cost case the finance ministry can defend |
| Central data hoarding versus local need | Administrative Information Sharing Center — a relay, not a vault | Audit logs and prior consent address privacy without forcing centralisation |
| Outsourced vendors run critical systems | Centralised IT department; CIO oversight; mandated cross-learning | Insert knowledge-transfer rules into every contract |
| Bureaucratic resistance to citizen channels | Training plus performance management plus political signalling | Settle the political bargain about visibility before launching the tool |
| Inter-ministerial conflict (MOGAHA vs MIC) | Special Committee for E-Government reporting to the President | The settlement comes from above; equals cannot resolve it |
6.3 The unfinished agenda
Three items remain unfinished in the case and in the broader Korean e-government story. First, the privacy and cyber-security trade-off has not been settled. The sharing relay made data more usable; it also concentrated audit responsibility and created a single point of failure. The case does not enumerate the cyber incidents that almost certainly occurred during scale-up. Second, the displacement of clerical employment has not been honestly accounted for. The case raises the fear in Meeting 6 and meets it with training rhetoric; the actual labour-market outcomes deserve a follow-up study. Third, the political settlement around e-participation remains under negotiation. The E-Participation Index at 1.0 does not mean that the bureaucracy welcomes citizen input — it means the channels exist; whether bureaucrats respond to them is a different question.
6.4 The single message for practitioners
If you have one week back in your office, do not draft the e-service architecture. Draft the legal amendment that will outlast you. Korea’s ranking sits on three laws drafted over thirteen years — the Self-Governance Act (1988), the Framework Act on Informatization Promotion (1995), and the E-Government Act (2001). Without that ladder the same investments would have produced parallel pilots that died at the next election, not a national system.
6.5 First action — concrete and specific
This week, read the 2001 E-Government Act and the 1995 Framework Act on Informatization Promotion. Both are short. Then sit with your country’s closest equivalent — or its absence — and write a single page comparing scope, inter-agency duties, and the institutional home for e-government policy. That page is the seed of every later decision: the coordinating committee, the IT department, the procurement rules, the sharing-relay legal cover. The most consequential e-government failures of the last twenty years have failed not on technology but on the absence of this page.
This Companion is a learning aid produced for the Ministry of Strategy and Finance · KDI School of Public Policy and Management, KSP Knowledge Sharing Program — Localizing E-Government in Korea (2014). Use alongside the original report.
What This Report Does Not Say
1 Success Bias — What the Report Says and What It Leaves Out
The purpose of this report is "to share Korea’s success with developing countries." Look for the traces that purpose has left in the text. A purposeful text always makes choices about what to include and what to omit. A report having success bias does not mean it lies — it means it selects. Reading well is reading what is selected against.
| What the report says | What the report does not say |
|---|---|
| ‘Korea ranked #1 in the UN E-Government Survey for three consecutive years’ | What does the UN index actually measure? Does it weight institutional capacity, citizen trust, or only the existence of online services? Korea’s strength is on what is measured, or on what is measured well? |
| ‘District A implemented 71 e-government applications since 1995 as part of its Smart District — Cyber City Project’ | How many of the 71 applications were actually used, by how many citizens, in their first year? The application count is an output; the citizen-usage rate is the outcome the report does not give. |
| ‘The President nominated Lee because his vision connected with Mayor Lee’s vision’ | What happened to the districts whose mayors did not connect with the President’s vision? The case treats District A as a representative pilot; it was selected precisely because it was a positive deviant. |
| ‘In 2011, seven government projects in five ministries received the UN Public Service Award’ | How many Korean projects were nominated and not awarded? The award rate, not the award count, would let a reader assess whether Korea is unusually effective or unusually good at applying. |
| ‘Internet access already 57 percent of the population’ (case setting, 2002) | What about the other 43 percent? The report does not analyse whether the non-online population received equivalent service through other channels, or whether they fell behind as the online channel became dominant. |
| ‘Information sharing expanded from 20 to 92 types and from 269 to 422 agencies’ | How many cyber-security incidents did the sharing relay produce? The expansion is in the chapter; the security-incident log is not. |
Find Success Bias for Yourself
For each pattern below, find one quotation from the report, write it down, and write the question that hides behind it.
| Pattern of statement | What to look for in the report |
|---|---|
| Index ranking as evidence | Find a sentence with ‘ranked first’ or ‘top-ranked’. Then ask what the index actually measures, and whether the index assigns weight to the things citizens experience (waiting times, error rates, redress channels). |
| Counterpart turned into a foil | The case casts Director General Cho, Congressman Kim, and Director Park as obstacles. Read each meeting twice — once as the case writes it, once from the counterpart’s own institutional perspective. The MOGAHA refusal is not unreasonable; the budget priority is not unreasonable; the data hoarding is not unreasonable. |
| Achievement stated, transition cost omitted | The case mentions employee fears in Meeting 6 but does not return to them in the outcomes. Where in the report would a labour-market impact analysis sit, and why is it not there? |
| Single district treated as national pattern | District A is a wealthy capital-region district with majority computer-related businesses (Exhibit 15). Where would the case sit if rewritten for a poor rural district? The report invites this question (Discussion Question 14) but does not answer it. |
| ‘Reckless’ admitted in mid-text, dropped in conclusion | Mayor Lee’s self-doubt at the close of Day 2 is the most honest line in the case. The five-pillar synthesis afterwards is much more confident. The gap between the two registers is itself a finding worth marking. |
2 Check Your Understanding
Answer the questions below to check your grasp of the report and this Companion.
3 Scenario Writing — What Would You Have Done?
This scenario presents an implementation barrier encountered in the field. The goal is to engage with real-world complexity, not textbook solutions. Read the questions below and write your response freely. Nothing you write is saved or shared.
Scenario
You are Amina Tarek, a 36-year-old deputy director in the Information Society Department of a lower-middle-income country. A new prime minister has been elected on a platform that promised, among other things, an integrated single-window citizen portal — Korea’s G4C named explicitly in the manifesto — to be operational within twenty-four months. The cabinet has approved a seed budget equivalent to 1.2 million US dollars. Your minister has asked you to lead the programme.
Three weeks in, two pressures arrive on the same Wednesday. The Central Statistics and Identity Authority — which holds the national civil registry — writes that under existing privacy law it cannot release individual records to other agencies without each citizen’s prior written consent; the authority’s director has read about the Korean Administrative Information Sharing Center and is sceptical that audit logs alone meet the law’s requirements. Separately, the Mayor of the capital city telephones to say his municipal IT team has already piloted a local petitions portal that he is now ready to scale — and asks for half your budget plus authority over the national rollout. There is no E-Government Act in your country; the only legal instrument is a 1998 Civil Service Regulation that requires every administrative form to bear a hand-written signature.
The minister wants your recommendation by next Monday. The prime minister’s office expects launch within twenty-four months. The Central Statistics director is pushing back on the legal basis. The capital mayor is moving anyway. Your engineering team estimates the integrated portal would consume roughly 60 percent of your seed budget on infrastructure alone, before any application development. What do you write in your recommendation?
Core Tensions in This Scenario
| Conflicting Values | Fundamental question |
|---|---|
| Top-down political mandate vs. legal-statutory foundation | The prime minister wants a 24-month launch; Korea took thirteen years (1988–2001) to build its legal ladder. How honest can you be in writing about the realistic timetable? |
| National integration vs. municipal initiative | The capital mayor is moving without you. Do you co-opt his pilot as the national prototype, or insist on national specification first — and risk losing the only working example? |
| Audit-log privacy vs. written-consent privacy | Korea’s relay solved the privacy objection with audit logs. Your law requires written consent. What is the responsible move — argue for legal change, or design within the existing consent regime? |
Connection to Korean Experience
Amina’s situation is the situation Mayor Lee was in on the first Monday of August 2002, with three differences. First, Lee had the 1988 Self-Governance Act and the 1995 Framework Act already on the statute book; Amina has only a 1998 Civil Service Regulation requiring wet signatures. Second, Lee was the elected mayor — the political principal — and could speak for his district; Amina is a deputy director, two layers below the political principal. Third, Lee operated within a presidential Special Committee architecture that could force inter-ministerial settlement; Amina has no equivalent forum. The report’s pillars recommend almost exactly what the prime minister is proposing — single-window service, sharing relay, citizen channels. The harder question, which the report does not address, is what Amina should do when the political mandate is years ahead of the legal ladder.
Re-read the scenario above and write — on paper or in a document — how you would act if you were Amina. There is no right answer. Draw on your own experience and home-country context; aim for 50–100 words. Nothing you write is saved.
Questions to consider — ① The prime minister has named G4C in the manifesto. What part of that mandate is a legitimate political choice, and what part requires you to push back as a technical adviser? ② Can you propose a phased version — anchor law in year 1, prototype sharing relay in year 2 — that meets the political timetable while building the legal foundation? Is partial proposal honest, or a way to disguise refusal? ③ Should you co-opt the capital mayor’s pilot as the national prototype, or insist on national specification first? Which choice is closer to what Mayor Lee actually did with District A? ④ Have you seen a similar pattern at home? What did the deputy director in that case do — and what would you do differently?
4 Assignments
- a.Summarise the chosen meeting in 3–5 sentences. Quote one original sentence and identify exactly where that material connects to (or fails to connect to) the five-pillar synthesis in the second half of the report.
- b.Is this conflict specific to Korea’s 2002 institutional landscape, or could it occur in a similar form in your own country? Compare against one specific case you have observed.
- c.Why do you think the report presents this meeting as a difficulty Mayor Lee has to manage, rather than as a structural constraint on the five-pillar synthesis as a whole? What would change in the reader’s overall impression if the meeting were treated as evidence against full transferability?
- a.Choose one Korean institution or instrument that corresponds to your type — Self-Governance Act, E-Government Act, Special Committee for E-Government, Administrative Information Sharing Center, IT Committee with vice-mayor and CIOs, We Ask Our Mayor — and evaluate its transferability along three dimensions: legal basis, governance, technical capacity.
- b.What must absolutely be modified before transfer, and what can be imported substantially as-is?
- c.Write the First Action in one sentence. It must specify a responsible person, a deadline, and one success metric.
- ①Current diagnosis — which of the five problem types applies, with evidence from the report and from country data
- ②Two or three Korean institutions or instruments worth learning from — why these, with transferability assessment
- ③Transfer conditions and required modifications — what to change from the Korean original, and why
- ④Roadmap — what to do in months 1–6, 7–24, with the sequence justified (anchor law first, coordination architecture second, citizen-facing services third)
- ⑤Limits of this report — what cannot be learned from it (privacy regime differences, civil-service capacity differences, internet penetration baseline), and where you would look to supplement
5 Further Reading
- Young B. Lee (2012). 2011 Modularization of Korea’s Development Experience: The Introduction of e-Government in Korea. The companion KSP module from which Exhibits 4, 5, 6, 7, 8 and 18 in the District A case are drawn. Reads as a top-down chronological account; the District A case reads as the bottom-up complement. The two together are stronger than either alone.
- Soonhee Kim (2008). Local Electronic Government Leadership and Innovation: South Korean Experience. The Asia Pacific Journal of Public Administration, 30(2), 165. The lead author’s academic version of the District A case (referred to in the case as Gangnam District). The academic article is more analytical and less narrative; reading both makes the editorial choices in the teaching case visible.
- Hyun Joon Kim, Jooho Lee and Soonhee Kim (2008). Making the Connection between Local Electronic Government Development Stages and Collaboration Strategy. International Journal of Electronic Government Research, 4(3), 36–56. The theoretical paper behind the three types and three phases of collaboration in Pillar 5. Worth reading before the assignment if the collaboration framework is the angle of your memo.
- Soon Chul Kim, Hyun Joon Kim and Heejin Lee (2009). An institutional analysis of an e-government system for anti-corruption: The case of OPEN. Government Information Quarterly, 26(1), 42–50. Seoul Metropolitan Government’s OPEN system as a counter-case to District A — same Korean context, different agency, much sharper anti-corruption framing. Useful for stress-testing the District A pillars.
- M. Jae Ahn and Stuart Bretschneider (2011). Politics of E-Government: E-Government and the Political Control of Bureaucracy. Public Administration Review, 71(3), 414–424. Frames e-government as a political instrument, not a technical project. Reading this against the District A case sharpens the question of why elected mayors were the unit of analysis Korea actually used.
- Hyun Joon Kim, Gary Pan and Shan Ling Pan (2007). Managing IT-enabled transformation in the public sector: A case study on e-government in South Korea. Government Information Quarterly, 24(2), 338–352. The vendor-management and inter-agency conflict angle of the Korean story, developed academically. Direct support for Type D (Vendor Lock) memos.
- United Nations Department of Economic and Social Affairs (2014). United Nations E-Government Survey 2014: E-government for the future we want. The methodology behind the ranking the District A report opens on. Knowing what the index actually measures is the precondition for reading any Korean e-government claim critically.
- International Telecommunication Union (2009). E-Government Implementation Toolkit: A Framework for e-Government Readiness and Action Priorities. The implementation framework most cited by other developing-country e-government programmes. Reading it alongside the District A five-pillar framework is a useful comparison of what implementation actually requires.
This Companion is a learning aid produced for the Ministry of Strategy and Finance · KDI School of Public Policy and Management, KSP Knowledge Sharing Program — Localizing E-Government in Korea (2014). Use alongside the original report.