LMS 3.0: From Delivery to Learning Orchestration

INTRODUCTION

AT 8:15 A.M. ON A TUESDAY IN SEPTEMBER, THE REGISTRAR OPENS A WAITLIST FOR NURSING 302 WHILE THE CLINICAL COORDINATOR CONFIRMS 12 HOSPITAL PLACEMENTS ACROSS TWO HEALTH SYSTEMS. ZOOM LINKS FOR THE SIMULATION LAB MUST BE TIME-GATED. BACKGROUND CHECKS, HIPAA MODULES, AND VACCINE RECORDS NEED VERIFICATION BEFORE STUDENTS STEP ONTO A FLOOR. A PROCTORING VENDOR EXPECTS ROSTERS BY 9:00 A.M., THE SIMULATION SYSTEM NEEDS PRECONFIGURED MANIKIN SCENARIOS, AND TRANSPORTATION VOUCHERS MUST BE ISSUED BY NOON. ADMISSIONS WANTS TO SEE CAPACITY BEFORE ADMITTING THREE LATE TRANSFERS. COMPLIANCE ASKS FOR A COMPLETE AUDIT TRAIL.

ON PAPER THIS IS “ONE COURSE.” OPERATIONALLY IT IS A CHOREOGRAPHY OF PEOPLE, TOOLS, TIME WINDOWS, AND POLICY. THE ORIGINAL LEARNING MANAGEMENT SYSTEM—WHERE WE UPLOADED A SYLLABUS AND POSTED ANNOUNCEMENTS—CANNOT RUN THAT CHOREOGRAPHY END TO END. THE WORK HAS MOVED FROM POSTING CONTENT TO COORDINATING FLOW.

A USEFUL METAPHOR LIVES HERE, BUT ONLY TO PLACE A PIN IN THE MAP: WE ARE MOVING FROM A WAREHOUSE OF MATERIALS TO A CONTROL TOWER. STOCKING SHELVES AND LABELING BINS MATTERED IN THE FIRST ERA; IN THE NEXT, COORDINATING WHAT MOVES, WHO IS CLEARED TO MOVE, AND WHEN THE RUNWAY IS OPEN IS THE JOB.

THIS IS THE CASE FOR LMS 3.0 AS AN ORCHESTRATION SYSTEM—WHAT THAT MEANS IN OPERATIONAL TERMS, HOW THE SOFTWARE CHANGES, AND WHY GOVERNANCE AND PROCUREMENT MUST FOLLOW.

WHAT THE FIRST TWO ERAS DID

THE FIRST ERA WAS COURSE WEBSITES.

1997: EARLY SYSTEMS, INCLUDING MY OWN COURSEINFO, SHIPPED TEMPLATES FOR SYLLABI, ASSIGNMENTS, DISCUSSION BOARDS, AND BASIC GRADEBOOKS ON MODEST WEB SERVERS. A FACULTY MEMBER COULD STAND UP A COURSE SHELL IN AN AFTERNOON.
1998: MY SYSTEM MERGED WITH BLACKBOARD INC. THE COMBINED COMPANY TOOK THE CONCEPT CAMPUS-WIDE AND BUILT CONNECTIVE TISSUE TO AUTHENTICATION SYSTEMS (LDAP, ACTIVE DIRECTORY) AND STUDENT INFORMATION SYSTEMS (MOSTLY VIA BATCH FLAT FILES).
EARLY 2000S: WE INTRODUCED BLACKBOARD BUILDING BLOCKS, AN EXTENSIBILITY FRAMEWORK THAT LET THIRD PARTIES ADD TOOLS INTO THE COURSE EXPERIENCE WITHOUT FORKING CORE CODE. STANDARDS LIKE SCORM 1.2 (CIRCA 2001) AND QTI MADE CONTENT PORTABLE ENOUGH TO IMPORT AND TEST ACROSS VENDORS.
2004: BLACKBOARD WENT PUBLIC ON NASDAQ AS BBBB. INSTITUTIONS STANDARDIZED ON A SINGLE LMS TO RUN WEB-BASED COURSES AT SCALE. THE VISIBLE SUCCESS METRIC WAS COURSE COUNT AND UPTIME.

WHAT THIS ERA DID WELL WAS TO CENTRALIZE THE ONLINE ARTIFACTS OF A COURSE. A STUDENT LOGGED IN, FOUND THE SYLLABUS, AND POSTED TO THE FORUM. THE OPERATIONAL WORK PRODUCT WAS CONTENT AND COMMUNICATION IN A COURSE SHELL. THE ARCHITECTURE MATCHED: A DATABASE OF COURSES, USERS, ROLES, AND FILES; A GRADEBOOK; APIS TO MOVE ROSTERS AND SCORES.

THE SECOND ERA STITCHED TOOLS TOGETHER.

