A Note from Bill...
Next month, IT Services will release its annual Client Satisfaction
Survey. This survey serves as a key indicator to whether we are meeting
our clients' expectations in delivering useful, reliable tools with
excellent customer service. As I've mentioned in previous articles,
continually improving client satisfaction is absolutely necessary for
IT Services to succeed at Stanford.
One influence on improving client satisfaction and providing great
customer service is, without a doubt, an employee's satisfaction with
their work environment. Many of you (a phenomenal 89%) participated
in our recent, short Employee Satisfaction Pulse Survey. Clearly, this
shows that we all care deeply about this organization and want to provide
input to help improve it. So why do I believe that employee satisfaction
is so critical to client satisfaction?
It almost goes without saying that our mood affects our performance.
The more pleased we are with our work environment, the
more likely we are to provide great client service. By
addressing internal staff concerns we are often also addressing
our clients' concerns and making them more successful.
I realize (especially from my own experience) that it is
unrealistic to expect everyone to be happy all the time.
However, when morale is high, we are all much more likely
to support each other. Such teamwork is clearly evident to our clients.
Every successful team maintains a pervasive attitude that the success
of the team is as important, if not more so, than the success of the
individual. I honestly believe that this is true for IT Services. While
we should all be working to create an environment that allows individuals
to be successful, it is because such success can lead to success for
the organization. None of us are truly successful—especially me—unless the entire organization succeeds.
Over the next couple of weeks, we will all be reviewing the results
of the employee survey in our work groups. All in all,
I'm very pleased with the results since they indicate that,
for the most part, we are moving in the right direction.
Please remember that the results are not an end in themselves—we
don't win anything for having a positive internal survey. Still, creating
a great organization where we all feel valued and supported is a crucial
stepping-stone to providing great service and services. Please join
me in working to continue this trend and in taking the next step to
leverage our improvements to deliver even better service to our clients.
- Bill Clebsch
IT Services
IPP Phase 2 Kicks Off
Wednesday, March 1st marked the beginning of Phase 2 of our annual
performance evaluation process.
The purpose of Phase 2 is to check in and review progress against
goals set in Phase 1. In addition, it allows for goals
and job descriptions to be updated or amended as necessary.
As always, the most critical thing to keep in mind is that this process
is first and foremost about communication regarding expectations, performance,
training, and tools that may be needed for successful job
performance.
The Phase 2 review includes:
- Section 1 (job description)
- Section 2 (principal objectives and goals)
- Section 3 (competencies)
- Section 5 (career development)
Hopefully, everyone has already started conversations with their
supervisor on the Phase 2 process. Updated
IPP forms are due no later than March 31, 2006. Any questions
can be directed to your supervisor or to Nilda
Bonet.
- Bill Clebsch
IT Services
2006 Client Satisfaction Survey
We are about to launch the 2006 Client Satisfaction Survey. As part
of the process, we invited all IT Services staff members
to help out by completing the version of the survey designed
for staff. We are asking you to complete the survey for
three reasons:
- We want to hear your feedback about our services and receive your
input on priorities for future directions (because you
are clients too);
- we want you to be informed of the questions we will
ask a random selection of Stanford faculty, students,
and staff next month; and
- we need your help to test the how well the survey works
and whether the questions are clear.
Your responses to the survey are confidential. MOR Associates
will receive the raw survey data directly and will complete
the needed analysis.
This is just a reminder: tomorrow is the last day to get your survey
in!
You can contact any member of the IT Services Client Satisfaction
Team with your questions or to provide feedback. You can also reach
us via email at itss-survey@lists.stanford.edu.
Thanks for helping out.
- The IT Services Client Satisfaction Team
Bill Clebsch, Jan Cicero, Jay Kohn, Chris Lundin, Nan
McKenna, Jim Knox, Teresa Janeway, Lynne Myers, Nancy Ware
Tips for Handling HelpSU Cases
As part of IT Services' continued focus on measuring our
operational activities to positively influence customer
satisfaction, we began publishing weekly "SLA Performance
Measures" in January. A previous
edition of its in bits had details about the metrics project.
We have created a Tips
page in
our "HelpSU for Consultants" area which offers
advice on how to handle HelpSU cases to promote the most
accurate measurement of "response time." If you
work in HelpSU to resolve cases, please take a moment
to review the suggested practices and tips.
SLA (Service Level Agreement) is a common industry term
to reflect the agreement between customers and service
providers about service levels, and is also the name of
a module in our Remedy Help Desk application. Our Remedy
SLA module measures the elapsed time (in business hours)
between receipt of a customer's HelpSU request and when
that request is marked "Resolved." These SLA
measurements are published weekly to the IT Services and
Administrative Services managers and directors.
At the current time, as a way to get started, we have
two specific resolution measurements for all groups using
the HelpSU application:
1. Urgent Cases resolved within 4 business hours (M–F,
8–5)
2. Non-urgent cases resolved within 12 business hours (M–F,
8–5)
The weekly report then tells us what percentage of cases
have been resolved within these times. These do not tie
to the SLAs which we now have in place with our clients,
but are a way to get started using the Remedy functionality.
In coming months, we anticipate adding additional, specific
measurements for particular clients, as well as measuring "response
time" (the time between a customer's HelpSU request
and when the support staff advises them that the problem
is received and under review). These measurements will
tie to the IT Services SLAs which we have with those clients.
- Chris Lundin
Client
Support; Help Desk Services
- Nan McKenna
Client Support; Process and Account Management
Changes in Shared Communications
I'd like to share a change in our reporting structure. Effective
immediately, Bob Moya and Karen Cox will report to me directly.
This change
comes as a directed effort to bring more of my focus and
attention to two
critical client-facing and cross-functional areas. They
will each bring
their groups along with them, somewhat lightening Bert's
load in Operations.
Please let me know if you have any questions or concerns
about this change.
- Jay Kohn
Shared Communication Services
New iOU
In late 2004, the Oracle Financials team was assigned
the task of improving Oracle usability for campus users.
A key goal was to reduce the amount of time required to
enter transactions in the system. Three areas were identified
for improvement: PCard, Reimbursements, and Purchase Requisitions.
The Oracle Financials team recognized from the start that
strong end-user involvement would be critical for this
effort. With the support of the executive sponsors, focus
groups were convened and field studies were conducted as
part of the solution design process.
At the outset, the team performed an evaluation of the
Oracle iExpenses module as a potential option for PCard
and Reimbursements. The findings indicated that iExpenses
was not a good fit for Stanford, so the team proceeded
to the next step: a customized solution for PCard.
With the help of the end-user field studies and a PCard
focus group, application and report requirements were gathered,
screen mock-ups created, code developed, and usability
studies performed. In October of 2005, PCard rolled out
campus-wide to great acclaim.
Then it was iOU's turn. Because it addressed Reimbursements,
Advances, Other Checks, and Petty Cash, the new system
and reports were dubbed "iOU" by the focus group
that helped design it; nifty shorthand for a fairly comprehensive
application!
Emerging from a successful test, a usability comparison
between the new iOU application and the current iPO module
has been revealing. For an identical reimbursement transaction
entry, the following numbers were recorded:
Number of screens:
iPO = 31
iOU = 12
Number of mouse clicks:
iPO = 67
iOU = 37
Elapsed time required for transaction entry:
iPO = 8 min 39 secs
iOU = 4 min 31 secs
This significant reduction in required effort for a standard
transaction will be music to the ears of thousands of users
across campus.
The process of granting authority for over 3,000 users
begins the week of March 27th. The transition should be
complete by May 1st, and iOU will be running on all cylinders.
- Shirley Hodges, Suzanne Schiessler, and Tricia
Richter
Administrative Systems
Strike !
Get your strikes in at the second not-so-annual IT Services Bowling
Party. The party will include free bowling and shoe rental,
pizza, and beer (a cash bar will also be available). Prizes
and trophies will be awarded for high score and low score.
A Sundial invitation should be on your calendar. Here are
the specifics:
- What: IT Services March Madness Bowling Party
- When: Thursday, March 30th; 3 p.m.–6 p.m.
- Where: Palo Alto Bowl, 4329 El Camino Real
See you on the lanes!
- Teresa Janeway
Client Support; Promotion and Publicity