Consultancy
Decisions before deliverables: what to build, what to buy, what to fix first.
How I approach it.
Select any item to reveal the detail.
A review of existing training against how people actually use it: completion data, learner feedback, the content itself. The output is a plain-English report on what is working, what is not, and a fix list ranked by effort against impact, so the starting point is obvious.
A program plan built on outcomes and evidence rather than content volume. It names the capabilities that matter, the gaps against them, and the sequence of builds that closes those gaps. Written to survive contact with the budget cycle.
A shortlist and recommendation from someone who has built and shipped inside these platforms, not just watched the demo. Scored against the actual requirements: authoring workflow, reporting, accessibility, integration and total cost. The scoring matrix stays with the team.
Where assistants genuinely help, how to ground them in the organisation's own documentation so they answer accurately, and where to hold back. Practical guardrails a team can apply, drawn from assistants I have shipped inside real courses.
Templates, standards and working sessions so a team ships consistent work without me in the room. The goal is a process the team owns: storyboard formats, QA checklists, brand components. I make myself progressively unnecessary.
Proof.
Student Success Portal.