Continuing from where we left off in Part 1, lets start exploring the interactive model and the need for itHUB a little more in this post.

III. INTERACTIVE MODEL

In the interactive model, the IT departments provide an e-business platform with a unified web interface to search, submit, track IT requests for their customers. The platform will also provide facilities for service providers to deliver on the requests in terms of ordering items and updating the details of the requests across multiple systems. In addition to the above requirements, the platform should also provide ways in which an IT customer can pose questions and get answers either from the other IT customers or from an IT service provider. The remainder of the article will refer to such an e-business platform as itHUB.

A. itHUB – The Platform

A two-sided platform [3] is a good starting point for itHUB. There are consumers that will request for services, check for statuses, post questions and/or answers, write blog articles, and rate the quality of services offered. There are service providers – IT departments – that fulfill requests. There are approvers – typically, managers of requestors – to approve requests made by their department users, so that the service providers can fulfill them.
2-sided itHUB Platform

In addition to IT departments, service providers can also be external vendors such as Walmart, Staples etc. Both platform provider and the sponsor could be the IT organization in question.

1) Platform Sponsor vs. Platform Provider

If the itHUB platform is built with enough abstraction, there is a possibility for IT organizations to repurpose itHUB so that it could be used as a service delivery platform for other departments. For example, a car manufacturer’s employee sales department could make use of the itHUB platform to fulfill car requests. In this particular case, the IT department will become the platform sponsor and the employee sales department will become the platform provider. The following section describes the network effects in itHUB.

2) The Network Effects

Network effect is the effect that one customer of the IT products or services has on the value of those products or services to other consumers [4]. The itHUB platform will benefit from having such network effects as shown in the next picture.

a) Same-side Network Effect

Customer-to-Customer Network effect is positive since more customers make IT products and services better. This is possible because of the interactions among the customers through social questions and answers and wikis/blogs. The more customers pose questions/answers and write blog articles about the IT products and services for clarification and usage scenarios.

The Network Effect

Service Provider-to-Service Provider Network Effect is negative as increased competition makes itHUB less attractive to external service providers such as Walmart, Staples, and PC Connection etc. The same-side network effect among internal IT service providers is positive as the internal IT departments work with each other to deliver on the IT requests.

b) Cross-side Network Effect

Customer-to-Service Provider Network Effect is positive as more customers attract more external service providers. Service Provider-to-Customer Network Effect is positive as more service providers attract more customers as the perceived speed of delivery of IT products and services by the customers.

c) Ideas for creating and sustaining the Network Effect

IT service management is often considered a one-time deal where customers are thought to come to IT for services and go away until another need arises. Though this is true, there is an opportunity for IT departments to create a loyal customer base where not only the IT support team but also the application teams can hear about the voices of the customers in terms of application user interface design, development, and deployment. This feedback loop is valuable in terms of designing applications for the better in the future. By creating an integrated e-business platform where not only IT requests are easier to create, submit, and track, but also providing a way for the customers to receive a fast, accurate, and friendly answers [5]. In this case, it is not just the IT support team that is responsible, but the entire community of IT customers and the service providers bears the responsibility of helping each other. As long as the platform is easy to use, reaching the critical mass, unlike in a public social platform, should not be a problem for IT departments since IT customers are the employees of the organization where IT departments are a part.

When it comes to external IT service providers such as Walmart, Staples, PC Connection etc., the platform has to ensure that the “winner-takes-all” scenario does not exist [6]. This can be easily mitigated with a procurement policy.

The next section discusses a couple of digital business models that the IT departments could adapt to further sustaining the network effect.

B. The Digital Business Model

IT could employ the Click-and-Mortar (C&M) business model [7] where it maintains a web storefront in addition to its physical office space. IT must exercise the Infomediary model [7] to facilitate transactions between the consumers and the external service providers such as Walmart, Staples, PC Connection etc. To facilitate the social interactions among its customers and the service providers, IT could employ the Community model [7]. Each business model – C&M, Infomediary, and Community – can be implemented in terms of content, customer experience, and the platform [8] and built into itHUB as follows:

The Components of the Digital Business Model

1) Content

  • Product/Service information.
    • IT related products and services information include description, images and videos, price, policies, and procedures for hardware, software, and applications offered by the IT department.
    • External service provider catalog.
      • This requires an integration of itHUB with the external service provider’s e-catalog and order placement solutions.
  • Questions and Answers
    • Questions and answers could also be posted by IT personnel in addition to being posted by the customers (user-generated)
    • Questions and answers are related to the products and services offered by the IT department and the external service providers
  • IT Product/Service related wikis and blog articles
    • HOW-TO articles describing the usage of a particular hardware, software, or applications with images and videos
      • For example, virus outbreaks and mitigation

