KN
Kylle NaidooWork, systems and things built.
Johannesburg · Remote
Operations · implementation · practical systems

I make complicated work easier to run.

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.

Evidence, not a sales pitch.

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.

What exists

A small set of concrete facts that are difficult to argue away on a bad day.

01

Enterprise delivery

Ran programme operations across international cohorts and distributed stakeholder groups.

02

LMS implementation

Worked with Canvas, Insendi, Moodle and Degreed, including onboarding, setup and troubleshooting.

03

Operational ownership

Maintained playbooks, documentation and handovers through team and role transitions.

04

Practical product building

Built and shipped small tools around real file and workflow problems instead of only planning them.

Work

The through-line is operations, implementation, technical support and making delivery less fragile.

EmeritusOperations SpecialistOct 2021 — Jun 2025

Global programme operations and implementation

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.

Client onboardingImplementationCanvasInsendiDocumentationProcess improvement
Duke Corporate EducationJohannesburg, South Africa2016 — 2021

Operations, compliance and regional IT support

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.

MoodleIT supportData & reportingB-BBEEStakeholder coordination

Things I've built

Different stages are labelled honestly. A prototype is not a business, and an experiment is not revenue.

Public beta

Shopify CSV Checker

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 →
Tested prototype

SCORM Patch

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 →
In development

Backstage Beach House

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 →

Useful things I can do

Not an exhaustive skills list. These are the areas where my past work gives me actual evidence.

Operations

Make delivery repeatable

Set up processes, playbooks, handovers and operating routines that reduce avoidable mistakes.

Implementation

Turn requirements into setup

Coordinate onboarding, platform configuration, stakeholders, dependencies and launch work.

Troubleshooting

Find the actual failure

Work through technical and operational problems without treating every symptom as the root cause.

Documentation

Make knowledge transferable

Write the thing down clearly enough that another person can use it without reconstructing the whole context.

Current direction

Stable work first. Experiments stay honest.

1
Long-term operations / implementation workLooking for a stable role with ownership, client interaction and hands-on problem solving.
2
Small tools with measurable demandBuild narrowly, publish quickly, and let real usage decide whether something deserves more time.
3
Keep meaningful creative work aliveContinue the visual novel as a project without asking it to carry the weight of financial stability.