Sequential Automated Task Management, an Asset?

Blog
August 29 2013

Yes, simplicity and speed are two terms used repeatedly. They are so that we can now speak of an automatic need, even evident in the business world. Yet in the daily management of information services, the reality may be very different and this obviously implies significant challenges. Indeed, this research performance often results in the selection of highly specialized complex solutions that do not represent the real needs of organizations. The latter seek software solutions that fit their maturity and their business needs but in vain, the "solution" becomes a nightmare.

Simplicity and Speed of Execution

It is a challenge to find ways to accelerate the pace of service management (internal and external), while ensuring stability. The introduction of automated processes, "workflows" and frameworks advocated by the majority certainly are a solid foundation, but the game is not won.

As an IT manager or IT project manager, customization and configuration of ITSM processes are crucial and you will be able to take the next steps without worrying about the stability of your previous implementations. The task management is a key point in the efficiency of your IT processes and automating them is even more so.

A powerful task management makes it possible to optimize :

  • automated assignment of tasks to resources
  • timeliness of your internal resources
  • transparency of the process through a dual display
  • managing your requests for services and thereby, improving the user experience / customer
  • the sequential operation of these tasks within different processes

Sequential Tasks

A continuous improvement approach was favored for the creation and management of tasks. Based on best practices as well as through various ITSM frameworks, sequentiality is now a priority. A priority that has a highly under-estimated value and that could forever change the way you manage your services and support processes. Using rules defined in terms of resources involved, we can now start operationalizing, monitoring, and ensure completion of dependent tasks.

In sum, this sequentiality allows resources to meet business processes related to different service requests.

Documenting the Service Catalog

The creation and automation of requests, however, are not providing optimal rendering. The combination of tasks to service requests is also essential in the context in which the organization is committed to streamlining costs and resources, as well as agreement management and service levels.

These service requests are ideally parts of a service catalog, encyclopedia of your existing services. These applications can be broken down and attached to tasks themselves connected together, allowing better management of services.

Types of Tasks

There are different types of tasks:

  • resources tasks : manually type tasks completed by a resource such as resetting a password, the configuration of a workstation / phone, application installation, training, impact analysis, quality analysis
  • automated tasks / approval : tasks initiating automatic processes such as approvals for the acquisition of equipment, licenses or applications as well as demadnes changes or simply changing a field or sending a email

Resource-User Interaction

In the best of worlds, jobs created and managed by the resources involved in a specific process should be visible to the customer. Through a web portal, an interface may be developed between the resource and the user to know how the tasks are progressing. The proposed transparency will increase customer appreciation and will certainly decrease the likelihood that engages a second request or a call for an update, thereby reducing the workload of the department support.