The short answer

A learning website should help a prospective learner choose the right course and then carry that choice into enrolment and the first learning session. Present eligibility, commitment and support clearly, preserve the selected course through the handoff, and test onboarding with people unfamiliar with your internal systems.

What must a learner know before choosing?

A course page should explain who the programme is for, what a learner should already know and what they will be able to practise. State the format, schedule, expected effort and any equipment or access requirements. Separate a verifiable qualification from a general statement about learning outcomes. Give a prospective learner a way to ask about suitability without forcing an application. These details help someone make a choice; an attractive catalogue alone does not resolve uncertainty about whether a programme fits their circumstances.

Where does the journey usually lose context?

Trace the route from search or a campaign to the course page, application, payment and learning platform. Check whether the course name, intake and fee remain visible throughout. A learner should not have to identify the same programme again on a generic form. If a different system takes over, explain that transition and the next expected step. Review confirmation emails as part of the experience. They should distinguish a received application from an accepted place and a payment receipt from actual access to learning.

What should enrolment ask for?

Ask for information needed at that stage, with a clear reason for any less obvious field. Do not collect a complete learner profile simply because an internal spreadsheet has those columns. Identify which details are required for eligibility, which support administration and which can wait until enrolment. Provide useful validation and a route to help when someone cannot complete a field. Test on a phone with an ordinary connection. Avoid making the learner re-enter information already supplied unless there is a genuine verification requirement.

What belongs in the first-session experience?

A new learner needs to know how to sign in, where to begin and whom to contact if access fails. Show the first task, relevant dates and any preparation in one place. Keep administrative notices separate from learning instructions. Test password recovery and account invitations, including expired links and duplicate email addresses. A clear first session does not require a custom platform; it requires decisions about sequencing, language and support. Examine whether learners reach the first meaningful activity, not merely whether their accounts were created.

How do you choose between platforms and custom work?

Start with programme requirements and the administrative workflow. Compare an existing learning platform, a configured product and a custom build against the same scenarios: enrolment, access, progress, assessment and reporting. Identify integration needs and who will maintain content and user accounts. A custom interface may improve discovery while the teaching experience remains in an established system. Do not build ordinary platform functions again without a reason. Include accessibility, data migration and support effort in the decision, rather than judging only the catalogue design.

How should the team evaluate improvements?

Observe prospective and newly enrolled learners completing the journey without coaching. Record where they hesitate, what they misunderstand and which support requests recur. Agree a baseline before changes, and review course selection, application completion and first-session access separately. Give every broken handoff an owner across admissions, finance and learning operations. Make a small set of changes and retest before expanding scope. The objective is continuity: a learner should arrive at the first session with the same understanding of the course that helped them choose it.

FAQ

Do we need a custom learning management system?

Not necessarily. An established platform may meet the teaching requirements while a better website and integration resolve discovery or onboarding problems. Compare options against real learner and administrator tasks.

What is the simplest first improvement?

Check the handoff from a specific course page to enrolment and confirmation. Preserving the course, intake and next step can remove uncertainty without replacing the whole platform.

Who should test the journey?

People who match your prospective learners and have not seen your internal systems, plus the administrators who process applications. Each group finds different problems.

Sources and further reading