Marcus Lee — Learning Management System Administrator

What does an LMS Administrator do when you are not resetting passwords?

First, thank you for asking, because some weeks it feels like the whole district thinks I am the password person. I mean, passwords matter—if a teacher cannot get in, nothing else matters—but the role is really about making the learning platform dependable enough that teachers do not have to think about the platform all day.

I manage course creation, terms, roles, enrollments, integrations, templates, permissions, archiving, and a lot of vendor coordination. But the leadership part is deciding how much consistency the district needs and where teachers need room to teach in their own way. If we lock everything down, the LMS becomes a compliance tool. If we configure nothing, every school invents a different system and students have to relearn navigation seven times.

How do you use technology to increase your own leadership capacity?

The platform gives us logs, usage patterns, integration status, and support trends. That helps me stop guessing. If teachers say assignments are disappearing, I can look at whether the issue is a course-copy setting, an integration, or a training gap. If students are not launching a resource, I can see whether the problem begins at authentication, enrollment, or the external tool.

I also automate the boring but dangerous parts—course creation, standard roles, term dates, and archiving. Automation gives me time to work with curriculum and school teams. The funny thing is, the better I do that work, the less visible my job becomes. Nobody sends a thank-you note because all 4,000 courses appeared correctly. They just start teaching, which is the point.

Tell me about a change that worked especially well.

Our course templates were a real win, although the first attempt was not. We originally built this beautiful, very detailed template with fifteen modules, district graphics, and instructions everywhere. Teachers hated it. I mean, they did not say “hate” in the survey, but that was the message. It felt like we had already designed their course before they arrived.

So we started over with teachers, students, special education staff, and instructional coaches. The new template had a consistent home button, weekly structure, accessibility basics, and a predictable place for help—nothing more. Teachers could build from there. Student support calls about finding assignments dropped, and new teachers had a much easier starting point. The win was learning that consistency should reduce cognitive load, not advertise how much the central office can configure.

Was there another win that changed how the district operated?

We created a start-of-term readiness process. Before that, the first Monday of a semester was basically a live test. We would discover that a term date was wrong, a school had created sections late, or a vendor sync had not processed over the weekend. Everyone was working hard, but we were working after students felt the failure.

Now we run staged checks: source rosters, course counts, teacher assignments, integrations, sample launches, and accessibility settings. School technology leads verify a small set of real courses before opening day. The first semester we used it, our opening-week tickets dropped noticeably. More important, the tickets we did receive were specific. Instead of “the LMS is broken,” we knew which layer to investigate.

What are the biggest hurdles in the position?

Ownership, honestly. The LMS touches the SIS, identity provider, curriculum tools, assessment tools, and gradebook. When something breaks, each system can look healthy by itself. You can spend hours with three vendors saying, “It left our system correctly.” Somebody has to own the student’s whole journey, not just their product boundary.

The other hurdle is change fatigue. Vendors release features constantly, and people assume a new feature should be enabled because it exists. I guess what I would say is that every toggle is a policy decision in disguise. Who can use it? What data does it create? Does it change grading or communication? Who will support it? Sometimes the most responsible answer is, “Not this semester.”

How do you work with teachers who are frustrated with the platform?

I try not to begin by defending it. If a teacher says the LMS takes too many clicks, they may be right. I ask them to show me what they are trying to accomplish. Sometimes there is a better workflow. Sometimes our configuration is the problem. And sometimes the requirement itself came from somewhere else, which means I need to connect them with the person who can reconsider it.

We also stopped offering training called “LMS Basics” as one giant tour. Teachers do not need fifty features on day one. We built short sessions around actual tasks: organize a week, give feedback, support an absent student, or make materials accessible. Adoption improved because the technology was attached to work teachers already valued.

Where does data governance show up in an instructional platform?

Everywhere. Roles determine who can see students. Course copies can carry information into the wrong term. External tools request names, email addresses, rosters, and sometimes grades. Retention matters because the LMS holds student work long after a class ends.

We document what each integration receives and why, review teacher and observer roles, and test what happens when a student transfers. I mean, a successful login is not proof that access is correct. The teacher has to see the right students, the student has to see the right course, and people who no longer have a legitimate role need to disappear.

What advice would you give someone moving into LMS administration?

Learn the technical side, but spend just as much time in classrooms and support meetings. You need to understand why a teacher structures a course a certain way and what a sixth grader experiences when every class uses different navigation.

Also, document everything you wish the last administrator had documented. Term setup, role rules, integrations, emergency contacts, course-retention decisions—all of it. The district should not lose the ability to operate the platform because one person goes on vacation. I say that as the person who once answered a vendor call from a campground, so, yes, I learned it personally.

Reflective questions

1. Which LMS conventions would reduce student cognitive load without limiting teacher practice?
2. How does your district verify instructional readiness before a term begins?
3. Who owns the complete student experience when several connected systems are involved?
4. What criteria should govern whether a newly released platform feature is enabled?
5. Which LMS integrations receive student data, and is their purpose documented?
6. How could professional learning begin with teacher tasks rather than a tour of software features?