The Fragmentation Problem
A teacher in Conakry wants to check her pension status, renew her national ID, and register for a professional development program. Three government services. Three separate accounts. Three passwords. Three verification processes where she uploads the same documents.
She loses a password. The recovery system for one ministry doesn’t work. She visits a government office in person, waits four hours, and starts the process over. Multiply this across 13 million people and dozens of services. That’s where Guinea is today.
Every agency built its own identity silo. No shared standards. No interoperability. Citizens pay the cost in time, trust, and access.
The Idea
One identity. Every government service.
A citizen creates a single verified account — tied to their phone number, national ID, or both — and uses it to access any participating government platform. No more juggling credentials. No more redundant verification.
This isn’t a new concept globally. Estonia did it. India did it with Aadhaar. But Guinea has its own constraints, its own infrastructure realities, and its own opportunities to get this right without repeating others’ mistakes.
What This Actually Requires
The technical side is the easier part. OAuth2 and OpenID Connect give us proven standards for federated authentication. MFA through SMS or biometrics is well-understood. The APIs to let agencies plug in are straightforward to design.
The hard part is everything else.
Government buy-in across multiple ministries, each with their own IT priorities and vendor relationships. A verification infrastructure that works for people in Conakry and people in rural Fouta Djallon. Data sovereignty guarantees that keep citizen information on Guinean soil, governed by Guinean law. Privacy controls that give people real visibility into who accesses their data and why.
And trust. Citizens need to believe this system protects them, not surveils them. That trust is earned slowly through transparency, not promised in a launch event.
Why It Matters Beyond Convenience
A unified identity layer isn’t just about fewer passwords. It’s foundational infrastructure.
Without it, every digital service Guinea builds — payments, healthcare records, education platforms — has to solve identity from scratch. That’s expensive, inconsistent, and fragile. With it, new services launch faster, cost less, and inherit a security baseline from day one.
It also changes the relationship between citizens and government. When people can see exactly which agencies accessed their information and revoke permissions, that’s a shift toward accountability. In a region where institutional trust is hard-won, that matters.
What Connects to This
The Unified Payment Gateway could leverage this identity layer for transaction verification. The Headless LMS API could use it for student and educator authentication. Each project I’m exploring in Guinea’s digital infrastructure reinforces the others.
Where I Am With This
This is early-stage research. I’m studying what worked and failed in other African identity initiatives — Nigeria’s NIN rollout, Kenya’s Huduma Namba, Rwanda’s Irembo. I’m mapping Guinea’s existing government IT landscape and the political dynamics around data governance.
I don’t have all the answers. I have a clear problem, a defensible architecture, and the conviction that Guinea deserves digital infrastructure built for its reality.
If you work in government technology, digital identity, or public sector innovation in West Africa, I want to hear from you: laminekalinko2@gmail.com.