2010: IMS GLOBAL (NOW 1EDTECH) RELEASED LTI 1.0, MAKING IT STRAIGHTFORWARD TO LAUNCH AN EXTERNAL TOOL WITH A SHARED CONTEXT. BY 2018, LTI ADVANTAGE ADDED GRADE RETURN AND DEEP LINKING.
INSTITUTIONS ADDED MOBILE APPS, VIDEO PLATFORMS, PROCTORING, PLAGIARISM DETECTION, AND SIMULATION LABS. WE TIED SIS AND DIRECTORY SYSTEMS TIGHTER, AND WE GOT BETTER DASHBOARDS. THE BIG OPERATIONAL UPGRADES WERE IDENTITY CONSISTENCY AND TOOL CHOICE.

BUT THE CENTER OF GRAVITY REMAINED CONTENT AND TOOLS PRESENTED IN A COURSE FRAME. WE ADDED BETTER PIPES AND MORE SPIGOTS. WHAT WE DID NOT ADD WAS A BRAIN THAT COORDINATES PEOPLE, TOOLS, TIME, AND POLICY AS A WHOLE.

PUSHING CONTENT IS NOT THE SAME AS RUNNING THE LEARNING OPERATION.

WHAT CHANGED ON THE GROUND

THREE FORCES MOVED THE CENTER OF GRAVITY FROM CONTENT TO ORCHESTRATION.

1) MODALITY AND SETTING DIVERSIFIED.

SYNCHRONOUS AND ASYNCHRONOUS MOVED FROM A BINARY TO A MIX. A WEEK MIGHT COMBINE A LIVE COHORT SESSION, A SIMULATION, AN EXTERNAL PLACEMENT, AND REFLECTIVE WORK.
SETTINGS EXPANDED: CAMPUS LABS, CLINICAL SITES, EMPLOYER FLOORS, LOCAL MAKERSPACES, AND HOME SETUPS ALL BECAME LEGITIMATE LEARNING VENUES. EACH VENUE CAME WITH ITS OWN POLICY ENVELOPE AND TIME CONSTRAINTS.

2) IDENTITY, ROLES, AND ENTITLEMENTS GOT MORE COMPLEX.

STUDENTS CARRY MULTIPLE AFFILIATIONS: DEGREE-SEEKING, CERTIFICATE EARNERS, EMPLOYEES IN TUITION PROGRAMS, VETERANS WITH FUNDING CONSTRAINTS. INSTRUCTORS CROSS INSTITUTIONS. PRECEPTORS AND MENTORS WORK OUTSIDE THE CAMPUS DIRECTORY.
ACCESS MUST BE MORE GRANULAR: WHO CAN SEE A SKILL PROFILE, A REFLECTIVE ARTIFACT, A PERFORMANCE VIDEO, OR A FEEDBACK LOG DEPENDS ON ROLE, AFFILIATION, AND CONSENT.

3) OUTCOMES MOVED FROM GRADES TO EVIDENCE.

GRADES STILL MATTER, BUT THEY NO LONGER SUFFICE. PROGRAMS MAP OUTCOMES TO SKILLS FRAMEWORKS (ESCO, O*NET, AND DISCIPLINE-SPECIFIC TAXONOMIES). EVIDENCE MUST BE PORTABLE AS MICRO-CREDENTIALS, BADGES, AND VERIFIED ASSESSMENTS.
FUNDERS AND REGULATORS ASK FOR PROOF: COMPLETION WITH WAGE GAINS, CLINICAL HOURS BY SETTING, ASSESSMENT VALIDITY, AND PRIVACY COMPLIANCE BY DESIGN.

Lesson — Treat identity and roles as dynamic contexts, not static labels.

The system needs to understand that students hold multiple affiliations and that instructors can cross institutions, while mentors may work entirely outside the campus directory. Access must therefore become more granular, depending on role, affiliation, and consent for who can see a skill profile or a performance video. This complexity is now the norm for managing learners.

THE DAY-TO-DAY CONSEQUENCES ARE IMMEDIATE. A PROGRAM DIRECTOR NEEDS TO KNOW IF A STUDENT IS CLEARED FOR A CLINICAL ROTATION AT HOSPITAL B NEXT WEDNESDAY FROM 7 A.M. TO 3 P.M., WHETHER THE REQUIRED MODULES ARE COMPLETE AND IN-DATE, WHETHER THE PRECEPTOR HAS ACCEPTED THE PLACEMENT, AND WHETHER TRANSPORTATION AND CHILDCARE WAIVERS ARE APPROVED. POSTING A FILE CANNOT ANSWER THOSE QUESTIONS. COORDINATING ROLES, TIME WINDOWS, PREREQUISITES, AND POLICY CAN.

DEFINING LEARNING ORCHESTRATION

LEARNING ORCHESTRATION COORDINATES THE WHO, WHAT, WHEN, WHERE, AND UNDER-WHAT-CONDITIONS OF LEARNING, AND RECORDS EVIDENCE THAT THE RIGHT THING HAPPENED.

IT IS NOT A NEW LABEL FOR INTEGRATIONS. IT IS A SET OF PRIMITIVES THE SYSTEM MUST REASON ABOUT.

