Initially, learners could pay for a programme only in full.

This model worked for the first event-planning programme, whose audience included established business owners with the capacity to pay the full fee. However, the audience for the subsequent photography programme was younger and included more Gen Z learners, many of whom had less purchasing power.

Customer Success spoke directly with prospective learners and identified affordability as a significant barrier to enrolment. The Product Manager shared this insight with me, and it informed the decision to introduce instalment payments.

The business challenge was to make programmes more accessible without creating confusion around payment obligations, compromising payment tracking, or granting platform access before the required payments were completed.

The updated payment experience offered three choices:

Rather than presenting these as simple labels, the interface needed to explain the financial commitment associated with each option.

When learners selected a plan, the payment information updated to show the amount due immediately, the remaining amounts, and their respective due dates. This helped learners understand both the initial cost and the commitment they were taking on.

The goal was to support an informed decision, not simply make the first payment appear smaller.

The payment flow also supported scholarship codes.

After selecting a payment option, learners could enter an eligible code to receive a discount. Because the discount affected the overall programme fee, the interface needed to communicate how it changed the total and the amounts due under the selected payment plan.

The updated breakdown made the discount and revised payment amounts visible, helping learners distinguish between what they needed to pay immediately and what remained outstanding.

This was especially important for instalment plans, where a learner needed to understand the relationship between the discounted total and each scheduled payment.

Payment was not an isolated transaction. It determined when a learner could enter the platform.

Under the earlier process, bank transfers required manual verification. Learners could then be contacted to provide information and have their accounts created. This introduced additional coordination between payment confirmation and onboarding.

With the updated flow, payment verification and email communications supported a more self-service enrolment process.

For learners paying in instalments, the experience also needed to support the full payment lifecycle:

This approach helped separate the decision to enrol from the operational steps needed to confirm full payment and activate access.

The design principle: Financial flexibility only works when learners can clearly understand their obligations and the system consistently communicates what happens next.

The introduction of instalments gave prospective learners another way to pay. Following the change, the team observed better learner uptake and re-engaged prospects who had previously faced affordability barriers.

Marketing and Customer Success team follow-ups and automated emails also supported payment completion.

However, we did not establish a quantified before-and-after conversion rate or a verified reduction in manual support effort. I therefore treat these as observed outcomes rather than a measured conversion uplift attributable to the interface alone.

For a newly enrolled learner whose cohort had not started, the dashboard displayed a prominent banner for the registered programme. The banner included a countdown to the start date, alongside options to watch the programme trailer or view more information.

Lessons remained locked until the scheduled start.

Once the programme began, the countdown disappeared and the learner could begin the learning experience.

This distinction helped the dashboard serve two purposes: reassuring learners that their enrolment was active before the cohort started, and directing them towards learning when the programme became available.

For returning learners, the experience prioritised continuity. They landed on the My Courses area, making it easier to locate an ongoing programme and resume learning without having to navigate the initial enrolment experience again.

Within a programme, content was organised into modules, with lessons and quizzes forming the learning structure.

I designed the experience to make this hierarchy clear so learners could understand how individual lessons fitted into the broader programme.

The interface also needed to communicate availability. A lesson could be part of the programme but still be unavailable because its scheduled release date had not arrived.

Lock indicators helped distinguish content that was available from content that was scheduled for later. This reduced ambiguity and made the cohort structure visible within the classroom itself.

The experience was therefore not only a way to access content. It also communicated the rules and rhythm of the programme.

I used clear lesson availability states and lock indicators to show which lessons were currently accessible and which were not.

This helped communicate that unavailable content was part of the programme schedule, not something the learner had missed or lost access to.

The experience also reflected a distinction between content availability and learner completion.

New modules were released according to the programme schedule, even if a learner had not completed every lesson in the previous module. This avoided turning the platform into a punitive system where falling behind once could prevent a learner from accessing all subsequent content.

The challenge was not simply to lock and unlock lessons. It was to preserve the structure of a shared learning experience while keeping learners informed and able to continue.

