Skip to main content

Value Elements

When discussing the elements of value creation through the delivery of services we always talk about customer preferences, perceptions and the business outcomes they generate.  We also throw in the elements of utility and warranty.  These are all critical in ensuring our ability to create value for our customers and capture value for ourselves as service providers.

The service relationship between service providers and their customers revolves around the use of and interaction of assets.   Assets are made up of both resources and capabilities and are provided by both the service provider and the customer.  These are critical value elements in the creation of usable, customer aligned services.

Many of our customers utilize our services in conjunction with their own assets to then build and deliver services or products our customers then deliver to their customers. We, as the service provider, consider these customer assets.  Without these there would be no basis for defining the value of a service. Therefore, performance of customer assets is a primary concern for service management. 

Organizations use resources and capabilities to create value in the form of goods and services.  Resources direct inputs for production.  Capabilities represent an organization’s ability to coordinate, control and deploy resources to produce value. They are characteristically experience driven, knowledge intensive and information based.  They are derived from the organization’s people, systems, processes and technologies.

Service providers must continually develop new and distinctive capabilities that align to the changing customer needs in order to retain customers with the suitable value offerings that would be difficult for the competition to duplicate, thus giving us the competitive advantage.  These must be balanced with the appropriate and adequate resources which the service provider is dependent upon for the delivery of fitting services.

For more information please click through to http://www.itsmacademy.com/lifecycle/ 

Comments

Popular posts from this blog

What is the difference between Process Owner, Process Manager and Process Practitioner?

I was recently asked to clarify the roles of the Process Owner, Process Manager and Process Practitioner and wanted to share this with you.

Roles and Responsibilities:
Process Owner – this individual is “Accountable” for the process. They are the goto person and represent this process across the entire organization. They will ensure that the process is clearly defined, designed and documented. They will ensure that the process has a set of Policies for governance.Example: The process owner for Incident management will ensure that all of the activities to Identify, Record, Categorize, Investigate, … all the way to closing the incident are defined and documented with clearly defined roles, responsibilities, handoffs, and deliverables. An example of a policy in could be… “All Incidents must be logged”. Policies are rules that govern the process. Process Owner ensures that all Process activities, (what to do), Procedures (details on how to perform the activity) and the policies (r…

How Does ITIL Help in the Management of the SDLC?

I was recently asked how ITIL helps in the management of the SDLC (Software Development Lifecycle).  Simply put... SDLC is a Lifecycle approach to produce the software or the "product".  ITIL is a Lifecycle approach that focuses on the "service".
I’ll start by reviewing both SDLC and ITIL Lifecycles and then summarize:
SDLC  -  The intent of an SDLC process is to help produce a product that is cost-efficient, effective and of high quality. Once an application is created, the SDLC maps the proper deployment of the software into the live environment. The SDLC methodology usually contains the following stages: Analysis (requirements and design), construction, testing, release and maintenance.  The focus here is on the Software.  Most organizations will use an Agile or Waterfall approach to implement the software through the Software Development Lifecycle.
ITIL  -  is a best practice for IT service management (ITSM) that focuses on aligning IT services with the needs …

Incidents when a Defect is Involved

Question: We currently track defects in a separate system than our ticket management system. With that said, my question is does anyone have suggestions and/or best practices on how to handle incidents when a defect is involved? Should the incident be closed since the defect is being worked on in another defect tracking system if it is noted in the incident ticket? I am considering creating an incident statuses of 'closed-unresolved' so the incident can still be reported on in our ticket management system but know it is being worked on/tracked in the defect system. With defects, it is possible that we may never work on them because they are very low priority and the impact is low to the user. However, in some cases a defect is being worked on. Should we create a problem ticket instead?
Thanks, René W.

Answer: RenĂ©. In ITIL, the activity you are describing is handled by the Problem Management process. ITIL does not use the term “defect” but it does use the term “known error” to…