PEOPLE AND IDENTITIES: A PERSON MAY HOLD MULTIPLE IDENTITIES (STUDENT, EMPLOYEE, MENTOR) ISSUED BY DIFFERENT AUTHORITIES. THE SYSTEM MUST RECONCILE IDENTITIES AND COMPUTE ENTITLEMENTS.
ROLES AND RELATIONSHIPS: INSTRUCTORS, PRECEPTORS, ASSESSORS, PEERS, ADMINISTRATORS, AND EMPLOYERS HAVE ROLES AND RELATIONSHIPS THAT CHANGE BY CONTEXT AND TIME.
RESOURCES AND CAPABILITIES: TOOLS (VIDEO, SIMULATION, PROCTORING), SPACES (LABS, HOSPITAL FLOORS), AND SERVICES (CREDENTIALING, BACKGROUND CHECKS) ARE RESOURCES THE SYSTEM CAN ALLOCATE AND CONFIGURE.
ACTIVITIES AND STATES: A LEARNING ACTIVITY HAS STATES (SCHEDULED, IN-PROGRESS, SUBMITTED, ASSESSED, VERIFIED) THAT THE SYSTEM MUST TRACK.
TIME AND WINDOWS: LEARNING HAPPENS IN WINDOWS WITH CONSTRAINTS—DEADLINES, LAB SLOTS, CLINICAL SHIFTS—AND WITH DEPENDENCIES.
POLICY AND CONSENT: RULES DETERMINE WHO CAN ACT, WHO CAN SEE, AND WHAT MUST BE COMPLETED BEFORE PROCEEDING. CONSENT APPLIES TO DATA SHARING AND OBSERVATION.
EVENTS AND EVIDENCE: THE RECORD OF WHAT HAPPENED—EVENTS, LOGS, SUBMISSIONS, ASSESSMENTS—MUST BE CAPTURED, LINKED TO OUTCOMES, AND MADE PORTABLE.

> In orchestration, “launch a tool” is a side effect of a plan, not the plan itself.

Lesson — Define learning operations using a core set of primitives like people, resources, and policy.

Instead of just focusing on integrations, an orchestration system must reason about its core components. These primitives include people with various identities, resources like labs and tools, and activities that have states like "scheduled" or "assessed." An operation is defined by these elements plus time windows, rules, and the resulting evidence.

IN ORCHESTRATION, THE SYSTEM ASKS: WHO MUST DO WHAT BY WHEN, UNDER WHICH POLICY, WITH WHAT RESOURCES, AND HOW WILL WE VERIFY AND REPORT IT.

ORCHESTRATION IS COORDINATION WITH PROOF.

ARCHITECTURE FOR LMS 3.0

AN ORCHESTRATION SYSTEM IS OPINIONATED ABOUT ARCHITECTURE BECAUSE THE OPERATIONAL LOAD DEMANDS IT.

1) EVENT BACKBONE

EVERY MEANINGFUL CHANGE IS AN EVENT—ENROLLMENT ACCEPTED, PLACEMENT CONFIRMED, CONSENT GRANTED, SUBMISSION RECEIVED, ASSESSMENT RECORDED. THE SYSTEM PUBLISHES AND CONSUMES EVENTS IN NEAR REAL TIME.
STANDARDS HELP: CALIPER ANALYTICS (1.0 RELEASED AROUND 2015) AND XAPI (CIRCA 2013) PROVIDE EVENT VOCABULARIES. INSTITUTIONS SHOULD DEMAND DIRECT ACCESS TO EVENT STREAMS FOR ANALYSIS AND AUDIT.

2) ORCHESTRATION ENGINE

A WORKFLOW ENGINE RUNS STATEFUL PROCESSES—PLACEMENTS, ASSESSMENTS, CREDENTIAL ISSUANCE—ACROSS TOOLS AND SERVICES. IT KNOWS PREREQUISITES, CHECKS POLICY, AND ADVANCES STATE.
LOW-CODE WHERE APPROPRIATE, BUT WITH VERSIONING AND CHANGE CONTROL. EACH FLOW MUST BE TESTABLE AND OBSERVABLE.

3) POLICY AND ENTITLEMENT LAYER

ATTRIBUTE-BASED ACCESS CONTROL COMPUTES WHO CAN ACT OR SEE, BASED ON ROLES, AFFILIATIONS, CONSENT, AND CONTEXT. POLICIES ARE DECLARED, NOT HARD-CODED.
CONSENT REGISTRY: WHO GRANTED WHAT, WHEN, TO WHOM, AND FOR WHAT PURPOSE—REVOCABLE AND AUDITABLE.

4) COMPETENCY AND OUTCOME GRAPH

A GRAPH LINKS PROGRAMS → COURSES → ACTIVITIES → ASSESSMENTS → EVIDENCE → COMPETENCIES. SKILLS FRAMEWORKS (LOCAL OR EXTERNAL) SIT AS FIRST-CLASS OBJECTS.
EVIDENCE PORTABILITY: MICRO-CREDENTIALS AND BADGES REFERENCE GRAPH NODES; THEY ARE NOT SCREENSHOTS OF TRANSCRIPTS.

