Why Design is More Than "Decoration": 5 Surprising Lessons from the Frontlines of Nigerian Tech
Imagine opening your banking app to find a specific payment from three months ago. You tap the magnifying glass icon and type the recipient's name. The screen returns "No results found." You know the transaction happened, yet the system insists it didn't. This frustration is often the result of a hidden technical constraint: the app is only searching the last 20 items visible on your screen rather than your entire history.
This is where Human-Computer Interaction (HCI) moves from academic theory to a daily reality. HCI is the multidisciplinary study of the interface between people and computers, focusing on making technology usable, efficient, and satisfying. In the global design landscape, the Nigerian tech ecosystem acts as a unique "stress test" for these principles. In a constrained environment characterized by limited bandwidth and diverse hardware, design is stripped of its luxury status; it becomes the invisible force that determines whether an app feels like a tool or a barrier. The following lessons reveal how we can bridge the gap between system logic and human life.
1. The Kuda "Glitch" and the Illusion of Control
A significant UX failure identified in the Nigerian fintech space involves the Kuda Bank transaction search. The app's history displays 20 transactions at a time, and the search function is limited only to those visible items. However, users approach the search icon with a "global search" mental model, assuming it will scan their entire account history.
This violates Shneiderman's 7th Golden Rule: Support Internal Locus of Control. This rule dictates that users should feel they are the initiators of actions and that the system should respond predictably. When a system silently limits a search scope, it strips the user of that control, making the system feel arbitrary rather than responsive.
The solution lies in Feedforward, a concept popularized by Don Norman. Unlike feedback, which tells you what happened after an action, feedforward provides information before the user acts so they can predict the outcome. For example, replacing a bare icon with a labeled input like "Search all transactions" immediately aligns the System Image with the user's expectations.
"Users carry a mental model built from prior experience... where a search icon always means 'search everything.' Kuda violates this expectation by silently limiting the search scope without informing the user. The system acts on different terms than what was communicated, stripping the user of meaningful control." — Kuda Transaction Search Analysis
2. "Design is Access": Why Minimalism is a Luxury
While Western design often prioritizes a "clean" aesthetic full of high-resolution animations, Nigerian platforms like Kippa (an SME bookkeeping tool) and LekeeLekee (a social platform) demonstrate that minimalism is often a functional requirement rather than just a style.
In these contexts, design must prioritize "low-device compatibility." This means intentionally removing heavy graphics to ensure the app runs on entry-level Android devices. However, "Access" in the Nigerian digital economy goes deeper than aesthetics; it requires offline functionality. Designing for an environment where data connections are intermittent means the system must allow users to record transactions or draft messages without a persistent network. Removing animations is not "bad design"—it is a strategic necessity to expand user reach.
"In Nigeria, design is not decoration; it is access." — Cindy Shontan
3. The NIMC Portal and the Two "Gulfs" of Frustration
The NIMC National Identification Number (NIN) Pre-Enrolment Portal serves as a primary case study for Don Norman's Gulf of Execution and Gulf of Evaluation.
The Gulf of Execution—the distance between a user's goal and the system's available actions—is widened by a lack of Signifiers and Affordances. For example, the portal lacks visual cues like asterisks to signify mandatory fields, and its dense, formal language ignores the principle of Progressive Disclosure (revealing information only as needed). This leaves users guessing how to interact with the "System Image."
The Gulf of Evaluation—the difficulty of interpreting what the system has done—is equally wide. When a user clicks "Submit" without a loading spinner or receives a generic "Invalid Input" error, they cannot evaluate their progress. These failures lead to high-stakes exclusion, particularly regarding the handling of the Reference Number:
Transient Visibility: The number is displayed only briefly on a confirmation page.
Lack of Persistence: There is no automatic delivery of the number via email or SMS, failing to match the
Written by Precious Olonade
Final-year CS student, web developer, and designer based in Osogbo, Nigeria. Writing about faith, football, film, software engineering, and life.
Read Next
The Structural Mandate: Why Design is the New Defense for Online Data
Reactive patching is obsolete. As "online" becomes the permanent default, real data protection means baking security into the architecture itself — not bolting it on after the breach. Here's why placing the end-user at the center of the system, not the server perimeter, is the structural mandate every platform needs.
Beyond the Code: 5 Hard Truths About Software Success Every Developer Needs to Know
We've all been there — a new feature request hits your desk, and your first instinct is to open the IDE and start coding. But technical brilliance can't save a project with zero version control or poor stakeholder engagement. From the "100 Percent Rule" that shields you from scope creep to the difference between a "High Grade" system and a genuinely "Quality" one, here are 5 hard truths every developer needs to know before their next build.