INTERACTIVE PROTOTYPE
Change Impact Explorer
Explore how a proposed change could ripple through a fictional library network.
- Idea
- Show how one change can affect systems, teams, and readers.
- Build
- Mapped three fictional scenarios and explained each dependency in plain language.
- Tech
- HTML and CSS with native expandable scenarios.
- User impact
- Helps a release planner see who to involve and what to test.
Replace the catalogue search
- Public website. Search results use the catalogue index.
- Mobile app. The app needs to handle changes to search results and filters.
- Branch staff. Staff need to verify that patrons can still find and reserve books.
Change how overdue notices are sent
- Loan system. Loan due dates trigger the reminder schedule.
- Notification service. The service sends reminders using each reader’s delivery preferences.
- Support desk. Staff need a way to explain missing or duplicate notices.
Retire a branch pickup location
- Reservation system. New holds must exclude that branch.
- Existing reservations. Open holds need an alternate pickup location.
- Branch staff. Staff need to coordinate transfers and notify affected readers.
