Description

This curriculum spans the design, execution, and governance of service request management in a manner comparable to a multi-workshop operational rollout, addressing the same workflows and decision logic used in real-world IT service delivery programs.

Module 1: Defining the Boundary Between Service Requests and Incidents

Establish criteria for classifying password resets as service requests versus incidents when associated with suspected credential compromise.
Implement routing rules to separate standard software installations (requests) from unexpected application failures (incidents) in the ticketing system.
Define escalation paths when a service request triggers an underlying system outage that transitions it into an incident.
Configure service catalog entries to exclude items that involve unplanned disruption, ensuring they are not misclassified as requests.
Document exceptions where user-initiated changes (e.g., workstation upgrades) require incident linkage due to risk of service degradation.
Train frontline analysts to recognize social engineering attempts disguised as routine access requests.

Module 2: Service Catalog Design and Standardization

Select which IT services to include in the catalog based on frequency, risk, and fulfillment complexity (e.g., laptop provisioning vs. firewall rule requests).
Define attribute requirements for each catalog item, such as approvers, cost centers, and required justification fields.
Implement version control for catalog entries when service offerings change due to vendor or compliance updates.
Integrate catalog data with CMDB to validate requester entitlements against configuration item ownership.
Enforce naming conventions and categorization to support reporting and prevent duplication across departments.
Conduct quarterly reviews with business units to deprecate obsolete services and identify new standardization opportunities.

Module 3: Workflow Automation and Approval Chains

Design conditional approval paths for hardware requests based on cost thresholds and requester role (e.g., executive vs. contractor).
Implement time-based escalation rules when approvals are not completed within SLA-defined windows.
Integrate with identity management systems to auto-approve low-risk requests from verified service accounts.
Configure parallel versus sequential approval models for multi-departmental requests like database access.
Log all approval decisions in audit trails to support compliance with data governance regulations.
Test failover routing for approver absence using delegation rules during PTO or role changes.

Module 4: Integration with Identity and Access Management

Map service request types to IAM provisioning workflows for automated user role assignment (e.g., onboarding).
Enforce least-privilege principles by validating access requests against job function codes in HR systems.
Implement recertification triggers for access granted via service requests, scheduling periodic reviews.
Block self-service requests for privileged accounts and enforce manual review by security teams.
Synchronize request fulfillment status with IAM systems to ensure access is revoked upon ticket closure.
Handle reconciliation when a user’s access request conflicts with existing group memberships or policies.

Module 5: Fulfillment Process Orchestration

Assign fulfillment ownership between service desk, specialized teams, and third parties based on technical scope (e.g., network vs. cloud).
Integrate with endpoint management tools to automate software deployment upon request approval.
Track fulfillment stages (e.g., pending, staged, deployed) to identify bottlenecks in provisioning timelines.
Implement pre-validation scripts to check system compatibility before fulfilling hardware or software requests.
Define rollback procedures when automated fulfillment fails or introduces configuration drift.
Measure fulfillment accuracy by auditing a sample of completed requests for compliance with standard builds.

Module 6: Metrics, Reporting, and Continuous Improvement

Select KPIs such as request-to-fulfillment cycle time, approval delay percentage, and reclassification rate.
Generate monthly reports showing top-requested services to identify candidates for self-service automation.
Monitor misclassification trends where service requests are converted to incidents and adjust triage guidance.
Compare SLA adherence across departments to detect systemic delays in approvals or fulfillment.
Use feedback loops from fulfillment teams to refine catalog item requirements and reduce rework.
Conduct root cause analysis on frequently rejected requests to improve requester guidance and validation rules.

Module 7: Governance, Compliance, and Audit Readiness

Define data retention policies for closed service request records in alignment with regulatory requirements.
Implement role-based access controls on the service request system to prevent unauthorized modifications.
Prepare audit packs demonstrating approval trails, fulfillment logs, and access entitlements for SOX or HIPAA.
Enforce mandatory justification fields for high-risk requests such as firewall exceptions or database exports.
Conduct access reviews to verify that fulfilled requests align with current user roles and responsibilities.
Document exceptions when emergency requests bypass standard workflows, requiring post-facto review.

Module 8: Self-Service Portal Strategy and User Experience

Select which request types to expose in the self-service portal based on risk, volume, and technical complexity.
Design intuitive request forms with dynamic fields that adapt based on user role or selected service.
Implement search and filtering to help users locate correct services without assistance.
Integrate with knowledge articles to provide contextual guidance during request submission.
Monitor abandonment rates to identify forms with excessive steps or unclear instructions.
Enforce input validation to reduce errors and rework, such as checking email format or cost center validity.