5) INTEGRATION TIER

STANDARDS-FIRST FOR TOOLS AND ROSTERS: LTI ADVANTAGE (NAMES-AND-ROLES, DEEP LINKING, GRADE RETURN), ONEROSTER FOR K–12 ROSTERS AND GRADES, AND VENDOR APIS WHERE NEEDED.
IDENTITY BROKERING: SAML, OAUTH 2.0, OPENID CONNECT, AND SCIM FOR PROVISIONING. MULTI-INSTITUTION AND EMPLOYER SCENARIOS REQUIRE FEDERATION BY DESIGN.

6) DATA PLATFORM

A UNIFIED DATA MODEL STORES PLANS, STATES, EVENTS, EVIDENCE, AND POLICIES WITH LINEAGE. SNAPSHOTS ARE USEFUL; EVENT HISTORY IS ESSENTIAL.
PRIVACY BY DESIGN: FERPA, GDPR, AND HIPAA-IMPACTED PROGRAMS DEMAND CONFIGURABLE RETENTION, PURPOSE LIMITATION, AND SUBJECT RIGHTS.

7) OBSERVABILITY AND AUDIT

DASHBOARDS FOR FLOW HEALTH, NOT JUST PAGE VIEWS—QUEUE DEPTH, ERROR RATES BY STEP, SLA ADHERENCE FOR PLACEMENTS AND ASSESSMENTS.
AUDIT TRAILS THAT A REGULATOR CAN FOLLOW WITHOUT A MANUAL.

THE ARCHITECTURAL POINT IS SIMPLE: THE LMS BECOMES THE COORDINATOR OF FLOWS AND EVIDENCE. THE COURSE SHELL, CONTENT STORE, AND GRADEBOOK REMAIN; THEY ARE NOW PARTS INSIDE A LARGER SYSTEM THAT RUNS TIME-BOUND, POLICY-CONSTRAINED WORK.

HOW ORCHESTRATION SHOWS UP DAY TO DAY

EXAMPLES MAKE THIS CONCRETE. FIVE COMMON CASES ILLUSTRATE THE CHANGE.

1) CLINICAL PLACEMENTS

INPUTS: STUDENT ELIGIBILITY, PARTNER HOSPITAL CAPACITY, PRECEPTOR ROSTERS, IMMUNIZATIONS, HIPAA AND OSHA MODULES, BACKGROUND CHECKS.
ORCHESTRATION: COMPUTE ELIGIBILITY, REQUEST PLACEMENT OFFERS, MATCH STUDENTS TO SLOTS, VERIFY CONSENT TO SHARE REQUIRED DATA WITH PARTNERS, PREFLIGHT ACCESS TO HOSPITAL SYSTEMS VIA LTI OR SSO, AND SCHEDULE REFLECTIONS AND ASSESSMENTS.
EVIDENCE: SHIFT ATTENDANCE, SKILL CHECKLISTS SIGNED BY PRECEPTORS, SIMULATION PERFORMANCE, AND ASSESSOR RUBRICS ROLL UP TO PROGRAM OUTCOMES AND CLINICAL-HOUR REQUIREMENTS.

2) APPRENTICESHIPS AND WORK-BASED LEARNING

INPUTS: EMPLOYER PROJECTS, MENTOR AVAILABILITY, SAFETY TRAINING, UNION RULES, WAGE REPORTING TIMELINES, AND REQUIRED OBSERVATIONS.
ORCHESTRATION: ASSIGN PROJECTS BASED ON PREREQUISITES, SCHEDULE CHECKPOINTS, ROUTE SUPERVISOR EVALUATIONS, VERIFY OFF-CYCLE FUNDING REPORTS, AND SURFACE PORTFOLIO EVIDENCE TO BOTH INSTITUTION AND EMPLOYER.
EVIDENCE: COMPETENCIES TIED TO O*NET OR INTERNAL FRAMEWORKS, WITH ARTIFACTS AND THIRD-PARTY VERIFICATIONS.

3) LAB COURSES WITH SCARCE EQUIPMENT

INPUTS: LAB STATIONS, TA SHIFTS, CONSUMABLES, AND SAFETY MODULES.
ORCHESTRATION: ALLOCATE SLOTS, ENFORCE PREREQUISITES (SAFETY FIRST), PROVISION INSTRUMENT ACCOUNTS, AND ROUTE INCIDENT REPORTS.
EVIDENCE: LAB NOTEBOOKS, SENSOR DATA, AND TA SIGN-OFFS ALIGNED TO COMPETENCIES.

4) ASSESSMENT WITH EXTERNAL RATERS

INPUTS: RATER ROSTERS, CALIBRATION EXERCISES, RUBRICS, AND PRIVACY CONSTRAINTS FOR VIDEO SUBMISSIONS.
ORCHESTRATION: ASSIGN RATERS WITH CONFLICTS OF INTEREST SCREENED, SCHEDULE CALIBRATION, BLIND SUBMISSIONS WHERE POLICY REQUIRES, AND ENSURE FEEDBACK RETURNS WITHIN SLA.
EVIDENCE: RUBRIC SCORES WITH INTER-RATER RELIABILITY TRACKED AND ROLLED UP TO OUTCOMES.

