Gates Foundation × SeamlessHR · 2025 – Present
Workforce Ecosystem
Designing for Africa's Frontline Workforce
Understand the workforce ecosystem — from evidence through models to capability architecture.
A research and service design programme spanning Nigeria and Kenya — producing strategic artefacts that aligned product, business, and field teams around how frontline work actually happens.
![[Replace] Workforce Ecosystem case study hero — research and service design artefacts](/assets/work/_placeholders/hero.svg)
Workforce Ecosystem Blueprint and lifecycle framework
Service blueprinting (high-level and detailed)
Capability architecture across eight domains
Cross-functional workshop facilitation
SeamlessHR product and engineering discovery
Field research execution in Nigeria and Kenya
- ·Research before product definition
- ·Lifecycle as the organising spine
- ·Capability architecture as the handoff layer
02 Design Principles
Three principles from the research
Patterns that held across industries and geographies — framed as constraints for service design and platform decisions.
Supervisors mediate scheduling, attendance, disputes, and trust between workers and organisations. Workforce systems must treat supervisory workflows as first-class — not as admin overlays on worker-facing features.
Workers and employers often lack shared visibility into employment status, pay cycles, and obligations — because of fragmented channels and informal arrangements. Service design must account for partial visibility and offline coordination.
Financial wellbeing, learning, benefits, and career mobility matter as much as payroll. Capability architecture must treat prosperity outcomes as peer domains — not add-ons to core HRM.
03 Evidence
Evidence → models → architecture. Six deliverables — each with a named output, not just a research activity.
Foundation
Evidence and synthesis — grounding the programme in multi-country field reality.
Frontline workforce dynamics in Nigeria and Kenya had not been documented at ecosystem scale. The programme needed grounded evidence before any product scope could be credible.
Designed and led multi-country research with 150+ participants — employers, workers, supervisors, and field partners. Output: a multi-country workforce evidence base.
Figure 01 — [Replace with artefact] Research overview board — output: multi-country workforce evidence base across Nigeria and Kenya.
- ·Multi-country scope chosen deliberately — patterns had to hold across markets, not collapse into single-market anecdotes
- ·Supervisor and employer perspectives weighted equally with worker interviews — coordination layer insight emerged from triangulation
Figure 02 — [Replace with artefact] Insight Framework mapping research themes to three design principles and capability gaps.
- ·Principles framed with design implications — product teams could act without re-interpreting raw research
- ·Supervisor layer, visibility limits, and prosperity beyond employment became the narrative spine for all downstream artefacts
Raw field notes risked staying anecdotal. Stakeholders needed actionable principles, not interview transcripts.
Synthesised research into three ecosystem design principles with implications for service and platform work. Output: Insight Framework — three ecosystem principles.
Models
Original design artefacts — the intellectual contribution of the programme.
HR product thinking defaults to employer–worker dyads. Frontline work involves supervisors, agents, informal intermediaries, and channel-specific coordination.
Mapped actors, relationships, channels, and coordination layers. Output: Workforce Ecosystem Blueprint — shared model of workforce interactions.
Figure 03 — [Replace with artefact] Ecosystem blueprint — output: shared model of workforce interactions across the employment lifecycle.
- ·Ecosystem model precedes journey maps — actors and relationships define what journeys are even possible
- ·Blueprint became the shared reference for Gates Foundation and SeamlessHR alignment workshops
Figure 04 — [Replace with artefact] Lifecycle framework — output: seven-stage workforce journey model with stage definitions and opportunity mapping.
- ·Lifecycle chosen over feature categories — stages hold cross-capability experiences that feature lists flatten
- ·Seven stages balance granularity with memorability — enough to guide service design without becoming operational taxonomy
Feature-based scoping would fragment the programme. The team needed one organising spine that could hold employer, worker, and supervisor perspectives.
Defined seven stages: Discover, Join, Show Up, Do Work, Get Rewarded, Grow, Thrive. Output: Workforce Lifecycle Framework — seven-stage workforce journey model.
Lifecycle stages needed operational detail — frontstage and backstage actions, support processes, and failure points visible to cross-functional teams.
Produced high-level and detailed service blueprints connecting worker, supervisor, and employer touchpoints to backstage processes. Output: Workforce Service Blueprint — operational view of workforce delivery.
Figure 05 — [Replace with artefact] Service blueprint — output: operational view of workforce delivery across lifecycle stages.
- ·Two fidelity levels — high-level for stakeholder alignment, detailed for squad-level design
- ·Backstage processes explicitly mapped — revealing where platform services vs human coordination is required
Architecture
Strategic handoff — capability domains for platform prioritisation.
Figure 06 — [Replace with artefact] Capability map — output: eight workforce capability domains with dependencies and platform service boundaries.
- ·Eight capabilities derived from research — Financial Wellbeing and Career Mobility elevated to peer domains
- ·Architecture defines handoff to BluAlliance platform strategy — deliberately stopping before UI
Service blueprints revealed dozens of opportunity areas. Without a capability map, prioritisation would collapse into feature debates disconnected from research.
Established eight interconnected capability domains derived from research — not imported from standard HR modules. Output: Capability Architecture — eight workforce capability domains.
The architecture became the handoff layer between workforce research and product strategy.
Handoff to platform strategy
The architecture became the handoff layer between workforce research and product strategy — eight capability domains product teams could prioritise without re-litigating the research foundation.
- Workforce Identity
- Recruitment
- Workforce Management
- Communication
- Learning
- Benefits
- Financial Wellbeing
- Career Mobility
04 Outcomes
What the deliverables established
Reflection
The hardest part wasn't understanding workers. It was creating a shared model that product, business, and field teams could all use to reason about the workforce ecosystem. Running this alongside SeamKit surfaced a useful tension: consistency (shared UI baseline) vs coherence (experiences that fit frontline reality). Both are necessary — ecosystem models ensure product work stays coherent with how work actually happens.
05 Unlocks
Capability architecture became the handoff layer for BluAlliance platform strategy — see the next case study.
Established shared language across Gates Foundation programme stakeholders, SeamlessHR product leadership, and field partners.
Ecosystem Blueprint, Lifecycle Framework, and Service Blueprint remain durable strategic artefacts beyond any single product release.
Parallel SeamKit work ensured UI consistency would not come at the cost of frontline coherence when product surfaces shipped.