Running a Service Control Retrospective for Campus Information Systems
An Information System Management lesson that turns post-release reflection into evidence about ownership, controls, user impact, and service improvement.
Information System Management becomes concrete when students can explain whether a control improved the service experience. A control is not successful simply because it exists in a checklist. It is successful when it reduces confusion, prevents avoidable failure, or gives decision makers better evidence.
A service control retrospective helps students review a recent release, incident, or support escalation and ask whether the chosen controls were useful in practice.
Classroom setup
Give each group a simple campus scenario: a learning management system update, a library access change, a student finance portal issue, or a helpdesk workflow revision. Ask them to identify three controls that were supposed to protect the service, such as approval gates, monitoring alerts, rollback steps, ownership rules, or user communication templates.
Retrospective prompts
Use these questions to structure the discussion:
- Purpose: What risk was each control meant to reduce?
- Evidence: What logs, tickets, analytics, or user feedback show whether the control worked?
- Ownership: Who noticed the signal, made the decision, and communicated the outcome?
- Friction: Did the control slow down useful work without improving service quality?
- Improvement: Should the control be kept, changed, automated, or retired?
Teaching note
Require students to separate opinion from evidence. A mature service review should not say only that a control felt helpful. It should connect the control to a visible service outcome, such as fewer repeated tickets, faster recovery, clearer ownership, or reduced user uncertainty.
Learning outcome
Students practise treating governance as a living service capability. They learn to evaluate controls by their contribution to reliability, accountability, and user trust rather than by their presence in documentation alone.