IT Support could never function well because its operational needs are extensive but its tool-embedded, globally accepted process is limited to covering only the basic fundamentals. A basic process cannot handle complexity.
The fact that Incident and Request Management have locked-in to the status quo through ITSM service tools has practically prevented the fundamentals from being extended by organisations who use them.
Every organisation has been constrained in this way.
A process that is rigidly locked-in and undeveloped completely misses ITIL's original intent. It's an irony, really. ITIL's purpose was always for organisations to understand the basis of good service management and then build upon its foundation to meet operational needs. The status quo means that accidentally, organisations have been unable to do so.
Against this backdrop, clearly, support always needed a dedicated "true" best practice methodology to define and standardise the functionality of service tools as they need to be so that organisations are not constrained by the extent of a framework alone.
This is the purpose of the Focus Framework for support Flow Management.
This White Paper explains some of support's many operational requirements that are generally unrecognised because they are too specific to be included in a general framework, so are absent in ITIL and the way the world works, but are integral to Flow Management methodology.
Introduction
The standard ticket-centric implementation of ITIL processes that every ITSM tool incorporates and so every organisation uses, stamps the belief that once a service ticket is raised with all of its requisite information, the correct ticket management process is one of just responding, "escalating" (reassigning) to another team as might be necessary, and completing the ticket before its SLA deadline is reached if that turns out to be possible.
IT support has many operational requirements though - many situations that often need to be navigated during the course of a ticket's lifecycle. Through support's process, teams need guidance for this, but process-led guidance is completely missing.
Once support's specific operational requirements are recognised and understood, which is what the Focus Framework brings forward, it becomes clear that our conventional approach is far from the mark, and in being deeply embedded in how the world works, is a substantial global constraint - the very costly reason that frequently weak support is commonplace.
What's in "the ITIL gap"?
The Focus Framework refers to support's standard practice process shortcomings as being "the ITIL gap". The process gap is wide, with many operational requirements in it, because Incident and Request Management are so minimal that they are in fact focused on the wrong thing - tickets, not the actual work that needs to be put in.
ITIL's processes are focused on the "ticket wrapper", not the mechanics of support activity that's needed to keep tickets moving towards timely completion. The ticket-focused process that means teams quickly lose focus beyond the initial ticket response, leading to many breaching their completion SLA and thereafter, there is still nothing to guide progression - nothing in the process to help ensure that tickets are eventually completed, and for the majority that are completed, that the outcome is successful in being quick and thorough enough.
As explained in the Focus Framework's other key article - "The ITSM breakthrough was always just two small steps away" - it is hard not to conclude that the basic ITIL approach couldn't be less adequate.
Sixteen general operational requirements that are missing from standard practice, that form the ITIL gap, are listed on page 9 of the Flow Management overview. You might recognise some of them, but without knowing what can be done to meet them until AP is understood.
Specific operational requirements - the most vital of them all - are explained in the AP Brief together with how to meet them. It covers those for good communication and coordination with service recipients so that support is no longer difficult to receive. Here, in this key article, are another four specific requirements of many more.
Four more of IT support's specific operational requirements
The Focus Framework sets out 21 support situations common to all IT support organisations that are unmanaged in ITIL standard practice but become closely guided and managed through Flow Management to transform support outcomes and the maturity of service operations. The four covered here are:
1. Team-wide and inter-team collaboration: It's uncoordinated, disconnected from support's process.
2. "Rejected" tickets, where the Service Desk needs to be reinvolved due to missing ticket information, or because of assignment to an incorrect ticket queue.
3. "Bounced" ticket management, when a need is assigned on to another resolver group.
4. Support waiting on a 3rd-party service provider (SIAM).
Handled well through AP for Flow Management, the transformation is:
1. Increased "first-level fix rate"; faster service; Service Desk enablement and learning; job satisfaction that comes from end-to-end ticket ownership; better team relationships; team-centred service (one aspect of it); lower cost of service provision.
2. Better inter-team relationships; Service Desk learning; avoidance of inappropriate delay.
3. Minimised delay for needs that weren't directed straight to the correct resolver group.
4. Close working relationship with suppliers; accountability for external service-provider support; meaningful service reviews; Service Integration and Management (SIAM) that works well.
All of the 21 support situations are identified in the framework's High Performance Principles course.
1. Disconnected collaboration
Collaboration tools for IT support are used in most IT organisations, whether it's Microsoft Teams, Slack, another service tool-integrated product, or a service tool's internal collaboration tool.
They are operationally essential, especially for the front-line Service Desk. Here, when a less experienced team member has a question about how to provide support for a ticket, they just need to ask and will often get replies from co-workers quickly enough that the ticket can be progressed well.
A Service Desk is usually very busy though. Teammates are usually caught-up in the support that they are providing, so cannot be relied upon for a prompt answer. Promptness is given a big boost if a team leader or manager is always on the collaboration tool's "pulse". Even then, though, a quick enough reply, and one that has the answer, can't be ensured every time. One of two things then happens:
The ticket is assigned onwards (escalated). Doing so avoids the ticket losing focus, to potentially sit untouched for a long period.
Sometimes, reassignment is inaccurate, and sometimes ticket information is missing that might have been captured if the collaboration was successful, increasing the need for covering situation #2 well - de-escalated (rejected) ticket management.
Ticket ownership is maintained, staying with the teammate who first responded because it's felt to be a case that the Service Desk should handle. A strong ticket management process is essential in this scenario, to avoid the common pitfall of such tickets falling into inaction, untouched for a long period. Busy Service Desks are responsible primarily for the constant influx of new support coming in. When not completed straight away at the initial response, as explained in the AP Brief, tickets naturally lose focus and age substantially before being reapproached.
The AP fix
The way to prevent both scenarios, both of which are detrimental because every Service Desk has the objective of maximising "first-level fix rate" and "first contact fix rate", is for collaboration to be integrated in a support process that ensures focus is always on the right activity at the right time, that is, AP. With it, collaboration situations can be given an allowed period for the collaboration to happen, making it "asynchronous" rather than needing to be in real time as is always the case without AP.
Flow Management's Async Collaboration app, called Team Together, integrates with tickets, AP, and Flow Management's Continual Knowledge Improvement app, to form a collaboration process in which teammates can post a question and not need to be concerned about getting an immediate reply. Instead, the "With Colleague" status rises to the top of the ticket owners's ticket list once the collaboration lead time has elapsed. At that point, if there hasn't been a reply, or one that helps maintain ticket ownership, the ticket is reassigned. The Service Desk has done everything that it can.
When effective help is provided before the collaboration lead time elapses, it is a first-level fix, and often a first contact fix, that lifts these key support metrics and pleases upper support teams in not receiving tickets that ought to be completed by the Service Desk, and not receiving tickets that haven't had enough background work carried out.
More importantly, though, with flow improved, a first-level fix often reduces how long is needed to reach completion, improving service experience, and it reduces cost per ticket because Service Desk staff are typically in lower salary brackets. It's also great for Service Desk learning and job satisfaction, in owning more tickets through to completion, or at least to a position where all requisite support activity has been carried out.
2. Tickets that need to be assigned back to the Service Desk (rejected tickets)
Some organisations ask upper-tier support teams to absorb and remedy Service Desk mistakes, where either the wrong team has been chosen, or the ticket is missing information necessary for it to be progressed, but doing so is naturally frowned-upon by those needing to absorb the mistake. Furthermore, it is important that Service Desk staff who are often quite new to the business and to IT, learn from mistakes when they are made, avoiding future recurrence, so having others absorb mistakes is not a good idea.
The AP fix
In Flow Management, like all of its capabilities, Service Desk Reinvolvement and Learning is integral to AP. Assignment back to the Service Desk is facilitated and naturalised, with delay to ticket progression absolutely minimised whereas ordinarily, in the absence of proactive, managerially overseen ticket management, with a Service Desk usually "caught-up in the here and now" of new tickets, rejected tickets easily end-up in an unmanaged place that is prone to a long delay or even unnoticed abandonment.
The reinvolvement and learning capability prompts when a ticket is being passed back, asking for selection of a reason, and for additional explanation. The person who raised the ticket and made the mistake is then notified of the reason, together with the team manager.
In AP, tickets at the "Rejected" status have a short progression threshold, so it immediately appears at the top of ticket lists for the remedial activity to be carried through straight-away. In advanced AP, together with other high priority statuses, it is team "swarmed" to ensure promptness of address.
With the advent of AP for asynchronous collaboration, Flow Management's Digital Channel Service Desk that relies on a well designed Service Catalogue to route tickets well, and to an extent, AI assisted ticket routing, the need for this capability lessens, but despite it not being a support situation that arises very frequently, it will always be an important factor that is generally unrecognised as being a requirement for good support; a gap in support's process that tickets fall down into, often leading to a bad service experience.
3. Bounced ticket management
The Focus Framework comprises twenty unprecedented good practice, high performance principles for IT support, plus many more specific principles. One specific is that when a ticket is "bounced", i.e., reassigned, to another support team and no support has yet been provided, if it was not raised from a call to the Service Desk call centre but was through digital channels and so necessitated a wait before initial triage, it must be responded-to ahead of new tickets arriving in the receiving team's ticket queue.
The reason for this principle is that if the ticket had been routed correctly in the first place, directly to the correct resolver group, the first response would already have happened, or would be happening very soon.
The Focus Framework sets out that the status for this situation should have a short progression threshold so that it quickly, or immediately, appears at the top of the receiving team's queue, removing the typical (industry benchmark) wait of over two hours each time a ticket is reassigned.
4. Coordination of support from 3rd-party suppliers
Good Service Integration and Management (SIAM) will manage contractual service levels well, in partnership with suppliers. In standard practice support though, support tends to be handed-off to suppliers and not revisited because "the ball is in the other court". It is a similar scenario to that explained in the AP Brief, of tickets that have missing information being handed-back to recipients but not revisted to ensure that the information is provided.
Generally speaking, it is a well recognised fact that suppliers do need to be managed. Like everything in support, prioritisation drives things forward and suppliers use the same weak system of prioritisation that everyone else does, that is the ITIL process. Involvement from an external service provider's client, to question whenever an agreed service level has not been met, is vital. Without it, like in any support organisation, "on-hold" tickets and those that have breached their SLA are naturally demoted in importance, resulting in ticket stagnation that can easily become an excessive delay.
AP brings forward the means to work closely with service partners, to proactively oversee SLA breaches. When a partner's SLA breaches, the internal support team's ticket reaches the top of a ticket list, prompting coordination with the supplier to "rein it in". The process produces insightful ticket notes at the right time that are useful for discussion at supplier service review meetings, bringing forward strong SIAM governance.
These examples, amongst the many ticket situations that all have specific operational requirements, reflect well the fact that the actual needs of IT support are not well recognised, let alone met. AP for Flow Management is the simple fix to meet them all.
Why not subscribe to the Service System blog written for HDI SupportWorld, to receive a key insight about IT support's struggles weekly...

© Opimise 2025. All rights reserved.