The resulting approach respected the programme's scheduled rhythm without unnecessarily blocking access to later modules because of incomplete earlier work.

Each module included a quiz following its lessons.

The quizzes provided learners with scores, giving them feedback on their performance as they moved through the programme. These scores did not contribute to the final assessment score.

Keeping the quizzes distinct from the final assessment reflected their role in the learning journey: they were checkpoints within the modules, rather than the final measure used to determine certification eligibility.

The final assessment followed a different set of rules.

It was available only within a scheduled assessment window, with defined opening and closing dates. Learners had to complete the required modules before the final assessment became available.

Learners could attempt the assessment up to three times within the allowed window. This gave those who did not pass an initial opportunity to try again, while preserving the programme's assessment schedule.

The interface needed to communicate these conditions so learners could understand when they were eligible to take the assessment and what their available options were.

Certificate access was also tied to specific programme conditions.

Learners needed to pass the final assessment, and certificates became downloadable after the assessment window closed.

This meant a learner who passed early could not immediately download their certificate while other learners were still within the scheduled assessment period.

The rule supported a coordinated cohort completion process. The design needed to make this restriction understandable by distinguishing between passing the assessment and the point at which the certificate became available.

Together, the quiz, assessment, and certification experiences established a progression from participating in the programme to meeting its completion requirements.

Introducing full payment, two-instalment, and three-instalment options gave prospective learners more flexibility in how they paid for a programme.

The team observed better learner uptake after instalments were introduced and previously interested prospects were re-engaged. This was an encouraging signal that the payment model was addressing a real barrier, although the team did not establish a quantified conversion uplift.

Payment verification and automated communications reduced the need to coordinate every enrolment step manually. Learners could receive payment confirmations, understand upcoming instalments, and return to complete outstanding payments through the platform's payment flow.

This created a clearer process for learners and a more structured approach to payment follow-up. The extent of any reduction in operational workload was not formally measured.

Learners could access their programmes through a consistent journey, from the dashboard to modules, lessons, quizzes, final assessments, and certificates.

The experience reflected the cohort model through scheduled programme starts, controlled lesson releases, assessment windows, and defined certificate eligibility.

The first event-planning programme, featuring Funke Bucknor-Obruthe of Zapphaire Events, reportedly generated approximately ₦20 million in revenue over its first three months, with around 50 or more learners associated with the programme.

These figures were reported as programme outcomes rather than independently audited results. They demonstrate early commercial traction for the academy, but they should not be interpreted as revenue generated by design alone.

The programme also offered learners exposure to an experienced industry practitioner. Some learners had the opportunity to accompany the facilitator to events and observe her work, extending the learning experience beyond the platform itself.

A photography programme followed, with a younger audience and a different affordability profile. It was still running at the time of this case study, so its final outcomes were not yet known.

Across the work, the team estimated that more than 100 people had used the platform. This is an approximate figure rather than a verified analytics total.

The strongest evidence available at this stage is the live delivery of the experience, the observed response to instalment payments, and the reported commercial traction of the first programme.

The team did not have verified before-and-after conversion figures, detailed payment-completion metrics, or a formal study establishing how the design affected learning outcomes. I would want to collect those measures before making stronger claims about the product's impact.

A more accessible payment option is only useful when learners understand the commitment they are making. Transparency and predictability are part of accessibility, not details to add after the payment model has been decided.

Cohort dates, lesson locks, assessment windows, and certificate release rules could easily have been treated as backend requirements.

However, each rule influenced what learners saw, what they could do, and how they understood their progress. Designing the interface meant making those rules visible and understandable.

This reinforced the importance of designing not only screens, but also the states, conditions, and transitions that connect them.

Koppoh needed to preserve a structured cohort model while making education more accessible. Learners needed flexibility and clarity, while the business needed predictable programme delivery and payment control.

The solution was not to optimise exclusively for either side. It was to create an experience that respected the programme structure while making enrolment and progression easier to understand.