Campus Service Evidence Review: 2026-07-03

This teaching update is now live at https://hicall.web.id/blog/2026-07-03-campus-service-evidence-review. Use it as a practical Information System Management studio for reviewing whether a campus digital service is supported by enough operational evidence.

Learning objective

Students learn to separate opinion from evidence when evaluating a digital service. By the end of the session, each group should be able to identify one service weakness, show the proof, and propose one realistic improvement action.

Scenario

A campus unit receives complaints that an online academic service is slow, confusing, or unreliable. The class acts as a service review team. Their job is not to blame the operator. Their job is to collect visible evidence and translate it into a decision note.

Evidence students should collect

Choose one campus service flow, such as course registration, payment confirmation, helpdesk ticketing, LMS access, or transcript request. Then collect three kinds of proof:

1. User evidence: screenshot of the confusing step, unclear message, or repeated action.
2. System evidence: response time, error message, status page, log excerpt, or ticket history.
3. Process evidence: owner, escalation path, service target, or missing handoff rule.

Classroom flow

1. Frame the service: name the service, users, and expected outcome.
2. Map the journey: list the steps a student or staff member must complete.
3. Capture evidence: save screenshots, timings, messages, or ticket examples.
4. Interpret the finding: explain what the evidence proves and what it does not prove.
5. Recommend one action: write a practical improvement with an owner and a follow-up check.

Student deliverable

Each group submits a one-page evidence note with this structure:

• service reviewed,
• evidence collected,
• interpretation,
• risk or limitation,
• recommended next action,
• owner or stakeholder,
• and the next verification step.

Assessment rubric

Use a simple 10-point rubric:

• 2 points: service flow is clearly described,
• 2 points: evidence is specific and observable,
• 2 points: interpretation is logical,
• 2 points: recommendation is realistic,
• 2 points: limitation and next verification step are included.

Lecturer note

This activity fits Information System Management because it connects service quality, governance, process ownership, and operational evidence. It also prepares students to discuss audits, service improvement, and digital transformation with a more concrete vocabulary.