2) Customer Experience

  • Easy-to-use
    • To create and sustain the network effect as described in the previous section, itHUB has to employ good usability guidelines
      • For example, 1-click request submission when the customer profile is completely known
      • If the customer is a new hire, allow ways in which multiple related items could be ordered in one request
        • This is an example of a composite request where several individual requests are added to one parent request
  • Shopping cart
    • itHUB must provide a way to instruct the customers regarding the number of items and the prices that they are about to request
    • There should be a way to save a set of items for later submission
    • There should be a way to save and send a set of items for a different customer to submit the order
  • Cost center / Project-based billing
    • itHUB must have access to the billing information of the customer to facilitate ordering price-based items
  • Messaging
    • Email/SMS acknowledgement
      • Whenever a request is placed and until the request is completely satisfied, itHUB must notify the requestor regularly through emails or text messages
    • Alerts
      • Notify the requestor whenever approval/rejection workflow is carried out
  • Customer generated Content
    • Ratings and reviews
      • Provide a way for customers to rate/review the products and services they received
        • This is an important feedback mechanism by which IT departments can and will learn about the products and services they are offering
        • Sentiment Analysis can be carried out on the reviews to figure out the satisfaction levels of customers
      • Questions and Answers (Q&A)
        • Q&A is a great way to create the network effect described in the previous section
  • Detailed history of requests
    • This is a great way to promulgate the amount of work IT has done to its customers, business units, and the entire organization
    • Keeping track of the detailed history of requests along with comments, ratings, reviews etc. will provide IT an opportunity to infer the seasonality, satisfaction levels of customers, improvement needs among others
  • Tailored recommendations based on the customer profile or the business unit
    • This feature is a differentiator in which the itHUB will be perceived as a platform that understands the needs of its customers

3) Platform

  • Internal components
    • Customer data
      • Address along with location, building, and floor
      • Customer’s position or title and department
        • To facilitate the approval process, the customer’s title is important
    • Customer Billing Information
      • Cost center, inter order number, project number are some of the attributes that are needed to be captured for the purposes of billing the customer
  • External components
    • Shipment of physical products to remote locations using UPS, FedEx etc.
      • In a geographically separated organizations, IT must take shipment of items to respective business units into account
    • Product and Services data from external service providers such as Walmart, Staples, and PC Connection
      • This is the crux of enabling B2B commerce with the external service providers

I’ll contiunue my discussion in the next post.


[3] Wikipedia. (2013). Two-sided market. Available: http://en.wikipedia.org/w/index.php?title=Two-sided_market&oldid=565480518

[4] Wikipedia. (2013). Network effect. Available: http://en.wikipedia.org/w/index.php?title=Network_effect&oldid=571703046

[5] InsideIntercom. (2013). How The Support Team Improves The Product - Inside Intercom. Available: http://insideintercom.io/how-the-support-team-improves-the-product

[6] InsideIntercom. (2012). Surviving & Thriving in Two-Sided Markets. Available: http://insideintercom.io/surviving-thriving-in-two-sided-markets

[7] M. Rappa. (2006). Business Models on the Web - Professor Michael Rappa. Available: http://digitalenterprise.org/models/models.html

[8] P. Weill and S. Woerner. (2013). Optimizing Your Digital Business Model - MIT Sloan Management Review. Available: http://sloanreview.mit.edu/article/optimizing-your-digital-business-model

Information Technology (IT) departments spend so much time and effort in providing products and services to their organizations. Oftentimes, by being caught up in the support mode, IT departments do not spend the time to supplement their support services using a well-defined online storefront.

Typically, the online forms to gather information about the IT service requests are either cumbersome for business users or archaic to lend themselves to submit, track, and administer requests from a single point of entry on the web. The purpose of this article is to build an online storefront – itHUB – an easy-to-use online destination for IT consumers to submit and track their hardware, software, and application requests.

I. INTRODUCTION

IT must evolve from providing an informational outlet for its services into providing interactive and anticipatory models of service management. IT Service Management Evolution

The following sections will illustrate the need for such an evolution by describing the problems/issues found in each of the models and some of the ways in which they can be improved/eradicated.

II. INFORMATIONAL MODEL

In the informational model, IT departments maintain a set of web pages or a set of MS Word/PDF documents to collect information about the request. Oftentimes, the collected information is then processed either manually or by using disparate systems – a type of system for approval and another for fulfilling the request. The following section describes the ways in which the IT requests are processed and the weaknesses found in the model.

A. Request Processing

