Information System Management lessons become stronger when students can test whether a digital service change actually delivered the value promised in a proposal. A release may be technically successful while still missing the operational, learning, or governance benefits that justified the work.
This activity asks students to review a small campus information system change after launch and decide whether the benefits are visible, incomplete, or unsupported by evidence.
Scenario
A department introduces a new online consultation booking flow for lecturers and students. The project proposal promised shorter waiting times, clearer appointment records, and better follow-up tracking. After one month, the team has usage logs, survey comments, and a few support tickets.
Student task
Ask each group to prepare a benefit realisation check with five sections:
- Promised benefit: What improvement did the project claim it would create?
- Evidence source: Which logs, tickets, interviews, or observations can support or challenge that claim?
- User impact: How did the change affect students, lecturers, administrators, and support staff?
- Gap analysis: Which benefit is still unclear, weak, or dependent on better adoption?
- Management decision: Should the team keep, adjust, expand, or pause the service change?
Teaching note
Encourage students to separate activity from benefit. More logins, bookings, or page views do not automatically prove better service quality. The strongest answers connect measurable behaviour with user experience and governance accountability.
Learning outcome
Students practise evaluating information system value after implementation. They learn to connect technical release evidence with service management questions about adoption, quality, accountability, and continuous improvement.