5) SHORT-CYCLE CREDENTIALS AT SCALE

INPUTS: CATALOG OF MICRO-CREDENTIALS, PREREQUISITE MAPS, PROCTORING CONTRACTS, AND BADGE ISSUERS.
ORCHESTRATION: PRE-VALIDATE IDENTITY, SCHEDULE ASSESSMENTS WITH AVAILABLE PROCTOR WINDOWS, AUTO-ISSUE BADGES ON VERIFIED OUTCOMES, AND EXPORT MACHINE-READABLE RECORDS TO REGISTRARS AND EMPLOYERS.
EVIDENCE: DEFENSIBLE ASSESSMENT ARTIFACTS AND EVENT TRAILS.

ACROSS THESE CASES, SUCCESS LOOKS LIKE FEWER EMAILS, FEWER SPREADSHEETS, FEWER LAST-MINUTE EXCEPTIONS, AND CLEANER REPORTING. THE ORCHESTRATION LAYER MAKES THE NEXT ACTION CLEAR AND RECORDS WHAT HAPPENED WITHOUT A SCAVENGER HUNT.

THE WIN IS FLOW CLARITY AND VERIFIABLE OUTCOMES.

THE MIDPOINT PIVOT

RETURN TO THE METAPHOR, BRIEFLY AND ONLY TO RESET DIRECTION. IN THE CONTENT ERA WE BUILT A WAREHOUSE WITH WELL-LABELED SHELVES. IN THE INTEGRATION ERA WE ADDED LOADING DOCKS ON THREE SIDES. IN LMS 3.0 WE BUILD THE CONTROL TOWER: WE WATCH THE RADAR, CLEAR TRAFFIC, ASSIGN GATES, AND RECORD EVERY MOVEMENT AGAINST A FLIGHT PLAN. THE PLANES (TOOLS AND CONTENT) STILL MATTER; THE SAFETY, TIMING, AND OUTCOMES COME FROM COORDINATED CONTROL.

GOVERNANCE THAT FITS THE NEW WORK

AN ORCHESTRATION SYSTEM CHANGES WHO OWNS WHAT AND HOW DECISIONS ARE MADE.

FROM FEATURES TO FLOWS: GOVERNANCE BODIES SHOULD EVALUATE AND FUND FLOWS—CLINICAL PLACEMENT, EXTERNAL ASSESSMENT, SHORT-CYCLE CREDENTIALING—NOT JUST TOOL PURCHASES. A FLOW HAS OWNERS, SLAS, AND RUNBOOKS.
DATA STEWARDS AT THE TABLE: REGISTRAR, IR, PRIVACY, AND SECURITY MUST SHAPE THE DATA CONTRACT EARLY—WHAT EVENTS ARE CAPTURED, FOR HOW LONG, FOR WHAT PURPOSES, AND HOW CONSENT IS MANAGED.
POLICY AS CODE: APPROVALS MOVE FROM PDFS TO EXECUTABLE RULES WITH VERSION CONTROL. CHANGE MANAGEMENT INCLUDES POLICY REVIEW AND TEST PLANS.
SHARED SERVICE MODEL: THE ORCHESTRATION ENGINE IS A SHARED SERVICE WITH INTAKE, PRIORITIZATION, AND CAPACITY PLANNING. ACADEMIC UNITS BRING FLOWS; THE CENTRAL TEAM IMPLEMENTS AND OPERATES.

> Approvals move from PDFs to executable rules with version control.

Lesson — Govern operational flows, not just technology features.

Instead of buying stand-alone tools, governance bodies should fund entire processes like clinical placements or credentialing. A flow has owners, service-level agreements (SLAs), and operational runbooks. This requires bringing data stewards like the registrar and privacy officers into decision-making early to shape the data contract.

PROCUREMENT FOLLOWS.

RFPS SHOULD SPECIFY STANDARDS (LTI ADVANTAGE, CALIPER, XAPI, ONEROSTER), EVENT ACCESS REQUIREMENTS (TOPICS, SCHEMAS, LATENCY), AND POLICY/ENTITLEMENT CAPABILITIES (ATTRIBUTE-BASED ACCESS, CONSENT REGISTRY) AS MUST-HAVES.
CONTRACTS SHOULD DEFINE SLAS FOR FLOWS (TIME TO PLACEMENT MATCH, ASSESSMENT TURNAROUND) IN ADDITION TO SYSTEM UPTIME.
PRICING SHOULD ALIGN TO ORCHESTRATION VOLUME WHERE APPROPRIATE—FLOWS RUN, EVENTS PROCESSED, CREDENTIALS ISSUED—RATHER THAN SEAT COUNTS ALONE.

A PRAGMATIC BUILD PATH

