System Center Best Practices: Outcome Based Implementation

Author by Nathan Lasnoski

Are you executing on a System Center or Private Cloud project just to replace one tool with another?  In some cases I'll start a call with a company regarding System Center and they'll say, "we need to get this in by the end of [insert date here]."  I usually try to coach them from thinking about platform deployment to outcomes instead.  In an System Center project, first start by thinking about what you want the outcome to look like, then work backwards.  This is the key best practice to understand for System Center and Windows Azure Pack (WAP) success.  

Here are some quick ways to articulate outcome:

  In the examples I described, we're talking about real outcome based conversation regarding a System Center project.  I find that when we discuss projects in this form we're able to articulate the "why" vs. just the "how.  

At the end of the project, I want companies to see measurable business value.  Here are some examples:

  "We saved $3 million in internal deployment costs simply based on time savings and another $1 million in external software costs we eliminated".  For global automations which turned a complex process into a simple end-user facing deployment mechanism.   "We can scale to three times our datacenter size without adding staff".  For enterprise application providers who need to scale and scale quickly.   "My team members love that they can access their work items from any device".  A global company who transitioned from Remedy to System Center Service Manager.   "I never had this visibility before".  A global company who moved from HEAT to System Center Service Manager.     Take this approach next time you are looking at any technology project.  You need to be confident that it will achieve a value for the business, just as the business needs to be confident that you are delivering a value to them.   Nathan Lasnoski

Author

Nathan Lasnoski

Chief Technology Officer