Section 1c: Supporting the Deployment of Learning Technologies

Description

Over the past several years, I've been involved in a range of activities that have supported the deployment of learning technologies, from technical documentation and training to change management and evaluation.

In June 2021 — just before Microsoft retired Skype for Business — I authored a Microsoft Teams FAQ to support trainers through the institutional transition to Teams. I also created a video walkthrough, Microsoft Teams Guide, which was used to deliver asynchronous training.

In 2023, while working in a development-focused team, I created a guide called Using Postman with Apollo Server to help new developers interact with a GraphQL development environment. This included instructions for authentication, storing JWT tokens, and running queries and mutations via Postman. While it was technical in nature, the resource also functioned as a learning technology support tool, easing onboarding and promoting consistency across the team.

An excerpt from Microsoft Teams Guide

Most recently, in July 2025, I published a blog post titled Using Blackboard's Swagger File to Create a Postman Collection and Make an API Call. This guide was informed by testing work I contributed to as part of the Digital Education Platform Project (DEPP), which explored the adoption of new LMS platforms. In the blog's “Step 4: Request an Access Token“, I reference a script adapted from one I originally developed to authenticate with Learnlight's bespoke language learning platform — demonstrating how techniques from previous roles fed into current work.

Reflection

Looking across these resources, I can trace a development in both approach and design — moving from instructional documents focused on immediate technical tasks to more accessible, learner-centred materials that anticipate different levels of user confidence.

For example, the Microsoft Teams FAQ included lengthy text blocks and oversized arrows that partially obscured key content. By contrast, my more recent API and Postman guides are more concise, streamlined, and visually clearer — reflecting lessons learned about information overload, visual accessibility, and cognitive load. Similarly, my Using Postman with Apollo Server guide — created in Confluence — omitted annotated visuals entirely, a gap I now actively address through better use of screenshots, highlights, and contextual labelling.

These reflections have shaped my understanding that effective deployment goes beyond technical rollouts. It involves building user confidence, collecting feedback, and iterating support based on real experiences. At Imperial, this has meant creating resources that cater to a diverse tester group across academic departments — with varying levels of technical fluency. I've provided asynchronous walkthroughs and clear reference materials that reduce the need for live support and empower users to explore new systems independently.

Much of this work was inherently collaborative. In the DEPP project, I worked closely with other learning technologists, developers, and colleagues during platform evaluation. Internal team testing sessions highlighted both technical issues and usability challenges, leading us to adapt instructions and examples for different contexts. For instance, colleagues reviewing the LMS test scripts reported that one case — requiring users to set up and submit assignments just to generate log entries — was too time-consuming in a sandbox environment. Based on this feedback, I revised the script so that testers could instead demonstrate that a detailed audit log for an individual user was shown. This adjustment made the test more flexible and scalable, while still achieving the goal of verifying assignment submissions. Feedback from administrative staff also influenced revisions — for example, simplifying language or prioritising practical marking workflows over advanced features. These contributions frequently drew my attention to areas I might not have identified alone, reinforcing the importance of team-based evaluation.

Supporting deployment now feels like an empathetic, iterative process — one that blends technical clarity with a deep understanding of staff needs. Collaboration has been key to this: co-developing resources, running pilot sessions, and integrating structured team feedback has consistently improved the quality and uptake of the materials I produce. I now approach training and resource development with this mindset, aiming not just to instruct but to support learning in the broader sense.

Summary

This section demonstrates how I have:

Supported the evaluation and deployment of LMS platforms through a mix of technical documentation, testing, and tailored guidance
Created training materials that evolve with user needs — from early platform migrations to current API and GraphQL workflows
Contributed to change management efforts by anticipating user challenges and aligning support with institutional processes
Developed resources that balance technical detail with accessibility and clarity, reflecting user feedback and evolving practice
Helped bridge development and pedagogy by aligning features and workflows with actual teaching needs
Advocated for usability, clarity, and sustainability in every stage of the deployment process
Worked collaboratively with colleagues through team testing and pilot sessions, adapting resources in response to feedback and improving adoption outcomes

Evidence

Documentation & Technical Workflows

Using Blackboard's Swagger File to Create a Postman Collection and Make an API Call (2025) (Blog post) Public, step-by-step guide informed by DEPP testing; demonstrates clear dissemination of API evaluation methods and supports reproducible endpoint testing.
Using Postman with Apollo Server (2023) (PDF) Internal developer documentation for GraphQL workflows (auth, JWT storage, queries/mutations); underpins consistent onboarding and team-wide technical practice.

Training & Rollout Support

Microsoft Teams FAQ (2021) (PDF) Trainer-focused guide produced during the Skype for Business → Teams transition; plain-English support that reduced friction and queries during institutional change.
Microsoft Teams Guide (Video) Short asynchronous walkthrough used alongside the FAQ; provides accessible, on-demand training to support deployment at scale.