Automated Onboarding for Online Faculty

Problem & Learner Context

Each year, a dozen new adjunct faculty join USC Price's online graduate programs — typically with limited experience teaching in a fully asynchronous environment. Without the social scaffolding of a physical campus, these instructors were left to navigate a fragmented and often isolating onboarding process largely on their own. Three distinct problems characterized the status quo.

Isolation. New instructors had little more than a few preliminary phone calls with HR and the Program Coordinator, plus functional emails walking through access procedures. The standing invitation to "reach out if you have any questions" added to the burden by forcing instructors to self-diagnose whether they were genuinely stuck or had simply overlooked an instruction. Those who were already confident self-starters had an outsized advantage over those who weren't.

Fragmentation. Different offices at USC Price managed different onboarding tasks — compliance trainings, email setup, LMS orientation, course content access — with little awareness of each other's requirements. One office might push outdated instructions after a tool update; another might repeat requirements an instructor had already completed. The instructor bore the greatest burden of coordination, with no consolidated view of their own progress.

One-size-fits-all training. Two hour-long sessions on Moodle and Adobe Connect were required of all new faculty two weeks before the semester. Most content was not targeted to each instructor's actual comfort level or specific teaching context, resulting in wasted time for those already proficient and information overload for those who weren't.

My Design Decisions & Rationale

The core insight driving the solution was that onboarding in an online environment needs to do the social work that a physical campus does automatically — and that this requires responsiveness, not just more information. That framing led to two foundational design decisions.

First, all onboarding content — previously distributed across separate offices — was centralized into a single HubSpot-based experience. This gave instructors a unified, transparent view of their own progress and eliminated the confusion caused by overlapping office responsibilities. HubSpot was chosen specifically for its workflow automation capabilities, which allowed the system to respond to instructor behavior in real-time without requiring manual monitoring from staff.

Second, an iterative design process was adopted because of a key constraint: certain tasks could only be completed after others were finished. For example, an instructor could only access Moodle course content after their USC NetID was provisioned — a step outside the design team's direct control. Mapping these dependencies forced the experience to be structured around each instructor's realistic situation rather than an idealized linear sequence. Each design iteration cycled between ideation, wireframing, and testing with actual faculty, surfacing constraints that weren't visible from planning documents alone.

Project Walkthrough & Highlights

The final system had two defining features: the centralization of previously fragmented onboarding content into one coherent experience, and a layer of logic-driven automation that enabled personalized — but non-invasive — support based on how each instructor engaged with the system.

HubSpot workflows were the vehicle for this personalization. One workflow assessed instructor comfort after each onboarding module: at the conclusion of a task, instructors rated their perceived confidence on a 1–5 scale. Based on their cumulative score, the system automatically triggered varied responses — from a warm invitation to schedule a one-on-one meeting, to a curated set of supplemental resources, to a brief virtual affirmation. A second workflow tracked time since last login; if an instructor had been absent for more than seven days, a gentle nudge email was automatically sent to re-engage them — without ever requiring a staff member to manually follow up.

These automations were designed to feel supportive rather than surveillance-like: the goal was to replicate the informal check-in a colleague might offer in a physical office, at scale and without administrative overhead.

Results & Evidence of Value

[Describe any measurable outcomes from the onboarding system — completion rates, time-to-readiness, instructor self-reported confidence, or reduction in support requests to staff. If post-launch data is unavailable, describe the evaluation metrics and collection mechanisms designed into the system blueprint.]

Reflection & Lessons Learned

[Identify one aspect of the onboarding system's design or implementation that didn't perform as intended, how you would approach it differently given more time or stakeholder access, and the broader design or systems insight you carry forward from this project.]