Gates Foundation × SeamlessHR · 2025 – Present
BluAlliance
Building for Africa's Frontline Workforce
Translate ecosystem models into platform strategy — prioritisation, channels, and a connected experience portfolio.
The workforce ecosystem research identified more opportunities than the organisation could realistically pursue. This work focused on where and how to act.
![[Replace] BluAlliance platform case study hero — experience portfolio overview](/assets/work/_placeholders/hero.svg)
Breeze information architecture
WhatsApp ESS experience flows
Frontline productivity and supervisor workflow frameworks
Workforce prosperity and benefits experience design
Future-state platform architecture
Product management roadmap prioritisation
Gates Foundation programme alignment
CX and field rollout planning
- ·Platform over isolated products
- ·Channel-native experiences
- ·Honest maturity framing
Input: the Workforce Ecosystem programme identified eight capability domains across Nigeria and Kenya. This project translated those domains into prioritised opportunities, platform vision, and a portfolio of connected experiences.
02 Strategic Decisions
More opportunity than capacity
The research surfaced more opportunities than the organisation could realistically pursue. Three strategic decisions shaped platform direction.
Eight capability domains and dozens of opportunity areas — but limited engineering capacity and parallel programme commitments. The team needed explicit prioritisation criteria and a matrix showing what was in vs out — not implicit backlog ordering.
Frontline workers operate across WhatsApp, feature phones, and occasional web access. Employers need admin surfaces. Forcing a single channel would exclude users; supporting every channel would fragment delivery without a shared platform layer.
Each opportunity could ship as a standalone product or as a service within a shared platform. The most valuable decision was defining what would be shared — so future products could evolve without fragmenting the workforce experience.
03 Evidence
From capability handoff through future-state architecture — eight artefacts showing how strategy became platform direction.
Strategy
Prioritisation and platform direction — where the strategic work happened.
The ecosystem research produced eight capability domains. Product teams needed a map connecting research findings to actionable build areas without losing architectural coherence.
Translated capability architecture into an opportunity map aligned to research language. Output: eight domains mapped with dependencies and integration points.
Figure 01 — [Replace with artefact] Capability map — input from Workforce Ecosystem research across eight domains.
- ·Map inherits research language — no re-interpretation layer between ecosystem work and product squads
- ·Eight domains retained as reference; prioritisation handled in the next artefact
Figure 02 — [Replace with artefact] Prioritisation matrix — output: six opportunity areas chosen from eight capability domains with explicit rationale.
- ·Recruitment and Learning deferred to later phases — workforce management and communication prioritised for platform leverage
- ·Matrix made trade-offs legible to Gates Foundation and SeamlessHR leadership — not buried in roadmap tools
Without a prioritisation artefact, teams jumped from capability architecture to product debates. The decision layer — what to pursue first and what to defer — needed to be visible.
Built a prioritisation matrix scoring opportunities against impact, feasibility, and platform leverage. Output: six prioritised opportunity areas from eight capability domains.
Eight domains became six opportunities — explicit deprioritisation, not an implicit backlog.
Parallel squads risked building isolated products that couldn't integrate later — especially across WhatsApp, web, and supervisor tooling.
Defined BluAlliance platform vision: shared capability services powering multiple experience streams. Output: capability-led platform model.
Figure 03 — [Replace with artefact] Platform vision — shared services layer with experience streams (Breeze, WhatsApp ESS, supervisor tools) on top.
- ·Platform decision made explicitly — shared services for identity, workforce management, and communication
- ·Experience streams can ship independently but inherit platform services — avoiding isolated product trap
Experience Portfolio
Connected experiences across channels — each stream tagged by delivery maturity.
Delivery maturity
Employers and employees need a consolidated workforce experience — but standard HR IA patterns organise around systems, not goals.
Redesigned Breeze information architecture around employee needs and lifecycle workflows. Output: goal-oriented navigation and self-service surfaces.
Figure 04 — [Replace with artefact] Breeze IA — restructuring employee experiences around goals, workflows, and lifecycle needs.
- ·IA organised by jobs-to-be-done, not HR module taxonomy
- ·Supervisor coordination surfaces integrated — not relegated to admin settings
Figure 05 — [Replace with artefact] WhatsApp ESS — extending workforce services into familiar channels to improve accessibility and adoption.
- ·WhatsApp treated as first-class channel — not a notification layer for web ESS
- ·Flows designed for partial connectivity and async responses
Frontline workers don't sit at desks. WhatsApp is often the primary digital channel — ESS via messaging requires different interaction patterns than web forms.
Designed WhatsApp ESS flows for worker self-service — leave, payslip, attendance — using conversational patterns native to the channel.
Supervisor coordination emerged as the critical insight from ecosystem research but had no dedicated product surface.
Designed frontline productivity framework: team visibility, shift coordination, attendance, escalation — designed around supervisory workflows.
Figure 06 — [Replace with artefact] Supervisor workflow framework — supporting workforce coordination through supervisory-first design.
- ·Direct response to Design Principle 01 — design for the supervisor, not just HR
- ·Framework spans mobile and web — supervisors operate in field contexts
Figure 07 — [Replace with artefact] Prosperity framework — capabilities supporting both workforce productivity and worker prosperity.
- ·Prosperity framed as capability cluster — not a benefits add-on module
- ·Financial wellbeing includes savings, access, and visibility — not just payroll
Research showed prosperity extends beyond employment — benefits, financial wellbeing, learning, and career mobility matter as peer capabilities.
Designed prosperity framework connecting benefits, financial wellbeing, and career mobility within the platform capability model.
Architecture
Target state — what shared platform services enable long-term integration.
Experience streams progressing in parallel needed a target architecture so integration wouldn't require rework when streams converged.
Defined future-state platform architecture — shared services, data model, integration points, and channel abstraction across Breeze, WhatsApp ESS, and supervisor tooling.
The most valuable decision was defining what would be shared — not what would ship first.
Figure 08 — [Replace with artefact] Future-state architecture — connecting current and future workforce experiences through shared platform strategy.
- ·Architecture designed for incremental delivery — streams can ship before full platform maturity
- ·Channel abstraction enables WhatsApp and web to share workforce data without duplicate systems
04 Outcomes
What the platform work established
Not all experience streams are shipped. Maturity states are documented explicitly — this case study reflects programme reality, not a launch narrative.
Reflection
The Workforce Ecosystem initiative helped us understand the workforce. This work focused on determining where and how to act. The most valuable strategic decision wasn't what to build first — it was defining what would be shared, so future products could evolve without fragmenting the workforce experience.
05 Unlocks
Prioritisation matrix made eight-to-six domain decisions legible — explicit trade-offs, not implicit backlog.
Channel strategy resolved: WhatsApp as first-class ESS alongside Breeze — a design decision, not a compromise.
Maturity tagging maintained stakeholder trust while parallel streams progressed at different speeds.
Future-state architecture enables integration without rework — streams converge on shared platform services.
Research foundation preserved — see Workforce Ecosystem for the capability architecture this platform work builds on.
← Workforce Ecosystem — understand the system: research, service design, and capability architecture