Kentucky Community and Technical College System: Serving a diverse group of end-users
With 16 colleges in 70 locations serving an estimated 130,000 faculty members, staff members, and students, KCTCS supports a broad swath of users.
KCTCS uses Oracle's PeopleSoft Enterprise Human Capital Management system to roll out self-service components to its various user constituencies, says CTO Paul Czarapata. PeopleSoft's Campus Solutions application allows students to enroll in classes, pay their bills and make scheduling changes. Czarapata says that module is relatively easy to administer, for two reasons.
First, he says, "the students really don't have that many mind-boggling choices -- they can see if they're admitted to a class and pay for it. Everything else is on Blackboard" -- a separate student-services system, widely used in higher education, that also incorporates self-service as a cornerstone. Second, "students pick up on [self-service] quicker than employees do," he adds. "For the most part, they're a little more technically savvy and used to doing things for themselves."
This past October, KCTCS rolled out an ambitious online benefits-enrollment system that relied heavily upon self-service options, a big change for KCTCS employees. "We've got a super-complex HR system," Czarapata acknowledges. "On the HR side, we've got a lot of choices." Change management and communications were critical to achieving a smooth rollout, he says, "especially since we had to reach 68 locations."
In trying to ensure that the benefits system matched the technical expertise of its users as it was being developed, KCTCS did have one advantage: We do know who our employees are, as opposed to a business trying to attract customers online, Czarapata says.
Another plus: Having worked together closely on other projects, IT developers generally agreed with HR's assessment of users' abilities -- and when they didn't, they felt free to make suggestions or ask questions. "Other times, IT might not push back as much, but on this project, most of the people have worked with each other for a long time," Czarapata says. "[IT's] role was to look at designs, follow the flow-through and establish filters to determine who gets the appropriate data," most of which was done in concert with the lead systems person from the HR side.
His advice to other organizations developing self-service systems for users with a wide range of abilities is: "Pilot, pilot, pilot." With a small group of test users, KCTCS developers were able to identify "land mines" and figure out where users needed more or different information, and do so quickly. "A small pilot means a faster feedback cycle," Czarapata points out.
Overall, Czarapata finds that end-users today tend to have high expectations that internal systems will look and act like the consumer Web applications they're familiar with -- an expectation he sometimes has difficulty fulfilling.
"It's not that big a deal for a Twitter or a Yahoo to be constantly tweaked, but monolithic ERP stacks don't change as rapidly on the UI side as today's generation expects," he laments. "We're kind of at the mercy of the vendor about how the self-service components work. The functionality to do everything [users] need to do is in there; it just looks clunkier than they'd like."