Skip to main content

Work Holistically

ITSM best practice frequently suggests working holistically.   This is particularly true when defining a strategy and architecting a design solution but when you think about it, this holistic viewpoint should permeate every investment, improvement, and action in the entire value stream from thought to end of life for every service or product deployed.

At a high-level thinking holistically involves looking at things from a people process technology perspective but cannot leave out our partners and suppliers.  No service, process, or functional team stands alone.   Changing one element of a complex system will impact others.  This is a real challenge because no one team can know everything about all aspects of the system.  Therefore, working holistically requires a balance between specialization (functions and departments) and the coordination of complex integrated process activities.  It is only then do we get a clear picture of the lifecycle of a service and any hope of managing it efficiently.

A holistic approach must expand to ensure that results are delivered to customers or the business.  Providers should consider the creation and management of this complex integration of hardware, software, data, processes, architectures, metrics, tools, cultures, partners and be sure that they are all coordinated to provide a defined value.   Did you get that; VALUE must be defined before we can create and manage the holistic solution.  The results delivered to customers are likely to suffer unless the provider works on the whole and not just the parts.

This holistic approach to looking at things is sometimes called systems thinking. By seeking to understand the system's structure, interdependencies and how changes in any area will affect the other parts and the whole system over time, organizations can create a sustainable long- term approach to service management. 

When systems can organically adapt to changes as they occur, the systems will be able to evolve in a way that is appropriate to the need.  This idea is something that most providers are aware and is likely not new to you. When day to day firefighting sets in we forget.  As service providers, it is a good idea to step back from time to time and to consider “Are we really approaching this from a holistic view point?”  “Do we have that Systems Thinking approach?“.  In addition to ITSM, other best practices and methodologies agree about looking at the whole. One approach that can be helpful when working holistically is using the 'Theory of Constraints' as defined in the book The Goal: A Process of Ongoing Improvement (by Eliyahu M. Goldratt and Jeff Cox)to identify bottlenecks in an end-to-end process.   Use what works but be sure to think work and act holistically.


For more information and for (ITSM, Agile, DevOps and more…) training and certification: ITSM Academy ... educate & inspire!




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…