YOU DO NOT REPLACE EVERYTHING AT ONCE. YOU ESTABLISH THE ORCHESTRATION CORE AND MOVE FLOWS ONTO IT.

Lesson — Begin by fixing one high-friction process to demonstrate immediate value.

Instead of a total replacement, identify a few flows that cause the most friction by tracking staff hours and error rates—clinical placements and badge issuance are common examples. The goal is to establish the orchestration core and move flows onto it incrementally. The right early win is not a shiny interface but fewer exceptions, faster cycle times, and cleaner evidence.

STEP 1: INVENTORY FLOWS

IDENTIFY THREE HIGH-FRICTION FLOWS BY EVIDENCE: NUMBER OF EXCEPTIONS, STAFF HOURS CONSUMED, AND ERROR RATES. CLINICAL PLACEMENTS, EXTERNAL ASSESSMENTS, AND BADGE ISSUANCE ARE COMMON STARTING POINTS.

STEP 2: ESTABLISH THE EVENT BACKBONE

WORK WITH YOUR LMS, SIS, AND TOOL VENDORS TO TURN ON EVENT PUBLISHING. IF A VENDOR CANNOT PROVIDE EVENT FEEDS, ISOLATE THAT RISK AND PLAN A REPLACEMENT.

STEP 3: STAND UP THE ORCHESTRATION ENGINE

CHOOSE A WORKFLOW PLATFORM THAT CAN RUN STATEFUL PROCESSES WITH VERSIONING AND OBSERVABILITY. START WITH A SMALL TEAM AND ONE FLOW.

STEP 4: MODEL POLICY AND CONSENT

EXTERNALIZE POLICY DECISIONS. CREATE A CONSENT REGISTRY TIED TO IDENTITIES. DOCUMENT WHO CAN ACT AND SEE AT EACH STEP.

STEP 5: CONNECT COMPETENCIES TO EVIDENCE

PICK ONE PROGRAM AND MAP ACTIVITIES AND ASSESSMENTS TO COMPETENCIES. USE THAT GRAPH TO DRIVE WHAT EVIDENCE YOU CAPTURE AND HOW YOU PRESENT IT.

STEP 6: OPERATE AND ITERATE

PUBLISH RUNBOOKS. SET SLAS. MEASURE AND SHARE WEEKLY. EXPAND TO THE NEXT FLOW ONLY WHEN THE PRIOR ONE MEETS RELIABILITY TARGETS.

> What you gain in the first 90 days is not a shiny interface. You gain fewer exceptions, faster cycle times, and cleaner evidence.

THAT IS THE RIGHT EARLY WIN.

STANDARDS AND INTEROPERABILITY THAT MATTER

STANDARDS ARE THE CONNECTIVE TISSUE, BUT ONLY IF USED WITH INTENT.

1EDTECH LTI ADVANTAGE: USE DEEP LINKING FOR ACTIVITY PLACEMENT, NAMES-AND-ROLES FOR ROSTER CONTEXT, AND ASSIGNMENT-AND-GRADE SERVICES FOR SCORE RETURN. REQUIRE TOOLS TO SUPPORT THE FULL SET.
CALIPER AND XAPI: DECIDE WHICH EVENTS YOU WILL RELY ON, AGREE ON EXTENSIONS FOR YOUR USE CASES, AND WIRE A PIPELINE YOU CAN QUERY IN MINUTES, NOT WEEKS.
ONEROSTER AND SCIM: KEEP ROSTERS AND IDENTITY IN SYNC WHEN LEARNERS CARRY MULTIPLE AFFILIATIONS.
QTI: WHERE MACHINE-SCORED ASSESSMENTS MATTER, KEEP ITEMS PORTABLE.

A STANDARD IS NOT A PROCUREMENT CHECKBOX. IT IS A COMMITMENT TO HOW YOUR OPERATION WILL REASON ABOUT PEOPLE, TIME, POLICY, AND EVIDENCE.

DATA, PRIVACY, AND AUDIT

ORCHESTRATION RAISES THE BAR FOR DATA GOVERNANCE. YOU WILL CAPTURE MORE EVENTS AND MORE SENSITIVE CONTEXT.

PURPOSE LIMITATION: ENUMERATE PURPOSES FOR EACH DATA CATEGORY—INSTRUCTION, ADVISING, PLACEMENT, RESEARCH—AND BIND ACCESS TO PURPOSE.
RETENTION BY DEFAULT: SET RETENTION SCHEDULES BY DATA TYPE AND CONTEXT. A CLINICAL VIDEO MAY REQUIRE A DIFFERENT SCHEDULE THAN A FORUM POST.
CONSENT WITH TEETH: KEEP A LEDGER OF CONSENTS WITH ISSUERS, SUBJECTS, PURPOSES, AND EXPIRATION. MAKE REVOCATION OPERATIONAL, NOT THEORETICAL.
RIGHT-SIZED OBSERVABILITY: INSTRUCTORS SHOULD SEE FLOW HEALTH FOR THEIR COURSES; PROGRAM LEADS SHOULD SEE AGGREGATE SLAS; AUDITORS SHOULD SEE EVIDENCE TRAILS.
ZERO TRUST POSTURE: AUTHENTICATE AND AUTHORIZE AT EACH STEP. NEVER ASSUME A TRUSTED INTERNAL NETWORK.

