Getting started with Services

Body

Services are defined as means of creating organizational value by enabling outcomes.

We leverage the Service Catalog as the primary avenue to present services to the community.  In order to reduce complexity and streamline services, we leverage one shared services portal.  Therefore, services and service offerings must be named and described with care to make it clear and avoid confusing the community.

Services and their service offerings within the Service Catalog should have information that clearly conveys the name and purpose with expected outcome, who it is available to, how to request it including prerequisites or requirements, and what the community should expect.

Services and service offerings should be designed so that they can be measured.

Common Pitfalls to Avoid:

  • Naming the service or offering around a technology or team (use "Learning Management" rather than "Blackboard" or "Application Team")
  • Too broad or granular (avoid use of "request help from IT" or "request change to particular application setting")
  • No clear owner/accountability
  • Not recognizing complexity or dependencies/relationships to other services which over complicate things and create friction or frustration for community 

Details

Details

Article ID: 21335
Created
Mon 11/16/26 12:19 PM