Designing Service Portfolio KPIs for Campus Information Systems

A campus information system is not only a collection of applications. It is a service portfolio that should explain what value each system provides, who depends on it, and how leaders know whether the service is improving.

For Information System Management classes, this creates a practical KPI design exercise. Instead of asking students to memorize governance frameworks, ask them to map one campus service such as enrollment, learning management, finance, library access, or helpdesk support.

Teaching frame

A strong service KPI should answer four questions:

1. Who is the user? Students, lecturers, administrators, leadership, or external partners.
2. What outcome matters? Faster service, fewer errors, better access, improved compliance, or clearer reporting.
3. What evidence is available? Logs, ticket queues, survey data, transaction status, uptime records, or release notes.
4. What action follows? Continue, improve, automate, train, redesign, or retire.

This approach helps students avoid vanity metrics. A dashboard with many numbers is not automatically useful. The useful KPI is the one that supports a decision.

Classroom activity

Give each group one campus service. Ask them to create:

• one user-experience KPI
• one operational reliability KPI
• one governance or compliance KPI
• one learning or adoption KPI

Then ask them to defend why each metric is actionable. If the team cannot explain what decision would change when the metric changes, the KPI needs redesign.

Reflection

The best Information System Management learning happens when students see that technology performance and institutional value are connected. Service portfolio KPIs make that connection visible.