THESE ARE NOT BOLT-ONS. THEY ARE THE BASIS FOR THE AUDITS YOU WILL FACE AND THE TRUST YOU MUST MAINTAIN WITH LEARNERS AND PARTNERS.

ANALYTICS THAT ANSWER REAL QUESTIONS

WITH AN EVENT BACKBONE AND A COMPETENCY GRAPH, ANALYTICS CAN FINALLY ANSWER OPERATIONAL AND OUTCOME QUESTIONS TOGETHER.

OPERATIONAL: WHERE DO PLACEMENTS STALL? WHICH STEPS GENERATE EXCEPTIONS? WHICH TOOLS INTRODUCE ERROR? ARE SLAS MET BY SITE AND BY PARTNER?
OUTCOME: WHICH SEQUENCES LEAD TO MASTERY FASTER? HOW DOES WORK-BASED LEARNING PERFORMANCE ALIGN TO LATER EMPLOYMENT? WHICH ASSESSMENTS SHOW THE STRONGEST VALIDITY EVIDENCE?
EQUITY: WHO EXPERIENCES DELAYS OR DENIAL AT WHICH STEPS, AND WHAT POLICY OR PRACTICE CHANGE REDUCES THOSE GAPS?

THE DIFFERENCE FROM DASHBOARD-ERA ANALYTICS IS FOCUS. YOU ARE NOT COUNTING CLICKS. YOU ARE MEASURING A FLOW AND AN OUTCOME, TOGETHER, WITH EVIDENCE ATTACHED.

MARKET IMPLICATIONS

VENDORS AND INSTITUTIONS WILL BOTH CHANGE.

INCUMBENT LMS PROVIDERS WILL EXPOSE WORKFLOW, POLICY, AND EVENT CAPABILITIES, OR THEY WILL PARTNER WITH ORCHESTRATION LAYERS THAT DO. THE COURSE SHELL REMAINS, BUT THE HUB SHIFTS UP-STACK.
TOOL VENDORS WILL SHIP DEEPER LTI ADVANTAGE SUPPORT, PUBLISH CALIPER AND XAPI STREAMS, AND ACCEPT POLICY DECISIONS FROM THE ORCHESTRATION LAYER.
NEW ENTRANTS WILL SPECIALIZE IN FLOWS—PLACEMENTS, ASSESSMENTS, CREDENTIALING—WITH STRONG EVENT AND POLICY DNA, INTEGRATING THROUGH STANDARDS RATHER THAN PRIVATE HOOKS.
INSTITUTIONS WILL ORGANIZE AROUND FLOWS, NOT FEATURES. TEAMS WILL LOOK LIKE OPERATIONS CENTERS WITH RUNBOOKS, SLAS, AND WEEKLY REVIEWS.

FUNDING FOLLOWS CLARITY. WHEN LEADERSHIP CAN SEE CYCLE TIME DROP BY DAYS AND EXCEPTIONS FALL BY HALF, BUDGETS MOVE FROM PILOTS TO PLATFORMS.

ANTI-PATTERNS TO AVOID

BUILDING A SECOND MONOLITH: THE ORCHESTRATION LAYER COORDINATES; IT SHOULD NOT SWALLOW EVERY FUNCTION.
HIDING POLICY IN CODE: IF ONLY ONE DEVELOPER CAN EXPLAIN WHY A STEP BLOCKED, YOU HAVE OPERATIONAL RISK.
EVENT STREAMS AS AFTERTHOUGHT: IF YOU CANNOT OBSERVE IT, YOU CANNOT GOVERN IT.
STANDARD BY LOGO, NOT BY CAPABILITY: REQUIRING “SUPPORTS LTI” WITHOUT VERIFYING ADVANTAGE SERVICES PUTS YOU BACK IN CUSTOM GLUE.
IGNORING IDENTITY FEDERATION: CROSS-INSTITUTION AND EMPLOYER FLOWS BREAK WHEN IDENTITY IS A ONE-CAMPUS ASSUMPTION.

IF YOU CANNOT CHANGE IT SAFELY ON THURSDAY AT 4 P.M., YOU DO NOT OPERATE IT.

A SHORT HISTORY THAT EXPLAINS THE PRESENT

IT HELPS TO REMEMBER HOW WE ARRIVED HERE.

