The Desktop Transformation Implementation Cycle – Use Case Normalization

By Greg LaVigne

In my previous post, I introduced the conceptual model of
the Desktop Transformation Implementation Cycle: The
Desktop Transformational Implementation Cycle

Earlier posts covered business case and rationale
considerations, so I’ll move into the Use Case Normalization phase.

Use Case Normalization involves a combination of two
distinct focuses:

  • User Rationalization
  • Application Rationalization

is all about gaining a
detailed and documented understanding of what an organizations end user
community does and how they do it. It definitively paints a picture of the end
user landscape. A sampling of key questions includes:

  • What roles end users are filling? What divisions,
    departments or teams are they on?
  • How do they work in terms of their daily activity? Are they
    mostly at a desk? Are they campus roamers who bounce between meetings? Or, are
    they out in the field dealing with the occasional limited network connectivity
  • When do they work?
    Are they 9-5 at an office location? Are they overnight shift workers? Or
    are they overseas?
  • What tools do they use? Which applications? What kind of
    peripherals? What are their multimedia utilization requirements? Do they have
    local printers?

Admittedly, gathering this kind of detail on a team-by-team,
or ideally a user-by-user level, is not an inconsequential effort. However, the
more detail that can be gleaned and reviewed, the better the alignment to an
appropriate desktop virtualization solution can be achieved. More importantly,
using this information to identify users that don’t fit the parameters of a
given solution is imperative if you want to achieve the desired results; chief
among them is putting or keeping smiles on your end users faces.

is related, but different
in that we are focusing on the applications.
 Key data points to capture here include:

  • What applications are still being used? This is different
    than what applications are installed as used and installed are two different
  • Determine which applications app are still needed. Just
    because they’ve been used, doesn’t mean they’re still needed. This list becomes
    your master application list to work off.
  • Look for consolidation opportunities. How many .pdf
    converters or readers do you need? How many compression utilities can be
  • Once the master application list is built, determining who
    the appropriate SME is becomes the next challenge. This SME will then drive
    application preparation and migration efforts.

The Use Case Normalization may be the most crucial aspect
to get right and thus needs to be given the highest priority. Yet, in talking
with organizations, it seems to be one of the areas most taken for
granted.  From what I’ve experienced and observed,
this sort of approach is what ultimately leads to costly miscalculations and
even failure. A combination of User Rationalization and Application
Rationalization definitively defines your organizations various Use Cases. The
information collected then allows you to map Use Cases to specific Transformation
Solutions. Proper Use Case mapping is the absolute key that leads to a
successful journey.

Next up is the Solution
Development phase.  Until then!




Written by , Posted .