The following diagram illustrates the various steps involved in processing IT requests in the informational model-based IT departments: Typical IT Request processing

1) Submit Request

The IT customer performs this step. It could be as easy as filling out a web form, printing and filling out a MS Word/PDF document or as difficult as making several phone calls or writing several emails to find out as to which web form to use or which MS Word/PDF document to fill out for the request. In some cases, a proper form of request submission might not even exist.

2) Analyze Request

Typically, the IT support center or Help Desk performs this step. IT help desk personnel will carefully review the submitted request and send it back to the IT customer if more information is needed to process the request further.

3) Route Request

Typically, the IT support center or Help Desk performs this step. Depending upon the request, there may be a need to get multiple approvals from department manager, general manager among other management team members. Routing request could also be done to get some type of verification from the subject matter expert (SME) who will end up satisfying the request upon approval.

4) Process Approvals

Typically, the IT support center or Help Desk performs this step. It is also possible for IT service providers to perform this step as well. There may be a need to include additional approvers before satisfying the request. For example, a request for a network share might require an additional approval from the owner of the share in addition to the approvals from the management team. This step is performed to ensure that the request is a legitimate need from the IT customer to perform his/her job.

5) Deliver on Request

Either the IT service provider or the IT help desk performs this step. For example, the IT help desk (or a similar department within IT) would most probably satisfy requests for hardware items whereas the IT service provider might need to involve its SMEs to get the application properly installed and configured on the IT customer’s computer.

6) Order Item

Either the IT service provider or the IT help desk performs this step. If the request involves items that are not readily available, the item has to be ordered from external vendors/service providers. There may be a need to involve the purchasing/procurement division of the organization that the IT department is a part of. This step might take from a few days to several weeks or months depending upon the price tag of the item.

7) Update Details

Typically, the IT support center or Help Desk performs this step. Depending upon the type of request, the help desk personnel might have to update several systems such as asset tracking system, request management system, procurement system etc. Oftentimes, these systems capture either the same or different details about the request and its outcome.

B. Weaknesses of the Informational Model

As described in the above section, this model is only concerned with providing information to facilitate the submission of IT requests.

1) Higher Search and Information Costs

In most cases, the search and information costs [1][2] associated with locating the correct IT request type for submission are high. For example, a new hire might require a wide variety of hardware, software, and organization-specific applications to be productive in his/her role in supporting the business goals of the organization. Finding and submitting requests with relevant details mandated by those request types could take days or weeks for the new hire.

In some cases, the bare minimum requirements such as user id creation within the corporate directory for the new hire might have to be submitted by another team member who is already in the system.

a) Lack of user community

The other reason for the higher search and information costs associated with this model is because of the centralized dispersal of information regarding the IT requests. All requests are directed to IT irrespective of their criticality. Oftentimes, the IT personnel are exhausted answering the same questions repeatedly. Without a streamlined process for facilitating questions and answers, the IT department wastes time answering common questions instead of catering to real requests.

2) Higher Policing and Enforcement Costs

As described in the request processing section, steps 2, 3, and 4 are highly time consuming in terms of coordination of the approval efforts between IT and the business units.

3) Higher Integration Costs

As described in steps 6 and 7, there could be 2 or more data repositories where the details of the requests are kept. As the number of systems, where the details of the requests are kept, increase, the integration costs go up significantly in terms of data, application, and process integration efforts. For example, the IT customer profile information, for the purposes of satisfying IT requests, must include location of the customer in terms of building and floor information. Otherwise, tracking the location of the customer during the delivery of a hardware item must be sought out manually. This is especially difficult if the organization is spread across multiple geographical locations. Oftentimes, the IT customer information is kept in the employee management systems such as PeopleSoft and it is not kept up to date in terms of the IT customer’s location information. As described in step 6, when there is a need to order items, there is also a need for billing information in terms of the cost center, internal order number or project number that the cost of the item has to be cross-charged with. Once an item has been purchased, it becomes an asset of the organization and therefore needs to be tracked for depreciation etc.

C. Moving up the Evolution Chain

As can be seen, the amount of information needed to deliver on an IT request quickly adds up. In this informational model, the majority of the integration work is done manually and therefore, the model is neither cost effective nor efficient in managing information across multiple systems. It is absolutely essential for the IT department to move up the service management evolution chain and adopt the interactive model as described in the next section.

I’ll contiunue my discussion in the next post.


[1] Investopedia. (2010). Search Cost Definition. Available: http://www.investopedia.com/terms/s/search-cost.asp

[2] Wikipedia. (2013). Transaction cost. Available: http://en.wikipedia.org/w/index.php?title=Transaction_cost&oldid=572207418