1997: EARLY LMS PLATFORMS PROVED THAT COURSE WEBSITES COULD BE STOOD UP QUICKLY AND USED BY NON-TECHNICAL FACULTY.
1998–2004: BLACKBOARD BROUGHT INSTITUTIONAL SCALE, VENDOR ECOSYSTEMS, AND OPERATIONAL RELIABILITY. BUILDING BLOCKS CREATED A PATTERN FOR EXTENSIBILITY THAT RESPECTED THE CORE.
2006: BLACKBOARD ACQUIRED WEBCT, CONSOLIDATING THE CATEGORY AND CREATING A SINGLE TARGET FOR CONTENT STANDARDS AND INTEGRATIONS ACROSS MUCH OF HIGHER EDUCATION.
2010S: LTI SPREAD, MOBILE MATURED, AND THE TOOL MARKETPLACE GREW. THE SYSTEM BECAME A HUB WITH MANY SPOKES.
2020: PANDEMIC CONDITIONS STRESS-TESTED THE HUB MODEL. WE SAW THE LIMITS OF CONTENT-FIRST DESIGN WHEN FIELDWORK, LABS, AND EXTERNSHIPS NEEDED COORDINATION AT VOLUME.

EACH PHASE ADDED CAPACITY. NONE FULLY ADDRESSED FLOW. THAT IS THE REMAINING GAP AND THE PRESENT OPPORTUNITY.

WHAT THE OPERATING TEAM LOOKS LIKE

AN ORCHESTRATION-FIRST LMS SHAPES TEAM STRUCTURE AND DAILY PRACTICE.

ROLES: FLOW OWNERS (PRODUCT-STYLE), WORKFLOW ENGINEERS, POLICY STEWARDS, EVENT/DATA ENGINEERS, AND SERVICE RELIABILITY OWNERS.
CADENCE: WEEKLY FLOW HEALTH REVIEWS, INCIDENT POSTMORTEMS THAT INCLUDE POLICY AND DATA, AND QUARTERLY BACKLOG PRIORITIZATION ACROSS UNITS.
ARTIFACTS: FLOW DIAGRAMS UNDER VERSION CONTROL, POLICY-AS-CODE REPOSITORIES, CONSENT LEDGERS, AND PUBLISHED SLAS.
METRICS: TIME TO CLEAR A PLACEMENT, ASSESSMENT TURNAROUND, EXCEPTION RATE, EVIDENCE COMPLETENESS, AND PRIVACY REQUESTS SATISFIED.

THIS IS NOT FOREIGN. IT IS THE OPERATIONAL LANGUAGE EVERY MATURE DIGITAL OPERATION USES. WE ARE APPLYING IT TO LEARNING.

HOW TO TALK ABOUT THIS WITH FACULTY AND STAFF

PEOPLE DO NOT FEAR CHANGE; THEY FEAR LOSS. WHEN INTRODUCING ORCHESTRATION, EMPHASIZE ADDITIONS.

LESS OVERHEAD: FEWER EMAILS AND SPREADSHEETS, CLEARER NEXT STEPS, FASTER RESOLUTIONS.
MORE VISIBILITY: LIVE STATUS FOR PLACEMENTS AND ASSESSMENTS, TRANSPARENT POLICIES, AND PREDICTABLE TIMELINES.
BETTER EVIDENCE: CLEARER DEMONSTRATION OF LEARNING FOR STUDENTS, CLEANER REPORTING FOR PROGRAMS.

KEEP THE METAPHORS LIGHT AND THE BENEFITS CONCRETE. BRING BEFORE-AND-AFTER RUNBOOKS, NOT CONCEPT ART.

THE BET I’D MAKE TODAY

BUILD THE CONTROL TOWER AND WIRE IT TO THE PLANES YOU ALREADY FLY. START WITH ONE PAINFUL FLOW AND PURSUE THREE OUTCOMES: FEWER EXCEPTIONS, SHORTER CYCLE TIMES, AND STRONGER EVIDENCE. USE STANDARDS WHERE THEY ARE READY (LTI ADVANTAGE, CALIPER, XAPI, ONEROSTER) AND PUSH VENDORS TO PUBLISH EVENTS AND ACCEPT POLICY DECISIONS.

IF YOU ARE A VENDOR, EXPOSE ORCHESTRATION PRIMITIVES—EVENTS, WORKFLOWS, POLICY HOOKS—AND PRICE FOR FLOWS, NOT JUST SEATS. IF YOU ARE AN INSTITUTION, FUND THE SHARED SERVICE, APPOINT POLICY STEWARDS, AND HOLD WEEKLY FLOW REVIEWS.

THE OLD LMS JOBS DO NOT VANISH. COURSE SHELLS, CONTENT, AND GRADEBOOKS STILL MATTER. BUT THE CENTER OF GRAVITY HAS MOVED. THE SYSTEM THAT WINS THIS DECADE IS THE ONE THAT COORDINATES PEOPLE, TOOLS, TIME, AND POLICY—AND PROVES THE OUTCOME HAPPENED.

RETURN ONE LAST TIME TO THE METAPHOR THAT HAS EARNED ITS KEEP. THE WAREHOUSE IS STOCKED AND THE PLANES ARE SOUND. THE VALUE NOW IS IN THE TOWER—THE QUIET, DISCIPLINED WORK OF CLEARING TRAFFIC, SEQUENCING MOVEMENT, AND RECORDING EVERY TAKEOFF AND LANDING. THAT IS LMS 3.0.

LMS 3.0: from content delivery to learning orchestration