Skip to main content

Do LESS with LESS! Really??

Since the start of the millennium we have all heard that we must do “More with Less”.

I recently read an article where the idea of “Less for Less” was looked at from the perspective of if our resources are cut then we will have to cut programs, products, and services also.  Perhaps we should look at how to cut back on to whom and what we produce in order to stay within our means. Government sequestration may have triggered this way of thinking for some service providers. This is a catchy title but is this really the case?  Is there a different perspective on “Less for Less”?
Think back a few years when a downturn in the economy negatively impacted the workforce.  Families got creative.  The new trend became staycation instead of vacation.   A staycation meant less travel arrangements for less time in planning, less time on the road or in airports and therefore less missed connections, less cost for the family resulting in less stress and less debt!  What about VALUE!  Was there value in this?  Many did less for less and experienced real joy with lifelong memories! 
When we consider the increase for demand of new or changed services from customers it is difficult to imagine how service providers can produce value with the concept of “Less”.  The business demand is for MORE.  
Some things IT staff and service provider executives would all like to see less of!
LESS MEETINGS!
In a recent discussion with ITSM practitioners is was noted that “Every time there is a release we have a barrage of meetings sucking up a lot of time and resources to resolve it!  I am sick of meetings. We just get through one fiasco and another is brewing!  “We keep doing the same thing over and over and expect a different result next time.”
LESS STRESS and OVERTIME!
These 60 and 80 hour workweeks are killing us!  What is work life balance again?
 
LESS BLAME GAME!
Dedicated people who are working hard do not want to feel that they are not enabled for success, it must be the infamous “THEY” who are at fault! 
 
What would you like to see less of?  Add your list here!...
What could you do less of that would result in less of what’s on your list?  
 “Less resistance” could prove to be for service providers what staycations were to families who adapted to “less for less” and created some of their most memorable times together.  For example: Less resistance to governance and process control might produce less chaos resulting in less time and meetings less frustration and less fires. Oh, did I mention less work, less effort and less stress?  Perhaps a little less resistance to invoking best practice for proactive planning process into service design could result in less resources, cost overruns and lost revenue due to unsatisfied customers.

Optimizing value for service providers and their consumers might just be doable by thinking about “LESS for LESS” and how LESS could result in true VALUE for all involved.   Do LESS with LESS!  Really!!

Comments

Dutch said…
Interesting article, but not so much about "Less" as well as increasing performance, by increasing the effectiveness of our actions, by decreasing the effects of the negative elements in our environment. For every example provided I can see what needs to be done "more" in order to mitigate the issue. One doesn't really create more value by doing less, instead I'd like to refer back to the mantra: "Work smarter, not harder".
Rose Lariviere said…
Great Perspective. Ties in with "Less" work in progress and "More" productivity! Like!

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…