Enterprise delivery
Ran programme operations across international cohorts and distributed stakeholder groups.
My background is in client operations, learning-platform implementation, technical support and documentation. I like work where something is messy, important and fixable — then making it clearer, repeatable and easier for the next person to handle.
This page is deliberately factual. Some projects worked, some are still experiments, and some ideas did not go anywhere. The point is not to turn everything into a success story. It is to keep a visible record of what I have actually done, learned and built.
A small set of concrete facts that are difficult to argue away on a bad day.
Ran programme operations across international cohorts and distributed stakeholder groups.
Worked with Canvas, Insendi, Moodle and Degreed, including onboarding, setup and troubleshooting.
Maintained playbooks, documentation and handovers through team and role transitions.
Built and shipped small tools around real file and workflow problems instead of only planning them.
The through-line is operations, implementation, technical support and making delivery less fragile.
Managed end-to-end operations for more than 30 online learning programmes, supported up to seven global clients at once, coordinated programme setup across clients, educators and internal teams, and handled LMS implementation, onboarding and troubleshooting.
Progressed through administrative, IT and B-BBEE responsibilities. Supported Moodle and virtual learning delivery, handled day-to-day technical issues, coordinated reporting and compliance documentation, and worked across teams to get required information completed on time.
Different stages are labelled honestly. A prototype is not a business, and an experiment is not revenue.
A pre-flight and repair tool for Shopify product CSVs. It checks common import failure modes, separates errors from warnings, and only applies automatic fixes when the correction is deterministic.
Open the live tool →A narrow repair utility for SCORM packages with an unambiguous launch-file capitalization mismatch. Built around a simple rule: if the repair is not safe to infer, do not guess.
Open the prototype →A portrait visual-novel experiment built in Unity and Naninovel, combining character-driven scenes with personality-based choices, unusual UI interactions and a deliberately playful production-show framing device.
See what I'm working toward →Not an exhaustive skills list. These are the areas where my past work gives me actual evidence.
Set up processes, playbooks, handovers and operating routines that reduce avoidable mistakes.
Coordinate onboarding, platform configuration, stakeholders, dependencies and launch work.
Work through technical and operational problems without treating every symptom as the root cause.
Write the thing down clearly enough that another person can use it without reconstructing the whole context.