Pain in the Asset, Part I

Original Post: August 16, 2017

Let's face it, managing assets through a lifecycle can be a pain.  In most companies--regardless of industry--there are multiple stages with multiple tasks requiring multiple people to work on them.  For example, asset lifecycle management in an IT organization typically involves:

• a purchasing function 

• a configuration and deployment team (sometimes these are separate roles...) 

• infrastructure management and support 

• refresh and recycle  

Each of these tasks, by themselves, is generally manageable.  The problem, however, is that asset lifecycle management doesn't work well when managed in discrete chunks--it's a continuous cycle.  Imagine if we raised kids this way...if the lessons our children learn in their infant years didn't carry over into their toddler or early school years.  And, in turn, if the experiences from these times weren't available to recall as young adults and into their parenting years.  Just think of the chaos!  We'd have to re-learn things we should already know every couple of years and would continually make the same mistakes over and over again.  

Hmmm...

That sounds A LOT like how Asset Lifecycle Management is handled now--many tasks, many tools, and far too many inefficiencies.  Luckily, there's an easier way to do all of this.  In Part II of this post, I'll discuss how making multiple discrete steps in ANY asset lifecycle management process is much simpler than you might think.  Of course, if you can't wait for Part II, drop us a note and we'll give you a sneak peak.