Once the broader architecture of the LETE program was established, the next question became considerably more practical.
What should students encounter first?
The temptation with a new program is often to begin with theory. Learning models, historical foundations, terminology, and frameworks all have an obvious place in the curriculum.
Those elements are important, but they weren’t what I had spent years watching break down in real organizations.
What repeatedly caused problems in practice was communication.
Instructional designers could describe what they wanted but struggled to explain what was happening inside the system.
Technical staff could diagnose system behavior but struggled to understand why those behaviors mattered instructionally.
Faculty understood their content but were often frustrated by the technology supporting it.
Everyone involved was intelligent and capable.
They were simply speaking different professional languages.
LETE 1303 became my attempt to help students become translators.
Two Worlds That Rarely Meet
Throughout my career, I have spent significant time operating in both instructional and technical environments.
I’ve worked with faculty.
I’ve worked with instructional designers.
I’ve worked with database administrators.
I’ve worked with programmers.
I’ve worked with system architects.
One of the most common patterns I observed was that problems often persisted not because the solution was difficult, but because the people involved lacked a shared vocabulary.
A faculty member submits a support request.
Technical staff cannot reproduce the issue.
The ticket bounces back and forth.
Frustration grows.
Nobody is necessarily wrong.
Nobody is necessarily incompetent.
The information needed to solve the problem simply never gets communicated effectively.
Over time I became convinced that educational technology professionals needed more than pedagogical knowledge.
They needed enough technical literacy to participate meaningfully in those conversations.
Not to become programmers.
Not to become system administrators.
To become effective collaborators.
Why HTML and CSS Showed Up in a Learning Technology Course
One of the earliest design decisions that raised eyebrows was the introduction of HTML and CSS concepts.
This occasionally surprises people.
LETE is not a computer science program.
Students aren’t expected to become web developers.
That was never the goal.
The goal was literacy.
Most learning management systems, content management systems, accessibility tools, and web-based learning environments are built on technologies that instructional designers rarely see directly.
The result can be a kind of learned helplessness.
If formatting breaks, call IT.
If accessibility fails, call IT.
If something looks wrong, call IT.
But often the issue is not particularly complicated once someone understands the underlying structure.
A designer who understands basic markup sees systems differently.
They recognize patterns.
They ask better questions.
They communicate more effectively.
Most importantly, they become more difficult to intimidate with technical jargon.
[Insert story from your career where understanding basic HTML, CSS, or LMS structure allowed you to solve a problem quickly or avoid an unnecessary escalation.]
The objective was never coding proficiency.
The objective was confidence.
Support Tickets Are a Professional Skill
One assignment in particular became central to the course.
Students were required to write professional technical support tickets.
Some students initially viewed the activity as busy work.
Many changed their minds after seeing how difficult it actually was.
A surprising number of people know there is a problem.
Far fewer can describe the problem clearly enough for another person to solve it.
The assignment forced students to think through questions like:
- What exactly happened?
- What did you expect to happen?
- What steps reproduce the issue?
- What information would a support specialist need?
Those skills are not limited to technology environments.
They are problem-solving skills.
They are communication skills.
They are leadership skills.
And they are remarkably transferable.
Learning Through the Teaching Lab
From the beginning, I wanted the course to feel less like a survey class and more like a working environment.
Many of the activities were structured as small professional simulations.
Students diagnosed problems.
Students documented solutions.
Students evaluated tools.
Students explained decisions.
Students practiced communicating technical concepts in plain language.
Rather than simply reading about learning technologies, they interacted with them.
The goal was to build habits rather than memorization.
Professionals rarely succeed because they know every answer.
They succeed because they know how to investigate, communicate, document, and adapt.
Those were the habits I wanted students practicing from the first semester.
The Portfolio Starts Earlier Than Students Think
One design choice carried over directly from the broader program philosophy.
Students were building portfolio assets almost immediately.
Many did not realize it at first.
The point was not simply completing assignments.
The point was producing evidence.
Evidence of troubleshooting.
Evidence of analysis.
Evidence of communication.
Evidence of reflection.
One of the themes that increasingly shaped the program was the idea that future employers care as much about process as products.
A polished deliverable is useful.
Understanding how and why it was created is even more valuable.
That realization would eventually influence several later courses throughout the program.
One of the most important things I did in having the start to create a portfolio was to have the elaborate on what they learned as part of creating each artifact they added, while they still remembered what was in their heads at the time.
What Surprised Me
No curriculum survives first contact with students unchanged.
The first delivery of LETE 1303 immediately revealed assumptions I needed to revisit.
Some activities worked exactly as intended.
Others exposed friction points.
Some concepts students grasped immediately.
Others required additional scaffolding.
A few assignments generated insights that directly affected the development of LETE 2301 before that course was even finished.
The most valuable part of teaching is often discovering where your assumptions were wrong.
And there were definitely a few surprises.
Giving students a week to work on projects without requiring a deliverable as a check-in to reduce the pressure on them was a disservice. Many skipped the week doing no work at all. several others could have used an early intervention based on an intermediate check-in. My communication by announcement or weekly videos check-ins needed to be as structured as the rest of the course
Looking Ahead
Building LETE 1303 confirmed something I have suspected for years.
Educational technology professionals benefit from understanding how systems work, not just how systems are used.
The goal was never to turn instructional designers into programmers.
The goal was to help future professionals become more capable translators, troubleshooters, and problem-solvers.
Teaching the course also revealed several assumptions that needed adjustment.
Some of those changes were incorporated immediately.
Others fundamentally altered the development of LETE 2301.
The next entry in the Curriculum in Progress series explores those discoveries and how real student behavior reshaped a course that was still under construction.