What Nigeria’s Talent Debate Gets Right and Wrong

When Tosin Eniolorunda, the CEO of Moniepoint, noted that the company's decision to hire exclusively from Nigeria in 2024 "came at a cost" in 2025, the statement quickly triggered a familiar debate. Some interpreted it as evidence of a talent gap in Nigeria. Others saw it as a commentary on compensation, training investment, and organizational maturity.

Both interpretations miss and reveal something important. The real issue is not whether local talent can meet global standards. It is what it actually takes for any workforce, in any market, to consistently deliver at that level inside fast-scaling organizations.

Talent is rarely the binding constraint

A recurring error in discussions about workforce performance is the assumption that outcomes are primarily determined by talent quality. In practice, performance is a function of three variables: the quality of available talent, the intensity of capability-building investment, and the strength of organizational systems that shape execution.

When companies restrict hiring to a single geography, they do not automatically reduce talent quality. What they do is increase dependency on internal systems to close readiness gaps. If those systems are weak or underdeveloped, the organization will experience predictable friction in onboarding, productivity ramp-up, and consistency of output.

This is likely the underlying meaning of "paid dearly." It is less about absence of ability and more about the cost of converting potential into performance at scale.

The infrastructure behind high performance

High-performing organizations rarely rely on talent alone. They invest in structured development systems that reduce variability in output over time. This includes onboarding programs, mentorship structures, technical training pipelines, and clear performance architectures.

Historically, several Nigerian institutions demonstrated this approach effectively. Firms such as United Bank for Africa and Zenith Bank built strong internal capability systems that assumed graduates were raw material rather than finished product. Employees were developed through structured rotations, formal training academies, and in some cases international exposure. The outcome was not immediate productivity, but long-term institutional strength.

The shift in modern scaling models

In contrast, many newer technology and fintech companies operate under different constraints. Speed of execution, capital efficiency, and rapid scaling often take precedence over long-cycle capability development. This creates an implicit assumption that the labor market will supply "job-ready" talent.

This assumption works well in mature ecosystems where industry standards are tightly aligned with educational outputs and professional certification systems. In emerging markets, however, the gap between academic preparation and workplace expectations is often wider. When companies do not invest in bridging that gap internally, they absorb the cost through reduced early-stage productivity.

The constraint is therefore not simply talent availability. It is the presence or absence of institutional mechanisms that convert talent into performance at scale.

The compensation and expectation gap

Much of the public reaction to the Moniepoint statement centered on compensation. This is not incidental. Performance expectations cannot be decoupled from the conditions provided to achieve them.

Where organizations expect global-level output, they must also provide globally competitive inputs. These inputs include not only salary structures but also tools, training access, management quality, and career development pathways. When this alignment is weak, performance gaps are often misinterpreted as capability gaps rather than structural misalignment. This misdiagnosis leads organizations to seek better talent externally rather than strengthening the systems that develop existing talent.

The trade-off between speed and capability building

The core tension in the debate is not ideological. It is operational. Organizations must choose how to balance speed of scaling with depth of capability development.

A speed-first model reduces training overhead and accelerates output but increases dependency on precise hiring and immediate readiness. A development-first model increases upfront cost and slows initial output but produces more resilient long-term performance. Both models are valid. The risk arises when organizations attempt to operate a speed-first hiring philosophy while expecting development-first outcomes.

What the debate actually reveals

The public reactions to the Moniepoint statement reflect three competing interpretations of performance reality. One view assumes talent deficiency. Another attributes outcomes to compensation and structural investment. A third emphasizes the erosion of intentional capability-building practices in modern organizations.

The more accurate explanation incorporates elements of all three but assigns causality differently. Nigerian talent is not the limiting factor. Rather, the limiting factor is the degree to which organizations invest in systems that develop, align, and sustain that talent at scale.

Implications for building competitive organizations

The strategic lesson is straightforward but often overlooked. Hiring strategy and capability-building strategy cannot be separated. A locally focused hiring approach is viable only when matched with strong internal development infrastructure. Without that, organizations will repeatedly encounter the same constraint, regardless of how strong individual hires may be.

The question is therefore not whether to hire locally or globally. It is whether the organization is designed to turn the talent it hires into the performance it expects. In that sense, the Moniepoint CEO's comment is less a verdict on labor markets and more a reflection on organizational design. The cost was not simply in hiring locally. It was in underestimating what it takes to make local hiring perform at global standards without equivalent investment in development systems.

For emerging market companies, that distinction is not semantic. It is strategic.