EME4043 is instructional technology leadership — and its statewide description is notable for how deliberately it refuses to be a school-focused course.
Students "will examine the role of the technology leader in effective integration, management and use of technology in a variety of settings, including education, training, military, public sector and non-profits. The course focuses on technology, information, and information literacy. Special attention is paid to the role of systems thinking in effective technology leadership."
⚠ That list of five settings is doing real work. Most courses with "instructional technology" in the title assume a school. This one explicitly spans the sectors where instructional design is actually practised — and the leadership problems genuinely are common across them, because they are not really problems about technology.
The recurring pattern the course exists to address is worth stating. Organisations buy learning technology that is then not used, or used badly, or abandoned. ⚠⚠ The cause is almost never that the technology did not work. It is that nobody established what it was for, nobody was trained properly, the workflow around it never changed, the incentives pointed elsewhere, or the people expected to use it were never consulted. These are leadership and systems failures wearing a technology costume.
Which is why the description names systems thinking specifically. A technology decision is never isolated: it changes workflows, roles, skill requirements, budgets and power. ⚠ A leader who evaluates a tool on its features and not on the system it is entering will make an expensive mistake, and it is a mistake made constantly.
Two Florida public institutions carry this number — the University of North Florida and the University of West Florida — at three credits, with identical titles.
| Institution | Its title | Credits | Contact hours |
|---|---|---|---|
| University of West Florida (SUS) | Instructional Technology Leadership | 3 | not published |
| University of North Florida (SUS) | Instructional Technology Leadership | 3 | not published |
✅ Both carriers use the statewide title unchanged and award three credits, and UWF's description matches the statewide description almost word for word. The 45 contact hours recorded here is Florida's convention for a three-credit lecture course. UWF places the course in the School of Education, Department of Instructional Design and Technology.
⚠ UNF's catalogue was not reachable when this guide was written — its online catalogue is client-rendered and its archived catalogue PDFs are blocked to automated retrieval. The matching titles make divergence unlikely, but UNF students should treat their syllabus as governing.
Worth dwelling on, because it changes who should take this course and what they should expect.
Florida's description names education, training, military, public sector and non-profits. ⚠ Most courses titled "instructional technology leadership" would mean school technology leadership. This one deliberately does not.
What differs between the sectors is worth knowing: public sector and military settings have procurement rules that constrain what can be bought and from whom; non-profits operate under funding restrictions that make sustainability the binding constraint; corporate settings can move fast and change direction faster; schools carry student data privacy obligations and community accountability that others do not.
⚠⚠ What is common is the leadership problem itself — that technology fails for organisational reasons rather than technical ones, and that the failure is predictable. A student who understands that transfers between sectors easily, which is a genuine career advantage in a field where people move between corporate, government and education work.
Students sometimes expect a survey of technologies and find a course about organisations. ⚠ That is the design, and it is correct.
The systems argument is that an organisation is a set of interacting parts, and that a change to one part produces effects elsewhere that were not intended and are frequently not noticed until later. A new learning platform does not simply replace an old one: it changes what instructors can do, what support staff must know, what data exists about learners, what reporting becomes possible, and what work is created for whom.
⚠⚠ The characteristic failure is a locally sensible decision with unaccounted-for consequences elsewhere — a platform chosen on price that generates years of support burden, or a tool adopted for one department that fragments the organisation's data.
⚠ The practical discipline this implies is asking, before any technology decision: whose work changes, what skills does that require, what else connects to this, what happens when it is replaced, and who was not consulted who will have to live with it. Those questions are unglamorous and they prevent most of the failures the field is known for.
A specific point from the change management literature that is worth carrying out of the course.
When people resist a new technology, the instinctive leadership reading is that they are change-averse. ⚠⚠ Frequently they have information the decision-maker did not: the tool does not fit the actual workflow, it adds steps, it breaks something that worked, or the training assumed knowledge they do not have.
Treating resistance as a diagnostic signal rather than an obstacle is both more effective and more accurate, and it connects directly to the needs assessment discipline taught earlier in the sequence (EME3624) — ask the people doing the work.
A 4000-level course taken late in the sequence, after the design and development courses have shown what the work involves. No prerequisite is recorded statewide or by UWF.
⚠ It pairs naturally with EME4083 (Program Evaluation) — making an evidence-based case for a technology investment requires evaluation evidence, and the two courses supply the two halves of that argument.
⚠ It carries upper-division credit, which a bachelor's degree requires and a lower-division course cannot supply. Florida's statewide record classifies it as transferable to an institution offering the same course, with no Gordon Rule designation and no general-education category — programme coursework. It is marked for dual enrolment with elective high-school credit; ⚠ that marking is near-universal across the EME prefix, so it says nothing distinctive about this course.
✅ Matching titles and credits make this a straightforward transfer. Keep your syllabus.
⚠⚠⚠ This course is, right now, the most immediately applicable in the sequence — because organisations everywhere are making AI adoption decisions badly, and for exactly the reasons this course diagnoses.
The pattern is the one the field has seen before and should recognise instantly. A technology arrives with strong claims. Leadership feels pressure to adopt it. A tool is purchased. Training is a one-hour session. The workflow does not change. Nobody defined what success would look like. ⚠ Eighteen months later the licence is renewed out of inertia or quietly dropped, and no one can say whether it helped.
Everything this course teaches applies directly:
⚠⚠ There is also a distinctively leadership-level question here that a graduate should be ready for: what is the organisation's obligation to the people whose work changes? If routine content production is automated, the capable answer is not a redundancy programme — it is reskilling toward analysis, evaluation and judgement, which is what the rest of this sequence teaches. A technology leader who can see that and act on it early is doing the job the course describes.
For your own study these tools help with drafting a technology plan, generating stakeholder-analysis prompts and rehearsing a case to an executive. ⚠ The sharpest exercise available, though, is to apply the course's own evaluation framework to generative AI itself — honestly, including the costs and the unknowns. Doing that well is precisely the professional capability the course is trying to produce.
Generated September 15, 2026 · Updated September 15, 2026