Tabitha Kavyu · Designing Customer-Centred Systems

Featured Transformations

My job title has only ever said community or learner success. The role kept widening anyway, into customer support, customer experience, retention and Voice of Customer, often all in the same week. Working across all of it is how I found out where my strength actually lies. The vocabulary changed depending on which part I was standing in. The work underneath did not: understand the people an organisation serves, find where the experience breaks down, and design the system that makes success more likely.

Transformation One

From Reactive Support to Learner Success

Reimagining customer support as a strategic function

Support was answering questions well but working in isolation. Thousands of learner conversations were generating insight that never reached product, programme design or operations. I redesigned support as part of the learner success journey, so every interaction fed back into the system instead of ending in a closed ticket.

21% faster response time 20,000+ learners 11 cohorts

Context

When I became Head of Learner Success at AltSchool Africa, customer support was performing an essential operational function: responding to learner questions and resolving issues as they arose.

As the organisation scaled, support could no longer work as an isolated function. Thousands of learner conversations held valuable insight, but very little of it influenced product decisions, programme design or operational improvements. The challenge was not responding faster. It was building a system where every learner interaction improved the experience for the next learner.

Approach

Instead of treating support as a ticketing function, I redesigned it as part of the learner success journey. I documented standard operating procedures, gave the support team a clear view of the whole learner lifecycle, created structured escalation pathways with Programme Managers, and introduced regular reporting that surfaced recurring learner challenges.

Outcome

A more proactive, strategically aligned support operation. Response times improved, escalations got clearer, and learner insight started shaping decisions well beyond the support team. The function moved from resolving problems to preventing them.

Proof

Average human response time improved from 45 minutes 39 seconds to 36 minutes 03 seconds, roughly 21%, within three months
Supported more than 20,000 learners across 11 cohorts
Documented support processes adopted across the Learner Success function
Cross-functional collaboration improved between Support, Programme Management and Academic teams

I do not see customer support as a cost centre. I see it as one of an organisation's richest sources of strategic intelligence.

Transformation Two

Designing Customer-Centred Retention at Scale

Building systems that helped learners continue, not simply communicate

Learners who fully intended to continue were delaying payments and quietly drifting away. More reminders were not fixing it. I treated retention as a customer experience problem rather than a communications one, and built a multi-channel activation system that became standard practice across later cohorts.

Activation model adopted org-wide Cohort-specific engagement

Context

As AltSchool Africa grew, retention became critical. Many learners who intended to continue delayed tuition payments, disengaged academically, or drifted away quietly. Not because they lacked motivation, but because of competing priorities, uncertainty, and friction in the experience.

Reminders alone were not solving it. The problem needed an understanding of behaviour, not more communication.

Approach

I designed a multi-channel activation strategy: educational video walkthroughs, structured payment reminder campaigns, personalised outreach, and much clearer guidance on what to do next.

Alongside it I built cohort-specific engagement approaches shaped by how each group actually behaved, rather than assuming every cohort needed the same intervention.

Outcome

The payment activation model became standard practice for future cohorts, and engagement strategy became tailored rather than generic. Retention conversations shifted from chasing payments to understanding learners.

Proof

Designed a payment activation system adopted across subsequent cohorts
Led learner success initiatives supporting 20,000+ learners
Built engagement models across multiple programmes and learner populations
Leadership adopted the activation approach as ongoing operational practice

People rarely disengage because they lack intention. They disengage when systems make success difficult.

Transformation Three

Turning Customer Feedback into Organisational Strategy

Building a Voice of Customer system

Feedback was everywhere and useful nowhere: surveys, support conversations, office hours, community threads, student leaders, programme reviews. I built a closed-loop process that pulled all of it together and turned recurring patterns into decisions leadership could actually make.

Closed-loop VoC process Insight across four teams

Context

Customer feedback existed across surveys, support conversations, office hours, community discussions, student leaders and programme reviews. The information was valuable but fragmented.

Without a structured process, recurring learner challenges stayed disconnected from strategic decision-making.

Approach

I built a closed-loop Voice of Customer process bringing together insight from every major learner touchpoint: semester surveys, learner check-ins, support conversations, community engagement, student leadership discussions and graduation reflections.

Rather than only collecting feedback, I synthesised recurring patterns into reports that told leadership not just what learners were saying, but which organisational systems needed to change. Then we closed the loop and told learners what changed, so they kept telling us.

Outcome

Customer insight became part of decision-making, shaping programme design, operations, support processes, communication and product. The organisation moved from listening occasionally to learning continuously.

Proof

Built a structured Voice of Customer process spanning multiple learner touchpoints
Insight integrated across Community, Product, Learning and Operations teams
Leadership relied on learner insight reports to guide decisions
Customer feedback became part of cross-functional conversations rather than staying inside departments

Listening is only valuable if it changes decisions. My work is creating systems where customer voices become organisational intelligence.