Skip to main content

Digital Ingenuity

It is official.  All service providers are or soon will be going through some form of digital transformation. As you begin to transform be sure to take into consideration the Values of DevOps, Agile Service Management, Lean and ITSM.  They each have beneficial results and each dovetail together to ensure that the service provider can move fast, change on a dime to meet dynamic requirements, and also be able to deploy into an antifragile stable environment.  Business transformation can appear to be daunting.  Sometimes it is somewhat of a labyrinth, involving a constant need for collaboration and engagement between customers, business partners and Information Technology functions. All are required for proper strategic vision and operational execution. That is likely not news to you.  We KNOW that is required and yet there are many service providers that still today need to bridge the gap between Business, Development and Operational teams.  When setting expectations for a Digital transformation prepare for disruption.   Disruption, in this case, is exactly what you want to see.  

Status quo will not get us there.   Creative, forward-thinking individuals will need to step up and lead the charge to set visions that will disintegrate the existing landscape and replace it with new possibilities that are boundless.  Tactical plans will follow only if we help our IT professionals and practitioners with digital dexterity.

A 2017 Gartner Report indicated that ”Digital dexterity efforts must align with enterprise architecture to coordinate strategic plans, organizational goals, business outcomes and capability models that span IT and related business initiatives. In a similar vein, digital dexterity efforts are most successful as part of a sustained digital workplace program that boosts employee engagement and agility through a more consumerized work environment.
We examine below the four elements of building a sustained commitment to deliver digital business results via workforce digital dexterity. These elements are:
  • Talent — Designing digital literacy initiatives that recognize, and build on, individual personalities, interests, skills and roles.
  • Planning — Building a sustainable operational strategy for digital dexterity.
  • Culture — Creating a workplace culture that values and rewards digital dexterity initiatives.
  • Tools — Exploiting a variety of digital dexterity education services.
Digital ingenuity is required by service providers to integrate a cohesive effort. The reality is that communication, education and collaboration will trump every other aspect of a digital transformation.   If you are not seeing results today perhaps it is time to consider such a strategy and promote digital ingenuity with a digital workplace education program.

For more information 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…