Shift Left and Tiered Support
ISS continually looks for ways to improve customer service, reduce unnecessary delays, and make the best use of the skills available across the department.
One way we do this is through Shift Left.
Shift Left is an established IT service-management practice that moves appropriate work closer to its source and toward the person or team best positioned to complete it efficiently. In a support environment, this often means enabling a lower support tier to resolve work that previously required a higher technical tier.
Within ISS, our goal is simple:
Work should be performed at the lowest appropriate support tier that can complete it safely, reliably, and effectively.
Shift Left is not simply moving workload from one team to another. The receiving team must be given the knowledge, documentation, training, tools, access, authority, and escalation criteria needed to perform the work successfully.
Industry Foundation
ITIL uses the term Shift Left to describe moving work closer to its source and toward the optimum person or team in order to improve flow, resolution time, customer satisfaction, and efficiency.
In technical support, this can include moving appropriate work from specialized technical teams to frontline support teams. It can also include moving work toward self-service or automation when customers can safely complete the activity themselves.
For additional background, see Atlassian: Service Request Management — Shift Left, which describes Shift Left as moving request fulfillment closer to the front line and customer to improve resolution time, simplify support, and reduce cost.
ISS adapts this principle to our environment rather than attempting to implement it as a rigid framework.
ISS Support Tiers
The ISS Communications Standard establishes tier-based response expectations.
For technical support, the general model is:
Tier 0 — Self-Service and Automation
Tier 0 describes work that can be completed without direct technician involvement.
Examples may include:
-
Customer-facing knowledge articles
-
Self-service tools
-
Automated processes
-
Automated remediation
-
Password or account self-service
-
Standard request forms that trigger automated workflows
Tier 0 is not an employee support team and does not change the response tiers established in the ISS Communications Standard. It is useful terminology when discussing opportunities to move appropriate work closer to the customer.
Tier 1 — Help Desk
The Help Desk is the primary entry point for technology support and should resolve as many requests as reasonably possible at first contact.
Tier 1 should have the documentation, tools, training, and access necessary to resolve common and repeatable requests.
Tier 2 — Customer Support Services
Customer Support Services handles work requiring additional technical capability, field support, configuration, troubleshooting, or access beyond the normal Help Desk role.
Tier 2 should resolve work that does not require the specialized engineering or administrative expertise of Tier 3.
Tier 3 — Specialized Technical Teams
Tier 3 includes specialized technical teams such as Infrastructure and other ISS areas responsible for complex systems, applications, architecture, engineering, administration, advanced troubleshooting, and higher-risk technical work.
Tier 3 expertise should be used where that expertise adds value rather than routinely performing work that another tier could safely and effectively complete.
Shift Left Is About Capability
The purpose of Shift Left is not to push work onto another team.
The purpose is to build capability closer to the customer.
A successful Shift Left effort may require the higher tier to invest time before any work moves. That investment may include:
-
Developing procedures
-
Creating scripts or automation
-
Creating troubleshooting guides
-
Providing training
-
Providing appropriate system access
-
Establishing safeguards
-
Defining standard configurations
-
Identifying exceptions
-
Establishing escalation criteria
-
Updating ticket routing
-
Providing hands-on practice
The higher-tier team may spend more time initially preparing another team to perform the work. The benefit occurs over time as customers receive faster service and specialized staff spend less time on routine work.
Identifying Shift Left Opportunities
Shift Left opportunities may be identified through:
-
Ticket trends
-
Repeated escalations
-
Customer wait times
-
Recurring requests
-
Service reviews
-
Retrospectives
-
Customer feedback
-
Help Desk feedback
-
Team observations
-
Workload or capacity concerns
-
Service improvement activities
-
New tools or automation capabilities
ISS periodically reviews tickets and service activity to identify work that may be resolved more efficiently through training, documentation, automation, self-service, or transfer to another support tier.
Good Candidates for Shift Left
A type of work may be a good Shift Left candidate when several of the following are true:
-
The work occurs frequently enough for the transfer to provide meaningful value.
-
The work follows a repeatable or predictable process.
-
Standard procedures can be created.
-
The work can be performed safely with defined access and controls.
-
Scripts, automation, templates, or tools can reduce complexity or risk.
-
The receiving tier can reasonably learn the required skills.
-
Customers currently experience delays while waiting for a higher tier.
-
The higher tier is performing routine work that does not normally require its specialized expertise.
-
Clear boundaries can be established between standard work and exceptional conditions.
-
Escalation criteria can be clearly defined.
Frequency alone does not make work appropriate for Shift Left.
Work That Should Remain at a Higher Tier
Some work belongs at a specialized tier.
Work should generally remain with the higher tier when it requires:
-
Specialized engineering or architectural judgment
-
Broad or highly privileged administrative access
-
Significant security authority
-
Complex diagnosis with no repeatable process
-
High-risk changes
-
Decisions affecting large portions of the College
-
Unusual or uncommon technical expertise
-
Regulatory or compliance decisions
-
Significant vendor or architectural coordination
-
Knowledge that cannot reasonably be transferred to the receiving tier
The goal is not to eliminate higher-tier involvement.
The goal is to reserve specialized resources for work that genuinely requires specialized expertise.
The ISS Shift Left Process
ISS uses the following process:
Identify → Evaluate → Enable → Transfer → Validate → Improve
1. Identify
Identify a type or class of work that may be better performed by another support tier or through self-service or automation.
The opportunity may originate from any ISS employee or team.
The current team should be able to explain the expected benefit. Examples may include:
-
Faster customer resolution
-
Fewer handoffs
-
Reduced customer wait time
-
Better use of specialized staff
-
Improved first-contact resolution
-
Reduced backlog
-
Better coverage
-
Greater consistency
-
Increased automation or self-service
2. Evaluate
The current team and proposed receiving team evaluate whether the work is appropriate to move.
Consider:
-
Complexity
-
Frequency
-
Risk
-
Customer impact
-
Required permissions
-
Required knowledge
-
Security implications
-
Existing documentation
-
Training requirements
-
Tools or automation needed
-
Dependencies
-
Common failure conditions
-
Exceptions requiring higher-tier involvement
A transfer should provide a meaningful service or operational benefit without creating unreasonable risk.
Managers of the affected teams should participate in the evaluation.
3. Enable
Before work transfers, the receiving team must be prepared to perform it successfully.
The originating team is responsible for helping develop the capability needed for the transfer.
Depending on the work, preparation may include:
-
An IT Hub procedure
-
Step-by-step operating instructions
-
Scripts or automation
-
Required access
-
Technical training
-
Hands-on practice
-
Troubleshooting information
-
Known error conditions
-
Validation or testing steps
-
Customer communication guidance
-
Examples of normal and abnormal situations
-
Clear escalation criteria
Knowledge transfer should be demonstrated, not assumed.
Whenever practical, members of the receiving team should successfully perform the work with the originating team available before the responsibility formally transfers.
4. Transfer
A cross-team Shift Left transfer requires agreement between the affected managers.
When the managers agree that the work is appropriate to transfer and the receiving team is prepared, they may authorize the transition.
If the managers cannot agree, the matter should follow the escalation process defined in Escalation and Resolving Disagreements.
Before the effective date:
-
The receiving team must be prepared to perform the work.
-
Required access must be available.
-
Documentation must be published and accessible.
-
Escalation criteria must be documented.
-
Ticket routing or categories should be updated when applicable.
-
Appropriate team members must be notified.
-
The Help Desk should be notified when the change affects ticket intake or routing.
-
Service documentation and Team Info should be updated when applicable.
-
A clear effective date should be established.
The communication should make clear:
-
What work is moving.
-
Which team will normally perform it.
-
When the change becomes effective.
-
What remains with the originating team.
-
When and how the work should be escalated.
After the effective date, the new support tier should become the normal destination for that class of work.
5. Validate
Shift Left work should be reviewed after implementation.
Managers and participating teams should determine whether the change is producing the intended result.
Questions may include:
-
Are customers receiving faster service?
-
Are more requests being resolved without additional handoffs?
-
Is the receiving team successfully completing the work?
-
Are tickets being escalated back unnecessarily?
-
Are errors increasing?
-
Does additional training or documentation appear necessary?
-
Has higher-tier workload decreased as expected?
-
Has customer satisfaction improved?
-
Are the escalation criteria working?
The amount and timing of validation should be proportional to the significance of the transfer.
A high-volume or higher-risk transfer may require more formal review than a small recurring task.
6. Improve
Shift Left is an iterative process.
Based on actual experience, ISS may:
-
Improve documentation
-
Provide additional training
-
Refine scripts
-
Adjust permissions
-
Change ticket routing
-
Add automation
-
Clarify escalation criteria
-
Move additional related work
-
Move some work back to the higher tier
-
Develop customer self-service
A transfer that does not produce the intended result should be adjusted.
Shift Left is successful when it improves the service, not merely when work changes teams.
Service Ownership Does Not Necessarily Transfer
Moving operational work does not automatically change ownership of the underlying service.
For example, a specialized team may remain accountable for the architecture, health, maintenance, security, and technical direction of a service while another support tier performs defined operational tasks within that service.
The distinction is:
Service ownership identifies who is accountable for the service.
Work ownership identifies which team normally performs a particular activity.
Any actual change in Service Owner, Technical Lead, or Backup Technical Lead assignments should follow the service-ownership requirements defined in Service Ownership and Responsibilities.
Operational Escalation Must Be Defined
Every Shift Left transfer must define the conditions under which the receiving tier should stop and involve the higher tier.
Examples may include:
-
The documented process does not apply to the situation encountered.
-
A script or automated process reports an unexpected result.
-
Required access is insufficient.
-
The task requires a nonstandard configuration.
-
The activity could affect additional customers or services.
-
The employee identifies a security concern.
-
The expected result is not achieved.
-
The problem appears to involve a larger service degradation or outage.
-
The work requires technical authority reserved for the higher tier.
Escalation criteria protect both teams.
The receiving team should not be expected to improvise beyond the authority or capability that was transferred. The higher tier should remain available for exceptions requiring its expertise.
Operational escalation of a technical issue is different from the management escalation process for disagreements or unresolved organizational concerns.
For management escalation, see Communication and Collaboration — Escalation and Resolving Disagreements.
Responsibilities for a Cross-Team Shift Left Transfer
The following RACI identifies the normal responsibilities for a significant cross-team Shift Left effort.
R = Responsible for performing the work
A = Accountable for the decision or outcome
C = Consulted before the action or decision
I = Informed about the action or decision
| Activity | Originating Team | Receiving Team | Affected Managers | Service Owner |
|---|---|---|---|---|
| Identify a potential Shift Left opportunity | R | C | A | C |
| Evaluate suitability, risk, and expected benefit | R | R | A | C |
| Develop procedures, tools, training, and escalation criteria | R | C | A | C |
| Complete training and demonstrate readiness | C | R | A | C |
| Approve cross-team transfer | C | C | R/A | C |
| Communicate the transfer and effective date | C | C | R/A | I |
| Perform the work after transfer | C | R | A | C |
| Support defined technical escalations | R | R | A | C |
| Validate results after implementation | C | R | A | C |
| Identify and implement improvements | R | R | A | C |
The RACI may be adjusted for a particular transfer when responsibilities differ, but those differences should be documented before the transfer becomes effective.
Disagreements About a Transfer
A team should not unilaterally transfer ongoing work to another team.
The affected managers are responsible for working together to determine whether the proposed transfer is appropriate, whether the receiving team is prepared, and when the transition should become effective.
When the affected managers agree, they have the authority to approve and implement the transfer.
If the managers cannot agree, or if concerns remain about workload, risk, authority, readiness, or departmental impact, the matter should follow the escalation process defined in Escalation and Resolving Disagreements.
The transfer should not become operational until the disagreement has been resolved through the appropriate level of authority.
Shift Left Can Continue
A successful transfer does not necessarily represent the final destination of the work.
For example:
Tier 3 → Tier 2
may later become:
Tier 3 → Tier 2 → Tier 1
and some work may ultimately become:
Tier 3 → Tier 2 → Tier 1 → Tier 0
Each movement requires the same basic question:
Can the next level perform this work safely, reliably, and effectively while improving service to the customer?
If the answer is yes, ISS should consider enabling that capability.
Connection to Our Values
People Matter because customers should receive help as quickly and effectively as practical, and employees should have the tools and preparation needed to succeed.
Inclusiveness Matters because employees at every support tier can contribute ideas for improving how services are delivered.
Communication Matters because successful transfers require clear expectations, documentation, training, notification, and escalation criteria.
Integrity Matters because work should only move when the receiving team is genuinely prepared and authorized to perform it.
Excellence Matters because Shift Left encourages ISS to continually improve service delivery, reduce unnecessary delays, build broader capability, and use specialized expertise where it provides the greatest value.